10:56 a.m.
Hi Helge, the po4a upstream developers list,
Le 02/11/2011 10:15, Helge Kreutzmann a écrit :
First a typo/question:
"The configuration file consists of several sections, general, XML/XSL "
"support, POD support and HTML support."
(that's a po4a-build(1) string)
Looks like "general" is spelled with a lower case
"g", however in the
next string:;
"General includes the name and location of the po4a config file (probably "
"best to leave this as <filename>po4a.config</filename>), the po
directory "
If I understood correctly “general” is a just word, “global” would have
fit here as well, it's just the “common” part of the po4a-build.conf(5)
file. So I don't think there is any typo here, but Neil should be able
to enlighten us here.
-"This define a module alias named B<test>, based on the
B<man> module, with "
+"This defines a module alias named B<test>, based on the B<man> module,
with "
Fixed.
The next one I only mention once, but I saw it several times (e.g.
in
doc/po4a-build.conf.5.pod:35 and lib/Locale/Po4a/Sgml.pm:47 as well):
-msgid "Extra options for B<msgmerge>."
+msgid "Extra options for B<msgmerge>(1)."
It's not fundamentally an error, I don't even know if we want to fix it,
the po4a upstream developers list CCed to gather more opinions.
Btw. you use different markup for denoting programs, e.g. in
po4a-translate:30 you use L<>.
It's a POD feature, see perlpod(1) (not all manual shipped in po4a have
a POD source).
I'm not sure if that can be unfuzzied and also you might
consider
using the same phrase (albeit needing the same fix) from
po4a-updatepo:92? to remove one almost duplicate string.
-msgid "List the documentation format understood by po4a."
+msgid "List the documentation formats understood by po4a."
See also above:
-msgid "List the documentation format handled by po4a."
+msgid "List the documentation formats handled by po4a."
Plural was already used in the (few) translated languages I was able to
understand, so I also unfuzzyed all of them (anyway, grammar rules vary
among language). Since “understood” was already used in po4a-gettextize,
po4a-normalize, and po4a-translate, I fixed po4a-updatepo to use the
same wording (s/handled/understood).
This one I'm not 100% sure, please check:
-"provided PO file should be the translation of the POT file which were "
+"provided PO file should be the translation of the POT file which was "
Agreed, unfuzzyed too.
-"the addition of a new module boring, to make sure the
documentation is "
+"the addition of a new module boring, because you had to make sure the
documentation is "
I'm not sure if the original sentence of Locale::Po4a::Chooser(3) is
wrong, even if yours sounds better. The rest of the string might need
fixing too, more comments are welcome.
As long as this bug is open, I can continue filing the typos found
here, how would you like to proceed in the future?
Fine for me, I think other active po4a contributors are following the
BTS too, I just CCed the po4a upstream developers list to make sure of
that. For future typos, providing an actual patch[es serie] one could
review and acknowledge directly would be even more welcome, you may send
them directly to <po4a-devel(a)lists.alioth.debian.org> (it's a low
traffic list you may consider subscribing to).
Regards
David
10:24 a.m.
New subject: [Po4a-devel] Bug#646173: Typos found while translating the po4a documentation into German
Hello David,
first of all a happy new year.
Next round of typos / suggestions for improvement:
a) doc/po4a.7.pod:480
I'm not sure I understand the last sentence correctly.
... when there is no empty line before the =item
line and the content of the item.
Empty line *before* =item or *between* =item and the content of the item
(or both)?
And the "simpler" stuff:
Index: doc/po4a.7.pod
===================================================================
--- doc/po4a.7.pod (Revision 2523)
+++ doc/po4a.7.pod (Arbeitskopie)
@@ -463,9 +463,9 @@
=item -
If you changed the structure a bit (to merge two paragraphs, or split
-another one), undo those changes. If there is issues in the original, you
-should inform the original author. Fixing them in your translation only fix
-it for a part of the community. And moreover, it's impossible when using
+another one), undo those changes. If there are issues in the original, you
+should inform the original author. Fixing them in your translation only fixes
+them for a part of the community. And moreover, it's impossible when using
po4a ;)
=item -
@@ -502,11 +502,11 @@
the document. In that case, no new entry is created in the PO file, but a
new reference is added to the existing one instead.
-So, when the same paragraph appears twice in the original but are not
+So, when the same paragraph appears twice in the original but both are not
translated in the exact same way each time, you will get the feeling that a
paragraph of the original disappeared. Just kill the new translation. If you
prefer to kill the first translation instead when it was actually better,
-remove the second one from where it is and put it in place of the first one.
+remove the second one from where it is and put the first one in place of the second one.
In the contrary, if two similar but different paragraphs were translated in the
exact same way, you will get the feeling that a paragraph of the translation
@@ -547,12 +547,12 @@
to add a section about the translation itself, listing contributors and
explaining how to report bug against the translation.
-Addendum must be provided as a separate file. The first line constitutes a
+An addendum must be provided as a separate file. The first line constitutes a
header indicating where in the produced document they should be placed. The
rest of the addendum file will be added verbatim at the determined position of
the resulting document.
-The header have a pretty rigid syntax: It must begin with the string
+The header has a pretty rigid syntax: It must begin with the string
B<PO4A-HEADER:>, followed by a semi-colon (B<;>) separated list of
I<key>B<=>I<value>
fields. White spaces ARE important. Note that you cannot use the semi-colon
char (B<;>) in the value, and that quoting it doesn't help.
For me, I will now cease to work on po4a translation for now. I talked with
another German translator and he'll probably take over for the
remaining 30%, but still it would be a good time for an upload (also
for the web page), hint, hint.
If possible, however, I'll take care of the long term (whatever this
means) maintaince of the German translation.
Greetings
Helge
--
Dr. Helge Kreutzmann debian(a)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/
2:26 p.m.
New subject: [Po4a-devel] Bug#646173: Typos found while translating the po4a documentation into German
Hello David,
the new translator (Chris) just finished his first chunk and the
review was completed and some improvements could be found:
Index: doc/po4a.7.pod
===================================================================
--- doc/po4a.7.pod (Revision 2525)
+++ doc/po4a.7.pod (Arbeitskopie)
@@ -608,7 +608,7 @@
When B<mode=after>, the I<insertion point> is after the I<position
point>, but
not directly after! It is placed at the end of the section beginning at the
-I<position point>, ie after or before the line matched by the
+I<position point>, i.e., after or before the line matched by the
I<???>B<boundary> argument, depending on whether you used
B<beginboundary> or
B<endboundary>.
@@ -631,7 +631,7 @@
the end of section (like in man). In the former case, you want to make a
I<boundary> matching the I<end of a section>, so that the I<insertion
point>
comes after it. In the latter case, you want to make a I<boundary> matching
-the I<beginning of next section>, so that the I<insertion point> comes just
+the I<beginning of the next section>, so that the I<insertion point> comes
just
before it.
=back
@@ -671,7 +671,7 @@
=item If you want to add something at the end of the document, give a
B<position> matching any line of your document (but only one line. Po4a
won't proceed if it's not unique), and give an B<endboundary> matching
-nothing. Don't use simple strings here like B<"EOF">, but prefer
which have
+nothing. Don't use simple strings here like B<"EOF">, but prefer
those which have
less chance to be in your document.
PO4A-HEADER:mode=after;position=<title>About</title>;beginboundary=FakePo4aBoundary
@@ -734,10 +734,10 @@
explaining where your translation files are (PO and POT), where the original
documents are, their formats and where their translations should be placed.
-Then, calling po4a(1) on this file ensure that the PO files are synchronized
+Then, calling po4a(1) on this file ensures that the PO files are synchronized
against the original document, and that the translated document are
generated properly. Of course, you will want to call this program twice:
-once before editing the PO file to update them and once afterward to get
+once before editing the PO file to update them and once afterward to get a
completely updated translated document. But you only need to remember one
command line.
@@ -868,7 +868,7 @@
Even with these precautions, things can go wrong very easily here. That's
why all translations guessed this way are marked fuzzy to make sure that
-the translator review and check them.
+the translator reviews and checks them.
=head2 Addendum: How does it work?
@@ -960,13 +960,13 @@
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)?
+=head2 Why not put the original as comment along with translation (or other way around)?
-At the first glance, gettext don't seem to be adapted to all kind of
+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
interface all Debian packages use for their interaction with the user during
installation. In that case, the texts to translate were pretty short (a
-dozen of line for each package), and it was difficult to put the translation
+dozen lines for each package), and it was difficult to put the translation
in a specialized file since it has to be available before the package
installation.
@@ -1018,7 +1018,7 @@
=head2 But gettext wasn't designed for that use!
That's true, but until now nobody came with a better solution. The only
-known alternative is manual translation, will all the maintenance issues.
+known alternative is manual translation, with all the maintenance issues.
=head2 What about the other translation tools for documentation using
gettext?
@@ -1131,7 +1131,7 @@
=item *
Nothing changed for the end-user (beside the fact translations will
-hopefully be better maintained :). The resulting documentation file
+hopefully be better maintained :)). The resulting documentation file
distributed is exactly the same.
=item *
--
Dr. Helge Kreutzmann debian(a)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/
4714
days inactive
4793
days old
2 comments
2 participants
participants (2)
-
David Prévot -
Helge Kreutzmann