Commit 39b160b5 authored by Holger Wansing's avatar Holger Wansing

Update/proofreading on 'd-i i18n + l10n guide'

parent 8d037e2f
......@@ -10,7 +10,7 @@
-->
<!ENTITY alioth "alioth.debian.org">
<!ENTITY url-alioth "http://&alioth;/">
<!ENTITY url-alioth "https://&alioth;/">
<!ENTITY alioth-account-page '<ulink url="https://alioth.debian.org/account">https://alioth.debian.org/account</ulink>'>
<!ENTITY svn-debian-auth "&lt;alioth_username&gt;@svn.debian.org">
......@@ -23,7 +23,7 @@
<!ENTITY irc-channel "#debian-boot on &irc-server;">
<!ENTITY backports "backports.debian.org">
<!ENTITY url-backports "http://&backports;/">
<!ENTITY url-backports "https://&backports;/">
<!ENTITY url-status "https://d-i.debian.org/l10n-stats">
......@@ -92,22 +92,22 @@
<!ENTITY git-espeakup "git clone ssh://&git-debian;/git/pkg-a11y/espeakup.git">
<!-- Wiki page for fonts -->
<!ENTITY wiki-fonts "http://wiki.debian.org/DebianInstaller/GUIFonts">
<!ENTITY wiki-fonts "https://wiki.debian.org/DebianInstaller/GUIFonts">
<!ENTITY url-bts "http://bugs.debian.org/">
<!ENTITY url-bts "https://bugs.debian.org/">
<!ENTITY email-bts " <email>submit@bugs.debian.org</email>">
<!ENTITY email-debian-boot-list "<email>debian-boot@lists.debian.org</email>">
<!ENTITY email-debian-i18n-list "<email>debian-i18n@lists.debian.org</email>">
<!ENTITY url-debian-list-archives "http://lists.debian.org/">
<!ENTITY url-debian-list-archives "https://lists.debian.org/">
<!ENTITY url-debian-l10n "http://www.debian.org/intl/l10n/">
<!ENTITY url-debian-l10n "https://www.debian.org/intl/l10n/">
<!ENTITY url-tp "http://www.translationproject.org/">
<!ENTITY url-tp "https://www.translationproject.org/">
<!-- Keep this comment at the end of the file
Local variables:
......
......@@ -33,7 +33,7 @@ expected) as well as an enhancement suggestion or a feature request.
</para>
<para>
Debian bug reports are handled through a web and email
Debian bug reports are handled through a web and e-mail
interface. Access to the bug reports can be made through the BTS web
site: &url-bts;.
</para>
......@@ -72,7 +72,7 @@ translations as well as base-config and tasksel.
</para>
<para>
The subject of the bug report should begin by "[INTL:xx]". When the
The subject of the bug report should start with "[INTL:xx]". When the
package has several translatable materials, the subject should mention
which translation is sent.
</para>
......@@ -93,7 +93,7 @@ Generic method to send bug reports
<para>
Reporting a bug to a Debian package is just sending a specially
written mail to &email-bts;.
formatted mail to &email-bts;.
</para>
<para>
......@@ -179,7 +179,7 @@ mode standard
ui text
# offline setting - comment out to be online
#offline
# name and email setting (if non-default)
# name and e-mail setting (if non-default)
realname "John Doe"
email "johndoe@johndoe.com"
# You can add other settings after this line. See
......
<appendix id="checkouts"><title>Checkout commands</title>
<sect1>
<title>Translation checkout commands for d-i</title>
</sect1>
<para>
First said, translators don't need to checkout the repositories by
hand to translate the po files. They can get all files here:
......
......@@ -35,7 +35,7 @@ running <command>apt-get install &lt;package&gt;</command>.
message catalogs editor and its use is recommended by the
&i18n-coords;. Its support for non-Latin languages is very
complete, including correct Right-To-Left (RTL) and BiDi support
For Arabic/Hebrew and other RTL languages as well as support for
for Arabic/Hebrew and other RTL languages as well as support for
combined languages such as languages using the Devanagari script.
</para>
<para>
......@@ -145,7 +145,7 @@ idea on how their translation will look like, particularly the screens
length (use this utility on a usual 80x25 terminal). But as cdebconf
and debconf displays slightly differ, and as some scripts do heavy use
of text substitution, one should not fully rely on this program. Running
debian-installer is the only solution to test translations.
debian-installer is the only reliable solution to test your translation.
</para>
<para>
......
......@@ -29,8 +29,8 @@ If a translation team exists for a language, translators should
<emphasis>work with them</emphasis>. They should first check the
<email>debian-l10n-&lt;language&gt;</email> mailing list where
&lt;language&gt; is the language name in English
(e.g. <email>debian-l10n-polish</email>,
<email>debian-l10n-portuguese</email>, etc.)
(e.g. <email>debian-l10n-polish@lists.debian.org</email>,
<email>debian-l10n-portuguese@lists.debian.org</email>, etc.)
</para>
<para>
......
......@@ -29,34 +29,8 @@ Installing <acronym>SVN</acronym>
<para>
Translators and other &d-i; contributors need to install <acronym>SVN</acronym>
(Subversion) on their system. For Debian <emphasis>sid</emphasis> or
<emphasis>sarge</emphasis> users, just do <command>aptitude install
subversion</command>. Users of Debian <emphasis>woody</emphasis>
release may use backports from &backports;. The following entry to
<filename>/etc/apt/sources.list</filename> may be used for this:
</para>
<informalexample>
<screen>
deb &url-backports;debian stable subversion
</screen>
</informalexample>
<para>
Alternatively, Adam Conrad's backports may be used:
</para>
<informalexample>
<screen>
deb http://people.debian.org/~adconrad woody subversion
</screen>
</informalexample>
<para>
These backports are not officially supported by the Debian
Project. Though their maintainers are well-known and respected Debian
developers, they're the only people who can guarantee that these packages
are well maintained and secured.
(Subversion) on their system. Just do <command>aptitude install
subversion</command>.
</para>
<para>
......@@ -66,7 +40,7 @@ list.
</para>
<para>
For MS-Windows users, a good <acronym>SVN</acronym> client is <emphasis>TortoiseSVN</emphasis> which is free software. It can be downloaded from <ulink url="http://tortoisesvn.tigris.org/">http://tortoisesvn.tigris.org/</ulink>.
For MS-Windows users, a good <acronym>SVN</acronym> client is <emphasis>TortoiseSVN</emphasis>, which is free software. It can be downloaded from <ulink url="http://tortoisesvn.tigris.org/">http://tortoisesvn.tigris.org/</ulink>.
</para>
<para>
......@@ -96,7 +70,7 @@ name before using the SVN pseudo-URLS.
</para>
<para>
<filename>svn+ssh</filename> connections need that you use RSA key-based authentication to connect to &alioth;.
<filename>svn+ssh</filename> connections require you to use RSA key-based authentication to connect to &alioth;.
</para>
<para>
......@@ -249,10 +223,10 @@ user@host:~/level1-po> lokalize fr.po
.../...
</screen>
<para>
(use Lokalize or any other gettext utility, see <xref linkend="gettext-tools"/> for details about gettext files handling, editing and maintenance tools)
(Use Lokalize or any other gettext utility, see <xref linkend="gettext-tools"/> for details about gettext files handling, editing and maintenance tools.)
</para>
<para>
Once saved the modified version of the file, the status can be
Once you have saved the modified version of the file, the status can be
displayed with the <command>svn status</command> command:
</para>
<screen>
......@@ -268,9 +242,9 @@ modifications. These modifications can be committed by using the <command>svn co
user@host:~/level1-po> svn commit
</screen>
<para>
The user will then be dropped in a file editor (either
The user will then be dropped into a file editor (either
<command>vi</command> or any other file editor pointed by the EDITOR
variable. The changelog message can be then filled in the
variable. The changelog message can then be typed in the
editor. Saving it and exiting the editor will trigger the commit
action to the <acronym>SVN</acronym> repository.
</para>
......
......@@ -19,7 +19,7 @@ git repository</ulink>.
</abstract>
<copyright>
<year>2001-2010</year>
<year>2001-2017</year>
<holder>the &d-i; team</holder>
<holder>Petter Reinholdtsen</holder>
<holder>Dennis Stampfer</holder>
......
......@@ -69,7 +69,7 @@ tasks:
<para>
improves the framework to make the translators
life easy (status pages, spellchecking
framework;
framework);
</para>
</listitem>
<listitem>
......
......@@ -27,7 +27,7 @@ be automatically installed.
</para>
<para>
<emphasis>Language tasks</emphasis> are separated in two type of tasks: the <emphasis>&language;</emphasis> task and the <emphasis>&language;-desktop</emphasis> task. The former is installed for every standard system install while the latter is only installed if the <emphasis>desktop</emphasis> tasks is selected by the user (the <emphasis>desktop</emphasis> task installs a basic graphical environment, which can be completed with the <emphasis>Gnome</emphasis> or <emphasis>KDE</emphasis> tasks.
<emphasis>Language tasks</emphasis> are separated in two type of tasks: the <emphasis>&language;</emphasis> task and the <emphasis>&language;-desktop</emphasis> task. The former is installed for every standard system install while the latter is only installed if the <emphasis>desktop</emphasis> tasks is selected by the user (the <emphasis>desktop</emphasis> task installs a basic graphical environment, which can be completed with the <emphasis>Gnome</emphasis> or <emphasis>KDE</emphasis> tasks).
</para>
</sect1>
......@@ -57,22 +57,22 @@ Documentation about using Linux or &debian; in &language;;
</listitem>
<listitem>
<para>
Dictionaries or word lists for &language;
Dictionaries or word lists for &language;;
</para>
</listitem>
<listitem>
<para>
Set of manual pages translated in &language;
Set of manual pages translated in &language;;
</para>
</listitem>
<listitem>
<para>
Console input methods for &language;
Console input methods for &language;;
</para>
</listitem>
<listitem>
<para>
Console fonts for &language;
Console fonts for &language;;
</para>
</listitem>
<listitem>
......@@ -111,7 +111,7 @@ Appropriate choices for such task are:
<listitem>
<para>
Localization packages for packages which are included in the
<emphasis>desktop</emphasis> task
<emphasis>desktop</emphasis> task;
</para>
</listitem>
<listitem>
......@@ -121,7 +121,7 @@ Fonts useful for the display of &language;;
</listitem>
<listitem>
<para>
Special input methods for &language; in a graphical environment
Special input methods for &language; in a graphical environment;
</para>
</listitem>
<listitem>
......
......@@ -331,7 +331,7 @@ Review changes to existing templates
<para>Some peer review is strongly suggested when changing existing debconf templates and the changes are significant enough to motivate a peer review (maintainers should be aware that even minor changes might be inconsistent with the &d-i; writing style, so in doubt, any change should be considered as significant enough).</para>
<para>
In such case, it is recommended to first duplicate the existing template, with another name (for instance, the former name followed by <emphasis>_save</emphasis>.
In such case, it is recommended to first duplicate the existing template, with another name (for instance, the former name followed by <emphasis>_save</emphasis>).
</para>
<para>The changed template is then unmarked for translation (by removing the leading "_" character) and a review may be requested in the mailing list.
......@@ -417,11 +417,7 @@ chosen so that it matches only the occurrence that is changed.
<para>
The <classname>po4a</classname> package maintainers have written a
special tool named <command>msguntypot</command> to handle
such<emphasis>preventive unfuzzyfication</emphasis>. This utility will
soon (at the moment of this writing) be included in the
<classname>po4a</classname> package as it needs some of its Perl
modules. In the meantime, maintainers may ask for it to the
&i18n-coords;.
such <emphasis>preventive unfuzzyfication</emphasis>.
</para>
<para>
......
......@@ -6,6 +6,8 @@
<para>
The main page for internationalization of the installation manual is
<ulink url="https://d-i.alioth.debian.org/manual/">https://d-i.alioth.debian.org/manual/</ulink>.
It contains links to preview variants of the manual in the available languages as well as some
documentation and statistics.
</para>
</sect1>
......
......@@ -30,7 +30,7 @@ First contact with &d-i; development team
</title>
<para>
Translators or translation teams of a non supported language should contact the &d-i; i18n coordination team (see <xref linkend="coordination-team"/>). They should provide a real
Translators or translation teams of a not supported language should contact the &d-i; i18n coordination team (see <xref linkend="coordination-team"/>). They should provide a real
name (the Debian Project encourages the use of real names) and
possibly a GPG key (this is not mandatory but could help in the
future).
......@@ -45,7 +45,7 @@ steps is a very important step to quickly establish a strong relation with ident
<para>
The &i18n-coords; must have
the real name and a reliable email address of at least one translator
the real name and a reliable e-mail address of at least one translator
who must be an individual. This individual will be called the
<emphasis>language coordinator</emphasis> for the given language.
</para>
......@@ -122,7 +122,7 @@ can be provided.
</listitem>
<listitem>
<para>
<userinput>coord_email</userinput>: language coordinator email
<userinput>coord_email</userinput>: language coordinator e-mail
</para>
</listitem>
<listitem>
......@@ -154,7 +154,7 @@ describes specifics of the German language in Austria.
</para>
<para>
Informations included in a locale:
Information included in a locale:
</para>
<itemizedlist>
<listitem>
......@@ -210,7 +210,7 @@ The writer of a locale must use the locale files format. The contents
of this file must be in UTF-8. Translators shouldn't be afraid by
this: this part may be handled by a i18n specialist in Debian, most
often one of the &i18n-coords;. The new translator(s) will only need
to provide him/her the above informations when (s)he will need it.
to provide him/her the above informations when (s)he asks for it.
</para>
<para>
......@@ -282,8 +282,8 @@ Localechooser entry
<para>
First needed is having the new language added to
<classname>localechooser</classname> (the package responsible for
choosing language at the very beginning of the Debian Installer
process) This will be handled by the &i18n-coords;.
choosing language at the very beginning of a Debian installation).
This will be handled by the &i18n-coords;.
</para>
<para>
......@@ -311,17 +311,17 @@ Latin-1 console (several serial terminals). This includes so-called <emphasis>La
<listitem>
<para>
<emphasis>Category 2</emphasis>: languages that can be rendered et the Linux text console, without needeing a framebuffer terminal.
<emphasis>Category 2</emphasis>: languages that can be rendered at the Linux text console, without the need of a framebuffer terminal.
</para>
</listitem>
<listitem>
<para>
<emphasis>Category 3</emphasis>: languages that can be rendered et the Linux text console, only by using a framebuffer terminal. The
<emphasis>Category 3</emphasis>: languages that can be rendered at the Linux text console only by using a framebuffer terminal. The
key point for these languages is the availability of their glyphs in
the <classname>bterm-unifont</classname> package. These languages should
also not need complex rendering mechanisms such as combination
mechanisms. The difference with 2 is the possibility to display the language
mechanisms. The difference against Category 2 is the possibility to display the language
at the Linux console without framebuffer.
</para>
</listitem>
......@@ -395,7 +395,7 @@ reasonably sized alphabet.
<para>
It is allowed to add characters that can be entered directly using a
"standard" keyboard for the language and are printed on the tops of keys,
"standard" keyboard for the language and are printed on the keys,
for example as displayed on http://en.wikipedia.org/wiki/Keymap. This
includes characters accessible through AltGr and characters that can be
created using dead keys.
......@@ -430,7 +430,7 @@ value to <emphasis>needed_characters</emphasis>.
</para>
<para>
For font switch support in the bare Linux console, the language coordinator must
For font switching support in the bare Linux console, the language coordinator must
also provide which <classname>console-setup</classname> font should be used, to
be recorded in its <classname>debian/font-switch</classname> script.
</para>
......@@ -502,7 +502,7 @@ Account creation on Alioth
All &d-i; work is maintained in a centralized revision control system,
using <acronym>SVN</acronym>. For translators not familiar with
<acronym>SVN</acronym>, <xref linkend="svn-basics"/> will give them
enough information for them to be able to commit their translations
enough information to be able to commit their translations
themselves.
</para>
......@@ -634,7 +634,7 @@ value to <emphasis>mailing_list</emphasis>.
</para>
<para>
Optionnally, translators may subscribe to the &email-debian-boot-list; which is the development mailing list for &d-i;. Topics there are more technical but will allow translators to participate more deeply in &d-i; development.
Optionally, translators may subscribe to the &email-debian-boot-list; which is the development mailing list for &d-i;. Topics there are more technical but will allow translators to participate more deeply in &d-i; development.
</para>
<para>
......@@ -652,7 +652,7 @@ Announcement of the translation effort
When a new translation effort is started, the language coordinator
must announce it in the &email-debian-boot-list; mailing list so
that all &d-i; developers are aware of the new translation effort. A
short personal introduction will be appreciated, even if no
short personal introduction will be appreciated, even if not
mandatory. The &d-i; development team is a real team whose members
appreciate working together in a friendly environment.
</para>
......@@ -676,7 +676,7 @@ Finally, a new entry will be added to the file used by the scripts which generat
</para>
<para>
The new language process officially finishes here. The only work that's left to do is...translating.
The new language process officially finishes here. The only work that's left to do is ... translating.
</para>
</sect1>
......@@ -690,7 +690,7 @@ Follow the &d-i; development
Subscription to the &d-i; development list (&email-debian-boot-list;)
is also encouraged though not mandatory. This list has a traffic of
about 20-30 mails per day, including many administrivia mails
(packages uploads or bugs reports), but is the best method for being
(packages uploads or bug reports), but is the best method for being
involved in &d-i; development.
</para>
......
......@@ -115,7 +115,7 @@ is the following:
- "strings for this file"
</screen>
if the word is easy to find you won't need any help from me to locate
If the word is easy to find you won't need any help from me to locate
it and you just need to see which po file it belongs to. Emacs has a
very handy function "forward-paragraph" (ctrl-up on my system) that
takes you directly to the line containing the path. Otherwise you can
......@@ -128,11 +128,11 @@ search. Here follow a few practical examples that can help you; refer
to some documentation about regexp to find out more.
If you use emacs you can match an exact word by using
isearch-forward-regexp and "\&lt;word\&gt;"
isearch-forward-regexp and "\&lt;word\&gt;".
From the shell you can run 'grep -nw "word" lang_all.txt'
(the <quote>n</quote> parameter will tell grep to print the line number where match
occurs)
(the <quote>n</quote> parameter will tell grep to print the line number where the match
occurs).
Sometimes you may have to look for something like "a word composed
by two letters: the first is "p" the second is not a printable char";
......
......@@ -39,7 +39,7 @@ Activate language in localechooser
</title>
<para>
The language should be activated in the <classname>localechooser</classname> package. For this, the language entry in the <filename>languagelist</filename> shoul be uncommented and the <classname>localechooser</classname> must be rebuilt and uploaded.
The language should be activated in the <classname>localechooser</classname> package. For this, the language entry in the <filename>languagelist</filename> should be uncommented and the <classname>localechooser</classname> must be rebuilt and uploaded.
</para>
</sect2>
......@@ -63,7 +63,7 @@ Tasks related to the new language should be considered for addition in tasksel (
</para>
<para>
These tasks should also be added in the <filename>tasks.list</filename> file of the <classname>debian-cd</classname> package so that CD or DVD prioritize the task's components for inclusion on first CDs or DVDs</para>
These tasks should also be added in the <filename>tasks.list</filename> file of the <classname>debian-cd</classname> package so that CD or DVD prioritize the task's components for inclusion on first CDs or DVDs.</para>
</sect2>
......
......@@ -397,7 +397,7 @@ every Debian system as it is part of what is called the
This package installs scripts which periodically sends statistics about
installed packages on the local system to Debian Developers.
These statistics are used when building releases, for
instances for getting informations about the most used architecture
instances for getting information about the most used architecture
ports as well as the most used packages.
</para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment