Internationalization
samuelmaddock opened this issue · comments
edit: Localization is now supported. See contribution guide for localizing.
I'd love to be able to support new languages for Metastream. I've started moving strings into their own location https://github.com/samuelmaddock/metastream/tree/master/app/locale
Still need to put some thought into how language changing would affect UX. Also need to implement a way for mixing in strings as in ${username} has added "${mediaTitle}" to the queue.
Anyone have recommendations for how to coordinate the community in adding translations? It probably wouldn't be great to force them to fork the Git repo.
You probably want a translation management system. https://weblate.org/en/ seems decent and offers free hosting for open source projects, but open to other suggestions.
You could also use Crowdin (https://crowdin.com/page/open-source-project-setup-request) they also offer free coordination for OSPs and are the industry standard for computer applications. I've used it quite a lot when I was a translation manager for 3ds.guide and wiiu.guide and it was pretty straight forward
Can use Weblate. Free for open source projects.)
@orangesunny Can help set everything up
Hi all!
Nice to know that localization of Metastream is happening!
@KovalevArtem is right; I will be happy to help. I even wrote @samuelmaddock an e-mail when I found out about this nice piece of software a few weeks ago. We will be happy to host Metastream translations and help with the setup. Just let us know 😃
I also want to mention that there is a big difference between free and libre. Weblate is a libre software. ❤️
@samuelmaddock links in the issue message are not working anymore.
Hi, we simplify the way to set up the libre translation projects on the Hosted weblate. Now, every project maintainer or recognized contributor can set it by her/himself on https://hosted.weblate.org/hosting/
I am turning off my notifications here, but feel free to @ mention me with any questions. :)
Is this still not implemented, solved? This has been open since 2018 and @orangesunny has offered to help many times. Weblate in my understanding if free for open source projects in addition.
Transifex and Crowdin are two other web based translation altervative platforms for quick and easy "just get to work" as Weblate.
What's wrong? Is Metastream somehow incopatible with these type of solutions? Thanks for any clarification.
Hi everyone!
it's Andrii from Crowdin. Crowdin is free for open-source projects.
I can do a pull request with the integration setup. I would only need a green light from you and the minimal setup of this repo (create a Crowdin project and add some Actions secrets). Please tell me what type of content needed to be localized?
The integration can be completely automatic and can be done via Crowdin GH Action.
edit: Localization is now supported. See contribution guide for localizing.
I'd love to be able to support new languages for Metastream. I've started moving strings into their own location https://github.com/samuelmaddock/metastream/tree/master/app/locale
Still need to put some thought into how language changing would affect UX. Also need to implement a way for mixing in strings as in
${username} has added "${mediaTitle}" to the queue.Anyone have recommendations for how to coordinate the community in adding translations? It probably wouldn't be great to force them to fork the Git repo.
Add a new path: https://github.com/samuelmaddock/metastream/tree/master/packages/metastream-app/src/locale