Reorganize i18n
The same or similar expressions and phrases appear under different keys (files) making it difficult to consistently translate to other languages. This ticket is to reorganize i18n files and keys to enable easier translation.
-
client:model
namespace needs to contain labels and hints directly linked to the data model. In UI these keys are preferred for form fields, labels, etc. -
translations
namespace is the default namespace for i18n of UI components. UI components should useclient:model
whenever referring to the data model.
Originally the translations.json
files were not detected at folder depths more than 2, but we can now place them deeper in the source code tree, making it easier to identify the translation keys and use them consistently.
The changes will be made in several steps (merge requests):
- Clean up
client:model
and move model texts from other namespaces to the correspondingmodel/.../translations.json
. Update UI to always refer toclient:model
. - Break up large
translation.json
into correspondingsubfolder/translation.json
files.