| 1 |
By default, intltool/gettext will generate the .po file with the |
| 2 |
entries sorted completely alphabetically. This is not very useful for |
| 3 |
po-locations, so we've provided a script to generate .po files in a |
| 4 |
better order. Do: |
| 5 |
|
| 6 |
./regen.sh en_US.po |
| 7 |
|
| 8 |
(substituting "en_US" of course) to regenerate your .po file with the |
| 9 |
entries sorted as follows: |
| 10 |
|
| 11 |
* Top-level regions (continents, etc), sorted alphabetically |
| 12 |
|
| 13 |
* Countries, sorted alphabetically |
| 14 |
|
| 15 |
* Timezone names, not really especially sorted |
| 16 |
|
| 17 |
* State/Province names, sorted by country, then alphabetically |
| 18 |
within each country |
| 19 |
|
| 20 |
* City names, sorted by country, then alphabetically within |
| 21 |
each country |
| 22 |
|
| 23 |
All of the region and country names are immediately visible when |
| 24 |
adding a new location in the gweather-applet, and all of the country |
| 25 |
and timezone names are immediately visible when setting the timezone |
| 26 |
of a location in the clock applet. Thus, every translation will likely |
| 27 |
want to have all of those strings translated. |
| 28 |
|
| 29 |
The state/province and city names are more likely to only be seen by |
| 30 |
people living in those states/cities, and so are less critical to have |
| 31 |
100% translation of; they are sorted by country to make it easy to |
| 32 |
translate the city names in countries where your language is spoken |
| 33 |
first, and worry about the city names in other countries later. |
| 34 |
|
| 35 |
|
| 36 |
If you don't want to use this script, you don't have to, but you will |
| 37 |
need to use intltool 0.40.3 or later to rebuild your .po files from |
| 38 |
now on, because earlier versions don't have msgctxt support. |
| 39 |
|
| 40 |
|
| 41 |
Do note there is no need for a LINGUAS file in this directory, and the |
| 42 |
po/LINGUAS file shouldn't be modified for changes in this directory. |