Generating and managing the translations files for large scale applications like ERP etc is very cumbersome.

# 🚀 feature request.
Generating and managing the translations files for large scale applications like ERP etc is very cumbersome.

### Relevant Package

This feature request is for @angular/....

### Description
Using the angular's builtin translation which the angular platform provides, managing and generating the translation files for multiple locale is very cumbersome , error prone and very difficult to manage as the application size scales, as generating the translation files after adding new i18n tags , generates the a default file *messages.xlf* and it becomes very difficult to dig into this default file (because of size .. lines of code.) and parse out the new trans-units and then move them to each locale files manually , and paste the target tag for the new trans-units .

### Describe the solution you'd like
Either the translation file should be provided for each module or component level, or there must be some version control system used to check the differences/changes in the default messages.xlf file and these changes automatically being added to other locale files . Means atleast the new trans-units must be appended automatically to the locale files that the intended developer needs to create.

### Describe alternatives you've considered
We have gone through ngx-Translate etc tools that provides run-time translation using pipes, but if the angular's builtin internalization module provides additional updates in near future to ease the internationalization process for developers , its far better than other third party packages.

まず、messages.xlf を生成する Angular CLI の国際化ワークフローと、言及されている ngx-Translate の代替案を確認します。モジュール単位またはコンポーネント単位のファイルと、自動的な locale の更新について、想定する範囲を定義します。完了条件は、locale ファイル間で新しい trans-units を生成または同期するための、明確に指定された保守可能な方法が必要になることです。

索引モデルが issue の本文から書いたものです。