ABOUT-NLS 18 KB

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