I updated the SVN with changes to support translation. Translatable strings are all enclosed in _(""), and we’re using UTF-8 on all platforms.
When the program runs, it looks in the directory of the EXE for the file: locale<langcode>\LC_MESSAGES\bitcoin.mo
On Linux, it also looks for:
/usr/share/locale/
/usr/local/share/locale/
(are there other standard places it should look on linux?)
Here’s a quick walkthrough using poedit to make a .po and .mo file:
- Download the bitcoin sourcecode from SVN
- In the trunk directory, mkdir locale<lang>\LC_MESSAGES
- In poedit, File->New catalog->Paths tab
- Click the “New item” dotted rectangle button
- Put ”../../..” and MAKE SURE TO PRESS ENTER to add the path
- Click OK
- Save the file as “bitcoin.po” in the LC_MESSAGES directory you made
- It should then scan the sourcecode and find about 170 strings
- If it didn’t find anything, check Catalog->Settings->Path tab, make sure the ”../../..” was added
When you’re done translating, commit both bitcoin.po (the editable catalog file) and bitcoin.mo (compiled data used by the program).