As far as I understand, gettext tools (which django used) will automatically merge old translation and new one into one file. And as a programmer, I know it is good to see diff, both for source control and computer processing.
Limodou, it seems that the old translation is maintained by you. About this translation, maybe we should contact and talk in Chinese ... Gilbert On Jun 20, 8:39 am, limodou <[EMAIL PROTECTED]> wrote: > On 6/20/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > On Tue, 2007-06-19 at 02:31 -0700, Gilbert Fine wrote: > > > I found the translation for simplified Chinese was very outdated. I > > > updated the po file and translated. Here is a copy. Hopefully be > > > committed in official source after being reviewed. > > > When you are happy with the translation, please run "svn diff" and > > attach the resulting patch to a ticket in Trac. Then we'll be able to > > commit it. > > > I would prefer seeing diffs, rather than whole file replacements, since > > it makes it much easier for me to check that it is a recent version that > > is being translated and we aren't accidentally replacing new > > translations with old. > > But I remembered that the old style is django will automatically merge > the newest untranslated or changed message strings into django.po > file. I always worked at the new merged django.po before, but for now, > the old style seems gone? > > -- > I like python! > UliPad <<The Python Editor>>:http://wiki.woodpecker.org.cn/moin/UliPad > My Blog:http://www.donews.net/limodou --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
