Generating and managing the translations files for large scale applications like ERP etc is very cumbersome.
- Lenguaje dominante
- TypeScript
- Estrellas
- 27k
- Forks
- 11.8k
- Merge medio
- 14 h 23 min
- PR fusionados (30 d)
- 162
Descripción
# 🚀 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.
Guía de contribución
Línea de trabajo
Comienza revisando el flujo de trabajo de internacionalización de Angular CLI que genera messages.xlf y la alternativa ngx-Translate mencionada. Define el alcance previsto para los archivos a nivel de módulo o componente frente a las actualizaciones automáticas de locale; se considerará terminado cuando se requiera una forma especificada y mantenible de generar o sincronizar nuevas trans-units entre los archivos de locale.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- internationalization, tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100