Replies: 3 comments
-
I think we should either use a free/cheap cloud service or weblate, since I already know how to host weblate.
Hmm, I think we could just exclude translations file from the license and consider them BSD-licensed or public domain or whatever. |
Beta Was this translation helpful? Give feedback.
-
I migrated from vue-i18n to i18next as our i18n library in this branch. |
Beta Was this translation helpful? Give feedback.
-
We set up weblate to manage translations here: https://translate.pretix.eu/engage/venueless/ |
Beta Was this translation helpful? Give feedback.
-
Currently we are translating our user interface with vue-i18n, which uses it's own file format and syntax which can only be authored directly as a text file.
If and when we are involving more collaborators to localize venueless into more languages, this might become cumbersome fast and is inaccessible for non-programmers.
I think switching to are more well known library, format and syntax like https://www.i18next.com/ would make sense.
Additionally, should we start using and offering a tool like weblate to possible localization collaborators?
And, as a smaller point, how does this work with the venueless license?
Beta Was this translation helpful? Give feedback.
All reactions