Re: Re[2]: [PEAR-DEV] Translations (was Re: [PEAR-DEV] Pear Comitee)

> On 09 Jan 2002 19:47:55 +0100 > Marcel Beerta <marcel@beerta.de> wrote: > > > Because english is the most common language, i think that every > > documentation should have to be in english first. > I considerer this fact as an elite point of view :). Let the people write documentation in their native langage (if their cannot write in english), and translate in a second step will populate contributions.# Ok, i agree to this. > > This would help the translators of other languages, too. > As far as we get an english (or whatever langages) few days/weeks after the release, no prob. +1 > > I'm not very familar with french and I would translate stuff into > > german, so I had to wait for the translation of french to english, and > > then it could be translated into german which would increase the waiting > > time for the german ppl... just my 0,02$ > Currently working from good german tutorials... to frech :), next english. Just easier to translate to french in a first step :))). > > We just don t have to lost the goal, get a usefull documentation, and as soon as possible, for every langages used by php users. > > The only problem I see is the release process of pear, and the frequent updates. Maybe a release process will help to write documentations correctly and make the endusers life easier with production applications. I m always afraid to upgrade a library so often in a production system ;;)). That's a problem i see, too. When there is a new module release, the doc's have to be updated in every language. So it _could_ happen, that two people are translating the doc's in two different language-trees and finally nobody has an overview of who has updated which file in which language-tree. That's what I am a little bit afraid of. Greetings, -- Marcel "mazen" Beerta http://www.mazenphp.de | http://www.etcpasswd.de marcel@beerta.de