Social Income
Localization & Translations #57
Replies: 7 comments
-
|
Crowdin seems an option: "It’s free for open source projects, it integrates well with GitHub, and has moderation controls for managing large translator communities." It's also used on opencollective.com in a interesting way: the official language switcher shows directly the amount of missing translations:
|
Beta Was this translation helpful? Give feedback.
-
|
Another tool mentioned by @andrashee is locize.com |
Beta Was this translation helpful? Give feedback.
-
|
Some thoughts on using our existing setup with Why would we want to use a third party tool to manage translations? Following reasons come to mind:
These features could be (with some effort and to some extend) also provided by our existing admin tool:
One challenge: if have all text strings for the website as Just saying ... any thoughts @mkue, @andrashee, @sdwivedi? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting idea! Generally, I would be an advocate of using an i8n framework for the translation. They already solved all the problems of language detection, plurals, number, currency date formatting for us. One which seems to be often used is e.g https://www.i18next.com. It also comes with a next.js specific plugin: https://github.com/i18next/next-i18next These frameworks usually support quite some different input formats for the translations. JSON, getext, po files, ... Creating for example the json files from firestore (curated through firecms) at build time of the website could be an option. I definitely wouldn't grab the individual translations from the database at serve time. I personally would still explore the dedicated services for this, rather than using firecms. Locize is the company behind the framework mentioned above, but there are quite some of them. https://localizely.com/blog/nextjs-i18n-tutorial/ is another one with good integration and free for open source. Those translation management systems are explicitly built for this. E.g one can immediately see which keys are used in the code, but are missing in the translation and the other way around. Translations which are not referenced anymore in the code. This list could be a good inspiration https://github.com/jpomykala/awesome-i18n |
Beta Was this translation helpful? Give feedback.
-
|
One more interesting link how locize is used in a next.js setup, its challenges with client and server side rendering and how to automatically sync code with the platform https://locize.com/blog/next-i18next/ |
Beta Was this translation helpful? Give feedback.
-
|
From what I can see on the flutter packages localizely seems promising, it has also OTA updates as the only one from those mentioned, and as far as I can see has also integration with most used All other have some packages as well. And even if something won't work with the flutter packages we can still try to wrap it with our own code. I haven't got strong opinion. |
Beta Was this translation helpful? Give feedback.
-
|
i8n framework already in use. |
Beta Was this translation helpful? Give feedback.
-
How can we streamline the localization of the website, communication and the mobile app?
Some further thoughts:
Beta Was this translation helpful? Give feedback.
All reactions