Add translation infrastructure

impfen / apps-inoeg

Kiebitz Web Applications (for users, providers and mediators). Still a work-in-progress, use with care!

https://kiebitz.eu/

GNU Affero General Public License v3.0

0 stars 5 forks source link

Add translation infrastructure #7

Closed topialla closed 2 years ago

topialla commented 2 years ago

[x] Setup poeditor and connect to repo
[ ] find out how outputs etc can work, poe seems to create one file per translation
[ ] check if weblate works differently

benbender commented 2 years ago

This won't be that easy as the existing i18n-infrastructure in the frontend-code is custom and uses no real, common standard. Its current translation-files are simple yaml-files and not gettext or similar...

adewes commented 2 years ago

Which format do you require @topialla? We can write a script that converts to/from that format so that Weblate or another tool can work with the code base.

benbender commented 2 years ago

The format for poedit is .po/gettext . I would like to switch to https://lingui.js.org/ in mid-terms for the frontend.

The main benefits from my POV: we don't have to maintain the code, relative small foot-print, great tooling for extracting i18n-strings directly from code, lower global dependencies, better support in external tooling.