Add translation information for triggers and conditions

[joostlek]

Proposed change

Add translation information for triggers and conditions

Type of change

• Document existing features within Home Assistant
• Document new or changing features for which there is an existing pull request elsewhere
• Spelling or grammatical corrections, or rewording for improved clarity
• Editing or restructuring documentation guidelines
• Changes to the backend of this documentation
• Remove stale or deprecated documentation

Checklist

• I have read and followed the documentation guidelines.
• I have verified that my changes render correctly in the documentation.

Additional information

• This PR fixes or closes issue: fixes #
• Link to relevant existing code or pull request:

Summary by CodeRabbit

• Documentation
  • Expanded localization documentation with new guidance for additional translation categories.
  • Added coverage for translating trigger and condition strings, including example structures and usage notes.
  • Clarified how selectors should reference the appropriate translation keys for trigger and condition fields.

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

📝 Walkthrough

Walkthrough

This PR updates the internationalization documentation to add table entries for conditions and triggers translation categories, and introduces new documentation sections describing the localization structure, JSON examples, and translation_key usage for trigger and condition definitions.

Changes

Localization documentation update

Layer / File(s)	Summary
Trigger and condition localization docs docs/internationalization/core.md	Adds conditions and triggers rows to the translation category table, plus new sections documenting per-key structure, JSON examples, and translation_key selector references for triggers.yaml/conditions.yaml.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Related PRs: None identified.

Suggested labels: documentation

Suggested reviewers: None identified.

🐰 Poem

A rabbit hops through docs anew,
With triggers, conditions in full view,
Tables gain a fresh new row,
JSON keys begin to show,
Translation strings, now clearer too! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the documentation update for triggers and conditions.
Description check	✅ Passed	The description follows the template and covers the proposed change and type of change, with only minor fields left blank.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}