Skip to content

fix: Change translation domain name for bundle translation and add an example #20797

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2025
Merged

fix: Change translation domain name for bundle translation and add an example #20797

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion bundles/best_practices.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -397,10 +397,14 @@ Translation Files
-----------------

If a bundle provides message translations, they must be defined in the XLIFF
format; the domain should be named after the bundle name (``acme_blog``).
format; the domain should be named after the bundle name (``AcmeBlog``).

A bundle must not override existing messages from another bundle.

The translation domain must match the translation file names. For example,
if the translation domain is ``AcmeBlog``, the English translation file name
should be ``AcmeBlog.en.xlf``.

Configuration
-------------

Expand Down