Back

@aral

let's ask @jibec

hello @aral you really are lucky because floss community have a great tool to handle a smooth translation workflow between devs and translators: weblate. You can self host it yourself, or be welcomes on hosted.weblate.org or other communities like Fedora, Codeberg, etc.
One thing to remember, weblate will either commit directly on your git repo or open pull requests. It means you let it handle all translation files so that your life is made easy with no conflict:)
@goofy

@aral
the real question is the file format you will use.
Documentation and website are well handled in asciidoc and then translated in gettext files using the great po4a. All translation platforms handle it well.
But translating UI or libraries, especially in javascript is challenging. Take the time to make your choice, use an existing standard well supported, and do the best with it, please do not invent a new one. Languages have a lot of traps for devs, you may want to delegate this.
@goofy

@aral
since your code is already on codeberg and that codeberg already provides weblate, what leaded you to ask this question? Any worries or issues with weblate? Or maybe you simply did not know weblate instance exists on codeberg?
@goofy

@jibec @goofy Just doing my research, like I always do ;)