On Sun, 2007-06-03 at 11:34 +0200, Knut Ivar Nesheim wrote: > Hi! > > Currently Django is only translated to Norwegian Bokmål. I would very > much like to see a translation to Norwegian Nynorsk. I have a > sponsor, so I'll be able to do the hours required. I'll also be able > to help out with the Bokmål translation. > > I don't know how to get started. Could somebody please give me some > advice?
We use the standard GNU gettext utilities and PO file formats for translations. So make sure you have gettext installed (it exists for Windows as well as more Unix-like platforms, although I have no experience with installating it if you are using that platform). 1. Check out the latest Django code from subversion (see option 1 at http://www.djangoproject.com/download/ ). We only commit translations to the subversion trunk, so it's not practical to translate earlier versions of the code -- it will cause conflicts with other translators. 2. Create the initial PO files: change to the the django/ directory inside the source tree and run bin/make-messages.py -l nn (let's put Nynorsk under nn for now and we'll worry about the getting no/nb/nn served correctly later. It's not important right now.) 3. Start translating the newly created conf/locale/nn/LC_MESSAGES/django.po and djangojs.po files. You obviously don't have to translate all of the strings at once. 4. After you have done as much as you want initially, check that there are no errors. Under the django/ directory again, run bin/compile-messages.py -l nn If that reports any errors, you need to fix them. Files with errors are not committed to Django, because it can cause crashes for people using your particular translation. 5. The first time you've done enough to upload, create a new ticket in Trac and upload the django.po and djangojs.po files (we don't need the .mo files uploaded, because we'll recreate those at checkin time). 6. On subsequent times, use "svn diff" to generate the difference between what is already in subversion and your changes. Then just upload the changes to Trac. That way it is easy to merge in that patch with any translations from somebody else. Uploading the whole django.po or djangojs.po file each time makes my life (as the person who has to work out whether the changes are current, etc) much harder. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
