Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup i18n with Crowdin #185

Closed
3 tasks done
nathanaelhoun opened this issue May 21, 2022 · 3 comments · Fixed by #133
Closed
3 tasks done

Setup i18n with Crowdin #185

nathanaelhoun opened this issue May 21, 2022 · 3 comments · Fixed by #133

Comments

@nathanaelhoun
Copy link
Contributor

nathanaelhoun commented May 21, 2022

The setup is a bit strange for i18n at the moment:

  • The code languages listed in src/i18n/locales are not consistent: some are two characters locales code like fr.json, other are regionalized locale codes like zh-HANT.json or en-US.json
  • The languages listed here in src/i18n/languages.ts (availables to the users) doesn't correspond to the languages listed in Crowdin, nor to the files present in the src/i18n/locales/ folder. For instance:
    • zh-HANT is meant to be Chinese Traditional according to some sources, but it's mapped to Chinese Simplified on Crowdin.
    • "Nederlands" is marked in the UI, but it is "Dutch" on Crowdin. expected as we write the native language names in the UI
    • Vietnamese is translated to 90% but is not available to the users. (fixed by fix: existing locales in crowdin #562)

We have decided to not hold the 6.0.0 release for this, as the current translations are working. But this will be fixed before allowing translations again through Crowdin.

If you see some strings that need to be fixed before 6.0.0, please report them below this issue.

@nathanaelhoun nathanaelhoun changed the title setup i18n with crowdin bot (see separate issue) Setup i18n with Crowdin May 21, 2022
@comradekingu
Copy link

Some locales actually use country-specific codes.
However, your locale problem will not improve with Crowdin.
It creates non-workable alias locales, invalidating even good efforts.

Crowdin itself is a disservice to translators, as it is not possible to see more languages and draw from them, things get held up in voting, and large arrays of strings can't be browsed at once.
This makes for incomplete and inconsistent translations, at best reaching coverage by way of multiple translators having less oversight.

The "privacy" policy, has (among other things)

behaviourally targeted advertising cookies - These cookies are used to deliver adverts more relevant to you and your interests. They are also used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaigns. They are usually placed by advertising networks with the website operator’s permission. They remember that you have visited a website and this information is shared with other organisations such as advertisers. Quite often targeting or advertising cookies will be linked to site functionality provided by the other organisation.

@pepper3k
Copy link

pepper3k commented Jun 8, 2022

@comradekingu Sounds to me like a good time to ditch this platform

@comradekingu
Copy link

comradekingu commented Jun 8, 2022

@eitanprezes Weblate is as viable as its differentiation from other platforms.
Happy to help set up shop and help out on https://weblate.bubu1.eu/ or https://hosted.weblate.org/hosting/ if you drop the CoC in name and content (in favour of something like https://github.com/WeblateOrg/weblate/blob/main/CONTACT.md ).
As you can see I am an outside Weblate contributor and user.

Edit: Outside of https://docs.weblate.org/en/latest/formats.html?highlight=supported%20formats#translation-types-capabilities
the setup needs to be pointed to the stringbase files in what isn't the most polished workflow.
Don't know if they are shared between Win and macOS or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants