[Python-Dev] Translating docs
Alex Martelli
aleaxit at gmail.com
Sun Feb 26 02:34:41 CET 2006
More information about the Python-Dev mailing list
Sun Feb 26 02:34:41 CET 2006
- Previous message: [Python-Dev] Translating docs
- Next message: [Python-Dev] Translating docs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 25, 2006, at 4:43 PM, martin at v.loewis.de wrote: > Zitat von Facundo Batista <facundobatista at gmail.com>: > >> The question is, it's ok to use a third party system for this >> initiative? Or you (we) prefer to host it in-house? Someone alredy >> thought of this? > > I thought about it at one time, and I think the doc strings can be > translated very well using gettext-based procedures; I once submitted > a POT file to the translation project: > > http://www.iro.umontreal.ca/translation/registry.cgi?domain=python > > Translating the library reference as such is more difficult, because > it can't be translated in small chunks very well. > > Some group of French translators once translated everything for 1.5.2, > and that translation never got updated. A similar situation applies to Italy -- a lot of stuff is translated at http://www.python.it/doc/Python-Docs/html/ (the C-API and Extending and Embedding aren't translated, though), but it's 2.3.4- vintage docs. There's no real mechanism or process to ensure updates. Alex
- Previous message: [Python-Dev] Translating docs
- Next message: [Python-Dev] Translating docs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list