blob: 1bef9e486db7372fa5d53c9d9a5b355b534887d1 (
plain)
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
gettext, i18n, and the po/ subdirectory
05-Jun-2009
David Cantrell <dcantrell@redhat.com>
---------------------------------------
I have attempted to clean up our po/ subdirectory and bring it in to
conformance with GNU gettext tools as well as hook it in to GNU autoconf and
GNU automake. The gettext software has templates set up for this already,
so I'm just using those.
From time to time, we may have to update our gettext template files and or
expand or reduce the information in the files. How do you know what files
do what? Here's an explanation:
m4/gettext.m4
m4/iconv.m4
m4/lib-ld.m4
m4/lib-link.m4
m4/lib-prefix.m4
m4/nls.m4
m4/po.m4
m4/progtest.m4
po/Makefile.in.in
po/Rules-quot
po/boldquot.sed
po/en@boldquot.header
po/en@quot.header
po/insert-header.sin
po/quot.sed
po/remove-potcdate.sin
These files are copied in when 'gettextize' is run on the source
project. When we need to update to a newer minimum version of
gettext, these files will be replaced. In general, we should never
need to touch these files.
po/Makevars
Should be updated when we update gettext files with a new gettextize
run. A file called po/Makevars.template will appear and we can move
over our values to the new file and commit it. We do not need to
change this file on a regular basis.
po/POTFILES.in
This file contains a listing of all source files in the project that
have translatable strings.
po/LINGUAS
Space-delimited list of languages available. If a new language is
added, it should be added to this file.
po/*.po
Actual translated strings, as maintained by the translation team(s).
|
