Obviously, there are various way to simplify the translations, but the base condition is having the texts separated from the logic, etc. - should it be JSON configuration files, Unix message files, resource files, etc. Considering the variety technologies in use, one common base format plus conversion tools to different native formats for the different technologies would be probably useful (e.g. the CLI would hardly use the same format of such resource files directly, but it would still benefit from the possibility of sharing some texts and their translations with the front-end, etc.).
03/15/2023, 7:16 PM
We’re very interesting in adding configurability here- there are questions to solve but would be a good topic for a community RFC