File: README.i18n

package info (click to toggle)
postgis 2.5.1%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 75,792 kB
  • sloc: ansic: 139,314; sql: 136,281; xml: 48,954; sh: 4,906; perl: 4,509; makefile: 2,897; python: 1,198; yacc: 441; cpp: 305; lex: 132
file content (30 lines) | stat: -rw-r--r-- 985 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Translating these Applications
------------------------------

You will need the gettext utilities to work with the translation files.
Ensure you have the following utilities available:

  xgettext
  msgfmt

First, update the translation template ("pot") file

  make pot

This will create fresh template files in "po/", "shp2pgsql.pot" and 
"pgsql2shp.pot"

Second, copy a template to a translation file, using the filename 
pattern shp2pgsql_LANG.po. For example, for a French translation:

  cp shp2pgsql.pot shp2pgsql_fr.po
  cp pgsql2shp.pot pgsql2shp_fr.po

Finally, prepare your translations. There is header information in the 
translation file to identify yourself as the translator -- fill it in.

Important, set the CHARSET value in the header to the text character set 
you are using for your text file. We'd prefer you use UTF-8, if you can.

When your translation file is complete, commit your changes, or 
mail it to the postgis-devel list, and we'll commit it for you.