Hello David, the translation is finished, now the second last set of fixes for the translations are attached. I have a few more issues in the pipe, but they are more complex (concerning content) so I need to investigate them a little more before posting to this bug.
If you have any questions regarding the attached fixes, do not
hesitate to ask.
Greetings
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
Index: po4a-updatepo
===================================================================
--- po4a-updatepo (Revision 2550)
+++ po4a-updatepo (Arbeitskopie)
@@ -81,7 +81,7 @@
=item B<--msgmerge-opt> I<options>
-Extra options for B<msgmerge>.
+Extra options for B<msgmerge>(1).
=item B<-h>, B<--help>
Index: po4a-translate
===================================================================
--- po4a-translate (Revision 2550)
+++ po4a-translate (Arbeitskopie)
@@ -29,7 +29,7 @@
The B<po4a-translate> script is in charge of converting the translation
(which was done in a PO file) back into the documentation format. The
-provided PO file should be the translation of the POT file which was
+PO file provided should be the translation of the POT file which was
produced by L<po4a-gettextize(1)>.
=head1 OPTIONS
Index: share/doc/po4a-build.xml
===================================================================
--- share/doc/po4a-build.xml (Revision 2550)
+++ share/doc/po4a-build.xml (Arbeitskopie)
@@ -126,7 +126,7 @@
</example>
<refsect2 id="layout">
<title>configuration file layout</title>
- <para>The configuration file consists of several sections, general,
+ <para>The configuration file consists of several sections: General,
XML/XSL support, POD support and HTML support.
</para>
<para>General includes the name and location of the po4a config
Index: po4a
===================================================================
--- po4a (Revision 2550)
+++ po4a (Arbeitskopie)
@@ -422,7 +422,7 @@
=item B<--msgmerge-opt> I<options>
-Extra options for B<msgmerge>.
+Extra options for B<msgmerge>(1).
Note: B<$lang> will be extended to the current language.
Index: doc/po4a-build.conf.5.pod
===================================================================
--- doc/po4a-build.conf.5.pod (Revision 2550)
+++ doc/po4a-build.conf.5.pod (Arbeitskopie)
@@ -34,7 +34,7 @@
Typically used for manpages for shell scripts or other interpreters that
do not have their own documentation format like POD. Suitable XML can
-be generated directly from an existing manpage using C<doclifter> and
+be generated directly from an existing manpage using C<doclifter>(1) and
C<po4a-build> will then generate a POT file with no extra workload. The
POT file can then be offered for translation and the PO files added to
the relevant F<po/> directory. C<po4a-build> will then prepare not only
Index: doc/po4a.7.pod
===================================================================
--- doc/po4a.7.pod (Revision 2550)
+++ doc/po4a.7.pod (Arbeitskopie)
@@ -100,7 +100,7 @@
But the situation is rather different when it comes to documentation. Too
often, the translated documentation is not visible enough (not distributed
as a part of the program), only partial, or not up to date. This last
-situation is by far the worst possible one. Outdated translation can reveal
+situation is by far the worst possible one. Outdated translation can be
worse than no translation at all to the users by describing old program
behavior which are not in use anymore.
@@ -960,7 +960,7 @@
sentences by aggregating parts of sentences working for all existing
languages (or even for the 5 of the 10 most spoken ones, or even less).
-=head2 Why not put the original as comment along with translation (or other way around)?
+=head2 Why not put the original as comment along with translation (or the other way around)?
At the first glance, gettext dosn't seem to be adapted to all kind of
translations. For example, it didn't seemed adapted to debconf, the
Index: doc/po4a-runtime.7.pod
===================================================================
--- doc/po4a-runtime.7.pod (Revision 2550)
+++ doc/po4a-runtime.7.pod (Arbeitskopie)
@@ -41,7 +41,7 @@
extension only needs to exist during the time that F<po/POTFILES.in>
is being processed.
-The --keywords option can also be useful - see the xgettext
+The --keywords option can also be useful - see the B<xgettext>(1)
documentation.
=head1 Populating po/
@@ -55,7 +55,7 @@
Must exist, even if empty. Consists of a list of translations -
each line not starting with a '#' must match an existing PO file.
-e.g. if F<LINGUAS> contains a single line, 'fr', an F<fr.po> file
+E.g. if F<LINGUAS> contains a single line, 'fr', an F<fr.po> file
must exist alongside the F<LINGUAS> file.
$ cat po/LINGUAS
Index: lib/Locale/Po4a/Po.pm
===================================================================
--- lib/Locale/Po4a/Po.pm (Revision 2550)
+++ lib/Locale/Po4a/Po.pm (Arbeitskopie)
@@ -102,7 +102,7 @@
'encoding' => 0,
'filter' => 0);
-=head1 Functions about whole message catalogs
+=head1 Functions concerning entire message catalogs
=over 4
Index: lib/Locale/Po4a/Xml.pm
===================================================================
--- lib/Locale/Po4a/Xml.pm (Revision 2550)
+++ lib/Locale/Po4a/Xml.pm (Arbeitskopie)
@@ -337,7 +337,7 @@
the specified tags will be excluded, but if you use the "tagsonly" option,
the specified tags will be the only ones included. The tags must be in the
form E<lt>aaaE<gt>, but you can join some (E<lt>bbbE<gt>E<lt>aaaE<gt>) to say that the content of
-the tag E<lt>aaaE<gt> will only be translated when it's into a E<lt>bbbE<gt> tag.
+the tag E<lt>aaaE<gt> will only be translated when it's within a E<lt>bbbE<gt> tag.
You can also specify some tag options putting some characters in front of
the tag hierarchy. For example, you can put 'w' (wrap) or 'W' (don't wrap)
@@ -354,8 +354,8 @@
specify the attributes by their name (for example, "lang"), but you can
prefix it with a tag hierarchy, to specify that this attribute will only be
translated when it's into the specified tag. For example: E<lt>bbbE<gt>E<lt>aaaE<gt>lang
-specifies that the lang attribute will only be translated if it's into an
-E<lt>aaaE<gt> tag, and it's into a E<lt>bbbE<gt> tag.
+specifies that the lang attribute will only be translated if it's within an
+E<lt>aaaE<gt> tag, and it's within a E<lt>bbbE<gt> tag.
=item B<foldattributes>
@@ -377,7 +377,7 @@
The tags must be in the form <aaa>, but you can join some
(<bbb><aaa>), if a tag (<aaa>) should only be considered
-when it's into another tag (<bbb>).
+when it's within another tag (<bbb>).
=item B<inline>
@@ -386,7 +386,7 @@
The tags must be in the form <aaa>, but you can join some
(<bbb><aaa>), if a tag (<aaa>) should only be considered
-when it's into another tag (<bbb>).
+when it's within another tag (<bbb>).
=item B<placeholder>
@@ -401,7 +401,7 @@
The tags must be in the form <aaa>, but you can join some
(<bbb><aaa>), if a tag (<aaa>) should only be considered
-when it's into another tag (<bbb>).
+when it's within another tag (<bbb>).
=item B<nodefault>
@@ -426,11 +426,11 @@
The tags must be in the form <aaa>, but you can join some
(<bbb><aaa>), if a tag (<aaa>) should only be considered
-when it's into another tag (<bbb>).
+when it's within another tag (<bbb>).
-You can also specify some tag options putting some characters in front of
+You can also specify some tag options by putting some characters in front of
the tag hierarchy. For example, you can put 'w' (wrap) or 'W' (don't wrap)
-to overide the default behavior specified by the global "wrap" option.
+to override the default behavior specified by the global "wrap" option.
Example: WE<lt>chapterE<gt>E<lt>titleE<gt>
@@ -440,7 +440,7 @@
The tags must be in the form <aaa>, but you can join some
(<bbb><aaa>), if a tag (<aaa>) should only be considered
-when it's into another tag (<bbb>).
+when it's within another tag (<bbb>).
=item B<defaulttranslateoption>
@@ -661,7 +661,7 @@
=head2 MODIFYING TAG TYPES (TODO)
This is a more complex one, but it enables a (almost) total customization.
-It's based in a list of hashes, each one defining a tag type's behavior. The
+It's based on a list of hashes, each one defining a tag type's behavior. The
list should be sorted so that the most general tags are after the most
concrete ones (sorted first by the beginning and then by the end keys). To
define a tag type you'll have to make a hash with the following keys:
Index: lib/Locale/Po4a/Chooser.pm
===================================================================
--- lib/Locale/Po4a/Chooser.pm (Revision 2550)
+++ lib/Locale/Po4a/Chooser.pm (Arbeitskopie)
@@ -93,8 +93,8 @@
Locale::Po4a::Chooser is a module to manage po4a modules. Previously, all po4a
binaries used to know all po4a modules (pod, man, sgml, etc). This made the
-addition of a new module boring, to make sure the documentation is synchronized
-in all modules, and that each of them can access the new module.
+addition of a new module boring, because the author had to make sure the documentation was synchronized
+in all modules, and that each of them could access the new module.
Now, you just have to call the Locale::Po4a::Chooser::new() function,
passing the name of module as argument.
Index: lib/Locale/Po4a/Sgml.pm
===================================================================
--- lib/Locale/Po4a/Sgml.pm (Revision 2550)
+++ lib/Locale/Po4a/Sgml.pm (Arbeitskopie)
@@ -44,7 +44,7 @@
Locale::Po4a::Sgml is a module to help the translation of documentation in
the SGML format into other [human] languages.
-This module uses B<nsgmls> to parse the SGML files. Make sure it is
+This module uses B<nsgmls>(1) to parse the SGML files. Make sure it is
installed.
Also make sure that the DTD of the SGML files are installed in the system.
signature.asc
Description: Digital signature
