Translations

[bvanrijn]

I think it would be cool if Museeks was translatable. I can contribute a Dutch translation.

[martpie]

Hey @bvanrijn !

Translations are something we're thinking about. The main question is "where to manage these translations", it will probably be with a product like Transifex or any alternative. I would prefer not to manage them directly on the repository.

Considering the technical aspect of it, react-intl seems like the way to go.

Specs

• The translations are not managed in this Github project

Todo

• Choose a library to translate components (react-intl ?)
• Choose a service to host those translations (Transifex, Github, whatever), where translations will be maintained
• English translation first
• If it goes well, open to other languages
• Language selector component in the settings ? (+ auto-determinate OS language ?)
• Adapt the dev builds to fetch those translations or fetch them manually ?

@KeitIG Transifex is good, and powerful. I think it'll be enough for Museeks (elementary is using it by the way).

[kellertobias]

I would do the german translation, if my Ideas #146 or #143 are getting addressed (I am available after 24. Sept 2016)

[martpie]

I've update my first comment to add specs/tasks. I don't think it will be done soon anyway, because a lot of things has still to be done, and I don't really want to wait for translations to be ready at every release.

[BlueManCZ]

I don't know, if this has any update, but guy who develop Min browser, has translations done trough .json files and everybody, who can contribute, just create a copy of en-US and translate it to new language.

[martpie]

I had to use i18next recently, in combination of react-i18next, it worked perfectly, and this is probably what we will use. I do not want to implement it now though, because the UI is still changing and I do not want to wait of external contributors to do a release if a string is not translated ;)

[YurySolovyov]

I'm not sure if this approach is widely used, but I think English translation should act as baseline and other translations are "merged" (deep merge that is) into it. This way you never have a missing translations because English one is always up to date.

[igorer88]

I can help with the Spanish translation :)

[binyamin]

I can do hebrew translations