X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=l10n.dbk;h=a089e64b2406f5a2c491de02a914e6ae6a493fff;hp=92bf3b99ba40c7c4b9bc89ea27d37cf02e423a09;hb=d29e265025706f0a590a033db78d18b0d8313120;hpb=9c55352f61aeb85e523b2f2347b43533f7aeb1f7 diff --git a/l10n.dbk b/l10n.dbk index 92bf3b9..a089e64 100644 --- a/l10n.dbk +++ b/l10n.dbk @@ -4,7 +4,7 @@ %commondata; ]> -Internationalizing, translating, being internationalized and being translated +Internationalization and Translations Debian supports an ever-increasing number of natural languages. Even if you are a native English speaker and do not speak any other language, it is part of @@ -15,7 +15,7 @@ programs, you should read most of this chapter. According to Introduction to +url="&url-i18n-intro;">Introduction to i18n from Tomohiro KUBOTA, I18N (internationalization) means modification of a software or related technologies so that a software can potentially handle multiple languages, customs, and so on in the world, while @@ -45,12 +45,12 @@ task, and the process depends on the kind of text you want to see translated. For program messages, the gettext infrastructure is used most of the time. Most of the time, the translation is handled upstream within projects like the -Free Translation +Free Translation Project, the Gnome translation -Project or the KDE one. The +url="&url-l10n-gnome;">Gnome translation +Project or the KDE one. The only centralized resource within Debian is the Central Debian translation +url="&url-l10n;">Central Debian translation statistics, where you can find some statistics about the translation files found in the actual packages, but no real infrastructure to ease the translation process. @@ -60,23 +60,24 @@ An effort to translate the package descriptions started long ago, even if very little support is offered by the tools to actually use them (i.e., only APT can use them, when configured correctly). Maintainers don't need to do anything special to support translated package descriptions; translators should use the -DDTP. +Debian Description Translation Project (DDTP). -For debconf templates, maintainers should use the po-debconf package to ease +For debconf templates, maintainers +should use the po-debconf package to ease the work of translators, who could use the DDTP to do their work (but the French and Brazilian teams don't). Some statistics can be found both on the -DDTP site (about what is actually translated), and on the Central Debian translation +DDTP site (about what is actually translated), +and on the Central Debian translation statistics site (about what is integrated in the packages). -For web pages, each l10n team has access to the relevant CVS, and the +For web pages, each l10n team has access to the relevant VCS, and the statistics are available from the Central Debian translation statistics site. For general documentation about Debian, the process is more or less the same as -for the web pages (the translators have access to the CVS), but there are no +for the web pages (the translators have access to the VCS), but there are no statistics pages. @@ -89,7 +90,7 @@ same way as its program messages. There is an effort to handle Debian-specific man pages within a specific CVS +url="&url-cvsweb;manpages/?cvsroot=debian-doc">specific VCS repository. @@ -106,7 +107,7 @@ your feedback, so that this document can be enhanced.
How to get a given text translated -To translate package descriptions or debconf templates, you have nothing to do; +To translate package descriptions or debconf templates, you have nothing to do; the DDTP infrastructure will dispatch the material to translate to volunteers with no need for interaction from your part. @@ -207,7 +208,7 @@ from running. As a maintainer, never edit the translations in any way (even to reformat the layout) without asking on the corresponding l10n mailing list. You risk for -example breaksing the encoding of the file by doing so. Moreover, what you +example breaking the encoding of the file by doing so. Moreover, what you consider an error can be right (or even needed) in the given language.