Skip to content
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.

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

i18n - implement translation file merging #18276

Closed
4 tasks done
petebacondarwin opened this issue Jul 16, 2020 · 1 comment · Fixed by #18508
Closed
4 tasks done

i18n - implement translation file merging #18276

petebacondarwin opened this issue Jul 16, 2020 · 1 comment · Fixed by #18508

Comments

@petebacondarwin
Copy link
Contributor

🚀 Feature request

Command

  • build
  • serve
  • test
  • e2e

Description

Implement a feature to load up multiple specified translation files for a locale and merge the messages when generating translated copies of the project.
This was implemented in the standalone localize-translate tool in @angular/localize in angular/angular#36792

@ngbot ngbot bot added this to the Backlog milestone Jul 17, 2020
clydin added a commit to clydin/angular-cli that referenced this issue Aug 12, 2020
…es per locale

This change implements the capability to specify multiple translation files per locale. The specified translation files for each locale will be merged prior to localization. The Angular configuration file has been updated to allow for both a single string or an array of strings when specifying the translations for each locale. If the same message identifier is present in multiple translation files, a warning will currently be issued and the last file with the duplicate message identifier will take precedence.

Closes angular#18276
clydin added a commit to clydin/angular-cli that referenced this issue Aug 12, 2020
…es per locale

This change implements the capability to specify multiple translation files per locale. The specified translation files for each locale will be merged prior to localization. The Angular configuration file has been updated to allow for both a single path string or an array of path strings when specifying the translations for each locale. If the same message identifier is present in multiple translation files, a warning will currently be issued and the last file with the duplicate message identifier will take precedence.

Closes angular#18276
alan-agius4 pushed a commit that referenced this issue Aug 13, 2020
…es per locale

This change implements the capability to specify multiple translation files per locale. The specified translation files for each locale will be merged prior to localization. The Angular configuration file has been updated to allow for both a single path string or an array of path strings when specifying the translations for each locale. If the same message identifier is present in multiple translation files, a warning will currently be issued and the last file with the duplicate message identifier will take precedence.

Closes #18276
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants