Generating and managing the translations files for large scale applications like ERP etc is very cumbersome.
- Lingua principale
- TypeScript
- Stelle
- 27k
- Fork
- 11.8k
- Merge medio
- 14h 23m
- PR unite (30g)
- 162
Descrizione
# 🚀 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.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia esaminando il workflow di internazionalizzazione di Angular CLI che genera messages.xlf e l’alternativa ngx-Translate menzionata. Definisci l’ambito previsto per i file a livello di modulo o componente rispetto agli aggiornamenti automatici delle locale; il lavoro sarà considerato completato quando sarà richiesta una modalità specificata e manutenibile per generare o sincronizzare nuove trans-units tra i file di locale.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- angular, typescript
- Ambito
- internationalization, tooling
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100