On Sat,22.May.10, 18:35:13, Andrei Popescu wrote: > Hello, > > See attached a proposed patch for the d-i localization manual. The patch ...it generally helps if the patch is really attached :) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From 3a2fdf7c93bf7d4f59ac1631ca68a13cb787734c Mon Sep 17 00:00:00 2001
From: Andrei Popescu <andreimpopescu@gmail.com>
Date: Sat, 22 May 2010 18:24:23 +0300
Subject: [PATCH] several minor fixes, mostly typos
---
appendix/bug-reports.xml | 6 ++--
appendix/language-codes.xml | 2 +-
appendix/methods-advices.xml | 16 ++++++------
appendix/svn-basics.xml | 6 ++--
coordination.xml | 2 +-
language-tasks.xml | 4 +-
localization-config.xml | 2 +-
spellchecking.xml | 44 +++++++++++++++++-----------------
technical/prospective-languages.xml | 2 +-
translators/level1.xml | 34 +++++++++++++-------------
translators/level2.xml | 12 ++++----
translators/translators.xml | 11 ++++++--
12 files changed, 73 insertions(+), 68 deletions(-)
diff --git a/appendix/bug-reports.xml b/appendix/bug-reports.xml
index b86f3af..1d35d00 100644
--- a/appendix/bug-reports.xml
+++ b/appendix/bug-reports.xml
@@ -28,7 +28,7 @@ as &d-i; level 1 translations.
<para>
A <emphasis>bug report</emphasis> is only a special way to send
traceable information which is relevant for a given package. This may
-be a "real" bug report (i.e. something not working properly or as
+be a <quote>real</quote> bug report (i.e. something not working properly or as
expected) as well as an enhancement suggestion or a feature request.
</para>
@@ -73,7 +73,7 @@ translations as well as base-config and tasksel.
<para>
The subject of the bug report should begin by "[INTL:xx]". When the
-package has several translatable material, the subject should mention
+package has several translatable materials, the subject should mention
which translation is sent.
</para>
@@ -119,7 +119,7 @@ named John Doe):
<informalexample>
<screen>
-From: John Does <john.doe@johndoe.com>
+From: John Doe <john.doe@johndoe.com>
To: &email-bts;
Subject: [INTL:tlh] Klingon debconf templates translation
diff --git a/appendix/language-codes.xml b/appendix/language-codes.xml
index a174faa..b1d6202 100644
--- a/appendix/language-codes.xml
+++ b/appendix/language-codes.xml
@@ -58,7 +58,7 @@ used when the two languages differ too much.
<para>
<emphasis>pt/pt_BR</emphasis>: <emphasis>classical</emphasis>
Portuguese is spoken in Portugal as well as nearly all former
- Portugal colonies Brazilian Portuguese largely differs from
+ Portugal colonies. Brazilian Portuguese largely differs from
Portuguese and is of course used in Brazil. Two different
translation sets exist for Debian packages though both teams
work closely together (there is for instance only one mailing
diff --git a/appendix/methods-advices.xml b/appendix/methods-advices.xml
index b2abfdb..9aeaf41 100644
--- a/appendix/methods-advices.xml
+++ b/appendix/methods-advices.xml
@@ -35,7 +35,7 @@ If a translation team exists for a language, translators should
<para>
The list of all available translation teams is available at <ulink
-url="&url-debian-list-archives;i18n.html">&url-debian-list-archives;i18n.html</ulink>
+url="&url-debian-list-archives;i18n.html">&url-debian-list-archives;i18n.html</ulink>.
If in doubt, assistance and help may be requested on the
&email-debian-i18n-list; mailing list.
</para>
@@ -68,7 +68,7 @@ Use peer review
In all translation efforts, peer reviewing is a key point of the
quality assurance process. All translators may introduce errors,
spelling or grammar mistakes in their translations. Thus, reviews by
-another native speakers of the language (even if not familiar with the
+other native speakers of the language (even if not familiar with the
technical background) can help in tracking these down.
</para>
@@ -110,7 +110,7 @@ team.
If this contact is unsuccessful (unresponsive former translator), the
work can be taken over by a new translator, provided this is not
prohibited by a non free licensing (some translators unfortunately put
-statements that make their work non free such as restriction of
+statements that make their work non-free such as restriction of
distribution or restriction of modification).
</para>
@@ -202,16 +202,16 @@ Variables substitutions
In several &d-i; packages, some embedded variable names such as "You
are currently modifying ${PARTITION} properties" can be found.
Translators <emphasis>should not</emphasis> translate the variable
-names and be very careful about keeping braces and "dollar" signs. For
-instance, the French translation of the above is: "Vous modifiez
-actuellement les propriétés de ${PARTITION}".
+names and be very careful about keeping braces and <quote>dollar</quote> signs. For
+instance, the French translation of the above is: <quote>Vous modifiez
+actuellement les propriétés de ${PARTITION}</quote>.
</para>
<para>
When translating programs such as <classname>dpkg</classname>,
<classname>apt</classname> or <classname>shadow</classname>,
-translators should be careful about "%s" variables: the translation
-<emphasis>must</emphasis> have the same number of such variables than
+translators should be careful about <quote>%s</quote> variables: the translation
+<emphasis>must</emphasis> have the same number of such variables as
the original English string.
</para>
diff --git a/appendix/svn-basics.xml b/appendix/svn-basics.xml
index 556e565..6a642c0 100644
--- a/appendix/svn-basics.xml
+++ b/appendix/svn-basics.xml
@@ -11,10 +11,10 @@ account creation pages.
</para>
<para>
-Official Debian developers will probably use the same login than their
+Official Debian developers will probably use the same login as their
Debian login, but must go through the account creation process
-anyway. Non Debian developers should be aware that the login they
-will choose on &alioth; will be followed by "-guest". This has
+anyway. Non-Debian developers should be aware that the login they
+will choose on &alioth; will be followed by <quote>-guest</quote>. This has
absolutely no meaning of any kind of <emphasis>second class
citizens</emphasis> but is just an easy way for &alioth; system
administrators to know who is an official Debian developer.
diff --git a/coordination.xml b/coordination.xml
index 9ae4f1e..15ddb68 100644
--- a/coordination.xml
+++ b/coordination.xml
@@ -20,7 +20,7 @@ tasks:
<listitem>
<para>
reference point for maintainers and &d-i; release
- manageer for all internationalization issues;
+ manager for all internationalization issues;
</para>
</listitem>
<listitem>
diff --git a/language-tasks.xml b/language-tasks.xml
index 4ea0a96..4e0b2ac 100644
--- a/language-tasks.xml
+++ b/language-tasks.xml
@@ -4,7 +4,7 @@
<title>Introduction</title>
<para>
-The <classname>tasksel</classname> package is responsible for installation several <emphasis>package sets</emphasis>, for various activities (desktop, file server, ...).
+The <classname>tasksel</classname> package is responsible for the installation of several <emphasis>package sets</emphasis>, for various activities (desktop, file server, ...).
</para>
<para>
@@ -15,7 +15,7 @@ given language.
</para>
<para>
-These tasks are not meant to be optionnally slected during
+These tasks are not meant to be optionally selected during
<classname>tasksel</classname> runs. Indeed, they are
automatically selected depending on the language used for installation
as well as the type of install.
diff --git a/localization-config.xml b/localization-config.xml
index a6fc6ac..d06d6e5 100644
--- a/localization-config.xml
+++ b/localization-config.xml
@@ -64,7 +64,7 @@ Sending the needed information
<para>
The needed information should be sent as a bug report (severity
-<emphasis>normal</emphasis> against the
+<emphasis>normal</emphasis>) against the
<classname>localization-config</classname> package.
</para>
diff --git a/spellchecking.xml b/spellchecking.xml
index df8cfed..889fc89 100644
--- a/spellchecking.xml
+++ b/spellchecking.xml
@@ -9,10 +9,10 @@ produce statistics usually displayed on a web page. Spotting typos is
the most obvious feature, but translators can use it to improve the
overall quality of their translations.
-Translations are often spread over a bunch on po files translated by
+Translations are often spread over a bunch off po files translated by
different people with different styles even if belonging to the same
-language-team; the spellchecker gathers all of its output in a "per
-language" rather than "per po file" basis, so that each translator
+language-team; the spellchecker gathers all of its output in a <quote>per
+language</quote> rather than <quote>per po file</quote> basis, so that each translator
using it, will check not only his/her own translations.
</para>
</sect1>
@@ -34,16 +34,16 @@ ISO code
<listitem>
<para>
-"Unknown words" - is the number of unique words not found in the
-dictionary of a particular language. "-" , means that the spellchecker
-is not configured as to check translations for this language (usually
+<quote>Unknown words</quote> - is the number of unique words not found in the
+dictionary of a particular language. <quote>-</quote> , means that the spellchecker
+is not configured to check translations for this language (usually
because an aspell dictionary for the language is not available)
</para>
</listitem>
<listitem>
<para>
-"Messages" - contains all the strings for lang extracted from the po
+<quote>Messages</quote> - contains all the strings for lang extracted from the po
files: you can use any spellchecker against this file to look for
typos. This file is very useful also when improving consistency: when
translations are spread over many po files, it is difficult to make sure
@@ -54,23 +54,23 @@ example that "CD-ROM" is written always the same way.
<listitem>
<para>
-"List of unknown words" - is a sorted list of words not found in the
+<quote>List of unknown words</quote> - is a sorted list of words not found in the
aspell dictionary along with the number of occurrences.
</para>
</listitem>
<listitem>
<para>
-"suspect variables" - po files often contain variables ${LIKE_THIS}; a
+<quote>suspect variables</quote> - po files often contain variables ${LIKE_THIS}; a
script checks that the name of the variable in the msgid is matched in
-the msgstr. It's also checked that the number of variables in the
+the msgstr. It is also checked that the number of variables in the
msgstr is the same in the msgid.
</para>
</listitem>
<listitem>
<para>
-"custom wordlist" - translators can write a list of custom words not
+<quote>custom wordlist</quote> - translators can write a list of custom words not
found in the aspell dictionary for their language. More details about
wordlists can be found here (FIXME).
</para>
@@ -78,14 +78,14 @@ wordlists can be found here (FIXME).
<listitem>
<para>
-"all files" - is a tarball containing all the above files. translators
+<quote>all files</quote> - is a tarball containing all the above files. Translators
can download this and work off-line.
</para>
</listitem>
</itemizedlist>
Sometimes columns are followed by a "(*)": it means that the
associated file has changed since the last time the spellchecker was
-run. By clicking on the "(*)" it's possible to see what changed.
+run. By clicking on the "(*)" it is possible to see what changed.
</para>
</sect1>
@@ -95,10 +95,10 @@ run. By clicking on the "(*)" it's possible to see what changed.
<para>
First of all you should look for errors: typically typos or wrong
variables. The list of unknown words contains words not in the aspell
-dictionary and "out of their context"; once one has been found, you
+dictionary and <quote>out of their context</quote>; once one has been found, you
need to locate where the error is in the po file.
-Since "Messages" contains all the (translated) strings for all the po files,
+Since <quote>Messages</quote> contains all the (translated) strings for all the po files,
you can look for the wrong word there; the structure of the text file
is the following:
@@ -122,7 +122,7 @@ takes you directly to the line containing the path. Otherwise you can
search backward for "*** " to find it.
Things can be more complicated if the unknown word is very short and
-so it's matched too many times inside the file because is "sub-word" of
+so it is matched too many times inside the file because it is a <quote>sub-word</quote> of
longer words; in that case you should use regexps to restrict your
search. Here follow a few practical examples that can help you; refer
to some documentation about regexp to find out more.
@@ -131,7 +131,7 @@ If you use emacs you can match an exact word by using
isearch-forward-regexp and "\<word\>"
From the shell you can run 'grep -nw "word" lang_all.txt'
-("n" parameter will tell grep to print the line number where match
+(the "n" parameter will tell grep to print the line number where match
occurs)
Sometimes you may have to look for something like "a word composed
@@ -164,7 +164,7 @@ wrong braces
<listitem>
<para>
-missing "$" character
+missing <quote>$</quote> character
</para>
</listitem>
@@ -176,14 +176,14 @@ different number of variables in the msgid and the msgstr
</itemizedlist>
-the variable name should not be translated in the msgstr and braces
+The variable name should not be translated in the msgstr and braces
should not be changed. The variable name is replaced with something
more useful at run-time; if the translator manipulates it, the results
-will be rather ugly. When original msgid contains multiple occurrences
+will be rather ugly. When the original msgid contains multiple occurrences
of a particular variable, sometimes translators translate the string
as to use the variable just once; the script will report such strings
-as wrong and it's up to the translator to check if it's a mistake or
-not (this is the main reason for calling them "suspect variables").
+as wrong and it is up to the translator to check if it is a mistake or
+not (this is the main reason for calling them <quote>suspect variables</quote>).
</para>
</sect1>
diff --git a/technical/prospective-languages.xml b/technical/prospective-languages.xml
index eaee1b6..aee76bf 100644
--- a/technical/prospective-languages.xml
+++ b/technical/prospective-languages.xml
@@ -21,7 +21,7 @@ incomplete translation.
Prospective languages are kept in the file
<filename>packages/po/PROSPECTIVE</filename> along with the master po
files. Translators can continue translating, but the translations will
-be kept back and not spreaded into packages by the synchronisation
+be kept back and not spread into packages by the synchronisation
script (see <xref linkend="synchronisation-scripts"/>).
</para>
diff --git a/translators/level1.xml b/translators/level1.xml
index 9614a62..9bca1e2 100644
--- a/translators/level1.xml
+++ b/translators/level1.xml
@@ -11,7 +11,7 @@ Contents
</title>
<para>
-Level 1 consists of all "core" &d-i; packages, i.e. all packages with
+Level 1 consists of all <quote>core</quote> &d-i; packages, i.e. all packages with
translatable material in the &d-i; development tree.
</para>
@@ -40,11 +40,11 @@ Sublevels
</title>
<para>
-In the past, all &d-i; level 1 strings were gathered into a single "master" file. While that was easy to manage, it had the inconvenience of grouping very important and often used strings with very obscure strings that are relevant for some architectures only, or some special (and rarely used) features.
+In the past, all &d-i; level 1 strings were gathered into a single <quote>master</quote> file. While that was easy to manage, it had the inconvenience of grouping very important and often used strings with very obscure strings that are relevant for some architectures only, or some special (and rarely used) features.
</para>
<para>
-In order for translators to better prioritize their work, this master file has been splitted into five "sublevel" files:
+In order for translators to better prioritize their work, this master file has been split into five <quote>sublevel<quote> files:
</para>
<itemizedlist>
@@ -232,13 +232,13 @@ This script will output the offending line(s) number(s) as well as the number of
<sect3>
<title>
-"Choose language" menu entry
+<quote>Choose language</quote> menu entry
</title>
<para>
This entry is the language selection screen entry for each
-language. Translators can translate it but they should keep "Choose
-language" in English as an alternative so that users mistakenly
+language. Translators can translate it but they should keep <quote>Choose
+language</quote> in English as an alternative so that users mistakenly
choosing a language can still find the appropriate entry to change it
back to their own language.
</para>
@@ -252,11 +252,11 @@ Main menu entries
<para>
Most &d-i; packages have a main menu entry, which is the text that appears
-in the &d-i; main menu to allow users to select the orresponding action.
+in the &d-i; main menu to allow users to select the corresponding action.
</para>
<para>
-The length of this main menu entry is limited to 58 columns, ie 58 characters
+The length of this main menu entry is limited to 58 columns, i.e. 58 characters
for single-width languages and only 29 characters for double-width languages.
These main menu entries all have a comment with <quote>Main menu item</quote> in the PO and POT files.
</para>
@@ -269,22 +269,22 @@ Variable names
</title>
<para>
-Many places in &d-i; use variables (e.g. "${LOCALE} is currently not
-supported in Debian"). The variable names should <emphasis>not be
+Many places in &d-i; use variables (e.g. <quote>${LOCALE} is currently not
+supported in Debian</quote>). The variable names should <emphasis>not be
translated</emphasis> and be kept inside braces prepended by the
dollar sign in the translation.
</para>
<para>
-This constraint is checked by the spell checking scripts which report
+This constraint is checked by the spell checking scripts, which report
these errors separately (see <xref linkend="spellchecking"/> for
details about the spell checking scripts).
</para>
<para>
-Advanced translation software such as <command>kbabel</command> are
-able to visually display such errors and warn about them before saving
-files.
+Advanced translation software such as <command>kbabel</command> (renamed
+to <command>lokalize</command> in KDE4) are able to visually display such
+errors and warn about them before saving files.
</para>
</sect3>
@@ -295,7 +295,7 @@ Choices entries
</title>
<para>
-Several entries in PO files are unsplitted choices list such as:
+Several entries in PO files are unsplit choices lists such as:
</para>
<informalexample>
@@ -311,7 +311,7 @@ msgstr ""
<para>
For these translations, translators should take care of separating all
choices with a normal comma sign, even if commas are not used in their
-language. Only standard commas should be used and not special commans
+language. Only standard commas should be used and not special commas
such as those used by the Arabic language.
</para>
@@ -362,7 +362,7 @@ is intended to setup the default Debian archive mirror country,
depending on the language. Translators should put there the ISO-3166
code of the country to be used as default, most often their own
country name, or the country their language is spoken in. For
-instance, the Brazilian Portuguese translator will use "BR" as
+instance, the Brazilian Portuguese translator will use <quote>BR</quote> as
translation there, as this is the ISO-3166 code for Brazil.
</para>
diff --git a/translators/level2.xml b/translators/level2.xml
index bc14d27..0c53921 100644
--- a/translators/level2.xml
+++ b/translators/level2.xml
@@ -150,13 +150,13 @@ translations.
</listitem>
<listitem>
<para>
-<filename>debian/po/templates.pot</filename> : text of the screen shown to users. These files are named <emphasis>debconf</emphasis>
+<filename>debian/po/templates.pot</filename>: text of the screen shown to users. These files are named <emphasis>debconf</emphasis>
translations.
</para>
</listitem>
<listitem>
<para>
-<filename>po/tasksel.pot</filename> : messages displayed by the
+<filename>po/tasksel.pot</filename>: messages displayed by the
program. These files are named <emphasis>program</emphasis>
translations.
</para>
@@ -169,7 +169,7 @@ Access to these files:
<itemizedlist>
<listitem>
-<acronym>GIT</acronym> access: &git-tasksel;
+<acronym>GIT</acronym> access: &git-tasksel; (documenting how to use GIT is way out of the scope of this document)
</listitem>
<listitem>
<para>
@@ -338,12 +338,12 @@ Specific recommendations
</title>
<para>
-The ISO-3166 list includes all <emphasis>countries, regions are areas of
+The ISO-3166 list includes all <emphasis>countries, regions and areas of
specific geopolitical interest</emphasis> in the world. Translators
should be aware that this translation is far from being a trivial
work and may very quickly turn into some deep and complicated
political difficulties. The original English names are those used
-officially by the relevant countries to design themselves. Please make
+officially by the relevant countries to designate themselves. Please make
your best for staying as neutral and close to these names as
possibles. Some countries Foreign Affairs (or equivalent) ministries
keep lists of <emphasis>country</emphasis> names translations in their
@@ -577,7 +577,7 @@ it.
<itemizedlist>
<listitem>
-<acronym>GIT</acronym> access: &git-eject; (documenting how to use GIT is way out of scope of this document)
+<acronym>GIT</acronym> access: &git-eject;
</listitem>
<listitem>
<para>
diff --git a/translators/translators.xml b/translators/translators.xml
index 3c19dfc..7285968 100644
--- a/translators/translators.xml
+++ b/translators/translators.xml
@@ -51,13 +51,18 @@ level contents.
<orderedlist>
<listitem>
<para>
- level 1: all core &d-i; packages;. This level is splitted
- in five "sublevels" by order of strings priority (sublevel 1 groups together the strings used in all default installs while sublevel 5 groups together very rare strings used only for uncommon architectures).
+ level 1: all core &d-i; packages;
+ </para>
+ <para>
+ This level is split in five "sublevels" by order of strings
+ priority (sublevel 1 groups together the strings used in all
+ default installs while sublevel 5 groups together very rare
+ strings used only for uncommon architectures).
</para>
</listitem>
<listitem>
<para>
- level 2: all non core &d-i; material involved for
+ level 2: all non-core &d-i; material involved for
user interaction screens during a <emphasis>default
priority</emphasis> installation of a Debian base
system with default choices;
--
1.7.1
Attachment:
signature.asc
Description: Digital signature