+-----------------------------+
| +-------------------------+ |
| | xMule Translation HOWTO | |
| +-------------------------+ |
+-----------------------------+

Author: pure_ascii <pure_ascii@donkey-chat.de>


Initial translation:
--------------------

1. Build the xmule-w_o-strings.pot file:

   > cd po; make xmule.pot-update

2. Build the strings.pot file:
   (This can't be done in 1. as in strings.en the strings are not marked.)
   
   > xgettext -a -o strings.pot ../src/strings.en

3. Merge the 2 pot files:

   > msgcat --use-first -o xmule.pot xmule-w_o-strings.pot strings.pot

4. Copy the pot file to your language's po file:
   (Substitute <lang> with your language abbrevation, like "de" or "en".)

   > cp xmule.pot <lang>.po

5. Edit the <lang>.po and enter the translations for the strings after "msgid" 
   after "msgstr". (Or use special software for that.)
   You can get the translations of the strings from strings.en from xmule.rc
   via the related IDs. (Maybe this can be automated, I've done copy&paste.)

6. Test the translation: 

   > msgfmt -c --statistics -o <lang>.mo <lang>.po 
   > mkdir <datadir>/locale/<lang>/LC_MESSAGES
   > mv <lang.mo> <datadir>/locale/<lang>/LC_MESSAGES/

   where <datadir> is the datadir choosen while ./configure, 
   default: ${prefix}/share, e.g. /usr/share

7. Send the <lang>.po file to me or one of the other developers, if you have
   no CVS write access to po/ yourself. 

8. If you have CVS write access yourself, add <lang> to po/LINGUAS. 



Update translation:
-------------------

1.-3. like above

4. Check if the translation is up to date:

   > msgmerge -v -o <lang>.pox <lang>.po xmule.pot

5. Check the <lang>.pox for "fuzzy" or empty entries and correct them.
   (Or use special programms for that.)

6. Update the <lang>.po:

   > mv <lang>.pox <lang>.po

7.-8. like above. 


---END---
