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

Support multiple languages (i18n) #492

Open
nicksellen opened this Issue Apr 13, 2017 · 13 comments

Comments

6 participants
@nicksellen
Copy link
Member

nicksellen commented Apr 13, 2017

Might get a lot more support if people can use the site in their native language.

angular-translate is a great, mature library for angularjs.

For managing the translations I just started trialling crowdin for a blog. Seems great! And they are into open source [1].

Another option is Transifex which we use for foodsaving.world - see our dashboard. But they have gone a bit cold on open source projects (there used to be a whole page on their website [2]), but now just a bit on the pricing page, and a few more criteria than just open source:

We offer Transifex for free to Open Source projects that have no funding, revenue, and/or commercialization model.

[1] https://crowdin.com/page/open-source-project-setup-request
[2] https://www.transifex.com/customers/open-source/

@nicksellen

This comment has been minimized.

Copy link
Member

nicksellen commented Apr 13, 2017

Crowdin has direct github integration (creates PRs for you), for transifex you use a cli tool to push/pull translation files (or run an integration thing yourself on a server - much more cumbersome).

@simison

This comment has been minimized.

Copy link
Member

simison commented Apr 13, 2017

Thanks, the basics of i18n setup is pretty straightforward indeed but it causes quite a lot of extra work down the road and extra work at this point is what we really need to avoid. :-)

Frankly it doesn't really bring important numbers (reply rates + member count) up so this won't be a priority at this point, but definitely something in the future! First we need to get usage stats into healthy basis.

@simison

This comment has been minimized.

Copy link
Member

simison commented Apr 13, 2017

(Just writing these down for later)

Usable stats to study for decision making regarding i18n:

  • hitchwiki translation stats (translations had low impact / usage)
  • BeWelcome language stats
  • Browser languages
@kalpaitch

This comment has been minimized.

Copy link

kalpaitch commented Apr 13, 2017

Adding another :)

@nicksellen

This comment has been minimized.

Copy link
Member

nicksellen commented Apr 13, 2017

a lot of extra work down the road

For who? Translators themselves probably exist in the community, it's a great thing that non-developers can contribute.

Frankly it doesn't really bring important numbers (reply rates + member count) up

You suspect it won't, but of course you need to measure to know :p

The BeWelcome stats show most users are using it in countries where English is not the national language.

The stats can only show the current and past behaviour, not what would happen if translations were in place.

@simison

This comment has been minimized.

Copy link
Member

simison commented Apr 13, 2017

a lot of extra work down the road
For who? Translators themselves probably exist in the community, it's a great thing that non-developers can contribute.

For anyone managing the volunteering. Crowdsourced translations need replying a lot of emails, instructing people, giving notices when new features/string changes are pushed out, as well taking into account languages in design process (ltr/rtl, different widths).

That was my experience with several big crowdsourced i18n projects. Probably lots of things to do different for whole process go smoother (or just finding someone to deal with that all).

My thinking goes more along the line that same amount of effort put to something else makes bigger impact, like references.

I like i18n and love to see projects like this translated to crazy languages, we'll do it eventually for sure. Also as far as feature requests we see in the feedback, i18n comes up quite rarely. References and something to do at the site if you're not hosting are mentioned frequently in feedback.

The stats can only show the current and past behaviour, not what would happen if translations were in place.

I think the most feasible mvp to gather some data would be to translate just the landing page.

Thanks for brainstorming next features! It's great.

@nicksellen

This comment has been minimized.

Copy link
Member

nicksellen commented Apr 13, 2017

For anyone managing the volunteering

Thats what crowdin does :) And can ignore rtl languages for some time I think...

same amount of effort put to something else makes bigger impact, like references

That assumes developers are generic resources to be deployed anywhere on the project. It might be quite feasible to get a new contributor who joins specifically to add translation support as it's understandable, and self contained kind of task (experience: doing a talk about https://foodsharing.de at a meetup and having someone come up afterwards offering to translate it).

Could be a notable PR push too ("trustroots launches in Germany|France", etc...).

I'm not proposing doing any of those things though, so it can sit here until someone is :)

@simison

This comment has been minimized.

Copy link
Member

simison commented Apr 13, 2017

That assumes developers are generic resources to be deployed anywhere on the project. It might be quite feasible to get a new contributor who joins specifically to add translation support as it's understandable

That's true, tho we should try to get everyone work towards one vision and not implement stuff just because someone absolutely wants to implement it. ;-) That path leads to bloat.

@simison simison changed the title Support multiple languages Support multiple languages (i18n) Apr 13, 2017

@simison simison added the AngularJS label Apr 21, 2017

@simison simison removed the easy label Jun 14, 2018

@simison simison added the framework label Nov 3, 2018

@simison simison added this to To do in Framework refactor via automation Nov 3, 2018

@guaka guaka removed the [Priority] Low label Nov 24, 2018

@guaka

This comment has been minimized.

Copy link
Member

guaka commented Nov 24, 2018

I removed [Priority] Low - I feel accommodating people who don't speak English is very important for growth (plus helping with translation is a great way to participate for people who want to help grow Trustroots)

@mrkvon

This comment has been minimized.

Copy link
Member

mrkvon commented Dec 3, 2018

Recent discussions on slack and forum suggest that this will be implemented during the migration to react.

Also on forum.

So far I've seen libraries react-i18next and react-intl. Anybody has an experience with any of these?

The latter seems to be more popular (github stars and npm weekly downloads), but the former one is close behind.

@mrkvon mrkvon referenced this issue Dec 6, 2018

Merged

Internationalization (i18n) with react-i18next #921

1 of 2 tasks complete

@guaka guaka added i18n and removed i18n labels Dec 7, 2018

@mrkvon mrkvon closed this in #921 Dec 13, 2018

Framework refactor automation moved this from To do to Done Dec 13, 2018

@mrkvon

This comment has been minimized.

Copy link
Member

mrkvon commented Dec 19, 2018

Seems to me that this is still far from being resolved. I'm reopening until we write followup issues.

  • Translation tools and environment
  • UI
  • Getting volunteers to translate
  • ...

@mrkvon mrkvon reopened this Dec 19, 2018

Framework refactor automation moved this from Done to To do Dec 19, 2018

@nicksellen

This comment has been minimized.

Copy link
Member

nicksellen commented Dec 23, 2018

Maybe the points on yunity/karrot-frontend#1118 are useful to consider.

@mrkvon mrkvon moved this from To do to In progress in Framework refactor Dec 28, 2018

@comradekingu

This comment has been minimized.

Copy link

comradekingu commented Jan 12, 2019

@nicksellen I find Crowdin to be a subpar tool, allowing no quick interface to see the relation between prior strings and their translation. Also taking away from its appeal is that it is closed source. That speaks volumes in terms of preference, or hypocrisy. I would suggest using Hosted Weblate, which is both libre software, and gratis for other libre software. Transifex is not even worth the time of day to complain about it, speaking as someone who has used it for hours, every day since 2013, and not since they last updated their EULA/terms of use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment