eloquence
Regarding Localization
I badly want to start writing reviews in my native language which is Tamil (ta) and I see that only languages of those interface translation is completed 25% and above are pulled and enabled in the platform according to the project in TranslateWiki. Is that right?
If yes, as of today, Tamil language translation is above 25% complete, will it be enabled any time soon?
Also I believe, tying interface language to review language is a bad choice. A user may want to use the platform interface in English, for example, but may choose a language of choice for their review. A simple language selection for review can be added to the form in the create review screen instead of enforcing the interface also to be in that language.
Hey @PrasannaVenkadesh, thanks a lot for working on the Tamil translation. The TranslateWiki page describes the threshold for committing a language to version control. To date we've only enabled languages once they're fully translated, per this FAQ entry: https://lib.reviews/faq#language
Honestly, in general I think that's a good policy to avoid situations where users attempt to use the site in their language but find themselves randomly encountering English strings all over the place. That could be very frustrating for users who are not multilingual/bilingual. So I do think for the user interface I would want to keep it at 100% before we enable a language to change the UI.
That said, I fully agree with you that we should decouple UI language from content language. I see no reason why we shouldn't enable additional content languages for bilingual speakers, even if no full translation of the UI exists yet.
