search

getify / You-Dont-Know-JS

A book series on JavaScript. @YDKJS on twitter.
Other
179.37k stars 33.48k forks source link

Is the open parts of book welcome translate to other language like chinese? #9

Closed yuanyan closed 10 years ago

getify commented 10 years ago

Thank you for your question. I will research and get back to you with a definitive answer when I can.

getify commented 10 years ago

I promised a "definitive answer" and I do not have one yet. However, let me add some additional thoughts:

  1. I initially thought, "sure, this is OSS, go for it". But then, I thought, "well, O'Reilly is going to license official translations of the published works". If I authorize translations of the drafts, does that dilute or prohibit O'Reilly's rights to do so? Probably not, but not positive.
  2. A translation appears to indeed be considered, under US copyright law, a "derivative work", according to this article anyway.

  3. This content is licensed under: Creative Commons CC BY-NC-ND 3.0. http://creativecommons.org/licenses/by-nc-nd/3.0/

    ...which does indeed prohibit derivative works, unless the copyright holder (me) grants specific permission.

  4. If I were going to authorize such, it would certainly be that I required the translations to be submitted back to this repo, and not to be distributed through any other channel besides this repo.
  5. Right now, it appears I need to consult with O'Reilly before I can give any official yay or nay.
yuanyan commented 10 years ago

Got it, thank you very much for the answer.

cirocosta commented 10 years ago

Any updates for this? I'd really enjoy contributing for a pt-BR translation as i'm liking a bunch the content that is being produced.

getify commented 10 years ago

I don't have any updates on that as the contract stuff is still being worked out. But I will update here once I have an answer in any direction. :)

getify commented 10 years ago

OK, I finally have a more official answer from O'Reilly.

The content is released here under a "CC-NC-ND" license, which means it cannot be used in a commercial way, nor can derivative works be made (unless otherwise excepted). A foreign translation is a "derivative work" and thus would not be allowed outright.

However, I can grant specific permission for people to translate the material from this repo into a foreign language. I am willing to do so, on a case-by-case basis, provided the content is not changed, is not used commercially (for sale), and is given back to this public repo. So, please email me (getify on gmail) and we will work that out. :)

On the other hand, if you'd like to make a commercial translation of the fully published work, you would contact O'Reilly and request to purchase the license to do so from them.

Hope that clears everything up! :)

dandv commented 9 years ago

@cirocosta, @yuanyan: please consider the downsides and long-term detrimental effects before translating into languages other than English.

cirocosta commented 9 years ago

@dandv thanks for linking this! That article from Jeff Atwood you referenced is great. I've actually changed my mind between the day i added that comment here and today :smiley:

dandv commented 9 years ago

@cirocosta: :+1: Good to see wisdom. See also my final sentence here :)

ceoaliongroo commented 8 years ago

Hi @getify, for me the idea is not clear.

You want and could do access to this github repository, to do the translation?

getify commented 8 years ago

If you want to do a foreign language translation for free, do so by forking this repo, making all your changes publicly to that repo, then making a PR back here to this repo.

ceoaliongroo commented 8 years ago

Great! thanks for the answer.

kosson commented 8 years ago

@dandv Sometimes there are facets very difficult cu comprehend, and the best thing to have at hand is some documentation in your own language. That is establishing a context for a quicker apprehension of some red hearing topics. I was bit by the bug of translating YDKJS in our own language... still contemplating. P.S. Baby steps is always best in your mother tongue.

dandv commented 8 years ago

Salut Nicule,

What facets if I may ask? This is software development, not German philosophy with untranslatable words. The keywords are in English. Most docs are in English. By translating into other languages, you're not only wasting your time but depriving others of good motivation to learn English.

On Sat, Jan 30, 2016, 08:26 Nicolaie Constantinescu < notifications@github.com> wrote:

@dandv https://github.com/dandv Sometimes there are facets very difficult cu comprehend, and the best thing to have at hand is some documentation in your own language. That is establishing a context for a quicker apprehension of some red hearing topics. I was bit by the bug of translating YDKJS in our own language... still contemplating.

— Reply to this email directly or view it on GitHub https://github.com/getify/You-Dont-Know-JS/issues/9#issuecomment-177228241 .

kosson commented 8 years ago

Salut, I refer to facets to the many aspects a particular topic would present to the one learning the language. I agree with the full involvement with the learning materials in English, but on the other hand I have some experience with those people who would find it faster if a tough to crack concept would be presented in their own language. I have some experience with evangelizing Open Educational Resources in Romania, and this particular supplementary aid was raised many times. This is the reason I've started the following repo: JavaScript, învăț eu, înveți și tu

hectorip commented 6 years ago

Salut Nicule,

What facets if I may ask? This is software development, not German philosophy with untranslatable words. The keywords are in English. Most docs are in English. By translating into other languages, you're not only wasting your time but depriving others of good motivation to learn English.

On Sat, Jan 30, 2016, 08:26 Nicolaie Constantinescu < notifications@github.com> wrote:

@dandv https://github.com/dandv Sometimes there are facets very difficult cu comprehend, and the best thing to have at hand is some documentation in your own language. That is establishing a context for a quicker apprehension of some red hearing topics. I was bit by the bug of translating YDKJS in our own language... still contemplating. — Reply to this email directly or view it on GitHub #9 (comment) .

That is a very short-sighted point of view. I agree that every decent developer should learn an even code in English, but sometimes, there are developers that are struggling enough to learn the basics of something like JS (and don't know English) to add more to their burden, forcing them to study a language they don't know at the same time they are trying to study and learn a programming language.

dandv commented 6 years ago

Perhaps they should focus on learning one thing at a time.