[Cc: to Django-IT and Django-I18N] Malcolm Tredinnick wrote: > One thing we do have to watch out for as translation activity picks up > is that we currently have no language coordinators/maintainers. This > could potentially lead to translation "battles" with some phrases > changing back and forth, if there's any confusion or dispute. Having the > names of previous contributors makes tracking down the history and > resolving these problems a little easier.
That's not going to help when one's having "battles" with oneself. Case in point, before 0.96 I updated the italian translation, more or less out of the blue. Then some discussion ensued on the italian Django mailing list, which prompted me to make further updates a couple of times. In the meanwhile, the author named the .po file stayed the same, of course. :-) > However, Jacob and I have discussed (after prompting from the > translators) giving commit privileges under django/conf/locale/ to > certain language maintainers -- one for each language -- to keep things > on an even keel there. That makes a lot of sense to me, because, > frankly, I have no way to judge if a patch for, say, the XYZ locale is > an improvement or not; I would much rather have a native speaker take > responsibility there. That would be great. It would make it easier having more frequent updates and corrections, relieving the burden of committing them from the main developers. It could also lead to a bit more instability and more changes than necessary, but that can be mitigated if the language maintainers try to discuss changes locally a bit, before committing them. Yes, I'm promising I'll do better on that front, from now on. ;-) > Jacob wants to make it easier for those people to > set up passwords via the web interface to ease his load a little, so > that will happen in due course, but I realise he seems pretty busy at > the moment, so I'm not pushing that yet. For now, we don't really have a > problem here, so it's not blindingly urgent. Well, as they say, best is enemy of good. :-) Setting up passwords centrally is a one-time job, while the translation-committing burden lightening is ongoing: maybe it's better not to wait for such a web interface to materialize. > Assuming you're happy with allowing locale maintainers to commit > directly (it's pretty normal on a lot of other projects), I don't think > there's a technical reason for having the names in the code, so we > should be consistent. Ok, go ahead and strip the italian translation of them too, I and the previous translator (hi, C8E!) are in AUTHORS already. No, I'm not creating a patch. ;-P -- Nicola Larosa - [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
