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

German translation #26

Closed
franzdumfart opened this issue Oct 22, 2011 · 4 comments
Closed

German translation #26

franzdumfart opened this issue Oct 22, 2011 · 4 comments

Comments

@franzdumfart
Copy link

Howdy guys,

is there any interest in a german translations of the project? web-learn-jquery-com is very useful, why not spread it broader?
If there is any interest in another language of the project, i will try to write down the german version (maybe in the cold months of this year) :-)

regards from austria,
samuel

@addyosmani
Copy link
Member

Hey Samuel,

I think that internationalization is definitely something we would be interested in. It really depends on a) whether we currently support a way of easily switching to a different language and b) if not, how we might enable adding content in other languages in a way that makes it manageable in the future.

I'll defer to @ajpiano with respect to the tech side of this as he may have some insights into how our current setup may be able to facilitate this.

Cheers and thanks for the offer,
Addy

@herberthamaral
Copy link

Hi Addy,

When this book was being written by Rebecca (I was the pt-BR translator), we came up with some solutions for this problem. We've tried:

1 - Translations on other branches, english on master (too many branches to keep track - quite hard to manage).
2 - Translations on other repositories, referenced on the official repo as git submodules (it is bad for translations once it does not have the complete code base).
3 - Translations on other repositories, with no relation with the official repo, just a link on readme pointing the official translation repo to that lang (best so far).

What do you guys think?

@addyosmani
Copy link
Member

Hi @herberthamaral,

Thanks for your thoughts on this.

In my opinion, option 3 probably works the best here. That said, I think there are some addition concerns worth considering as jQuery Fundamentals has been bequeathed to the jQuery project for future maintenance. Out of the box this repo (rather, the version of this repo currently in branch, but will makes it's way to master) has been setup to output a version of the official jQuery learning site. The content is likely to (at some level) self-reference this fact.

Any person or group that wanted to fork the repo and work on a translation (which they are of course free to) might run into some trouble with how exactly to deliver the content. e.g as it isn't on a jQuery domain, would the translated version have to deliver the content differently or with a different site name? Would we simply expect people to read through the repo rather than having it hosted somewhere? or would some sort of agreement be worked out where the translated version could be posted to learn.jquery.com/fr/ for example pending a review by a team member?

I guess the concerns I have are avoiding confusion for translators and users. The jQuery project would probably also like to avoid an issue where say, a translator has pushed a copy of jQuery property (learn.jquery.com) to www.theirdomain.com/learningsite/french when it might be controlled by someone else who adds adverts to it etc.

What I think would be useful for us to do is keep this issue open until we have a chance to have a broader discussion about the best way to solve it. A call (once we've stabilized the English content and launched that site) may offer a chance for a cleaner solution. Given that so much of the content is in flux at the moment, I feel this might be the best course of action.

CC'ing @ajpiano in case he has more thoughts on this.

Cheers!

@scottgonzalez
Copy link
Member

The site content is MIT, so the community is free to translate it on their own, but we don't have the infrastructure or time to help with such an effort. Anyone interested in doing translations can certainly ping us on GitHub or IRC with ideas, questions, concerns, etc.

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