Closed topialla closed 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...
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.
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.