|
1
by budgester at budgester
Initial import of IRM codebase |
1 |
Making a New translation |
2 |
--------------------------
|
|
3 |
||
4 |
Copy locale/po/irm.pot to locale/po/<lang_code>.po, and then edit that new |
|
5 |
file appropriately. Add a relevant entry to the array $supported_languages |
|
6 |
at the top of include/i18n.php, providing an appropriate country code and |
|
7 |
the correct encoding from the po file. |
|
8 |
||
9 |
If you're getting the irm.pot from a released version of IRM, it won't be |
|
10 |
the latest. Contact irm-devel@lists.sf.net for info on where the most |
|
11 |
up-to-date irm.pot can be obtained from. Also, please subscribe to |
|
12 |
irm-devel (http://lists.sf.net/mailman/listinfo/irm-devel) so you get |
|
13 |
announcements of updated translations. |
|
14 |
||
15 |
Tools for assisting translations include poedit, kbabel, and gtranslator. |
|
16 |
There is also a gettext mode in EMACS. |
|
17 |
||
18 |
(Suggestions for good translator's howtos appreciated) |