Debian Codegraph @

ABOUT-NLS

raw
1 Some of this discussion is obsolete - lynx does not bundle the "intl"
2 directory, and consequently the "--with-included-gettext" configure option is
3 not supported.
4 ------------------------------------------------------------------------------
5
6 Notes on the Free Translation Project
7 *************************************
8
9 Free software is going international! The Free Translation Project
10 is a way to get maintainers of free software, translators, and users all
11 together, so that will gradually become able to speak many languages.
12 A few packages already provide translations for their messages.
13
14 If you found this `ABOUT-NLS' file inside a distribution, you may
15 assume that the distributed package does use GNU `gettext' internally,
16 itself available at your nearest GNU archive site. But you do *not*
17 need to install GNU `gettext' prior to configuring, installing or using
18 this package with messages translated.
19
20 Installers will find here some useful hints. These notes also
21 explain how users should proceed for getting the programs to use the
22 available translations. They tell how people wanting to contribute and
23 work at translations should contact the appropriate team.
24
25 When reporting bugs in the `intl/' directory or bugs which may be
26 related to internationalization, you should tell about the version of
27 `gettext' which is used. The information can be found in the
28 `intl/VERSION' file, in internationalized packages.
29
30 One advise in advance
31 =====================
32
33 If you want to exploit the full power of internationalization, you
34 should configure it using
35
36 ./configure --with-included-gettext
37
38 to force usage of internationalizing routines provided within this
39 package, despite the existence of internationalizing capabilities in the
40 operating system where this package is being installed. So far, only
41 the `gettext' implementation in the GNU C library version 2 provides as
42 many features (such as locale alias or message inheritance) as the
43 implementation here. It is also not possible to offer this additional
44 functionality on top of a `catgets' implementation. Future versions of
45 GNU `gettext' will very likely convey even more functionality. So it
46 might be a good idea to change to GNU `gettext' as soon as possible.
47
48 So you need not provide this option if you are using GNU libc 2 or
49 you have installed a recent copy of the GNU gettext package with the
50 included `libintl'.
51
52 INSTALL Matters
53 ===============
54
55 Some packages are "localizable" when properly installed; the
56 programs they contain can be made to speak your own native language.
57 Most such packages use GNU `gettext'. Other packages have their own
58 ways to internationalization, predating GNU `gettext'.
59
60 By default, this package will be installed to allow translation of
61 messages. It will automatically detect whether the system provides
62 usable `catgets' (if using this is selected by the installer) or
63 `gettext' functions. If neither is available, the GNU `gettext' own
64 library will be used. This library is wholly contained within this
65 package, usually in the `intl/' subdirectory, so prior installation of
66 the GNU `gettext' package is *not* required. Installers may use
67 special options at configuration time for changing the default
68 behaviour. The commands:
69
70 ./configure --with-included-gettext
71 ./configure --with-catgets
72 ./configure --disable-nls
73
74 will respectively bypass any pre-existing `catgets' or `gettext' to use
75 the internationalizing routines provided within this package, enable
76 the use of the `catgets' functions (if found on the locale system), or
77 else, *totally* disable translation of messages.
78
79 When you already have GNU `gettext' installed on your system and run
80 configure without an option for your new package, `configure' will
81 probably detect the previously built and installed `libintl.a' file and
82 will decide to use this. This might be not what is desirable. You
83 should use the more recent version of the GNU `gettext' library. I.e.
84 if the file `intl/VERSION' shows that the library which comes with this
85 package is more recent, you should use
86
87 ./configure --with-included-gettext
88
89 to prevent auto-detection.
90
91 By default the configuration process will not test for the `catgets'
92 function and therefore they will not be used. The reasons are already
93 given above: the emulation on top of `catgets' cannot provide all the
94 extensions provided by the GNU `gettext' library. If you nevertheless
95 want to use the `catgets' functions use
96
97 ./configure --with-catgets
98
99 to enable the test for `catgets' (this causes no harm if `catgets' is
100 not available on your system). If you really select this option we
101 would like to hear about the reasons because we cannot think of any
102 good one ourself.
103
104 Internationalized packages have usually many `po/LL.po' files, where
105 LL gives an ISO 639 two-letter code identifying the language. Unless
106 translations have been forbidden at `configure' time by using the
107 `--disable-nls' switch, all available translations are installed
108 together with the package. However, the environment variable `LINGUAS'
109 may be set, prior to configuration, to limit the installed set.
110 `LINGUAS' should then contain a space separated list of two-letter
111 codes, stating which languages are allowed.
112
113 Using This Package
114 ==================
115
116 As a user, if your language has been installed for this package, you
117 only have to set the `LANG' environment variable to the appropriate
118 ISO 639 `LL' two-letter code prior to using the programs in the
119 package. For example, let's suppose that you speak German. At the
120 shell prompt, merely execute `setenv LANG de' (in `csh'),
121 `export LANG; LANG=de' (in `sh') or `export LANG=de' (in `bash'). This
122 can be done from your `.login' or `.profile' file, once and for all.
123
124 An operating system might already offer message localization for
125 many of its programs, while other programs have been installed locally
126 with the full capabilities of GNU `gettext'. Just using `gettext'
127 extended syntax for `LANG' would break proper localization of already
128 available operating system programs. In this case, users should set
129 both `LANGUAGE' and `LANG' variables in their environment, as programs
130 using GNU `gettext' give preference to `LANGUAGE'. For example, some
131 Swedish users would rather read translations in German than English for
132 when Swedish is not available. This is easily accomplished by setting
133 `LANGUAGE' to `sv:de' while leaving `LANG' to `sv'.
134
135 Translating Teams
136 =================
137
138 For the Free Translation Project to be a success, we need interested
139 people who like their own language and write it well, and who are also
140 able to synergize with other translators speaking the same language.
141 Each translation team has its own mailing list, courtesy of Linux
142 International. You may reach your translation team at the address
143 `[email protected]', replacing LL by the two-letter ISO 639 code for your
144 language. Language codes are *not* the same as the country codes given
145 in ISO 3166. The following translation teams exist, as of August 1998:
146
147 Chinese `zh', Czech `cs', Danish `da', Dutch `nl', English `en',
148 Esperanto `eo', Finnish `fi', French `fr', German `de', Hungarian
149 `hu', Irish `ga', Italian `it', Indonesian `id', Japanese `ja',
150 Korean `ko', Latin `la', Norwegian `no', Persian `fa', Polish
151 `pl', Portuguese `pt', Russian `ru', Slovenian `sl', Spanish `es',
152 Swedish `sv', and Turkish `tr'.
153
154 For example, you may reach the Chinese translation team by writing to
155 `[email protected]'.
156
157 If you'd like to volunteer to *work* at translating messages, you
158 should become a member of the translating team for your own language.
159 The subscribing address is *not* the same as the list itself, it has
160 `-request' appended. For example, speakers of Swedish can send a
161 message to `[email protected]', having this message body:
162
163 subscribe
164
165 Keep in mind that team members are expected to participate
166 *actively* in translations, or at solving translational difficulties,
167 rather than merely lurking around. If your team does not exist yet and
168 you want to start one, or if you are unsure about what to do or how to
169 get started, please write to `[email protected]' to reach the
170 coordinator for all translator teams.
171
172 The English team is special. It works at improving and uniformizing
173 the terminology in use. Proven linguistic skill are praised more than
174 programming skill, here.
175
176 Available Packages
177 ==================
178
179 Languages are not equally supported in all packages. The following
180 matrix shows the current state of internationalization, as of August
181 1998. The matrix shows, in regard of each package, for which languages
182 PO files have been submitted to translation coordination.
183
184 Ready PO files cs da de el en es fi fr it
185 .----------------------------.
186 bash | [] [] |
187 bison | [] [] |
188 clisp | [] [] [] [] |
189 cpio | [] [] [] |
190 diffutils | [] [] [] |
191 enscript | [] [] [] [] |
192 fileutils | [] [] [] [] |
193 findutils | [] [] [] [] |
194 flex | [] [] |
195 gcal | [] [] |
196 gettext | [] [] [] [] [] |
197 grep | [] [] [] [] |
198 hello | [] [] [] [] [] |
199 id-utils | [] [] |
200 indent | [] [] |
201 libc | [] [] [] |
202 m4 | [] [] |
203 make | [] [] [] |
204 music | [] |
205 ptx | [] [] [] |
206 recode | [] [] [] [] |
207 sed | |
208 sh-utils | [] [] [] |
209 sharutils | [] [] [] [] [] |
210 tar | [] [] [] [] |
211 texinfo | [] [] [] |
212 textutils | [] [] [] [] |
213 wdiff | [] [] [] [] |
214 wget | [] [] [] [] |
215 `----------------------------'
216 cs da de el en es fi fr it
217 7 4 26 4 1 18 1 26 4
218
219 ja ko nl no pl pt ru sl sv
220 .----------------------------.
221 bash | [] | 3
222 bison | [] | 3
223 clisp | | 4
224 cpio | [] [] [] | 6
225 diffutils | [] [] | 5
226 enscript | [] [] | 6
227 fileutils | [] [] [] [] [] [] [] | 11
228 findutils | [] [] [] [] [] | 9
229 flex | [] [] | 4
230 gcal | [] [] [] | 5
231 gettext | [] [] [] [] [] [] [] | 13
232 grep | [] [] [] [] [] [] [] | 11
233 hello | [] [] [] [] [] [] [] | 12
234 id-utils | [] | 3
235 indent | [] [] [] | 5
236 libc | [] [] [] [] [] | 8
237 m4 | [] [] [] [] | 6
238 make | [] [] [] | 6
239 music | [] | 2
240 ptx | [] [] [] [] [] | 8
241 recode | [] [] [] [] [] | 9
242 sed | | 0
243 sh-utils | [] [] [] [] [] | 8
244 sharutils | [] [] | 7
245 tar | [] [] [] [] [] [] [] | 11
246 texinfo | [] | 4
247 textutils | [] [] [] [] [] | 9
248 wdiff | [] [] [] [] | 8
249 wget | [] | 5
250 `----------------------------'
251 18 teams ja ko nl no pl pt ru sl sv
252 29 domains 1 12 21 11 19 7 5 7 17 191
253
254 Some counters in the preceding matrix are higher than the number of
255 visible blocks let us expect. This is because a few extra PO files are
256 used for implementing regional variants of languages, or language
257 dialects.
258
259 For a PO file in the matrix above to be effective, the package to
260 which it applies should also have been internationalized and
261 distributed as such by its maintainer. There might be an observable
262 lag between the mere existence a PO file and its wide availability in a
263 distribution.
264
265 If August 1998 seems to be old, you may fetch a more recent copy of
266 this `ABOUT-NLS' file on most GNU archive sites.
267
268 Using `gettext' in new packages
269 ===============================
270
271 If you are writing a freely available program and want to
272 internationalize it you are welcome to use GNU `gettext' in your
273 package. Of course the GNU General Public License applies to your
274 sources from then if you include `gettext' directly in your distribution
275 on but since you are writing free software anyway this is no
276 restriction.
277
278 Once the sources are change appropriately and the setup can handle to
279 use of `gettext' the only thing missing are the translations. The Free
280 Translation Project is also available for packages which are not
281 developed inside the GNU project. Therefore the information given above
282 applies also for every other Free Software Project. Contact
283 `[email protected]' to make the `.pot' files available to
284 the translation teams.
285