| | 46 | == How to Update Translations == |
| | 47 | |
| | 48 | 1. Ensure that you are running the latest subversion checkout of the code - run "svn update" in your local django subversion copy. |
| | 49 | 2. Run bin/make-messages.py -l <locale> and you get updated .po files |
| | 50 | 3. Update any untranslated and fuzzy messages with your favorite translation tool. Anything that looks like "%s" or "%(something)s" has to be copied precisely and the 's' may be a 'd' or 'x' or 'i', possibly. |
| | 51 | 4. Run bin/compile-messages.py -l <locale> and ensure there are no errors. |
| | 52 | 5. Upload the complete new .po files to Trac. |
| | 53 | |
| | 54 | It is best practice to just check every few weeks (once a month or so if you're really enthusiastic; less often if you're |
| | 55 | not) to see if there's been any big changes. |
| | 56 | |
| | 57 | Prior to any release, Django maintainers will make an announcement. Prior to 1.0, we'll have a couple of weeks of string freeze in order to give people time to be 100% translated. |
| | 58 | |