On Oct 7, 5:24 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sun, 2007-10-07 at 07:52 -0700, ludvig.ericson wrote:
> > Yeah, perhaps we should have some sort of triage process of
> > translations, when there's more than one translator for given
> > language? That way we can ensure a much higher quality.
>
> Soon (for some definition of "soon"), we -- the core devs -- want to
> move to a system where there are one or two designated maintainers for
> each locale. All that really means is that those people will have direct
> commit access to their directory under django/conf/locale/ and in that
> way, commits to the given language go through them. Not every language
> need necessarily have a maintainer immediately, because sometimes we get
> a contribution and then the person disappears. A little bit of
> persistence will be needed before moving to that step, but for most of
> our common languages, you guys have already shown that level of
> commitment.
Mh, yeah, might help. Though I can see controversy arise when two
translators are in dispute of a translation, making their change and
committing, then the other translator changes back and commits, and so
on, and that'd be pretty nasty for everybody using trunk, as it'd bump
the repository revision each time.
> I've been very aware of the lack of formal triage that goes on at the
> moment. Any large translation change from somebody I don't recognise as
> a regular translator, I'll usually bounce off the most recent regular
> translator. This particular Swedish patch had already crossed my
> boundary into needing another opinion before this thread started. Really
> small changes that look like obvious typo fixes or adding missing
> strings, I'll generally commit immediately, but even that's a bit risky.
Ah yeah, but you've to watch out with these typo-look-alikes, they can
be quite deceptive in terms of breaking grammar, and as have been
shown, some translation updates aren't called for because there's just
is no proper way to translate. (e.g., the neutrum/utrum genus on an
unknown noun.)
A triaging process would really solve 99% of the controversy problems,
and I don't see why this isn't possible right now - I mean, simple as
this:
1) Translator adds patch to trac, and notifies this mailing list and/
or locale specific (e.g., django-se)
2) Other translators review changes, and this is where triaging takes
place, just not in terms of trac logics: One or more translators will
have to approve or disapprove.
3) A commit happens, be it through you or the locale-specific commit
man.
(p.s., anybody know why does Google Groups mashes up the newlines in
most of my messages?)
--
Ludvig Ericson
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Django-I18N?hl=en
-~----------~----~----~----~------~----~------~--~---
