docs (docs-infra): i18n steps for subsequent changes

[daniel-sc]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Currently the documentation is missing a section on how to update translations for subsequent changes to an existing application.

Issue Number: N/A

What is the new behavior?

Added a section describing steps for text changes after the first i18n extraction.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[dgp1130]

Hi @daniel-sc, I think the previous section mentions repeating the process for new translations so I don't think we need a new section for this (admittedly the existing content could be a little clearer). We also don't typically recommend specific non-official tools on angular.io, and I don't think either of those should be necessary to work with translations (even if they might help). Is there a specific aspect of the i18n process where you were confused or struggling which we can improve in the docs here?

[daniel-sc]

Hi @dgp1130 thanks for your feedback!

Disclosure: I'm the author of one of the referenced tools https://github.com/daniel-sc/ng-extract-i18n-merge (should have included this in the original description..)

I'll try to give some reasons, why I think the addition would add value to angular i18n users:

1. As far as I can see there is no description for the process of updating an app with existing translations. (I think you referred to "7. Repeat the above steps for each language you want to add to your application.", which relates to adding new languages and not to updates?)
2. Many users are confused how to update the translations and many blogs etc. reference the unmaintained tool https://github.com/martinroob/ngx-i18nsupport - by including this in the official documentation this confusion could be resolved. See e.g.
   • https://stackoverflow.com/a/49676561/2544163 or
   • https://stackoverflow.com/questions/71775495/update-merge-i18n-translation-files-in-angular or
   • https://medium.com/dailyjs/maintaining-multi-language-angular-applications-26b74df8d085 or
   • https://ctoonfreetime.blogspot.com/2021/04/create-and-deploy-multi-language-i18n.html or
   • https://javaeeblog.wordpress.com/2019/01/04/angular-i18n/

But of course it is your decision if this is the right place for this!

[dgp1130]

Let's discuss more in angular/angular-cli#23428. If we need to modify documentation as part of that, we can revisit this suggestion.

[angular-automatic-lock-bot]

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.}