Localicious inzetten voor vertalingen

[phavekes]

This issue is imported from pivotal

Voor de apps gebruiken we Localicious om de vertalingen in sync te houden tussen de ios en android versie. Vanuit 1 yaml file worden verschillende formaten vertalingsbestand gegenereerd. We willen deze zelfde bron inzetten voor de vertalingen in de eduID frontend; zowel login als account.

The migrated code is in the feature branch https://github.com/OpenConext/OpenConext-myconext/tree/feature/localicious-546 with the corresponding PR #642. The following tasks are necessary before this story is done:

• Implement new version of I18n which is backwards compatible
• Ensure all translations are present in https://github.com/OpenConext/OpenConext-myconext/blob/feature/localicious-546/localizations.yaml
• Change all occurrences of I18n.t( to use the new key generated in the JS translations: https://github.com/OpenConext/OpenConext-myconext/tree/feature/localicious-546/account-gui/src/locale/js
• Add task to the github actions to re-generate the translations if the source has changed (See https://github.com/OpenConext/OpenConext-myconext/blob/feature/localicious-546/README.md?plain=1#L93)
• Add task to the github actions to copy the source translations to the mobile repo's if changed (3f5e2e2)

For more background information:

• https://jobs.picnic.app/en/blogs/localizing-native-apps-made-easy-with-localicious
• https://github.com/PicnicSupermarket/localicious

[phavekes]

Voor de twee apps (Android/IOS) wordt het gedeelde vertaalbestand localizations.yaml met github-actions in sync gehouden.

Voorbeeld om dit bestand in js om te zetten:

wget https://raw.githubusercontent.com/Tiqr/eduid-app-android/develop/localizations.yaml
localicious render localizations.yaml ./ --languages en,nl --outputTypes js -c SHARED

(Peter Havekes - Sep 6, 2024)