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

Translations of exercise instructions #203

Closed
suchja opened this issue Nov 4, 2017 · 9 comments
Closed

Translations of exercise instructions #203

suchja opened this issue Nov 4, 2017 · 9 comments

Comments

@suchja
Copy link

suchja commented Nov 4, 2017

Probably there is somewhere a project wide decision, but I was not able to find it. So I would like to know whether there is any idea of translating existing exercise documentation to languages like german, spanish, ...

I‘m a online teacher and found that it is, especially for beginners, much easier to have exercises in their native language.

Obviously the translation will add additional complexity to the project which might not be good for maintenance.

Curious to hear your thoughts.

@ilya-khadykin
Copy link

It will require a lot of work, especially considering the planned release of Exercism 2.0. But it's definitely possible. I guess this should be a community effort in any case.

Personally, I'm against this idea because English is an international language, and a good software developer should learn it at some point. It should happen sooner rather than later. But this is just my opinion and it doesn't reflect Exercism philosophy.

@NobbZ
Copy link
Member

NobbZ commented Nov 4, 2017

Personally I avoid German stuff in the programming world, unless it is really about core things that haven't changed in the last 40 years... About 90% of the programming related content I consumed in my early days was at least a major release behind. This changed my thinking about translations.

@katrinleinweber
Copy link

Have you tried automatic translations? I translated teaching material, release notes, help pages etc. for software every now and then until recently, but this seems to be an obsolete skill soon. @NobbZ's advice vs. the benefits of learning in your native language might find its synthesis in machine translation.

I piped the R exercise subtitles into deepl.com/translator just now and found them pretty good.

@wolf99
Copy link

wolf99 commented Nov 4, 2017

Providing Exercism 2.0 allows for it, CrowdIn could be used to offload some localisation effort - it's free for open source projects and is integrated with GitHub https://github.com/marketplace/crowdin.

OneSky seems moderately popular either

@suchja
Copy link
Author

suchja commented Nov 4, 2017 via email

@NobbZ
Copy link
Member

NobbZ commented Nov 4, 2017

Independent of the language of the exercise itself, we can't guarantee to have mentors speaking that localized language. So right after having implemented "Hallo, Welt" exercise, I'm confronted with a person that only speaks english… Or another language that is even more greek to me…

Be honest right from the start, the language of the service is english, nothing else.

@suchja
Copy link
Author

suchja commented Nov 5, 2017

@NobbZ that’s the killer argument. I only thought about the exercises itself, but that‘s (now also to me obvious) only the first step.

Thank‘s for all the suggestions. I‘ll have a look into automatic translation and haven‘t even heard about CrowdIn and the other stuff. So a lot to learn from this conversation.

Thank you again and I’m impressed how alive this project/community is.

@katrinleinweber
Copy link

About the "killer argument": we could make it clear that only the "self-service" parts of the website will be translated. That could prevent mentoring problems and even highlight what @NobbZ argued initially: you can't get around English. Maybe for the entry, but not for long.

@kytrinyx
Copy link
Member

kytrinyx commented Aug 3, 2018

The question about translations comes up on a regular basis, and for now we've decided that we aren't going to invest in it (for all the reasons that are mentioned above), even though there are very good arguments for investing in it (also mentioned above)!

I'm going to close this, as we're not planning on implementing it in the near term.

@kytrinyx kytrinyx closed this as completed Aug 3, 2018
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

No branches or pull requests

6 participants