From 46ea7192f23ae7de4755e9502a86a61da8dd3397 Mon Sep 17 00:00:00 2001 From: "Paul W. Frields" Date: Thu, 10 Apr 2008 02:34:36 +0000 Subject: Add L10n chapter to DocGuide (#441190) --- en_US/documentation-guide.xml | 10 +-- en_US/l10n.xml | 164 ++++++++++++++++++++++++++++++++++++++++++ en_US/rpm-info.xml | 5 ++ 3 files changed, 174 insertions(+), 5 deletions(-) create mode 100644 en_US/l10n.xml (limited to 'en_US') diff --git a/en_US/documentation-guide.xml b/en_US/documentation-guide.xml index e2472aa..6c63948 100644 --- a/en_US/documentation-guide.xml +++ b/en_US/documentation-guide.xml @@ -1,5 +1,5 @@ - + %FEDORA-ENTITIES-EN; - - - - ]> @@ -67,6 +63,10 @@ + + + diff --git a/en_US/l10n.xml b/en_US/l10n.xml new file mode 100644 index 0000000..98aee7d --- /dev/null +++ b/en_US/l10n.xml @@ -0,0 +1,164 @@ + + + + +%FEDORA-ENTITIES-EN; + +]> + + + Localization (L10n) + + This chapter discusses how translations are provided in &DISTRO; + documentation. + +
+ PO Files + + The cornerstone of translation when using XML files such as + DocBook is the Portable Object or + PO file. PO files provide a way for + independent individuals or teams to translate documents. The + &FDP; toolchain includes rules for creating, updating, and + maintaining these PO files. + + + PO files are usually found in two forms: + + + + + the .pot file, or + PO Template (POT) + + + + + + + the .po file, or + translation file (PO) + + + + + A POT is, as the name suggests, a blank template for new + translations. It contains some header information and a list of + strings based on the content of the original XML file from which + it was created. Translators do not alter the POT. The POT + should only be changed after changes are made to the original + XML file from which it is derived. + + + A translator who wishes to start working on a new language + copies the POT to a locale-specific PO file. Then the + translator uses any of a number of command-line or graphical + tools to translate each of the strings in the list. A single + POT is used to create many POs, one for each locale. These + files are normally named for their locale code, such as + de.po, it.po, and so + on. + +
+
+ Creating or Updating a POT + + The POT is named after the document from which it is derived. + If document named in the Makefile) is + foo-tutorial.xml, the POT is named + foo-tutorial.pot. + + + To create a new POT, use the following command: + + + + The same command is used to update the POT when the original XML + sources change. + + + Keep POT Fresh + + Update the POT whenever the original XML changes. Many + translators' tools automatically notify them of the change so + they can update translations quickly. + + +
+
+ Updating PO Files + + The translation files are created by the individual translators, + and document maintainers do not normally need to create them. + Translators update a list of locales in the + po/LINGUAS file which defines all the + locales for which translations exist. + + + Whenever the source XML files are updated, the maintainer must + at least update the POT. It is helpful, however, to also merge + these changes with the existing translations for those + translators who are not automatically notified of changes. + + + Staying Current + + Always make sure your local copy of PO is fresh, using the CVS + "update" command: + + + + + To merge new changes into the existing PO translations, use the + following command: + + +
+
+ Checking Statistics + + PO strings fall into three categories: + + + + + translated, meaning the string has + been handled by a translator and its source has not changed + since then + + + + + fuzzy, meaning the string has changed + since it was last handled by a translator + + + + + untranslated, meaning no translation + has yet been provided for this string, or it is brand new + + + + + To see a rough statistical tally of the string handling inside + the PO for a module, use the following command: + + + + For each locale in the list, a count is shown of translated, + fuzzy, and untranslated strings in that order. Tallies that + only provide two numerals are usually translated followed by + untranslated. Tallies with only one numeral are usually fully + translated. + + + To see only a specific locale, append a dash and the locale code + to the postat target: + + +
+ diff --git a/en_US/rpm-info.xml b/en_US/rpm-info.xml index a0aad61..221a806 100644 --- a/en_US/rpm-info.xml +++ b/en_US/rpm-info.xml @@ -28,11 +28,16 @@ 2005 2006 2007 + 2008 Red Hat, Inc. and others Fedora Documentation Guide Guidelines and procedures for producing documentation for Fedora + + +
Add L10n chapter (#441190)
+
Fix some organization and missing targets (#371531)
-- cgit