Revision 461a2ec9
b/README.i18n | ||
---|---|---|
13 | 13 |
|
14 | 14 |
1)for each language we want to add, we run makemessages, from our project's base: |
15 | 15 |
|
16 |
$ django-admin.py makemessages -l el -e=html,txt,py
|
|
16 |
$ ./bin/django-admin.py makemessages -l el -e html,txt,py
|
|
17 | 17 |
(./bin/django-admin.py makemessages -l el -e html,txt,py --ignore=lib/*) |
18 | 18 |
|
19 | 19 |
|
... | ... | |
36 | 36 |
|
37 | 37 |
|
38 | 38 |
3)when we have put our strings to be translated, from the project's base we run |
39 |
$ django-admin.py makemessages -l el -e=html,txt,py
|
|
39 |
$ django-admin.py makemessages -l el -e html,txt,py
|
|
40 | 40 |
processing language el |
41 | 41 |
|
42 | 42 |
this creates (or updates) the po file for the Greek language. We run this command each time we add new strings to be translated. After that, we can translate our strings, on the po file (locale/el/LC_MESSAGES/django.po) |
43 | 43 |
|
44 | 44 |
4)when we are ready, we run the following command from the project's base |
45 |
$ django-admin.py compilemessages |
|
45 |
$ ./bin/django-admin.py compilemessages
|
|
46 | 46 |
|
47 | 47 |
this compiles the po files to mo. |
48 | 48 |
|
Also available in: Unified diff