1Notes on the Free Translation Project 2************************************* 3 4 Free software is going international! The Free Translation Project 5is a way to get maintainers of free software, translators, and users all 6together, so that will gradually become able to speak many languages. 7A few packages already provide translations for their messages. 8 9 If you found this `ABOUT-NLS' file inside a distribution, you may 10assume that the distributed package does use GNU `gettext' internally, 11itself available at your nearest GNU archive site. But you do _not_ 12need to install GNU `gettext' prior to configuring, installing or using 13this package with messages translated. 14 15 Installers will find here some useful hints. These notes also 16explain how users should proceed for getting the programs to use the 17available translations. They tell how people wanting to contribute and 18work at translations should contact the appropriate team. 19 20 When reporting bugs in the `intl/' directory or bugs which may be 21related to internationalization, you should tell about the version of 22`gettext' which is used. The information can be found in the 23`intl/VERSION' file, in internationalized packages. 24 25Quick configuration advice 26========================== 27 28 If you want to exploit the full power of internationalization, you 29should configure it using 30 31 ./configure --with-included-gettext 32 33to force usage of internationalizing routines provided within this 34package, despite the existence of internationalizing capabilities in the 35operating system where this package is being installed. So far, only 36the `gettext' implementation in the GNU C library version 2 provides as 37many features (such as locale alias, message inheritance, automatic 38charset conversion or plural form handling) as the implementation here. 39It is also not possible to offer this additional functionality on top 40of a `catgets' implementation. Future versions of GNU `gettext' will 41very likely convey even more functionality. So it might be a good idea 42to change to GNU `gettext' as soon as possible. 43 44 So you need _not_ provide this option if you are using GNU libc 2 or 45you have installed a recent copy of the GNU gettext package with the 46included `libintl'. 47 48INSTALL Matters 49=============== 50 51 Some packages are "localizable" when properly installed; the 52programs they contain can be made to speak your own native language. 53Most such packages use GNU `gettext'. Other packages have their own 54ways to internationalization, predating GNU `gettext'. 55 56 By default, this package will be installed to allow translation of 57messages. It will automatically detect whether the system already 58provides the GNU `gettext' functions. If not, the GNU `gettext' own 59library will be used. This library is wholly contained within this 60package, usually in the `intl/' subdirectory, so prior installation of 61the GNU `gettext' package is _not_ required. Installers may use 62special options at configuration time for changing the default 63behaviour. The commands: 64 65 ./configure --with-included-gettext 66 ./configure --disable-nls 67 68will respectively bypass any pre-existing `gettext' to use the 69internationalizing routines provided within this package, or else, 70_totally_ disable translation of messages. 71 72 When you already have GNU `gettext' installed on your system and run 73configure without an option for your new package, `configure' will 74probably detect the previously built and installed `libintl.a' file and 75will decide to use this. This might be not what is desirable. You 76should use the more recent version of the GNU `gettext' library. I.e. 77if the file `intl/VERSION' shows that the library which comes with this 78package is more recent, you should use 79 80 ./configure --with-included-gettext 81 82to prevent auto-detection. 83 84 The configuration process will not test for the `catgets' function 85and therefore it will not be used. The reason is that even an 86emulation of `gettext' on top of `catgets' could not provide all the 87extensions of the GNU `gettext' library. 88 89 Internationalized packages have usually many `po/LL.po' files, where 90LL gives an ISO 639 two-letter code identifying the language. Unless 91translations have been forbidden at `configure' time by using the 92`--disable-nls' switch, all available translations are installed 93together with the package. However, the environment variable `LINGUAS' 94may be set, prior to configuration, to limit the installed set. 95`LINGUAS' should then contain a space separated list of two-letter 96codes, stating which languages are allowed. 97 98Using This Package 99================== 100 101 As a user, if your language has been installed for this package, you 102only have to set the `LANG' environment variable to the appropriate 103`LL_CC' combination. Here `LL' is an ISO 639 two-letter language code, 104and `CC' is an ISO 3166 two-letter country code. For example, let's 105suppose that you speak German and live in Germany. At the shell 106prompt, merely execute `setenv LANG de_DE' (in `csh'), 107`export LANG; LANG=de_DE' (in `sh') or `export LANG=de_DE' (in `bash'). 108This can be done from your `.login' or `.profile' file, once and for 109all. 110 111 You might think that the country code specification is redundant. 112But in fact, some languages have dialects in different countries. For 113example, `de_AT' is used for Austria, and `pt_BR' for Brazil. The 114country code serves to distinguish the dialects. 115 116 The locale naming convention of `LL_CC', with `LL' denoting the 117language and `CC' denoting the country, is the one use on systems based 118on GNU libc. On other systems, some variations of this scheme are 119used, such as `LL' or `LL_CC.ENCODING'. You can get the list of 120locales supported by your system for your country by running the command 121`locale -a | grep '^LL''. 122 123 Not all programs have translations for all languages. By default, an 124English message is shown in place of a nonexistent translation. If you 125understand other languages, you can set up a priority list of languages. 126This is done through a different environment variable, called 127`LANGUAGE'. GNU `gettext' gives preference to `LANGUAGE' over `LANG' 128for the purpose of message handling, but you still need to have `LANG' 129set to the primary language; this is required by other parts of the 130system libraries. For example, some Swedish users who would rather 131read translations in German than English for when Swedish is not 132available, set `LANGUAGE' to `sv:de' while leaving `LANG' to `sv_SE'. 133 134 In the `LANGUAGE' environment variable, but not in the `LANG' 135environment variable, `LL_CC' combinations can be abbreviated as `LL' 136to denote the language's main dialect. For example, `de' is equivalent 137to `de_DE' (German as spoken in Germany), and `pt' to `pt_PT' 138(Portuguese as spoken in Portugal) in this context. 139 140Translating Teams 141================= 142 143 For the Free Translation Project to be a success, we need interested 144people who like their own language and write it well, and who are also 145able to synergize with other translators speaking the same language. 146Each translation team has its own mailing list. The up-to-date list of 147teams can be found at the Free Translation Project's homepage, 148`http://www.iro.umontreal.ca/contrib/po/HTML/', in the "National teams" 149area. 150 151 If you'd like to volunteer to _work_ at translating messages, you 152should become a member of the translating team for your own language. 153The subscribing address is _not_ the same as the list itself, it has 154`-request' appended. For example, speakers of Swedish can send a 155message to `sv-request@li.org', having this message body: 156 157 subscribe 158 159 Keep in mind that team members are expected to participate 160_actively_ in translations, or at solving translational difficulties, 161rather than merely lurking around. If your team does not exist yet and 162you want to start one, or if you are unsure about what to do or how to 163get started, please write to `translation@iro.umontreal.ca' to reach the 164coordinator for all translator teams. 165 166 The English team is special. It works at improving and uniformizing 167the terminology in use. Proven linguistic skill are praised more than 168programming skill, here. 169 170Available Packages 171================== 172 173 Languages are not equally supported in all packages. The following 174matrix shows the current state of internationalization, as of March 1752002. The matrix shows, in regard of each package, for which languages 176PO files have been submitted to translation coordination, with a 177translation percentage of at least 50%. 178 179 Ready PO files bg ca cs da de el en eo es et fi fr 180 +-------------------------------------+ 181 a2ps | [] [] [] [] | 182 bash | [] [] [] [] | 183 bfd | [] [] | 184 binutils | [] [] | 185 bison | [] [] [] | 186 clisp | [] [] [] [] | 187 cpio | [] [] [] [] | 188 diffutils | [] [] [] [] [] [] | 189 enscript | [] [] | 190 error | [] [] | 191 fetchmail | () [] [] [] () | 192 fileutils | [] [] [] [] [] | 193 findutils | [] [] [] [] [] | 194 flex | [] [] [] [] | 195 gas | [] [] | 196 gawk | [] [] | 197 gcal | [] [] | 198 gcc | [] [] | 199 gettext | [] [] [] [] [] | 200 gnupg | [] [] [] [] [] [] | 201 gprof | [] [] | 202 grep | [] [] [] [] [] [] | 203 hello | [] [] [] [] [] [] [] [] | 204 id-utils | [] [] [] | 205 indent | [] [] [] [] [] | 206 jpilot | () [] [] [] | 207 jwhois | [] [] | 208 kbd | [] [] | 209 ld | [] [] | 210 libc | [] [] [] [] [] [] [] | 211 lilypond | [] [] | 212 lynx | [] [] [] [] | 213 m4 | [] [] [] [] [] | 214 make | [] [] [] [] | 215 mysecretdiary | [] [] | 216 nano | [] () [] [] [] [] | 217 nano_1_0 | [] () [] [] [] [] | 218 opcodes | [] [] [] | 219 parted | [] [] [] [] | 220 ptx | [] [] [] [] [] | 221 python | | 222 recode | [] [] [] [] [] [] | 223 sed | [] [] [] [] [] [] [] [] | 224 sh-utils | [] [] [] [] [] [] [] [] | 225 sharutils | [] [] [] [] [] [] | 226 sketch | () [] () | 227 soundtracker | [] [] [] | 228 sp | | 229 tar | [] [] [] [] [] [] | 230 texinfo | [] [] [] [] [] | 231 textutils | [] [] [] [] [] | 232 util-linux | [] [] [] [] | 233 vorbis-tools | | 234 wdiff | [] [] [] [] [] | 235 wget | [] [] [] [] [] [] [] [] | 236 +-------------------------------------+ 237 bg ca cs da de el en eo es et fi fr 238 1 12 11 31 36 9 1 8 39 15 1 50 239 240 gl he hr hu id it ja ko lv nb nl nn 241 +-------------------------------------+ 242 a2ps | () () [] | 243 bash | | 244 bfd | [] | 245 binutils | [] | 246 bison | [] [] | 247 clisp | [] | 248 cpio | [] [] [] | 249 diffutils | [] [] [] | 250 enscript | [] | 251 error | [] | 252 fetchmail | | 253 fileutils | [] [] [] | 254 findutils | [] [] [] [] [] [] | 255 flex | [] | 256 gas | | 257 gawk | [] | 258 gcal | | 259 gcc | | 260 gettext | [] | 261 gnupg | [] [] [] | 262 gprof | | 263 grep | [] | 264 hello | [] [] [] [] [] [] [] [] [] [] | 265 id-utils | [] | 266 indent | [] [] [] | 267 jpilot | () () | 268 jwhois | | 269 kbd | | 270 ld | | 271 libc | [] [] [] [] | 272 lilypond | [] [] | 273 lynx | [] [] | 274 m4 | [] [] [] [] | 275 make | [] [] [] [] | 276 mysecretdiary | | 277 nano | [] [] [] () [] () [] | 278 nano_1_0 | [] [] [] () [] () [] | 279 opcodes | [] | 280 parted | [] [] [] | 281 ptx | [] [] [] [] | 282 python | | 283 recode | [] [] [] | 284 sed | [] [] [] [] [] [] [] | 285 sh-utils | [] [] [] [] [] | 286 sharutils | [] [] [] | 287 sketch | () | 288 soundtracker | [] | 289 sp | | 290 tar | [] [] [] | 291 texinfo | [] [] | 292 textutils | [] [] | 293 util-linux | () [] | 294 vorbis-tools | | 295 wdiff | | 296 wget | [] [] [] [] [] | 297 +-------------------------------------+ 298 gl he hr hu id it ja ko lv nb nl nn 299 19 7 0 4 6 11 22 9 1 8 19 4 300 301 no pl pt pt_BR ru sk sl sv tr uk zh_TW 302 +----------------------------------------+ 303 a2ps | () () () [] [] [] () | 8 304 bash | | 4 305 bfd | [] [] | 5 306 binutils | [] | 4 307 bison | [] [] [] | 8 308 clisp | | 5 309 cpio | [] [] [] [] | 11 310 diffutils | [] [] [] [] [] | 14 311 enscript | [] [] [] | 6 312 error | [] [] [] | 6 313 fetchmail | () () [] | 4 314 fileutils | [] [] [] [] | 12 315 findutils | [] [] [] [] [] [] [] | 18 316 flex | [] [] [] | 8 317 gas | [] | 3 318 gawk | [] [] | 5 319 gcal | [] [] | 4 320 gcc | [] | 3 321 gettext | [] [] [] [] | 10 322 gnupg | [] [] [] | 12 323 gprof | [] [] | 4 324 grep | [] [] [] | 10 325 hello | [] [] [] [] [] [] [] | 25 326 id-utils | [] [] | 6 327 indent | [] [] [] [] | 12 328 jpilot | () () | 3 329 jwhois | () () [] | 3 330 kbd | [] [] | 4 331 ld | [] [] | 4 332 libc | [] [] [] [] [] [] | 17 333 lilypond | [] | 5 334 lynx | [] [] [] | 9 335 m4 | [] [] [] | 12 336 make | [] [] [] [] | 12 337 mysecretdiary | [] [] | 4 338 nano | () [] [] [] [] | 14 339 nano_1_0 | () [] [] [] | 13 340 opcodes | [] [] | 6 341 parted | [] [] [] | 10 342 ptx | [] [] [] [] [] [] | 15 343 python | | 0 344 recode | [] [] [] [] | 13 345 sed | [] [] [] [] [] [] | 21 346 sh-utils | [] [] [] [] [] [] [] [] [] | 22 347 sharutils | [] [] [] | 12 348 sketch | [] () | 3 349 soundtracker | [] | 5 350 sp | | 0 351 tar | [] [] [] [] [] [] [] | 16 352 texinfo | [] [] [] | 10 353 textutils | [] [] [] [] | 11 354 util-linux | [] [] [] | 8 355 vorbis-tools | [] | 1 356 wdiff | [] [] [] [] | 9 357 wget | [] [] [] [] [] [] [] | 20 358 +----------------------------------------+ 359 35 teams no pl pt pt_BR ru sk sl sv tr uk zh_TW 360 55 domains 5 13 2 12 25 11 11 41 34 4 7 489 361 362 Some counters in the preceding matrix are higher than the number of 363visible blocks let us expect. This is because a few extra PO files are 364used for implementing regional variants of languages, or language 365dialects. 366 367 For a PO file in the matrix above to be effective, the package to 368which it applies should also have been internationalized and 369distributed as such by its maintainer. There might be an observable 370lag between the mere existence a PO file and its wide availability in a 371distribution. 372 373 If March 2002 seems to be old, you may fetch a more recent copy of 374this `ABOUT-NLS' file on most GNU archive sites. The most up-to-date 375matrix with full percentage details can be found at 376`http://www.iro.umontreal.ca/contrib/po/HTML/matrix.html'. 377 378Using `gettext' in new packages 379=============================== 380 381 If you are writing a freely available program and want to 382internationalize it you are welcome to use GNU `gettext' in your 383package. Of course you have to respect the GNU Library General Public 384License which covers the use of the GNU `gettext' library. This means 385in particular that even non-free programs can use `libintl' as a shared 386library, whereas only free software can use `libintl' as a static 387library or use modified versions of `libintl'. 388 389 Once the sources are changed appropriately and the setup can handle 390to use of `gettext' the only thing missing are the translations. The 391Free Translation Project is also available for packages which are not 392developed inside the GNU project. Therefore the information given above 393applies also for every other Free Software Project. Contact 394`translation@iro.umontreal.ca' to make the `.pot' files available to 395the translation teams. 396 397