X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=l10n.dbk;h=e87276dc1fbcb0032496afeca7d6fd4570bd9ae8;hb=bafa67a2c7b794d78396cf18f8d8e44d3160e3ac;hp=dd555864937067e91429c5c898fffbca244bc884;hpb=c81927355fe51c8a09827d098d0caad05a052d67;p=developers-reference.git diff --git a/l10n.dbk b/l10n.dbk index dd55586..e87276d 100644 --- a/l10n.dbk +++ b/l10n.dbk @@ -1,10 +1,10 @@ %commondata; + %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 @@ -18,7 +18,7 @@ According to 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 +potentially handle multiple languages, customs, and so on in the world, while L10N (localization) means implementation of a specific language for an already internationalized software. @@ -33,7 +33,7 @@ character encodings is a really hard problem. Setting aside the i18n problems, where no general guideline can be given, there is actually no central infrastructure for l10n within Debian which could be -compared to the dbuild mechanism for porting. So most of the work has to be +compared to the buildd mechanism for porting. So most of the work has to be done manually.