|
1 README.i18n |
|
2 |
|
3 |
|
4 Using a translation |
|
5 ----------------------------------------------------------------------- |
|
6 |
|
7 All available translations can be found in the locale directory in the |
|
8 poweradmin base directory. The Dutch translation for example, can be |
|
9 found in nl_NL. To review the status of the translation, you can have a |
|
10 look at the nl.po file in the LC_MESSAGE directory. |
|
11 |
|
12 If you want to use a translation, say the nl_NL, all you have to do is |
|
13 edit inc/i18n.php file and change the $language variable to the desired |
|
14 language, for example "nl_NL". |
|
15 |
|
16 If this doesn't work, your system isn't setup properly. |
|
17 |
|
18 |
|
19 Adding a new translation |
|
20 ----------------------------------------------------------------------- |
|
21 |
|
22 If you want to create a new translation you can do the following. For |
|
23 example, if you want to create a Dutch translation: |
|
24 |
|
25 - cd /path/to/poweradmin/ |
|
26 - mkdir -p locale/nl_NL/LC_MESSAGES/ |
|
27 - cp docs/template.pot locale/nl_NL/LC_MESSAGES/nl.po |
|
28 - cd locale/nl_NL/LC_MESSAGES/ |
|
29 - vim nl.po |
|
30 - msgfmt nl.po -o message.mo |
|
31 |
|
32 |
|
33 Updating the translation template file |
|
34 ----------------------------------------------------------------------- |
|
35 |
|
36 If creating a new translation and you are not sure if the template file |
|
37 that was provided in the distribution, you may want to re-create the |
|
38 template file. To do so, do the following: |
|
39 |
|
40 |
|
41 - cd /path/to/poweradmin/ |
|
42 - xgettext --no-wrap -o docs/template.pot *.php inc/*.php |
|
43 |
|
44 The last command updates the template file in docs/ directory. |
|
45 |
|
46 |