On 25.4.2013 11:25, Claude Paroz wrote:
> For some time now, we are progressively setting things up so that our
> fabulous documentation can be translated.
>
> ...
>
> You'll also realize that the number of strings is huge! Beginning with
> the "index" and "intro" resources (containing the tutorial) might be a
> safe bet.
>
> ...

Hello to all!

The translation of all documentation undertaking is a bit of a surprise for
me. The number of strings is really huge.

Personally I'm not sure it needs all to be translated as the translations
will IMO always stay behind the original, in completeness and quality. Some
time ago, aside from founding a local site http://www.djangoproject.cz/, my
friend Michal Valoušek decided to translate the tutorial and some intro texts.

In my opinion, that is exactly best amount of work that should be done (if
any) -- to attract new developers. I think it is impossible to code on
level Python/Django expect without knowing English.

May I ask, where was the discussion about doing all doc translation so I
can look for the arguments?

I might be isolated soldier here but in my opinion human resources in
Django universe now is not needed for making Django bigger. I'd be close to
prescribe a diet if I was in charge.

A question to other language teams: Do you have resources and willingness
to translate the huge doc and keep up with the quality of the changing
original? I'm sure it is best to have no translation than to have
translation with errors.

I'd like to ask the Czech team members too as I'm certainly not working on
the entire Django doc translation.

Thanks,

Vláďa

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-i18n?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to