>>> ¡­And then you need another one to
>>> check what was written.  These are practical problems.  There are
>>> extant services to support this, they are expensive in either money or
>>> time, and the docs produced usually lag behind English quite a bit.
>>
>> Is this a good use for some PSF funding? Would companies be willing to
>> invest money in translating Python documentation?
>>
>> Just because we're Open Source, doesn't mean that everything we do has
>> to be purely volunteer.
>
>IHMO translating the *whole* Python documentation at once by a
>professional translator can be very expensive, no somthing that the
>PSF would affort. Which language would you pick? Depending on what?
>
>We already have motivated translators for free who only ask us for the
>permission to make tiny changes to make their life simpler and make
>the doc more visible. I'm in favor of allowing them to translate and
>make the translated doc official ;-)
>
>IMHO a better usage of the PSF funding would be to organize some local
>sprints to translate the Python documentation. Such sprints are fun,
>cheap, and can be a nice opportunity to recruit free and motivated
>translators. We are looking for people involved to translate the doc
>the doc is updated, not only translate the doc once and go away.
>Right?
>
>Victor
>