Hi Tyrael, No problem! To recruit people I ask them to join the mailing list and read the Howto. Here you have the link, sorry it is not in English. http://svn.php.net/repository/phpdoc/es/trunk/guia.odt (Open Office). Google translate may help you to understand more or less what I'm saying.
I don't split up the pages for translation, anyone can translate all the files they want. I just recommend them to do some research and make sure all the most common functions they use are translated. For example array and string manipulations, database connections, etc. I do review the files they translate but only the first files and I make sure they are doing a good job. After they get approved I ask them to get an SVN account and then it is their responsibility. Yes we have an small dictionary that is required to read and contribute so everyone uses the same words for translation: http://svn.php.net/repository/phpdoc/es/trunk/diccionario.txt. Keeping the translators interested is the hardest part. You need to follow up with the project, consistency is the key. Always Be ready to help them out, and be an example and contribute as much as you can. Make sure there are no errors in the build. And thank them for all the hard work. Hi Yago. > > Thanks for the heads up. > Could you share your HOWTO(if it's available in english), and I would be > curious how did you managed the the translation process. > I have some ideas, but I would appreciate any of your past experiences. > So for example how do you recruit people, how do you split up the pages for > translation, how do you review/merge the changes, I think you have some wiki > for the common language (I mean there are some frequently used words, and > you have to translate that consistently), how do you keep the contributors > interested, etc. > > Tyrael > -- Yago Ferrer
