Hey Everyone,
Thanks for all the feedback so far for the Ruby translation project. I've gotten to the point where I have some content that needs translation so I can continue integration with RDoc output. I've created a GitHub repository for this purpose:
The README.markdown file (displayed at the bottom of the project page) has some basic information, and points to more in detail instructions on how to go about with translation / editing:
I know there's already volunteers for Spanish translation, but other languages are welcome as well! That's it for now. Let me know if you have any questions.
Regards,
Chris White
http://www.twitter.com/cwgem
Chris,
Thanks for this effort. It makes it easy for people to focus on the
translation effort. I'll try to add translations, but I just returned
from holidays and right now my life is a bit of a mess. What do you
recommend for someone whose free time comes in little bursts? Should I
add myself as editor, instead of the main translator of a file? Or
should I just start a document and have people edit it if I don't
finish it?
Jesus.
···
On Sun, Aug 21, 2011 at 11:18 PM, Chris White <cwprogram@live.com> wrote:
Hey Everyone,
Thanks for all the feedback so far for the Ruby translation project. I've gotten to the point where I have some content that needs translation so I can continue integration with RDoc output. I've created a GitHub repository for this purpose:
GitHub - cwgem/Ruby-Documentation-Translation-Project: Translation project for making the Ruby documentation available in other languages
The README.markdown file (displayed at the bottom of the project page) has some basic information, and points to more in detail instructions on how to go about with translation / editing:
Translation Rules · cwgem/Ruby-Documentation-Translation-Project Wiki · GitHub
I know there's already volunteers for Spanish translation, but other languages are welcome as well! That's it for now. Let me know if
you have any questions.
Hello Jesús,
It's a bit difficult to answer without knowing when that free time is available. You can always try something like Bignum translation, which is not too bad size wise for starters. I'm at the point to where I need sample translated content so I can test integrating the translated content into RDoc's output. So to be honest one translated file would be sufficient.
Part of the reason why I chose to start with a few files is it would allow translators, both individual and teams, to figure out a workflow process early on. It also helps me figure out what flaws there might be in the existing process when things are on a smaller scale. One suggestion I might make is to contact the others who have indicated interest in Spanish translations and work something out regarding splitting up large files (Array is pretty decently sized), or just providing editing if you feel the schedule doesn't match up.
Regards,
Chris White
http://www.twitter.com/cwgem
···
On Aug 21, 2011, at 11:52 PM, Jesús Gabriel y Galán wrote:
Chris,
Thanks for this effort. It makes it easy for people to focus on the
translation effort. I'll try to add translations, but I just returned
from holidays and right now my life is a bit of a mess. What do you
recommend for someone whose free time comes in little bursts? Should I
add myself as editor, instead of the main translator of a file? Or
should I just start a document and have people edit it if I don't
finish it?
Jesus.