X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=l10n.dbk;h=92bf3b99ba40c7c4b9bc89ea27d37cf02e423a09;hb=e81cdebedab690ef881d87af6f533e51c026565c;hp=dd555864937067e91429c5c898fffbca244bc884;hpb=c81927355fe51c8a09827d098d0caad05a052d67;p=developers-reference.git diff --git a/l10n.dbk b/l10n.dbk index dd55586..92bf3b9 100644 --- a/l10n.dbk +++ b/l10n.dbk @@ -1,7 +1,7 @@ %commondata; + %commondata; ]> Internationalizing, translating, being internationalized and being translated @@ -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.