set up documentation translation infrastructure

[cotto]

As mentioned on #ps, we need to set up some infrastructure to allow Parrot's documentation to be translated into other languages. Initial suggestions of other projects that have solved this problem include Ubuntu, OpenOffice and Mozilla.

[anonymous]

The infrastructure from Ubuntu seems good.

[jimmy]

I think I'm the first volunteer for translation of Parrot's documentation in chinese.

The reply above is also mine.

[allison]

We could simply use Launchpad. It requires BSD licensing on all translations, but that wouldn't necessarily be a problem.

Also recommend taking a look at:  http://translate.sourceforge.net/. (I met with the development team last year and was impressed.)

[quevlar]

Hi,

I think using launchpad is a great idea in general, and for the amount of formats it handles in particular.

I browsed the repository and it seems all to be python language and the licence to be GPL.

I'm the second voluntary for translation into Spanish.

Sincerely,

Igor

[jkeenan]

In 22 months no one has taken this on, suggesting it is not a pressing need.

(Personally, I think translations are highly desirable. But, as became apparent in the course of Google Code-In efforts to get our README translated, many of our developers -- including people who are presumably not native English speakers -- don't agree. But, in any event, the ticket concerns a translation infrastructure, not translations themselves.)

Should we keep this ticket open in Trac at this time?

Thank you very much.

kid51

[dukeleto]

If you want to volunteer and work on translation of a specific document to a specific language, please open a ticket specifically for that. If you have an idea for a specific bit of infrastructure to help translations, add a ticket for that.

This ticket is too ambiguous.