Alan Cox wrote: > O> Actually, I disagree. English *is* the second language learned in >> school for most European developers (except, obviously, the ones from >> the British isles), and we don't have that problem. > > Not all those from the British Isles. A first language an English as > school language is not that uncommon for segments of the population, and > in Wales schooling may also be such that English is learned as a first > foreign language. > > That aside, please remember that Europe as a whole is a small place on the > bigger world stage. The total volume of potential developers in the huge > and rapidly modernising nations like India and China is vast, and there > are large highly skilled technical nations that don't teach English to > everyone technical by default. > > Key documents in other languages is a big help, especially those about > values, culture and standards because they are things that are not easy > to understand if your use of English is technically oriented. No doubt. My point was merely that the closer to the core of development, the less translated documents help as the emphasis on interaction *has* to increase. In that sense, a translation of "Linux Kernel Internals" and the other books written on the Linux kernel is more useful. That doesn't mean, of course, that there isn't documentation distributed with the kernel that is intended for users and therefore more useful in translation. However, I do feel that trying to keep up-to-date translations of design documentation is at least to some degree a fool's errand, which ends up having people rely on incomplete and outdated documentation, and cut them off from the overall community. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html