Bug#646173: Typos found while translating the po4a documentation into German
Hello Denis, On Fri, May 25, 2012 at 11:21:11PM +0200, D. Barbier wrote: The website is now regenerated and contains your German translation. Thanks, and sorry again for the delay. Thanks. I probably won't manage to send you the last sent of fixes in time for Wheezy, I'll keep it on my agenda and sent it to you later. (As the courier bug preventing me from reaching alioth is now fixed, this probably will be easier). 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
On 2012/4/30 Helge Kreutzmann wrote: Hello David, On Sun, Apr 29, 2012 at 03:57:22PM -0400, David Prévot wrote: Le 25/03/2012 10:11, Helge Kreutzmann a écrit : On Wed, Feb 29, 2012 at 07:49:02PM +0100, Helge Kreutzmann wrote: 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 Did you have a chance to review these last set of fixes yet? The proposed po4a-build.xml change, already discussed [0] in this bug log, actually discouraged me to review it. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646173#32 No problem; simply accept / change those which you concur, the other ones we can discuss later. Denis, if you were waiting for me [2], I apologize. Maybe those typos can be addressed later, or if you disagree, I can try and brace myself into it (eventually committing only changes that can be trivially unfuzzy, and keeping other ones for later, eventually keeping them in another bug report). 2: http://lists.alioth.debian.org/pipermail/po4a-devel/2012-February/002071.html I wish I could join the discussion over there, maybe then things would have gotten smoother… But great to see that a release is indeed in the pipe. Thanks for your work, looking forward to the release and do not hesitate to contact me if there is anything I can do to ease the process (though I might be a little slow in the coming weeks in answering). Hallo Helge, The website is now regenerated and contains your German translation. Thanks, and sorry again for the delay. Denis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Sun, Apr 29, 2012 at 03:57:22PM -0400, David Prévot wrote: Le 25/03/2012 10:11, Helge Kreutzmann a écrit : On Wed, Feb 29, 2012 at 07:49:02PM +0100, Helge Kreutzmann wrote: 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 Did you have a chance to review these last set of fixes yet? The proposed po4a-build.xml change, already discussed [0] in this bug log, actually discouraged me to review it. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646173#32 No problem; simply accept / change those which you concur, the other ones we can discuss later. Denis, if you were waiting for me [2], I apologize. Maybe those typos can be addressed later, or if you disagree, I can try and brace myself into it (eventually committing only changes that can be trivially unfuzzy, and keeping other ones for later, eventually keeping them in another bug report). 2: http://lists.alioth.debian.org/pipermail/po4a-devel/2012-February/002071.html I wish I could join the discussion over there, maybe then things would have gotten smoother… But great to see that a release is indeed in the pipe. Thanks for your work, looking forward to the release and do not hesitate to contact me if there is anything I can do to ease the process (though I might be a little slow in the coming weeks in answering). 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 tags 646173 - patch thanks Hi, Le 25/03/2012 10:11, Helge Kreutzmann a écrit : On Wed, Feb 29, 2012 at 07:49:02PM +0100, Helge Kreutzmann wrote: 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 Did you have a chance to review these last set of fixes yet? The proposed po4a-build.xml change, already discussed [0] in this bug log, actually discouraged me to review it. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646173#32 Denis, if you were waiting for me [2], I apologize. Maybe those typos can be addressed later, or if you disagree, I can try and brace myself into it (eventually committing only changes that can be trivially unfuzzy, and keeping other ones for later, eventually keeping them in another bug report). 2: http://lists.alioth.debian.org/pipermail/po4a-devel/2012-February/002071.html Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPnZ0hAAoJELgqIXr9/gny5goP+wazabRcAqVmWyioU1SKs2LZ Hy+C2rv81x6kQsPCzuYk2Gt7fOo/O0vM4/qMfxEhcDyRN3E4umN3HGGQthLc5+/e 7kYwfKXnTLpIs2CzPk9ppAt6EhFV/5rDRYRIC1Bu0RDMjbQGyYWm2Z3VqfBgqYQs Nk1cOHe2fujin/mPCDG0op9zRW5njsw/cej59mYhZe24D/jWNMFtfNCCHsQNsWdD BF2IK0vnYmwDqgyudgjocXrk4zBi7SJRKr5HuBjkO77Hbh1HWx2DlqyAuyeSKHaI HcHR+SP4iExIazWYrwGN1RGvLzPdBMXmAF1GYahKE3pcStwA+ayhBcdJau60/tMR dPpj43xvGRH5EYsrVCRuJPD8Q8/K2UHI3Ka7+pMyBshcnTmKJQDvQ3MCtxYZRdbx 1SC0iBdN8qEblKHT6cOI+1KXoV1iJC+nxpim0/T5Mb7ksR2WWcIRlkYDPLdHLl2/ T+I3Arcj4nqzaiyDIV3xQ4FGS2oqiM7fokCOQnpboEuvwFJKqwvotQcSDksxP04I gPzlJnYSi/Ze5NaKnXxSkqy/d09NMhKbj+I+lmlH2mvR04MgLYrAsPoBAiO67Zlv mOkJKczS/mUpsLOJLVXzAfoTbbUFlwKH/7OWshQSgEFciTnhd+zGPyxnHtl6LcUN GrYu+ACV7q3xJh5G7ymQ =axEp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Wed, Feb 29, 2012 at 07:49:02PM +0100, Helge Kreutzmann wrote: 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 Did you have a chance to review these last set of fixes yet? they are more complex (concerning content) so I need to investigate them a little more before posting to this bug. I would prefer first clearing the trivial issues and then work on the more complex ones. This separation makes sense as well, since the trivial ones should be easily unfuzziable, while the more complex ones I don't think. Thanks! 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
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 Ioptions -Extra options for Bmsgmerge. +Extra options for Bmsgmerge(1). =item B-h, B--help Index: po4a-translate === --- po4a-translate (Revision 2550) +++ po4a-translate (Arbeitskopie) @@ -29,7 +29,7 @@ The Bpo4a-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 Lpo4a-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 titleconfiguration file layout/title - paraThe configuration file consists of several sections, general, + paraThe configuration file consists of several sections: General, XML/XSL support, POD support and HTML support. /para paraGeneral includes the name and location of the po4a config Index: po4a === --- po4a (Revision 2550) +++ po4a (Arbeitskopie) @@ -422,7 +422,7 @@ =item B--msgmerge-opt Ioptions -Extra options for Bmsgmerge. +Extra options for Bmsgmerge(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 Cdoclifter and +be generated directly from an existing manpage using Cdoclifter(1) and Cpo4a-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 Fpo/ directory. Cpo4a-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 Fpo/POTFILES.in is being processed. -The --keywords option can also be useful - see the xgettext +The --keywords option can also be useful - see the Bxgettext(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 FLINGUAS contains a single line, 'fr', an Ffr.po file +E.g. if FLINGUAS contains a single line, 'fr', an Ffr.po file must exist alongside the FLINGUAS file.
Bug#646173: Typos found while translating the po4a documentation into German
Le 7 février 2012 19:55, Helge Kreutzmann a écrit : Hello David, On Mon, Feb 06, 2012 at 08:15:37PM -0400, David Prévot wrote: Please, no need to CC me or the po4a-devel list when replying to the bug report. Ok. The CC to the list should not have worked as discussed anyway. Le 01/01/2012 12:24, Helge Kreutzmann a écrit : -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. The sense is not the same (it's even the contrary), and I don't think your proposal is accurate. Well, then I don't understand the sentence. I just wanted to clarify the it. So if I understand you correctly, it should read. remove the second one from where it is and put the second one in the place of the first one Hallo Helge, Consider this example: foo.en.txt contains foo bar foo and foo.fr.txt contains tata titi toto There can be only one msgid foo in the gettextized PO file, but two different msgstr are provided. The paragraph tries to explain that you can replace (in foo.fr.txt) toto by tata if you want to keep the first translaton, or tata by toto if you prefer the second. This paragraph is easier to understand if you read it within its full context - Sometimes, you get the strong feeling that po4a ate some parts of the text, either the original or the translation. gettextization.failed.po indicates that both of them where gently matching, and then the gettextization fails because it tried to match one paragraph with the one after (or before) the right one, as if the right one disappeared. Curse po4a as I did when it first happened to me. Generously. This unfortunate situation happens when the same paragraph is repeated over 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 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. The author explains that one has to edit files (original and translation) until msgid and msgstr match. The problem is that this description makes sense only when you face this problem for real, otherwise it looks way too abstract. Moreover in such a case, po4a-gettextize will not complain and generate something like: #. type: Plain text #: foo.en.txt:2 foo.en.txt:5 #, fuzzy msgid foo msgstr #-#-#-#-# foo.fr.txt:2 #-#-#-#-#\n tata\n #-#-#-#-# foo.fr.txt:5 #-#-#-#-#\n toto Thus I wonder whether this piece of advice is still accurate, maybe it would be better to drop it entirely. Denis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Mon, Feb 06, 2012 at 08:15:37PM -0400, David Prévot wrote: Please, no need to CC me or the po4a-devel list when replying to the bug report. Ok. The CC to the list should not have worked as discussed anyway. Le 01/01/2012 12:24, Helge Kreutzmann a écrit : -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. The sense is not the same (it's even the contrary), and I don't think your proposal is accurate. Well, then I don't understand the sentence. I just wanted to clarify the it. So if I understand you correctly, it should read. remove the second one from where it is and put the second one in the place of the first one 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hi Helge, Chris, Please, no need to CC me or the po4a-devel list when replying to the bug report. Le 01/01/2012 12:24, Helge Kreutzmann a écrit : 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)? Both: the key words are “no empty line”, since po4a uses empty lines to split paragraphs, if I understood correctly. Maybe another “before” could make the sentence a little bit more explicit. Anyway, I guess a simple test can illustrate the issue, see the attached file (and how broken it is in the first place when opened with perldoc anyway, so maybe the end of the sentence should simply be dropped), and the resulted PO file: po4a-gettextize -f pod -m foo.pod -p foo.pot And the simpler stuff: Index: doc/po4a.7.pod === --- doc/po4a.7.pod (Revision 2523) +++ doc/po4a.7.pod (Arbeitskopie) Thanks applied, except the last line of the following one: -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. The sense is not the same (it's even the contrary), and I don't think your proposal is accurate. Le 26/01/2012 16:26, Helge Kreutzmann a écrit : the new translator (Chris) just finished his first chunk and the review was completed and some improvements could be found: All applied, thanks I also reorder the pages in SEE ALSO (since Colin just agreed to follow man-pages(7) advices in man-db too, #651482). Regards David =item 1 Spaces First paragraph. =item 2 No space after Second paragraph. =item 3 Spaces Third paragraph. =item 4 No space before Forth paragraph. =item 5 No space at all Fifth paragraph. signature.asc Description: OpenPGP digital signature
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 Bmode=after, the Iinsertion point is after the Iposition point, but not directly after! It is placed at the end of the section beginning at the -Iposition point, ie after or before the line matched by the +Iposition point, i.e., after or before the line matched by the I???Bboundary argument, depending on whether you used Bbeginboundary or Bendboundary. @@ -631,7 +631,7 @@ the end of section (like in man). In the former case, you want to make a Iboundary matching the Iend of a section, so that the Iinsertion point comes after it. In the latter case, you want to make a Iboundary matching -the Ibeginning of next section, so that the Iinsertion point comes just +the Ibeginning of the next section, so that the Iinsertion 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 Bposition matching any line of your document (but only one line. Po4a won't proceed if it's not unique), and give an Bendboundary matching -nothing. Don't use simple strings here like BEOF, but prefer which have +nothing. Don't use simple strings here like BEOF, but prefer those which have less chance to be in your document. PO4A-HEADER:mode=after;position=titleAbout/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 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/ signature.asc Description: Digital signature
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 BPO4A-HEADER:, followed by a semi-colon (B;) separated list of IkeyB=Ivalue 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 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/ signature.asc Description: Digital signature
Bug#646173: Re: Bug#646173: Typos found while translating the po4a documentation into German
Hello David, first of all, thanks for the pleasant work with you. On Tue, Dec 27, 2011 at 11:09:33PM -0400, David Prévot wrote: Le 20/11/2011 14:25, Helge Kreutzmann a écrit (message #57) : Thanks for everything, I just tried to address your last five reviews in that message (no need to CC me , I read the po4a bug reports). Just a few notes: Dropped the CC, and replied only to those necessary (and, at the end, the open/new ones): -In this example we assume that your generated man pages (and all PO and add +In this example we assume that your generated man pages (and all PO and addendum files) It's actually “addenda” (plural form). Ok, I was unsure if the plural would go for the first word as well (i.e. it was addendum files or addenda files). Additionally, the following issues are unclear to me: po4a:500 This string has explicit line breaks in the pot file (\n) but I cannot see anything special in the original file. See “-rm -rf man/translated”. I don't understand what you mean here. So far, whenever the original file had explicit line breaks I also inserted them faithfully in the translation as well. E.g. po4a:518 The order of the SEE ALSO entries is not according to the man page specification, which says to order by section and within a section by alphabet. However, I assume this different order is on purpose? I don't know if the order is in purpose (it seems so), but please note that man-pages(7) (if that's the document you're referring to) documents the man pages of the *Linux man-pages project*, and po4a is not part of it. I recently fixed the order of dctrl-tools pages after Chris Leick pointed me to that doc in #651219, but would prefer not to take action on other manual pages until Colin Watson replies to #651482. Fine with me, as stated, I won't report this further. Le 28/11/2011 10:24, Helge Kreutzmann a écrit (message #62) : --- lib/Locale/Po4a/Po.pm (Revision 2505) +++ lib/Locale/Po4a/Po.pm (Arbeitskopie) @@ -44,7 +44,7 @@ This module is part of the PO4A project, which objective is to use PO files (designed at origin to ease the translation of program messages) to translate everything, including documentation (man page, info manual), -package description, debconf templates, and everything which may benefit +package descriptions, debconf templates, and everything which may benefit from this. I didn't take this one, since one package may only have one description, but maybe am I missing something. I fixed the uppercase of po4a anyway, and applied your other proposals in r2517. Well, I thought this was a general description and everything was in plural (grammar wise). I don't understand this as beeing for a single package (or even only files in a package) at all. So I'd still go for plural, especially since there are *lots* of package descriptions in Debian alone. Le 09/12/2011 16:34, Helge Kreutzmann a écrit (message #67) : +# FIXME: A better (more precise) link should be given here #. type: textblock #: lib/Locale/Po4a/Po.pm:41 Feel free to propose one, that could be added to a new SEE ALSO section for example. When the translation is complete I'll go through the open issues once more and will dig out a better link if available. I took care of trivial unfuzzy when possible, e.g. only three fuzzy strings in your PO file. Which I dealt with already. Now the new stuff: Index: po4a === --- po4a(Revision 2521) +++ po4a(Arbeitskopie) @@ -256,7 +256,7 @@ [po4a_alias:test] man opt:-k 21 opt_es:-o debug=splitargs This defines a module alias named Btest, based on the Bman module, with -the B-k 21 apply to all the languages and with B-o debug=splitargs +the B-k 21 applied to all the languages and with B-o debug=splitargs applied to the Spanish translation. This module alias can then be use like a regular module: Index: lib/Locale/Po4a/TransTractor.pm === --- lib/Locale/Po4a/TransTractor.pm (Revision 2521) +++ lib/Locale/Po4a/TransTractor.pm (Arbeitskopie) @@ -41,8 +41,8 @@ interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation. -This class is the ancestor of every po4a parsers used to parse a document to -search translatable strings, extract them to a PO file and replace them by +This class is the ancestor of every po4a parsers used to parse a document, to +search translatable strings, to extract them to a PO file and to replace them by their translation in the output document. More formally, it takes the following arguments as input: @@ -94,7 +94,7 @@ This is where all the work takes place: the parsing of input documents, the generation of output, and the extraction of the translatable strings. This is pretty simple using the provided functions presented in
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, next round, next change proposals, typos etc. Questions/Clarifications: #: doc/po4a.7.pod:100 I did not (fully) understand what reveal worse means. Is this proper English? #: lib/Locale/Po4a/TeX.pm:242 Here something before commands seems missing: The syntax of the Iparameters argument is the same as described for the commands. Fixes: Index: doc/po4a.7.pod === --- doc/po4a.7.pod (Revision 2512) +++ doc/po4a.7.pod (Arbeitskopie) @@ -401,7 +401,7 @@ Maybe I'm too dramatic here. Even when things go wrong, it remains ways faster than translating everything again. I was able to gettextize the -existing French translation of the Perl documentation in one day, even if +existing French translation of the Perl documentation in one day, even though things Bdid went wrong. That was more than two megabytes of text, and a new translation would have lasted months or more. Index: lib/Locale/Po4a/TeX.pm === --- lib/Locale/Po4a/TeX.pm (Revision 2512) +++ lib/Locale/Po4a/TeX.pm (Arbeitskopie) @@ -442,7 +442,7 @@ =item A variant -This indicate if a variant is used. For example, an asterisk (*) can +This indicates if a variant is used. For example, an asterisk (*) can be added at the end of sections command to specify that they should not be numbered. In this case, this field will contain *. If there is no variant, the field is an empty string. @@ -1006,8 +1006,8 @@ =item Bparse_definition_file -Subroutine for parsing a file with po4a directive (definitions for -newcommands). +Subroutine for parsing a file with po4a directives (definitions for +new commands). =cut @@ -1687,7 +1687,7 @@ number of arguments, their type and whether or not they should be translated. -=item Tranlation of the environment separator +=item Translation of the environment separator When \item is used as an environment separator, the item argument is attached to the following string. I also wish you a Merry Christmas (or whatever you celebrate). 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/ signature.asc Description: Digital signature
Bug#646173: Re: Bug#646173: Typos found while translating the po4a documentation into German
Hi Helge, Le 20/11/2011 14:25, Helge Kreutzmann a écrit (message #57) : as requested, the diff is attached. Thanks for everything, I just tried to address your last five reviews in that message (no need to CC me , I read the po4a bug reports). Just a few notes: -In this example we assume that your generated man pages (and all PO and add +In this example we assume that your generated man pages (and all PO and addendum files) It's actually “addenda” (plural form). -They take in argument a coma separated list of macros. +They take as argument a comma separated list of macros. I fixed a few other occurrences and consistently added an hyphen between “comma” and “separated”, ditto for s/in argument/as argument/. -Complete list of pages having this problem on my box (from 564 pages ; note +Complete list of pages having this problem on my box (from 564 pages; note Similar issues fixed in TransTractor.pm. Additionally, the following issues are unclear to me: po4a:500 This string has explicit line breaks in the pot file (\n) but I cannot see anything special in the original file. See “-rm -rf man/translated”. E.g. po4a:518 The order of the SEE ALSO entries is not according to the man page specification, which says to order by section and within a section by alphabet. However, I assume this different order is on purpose? I don't know if the order is in purpose (it seems so), but please note that man-pages(7) (if that's the document you're referring to) documents the man pages of the *Linux man-pages project*, and po4a is not part of it. I recently fixed the order of dctrl-tools pages after Chris Leick pointed me to that doc in #651219, but would prefer not to take action on other manual pages until Colin Watson replies to #651482. doc/po4a-build.conf.5.pod:139 I do not fully understand why this paragraph ends in a colon and why there is no language prefix in the example following (as I understood, the documents are the translated ones, right?) I have no clue about po4a-build, explicitly CCing Neil this time since he didn't respond to the message #32 of this BR either. lib/Locale/Po4a/Sgml.pm:150 I would do a s/valid/invalid/, however, I might not understand the content 100%. Not sure either, but anyway, this module is mostly useful for DebianDoc, and I'd prefer help moving the remaining DebianDoc stuff to DocBook XML than digging into this module ;-). Anyway, changes applied in r2516. Le 28/11/2011 10:24, Helge Kreutzmann a écrit (message #62) : --- lib/Locale/Po4a/Po.pm (Revision 2505) +++ lib/Locale/Po4a/Po.pm (Arbeitskopie) @@ -44,7 +44,7 @@ This module is part of the PO4A project, which objective is to use PO files (designed at origin to ease the translation of program messages) to translate everything, including documentation (man page, info manual), -package description, debconf templates, and everything which may benefit +package descriptions, debconf templates, and everything which may benefit from this. I didn't take this one, since one package may only have one description, but maybe am I missing something. I fixed the uppercase of po4a anyway, and applied your other proposals in r2517. Le 09/12/2011 16:34, Helge Kreutzmann a écrit (message #67) : +# FIXME: A better (more precise) link should be given here #. type: textblock #: lib/Locale/Po4a/Po.pm:41 Feel free to propose one, that could be added to a new SEE ALSO section for example. -to check that the update is needed (this avoids to change a POT just to +to check if the update is needed (this avoids to change a POT just to Applied in r2518. Le 18/12/2011 12:26, Helge Kreutzmann a écrit (message #72) : Applied in r2519. Le 27/12/2011 16:03, Helge Kreutzmann a écrit (message #77) : Also applied, in r2520, thanks again. I took care of trivial unfuzzy when possible, e.g. only three fuzzy strings in your PO file. Regards David signature.asc Description: OpenPGP digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hallo David, the next typos: Index: lib/Locale/Po4a/TransTractor.pm === --- lib/Locale/Po4a/TransTractor.pm (Revision 2511) +++ lib/Locale/Po4a/TransTractor.pm (Arbeitskopie) @@ -66,7 +66,7 @@ =item - another PO file, resulting of the extraction of translatable strings from -the input document ; +the input document; =item - Index: lib/Locale/Po4a/TeX.pm === --- lib/Locale/Po4a/TeX.pm (Revision 2511) +++ lib/Locale/Po4a/TeX.pm (Arbeitskopie) @@ -210,9 +210,9 @@ =item a minus (B-) In this case, the command won't be extracted from any block. -But if it appear alone on a bloc, then only the parameters marked as +But if it appear alone on a block, then only the parameters marked as translatable will be presented to the translator. -This is useful for font command. These commands should generally not be +This is useful for font commands. These commands should generally not be separated from their paragraph (to keep the context), but there is no reason to annoy the translator with them if a whole string is enclosed in such a command. 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, the next two: +# FIXME: A better (more precise) link should be given here #. type: textblock #: lib/Locale/Po4a/Po.pm:41 helge@sneo:/tmp/po4a-trunk$ svn diff Index: lib/Locale/Po4a/Po.pm === --- lib/Locale/Po4a/Po.pm (Revision 2510) +++ lib/Locale/Po4a/Po.pm (Arbeitskopie) @@ -489,7 +489,7 @@ Like write, but if the PO or POT file already exists, the object will be written in a temporary file which will be compared with the existing file -to check that the update is needed (this avoids to change a POT just to +to check if the update is needed (this avoids to change a POT just to update a line reference or the POT-Creation-Date field). =cut 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, the next batch of corrections / improvements. If you have any questions regarding them, do not hesitate to ask. I prepared them the same way as last time, I hope this is ok. Regarding the translation: My work speed will slow down quite a bit; I'm trying to solicit another translator to help me, but no guarantees. 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: doc/po4a-build.conf.5.pod === --- doc/po4a-build.conf.5.pod (Revision 2505) +++ doc/po4a-build.conf.5.pod (Arbeitskopie) @@ -105,7 +105,9 @@ in this directory and all PO files merged with that POT file. Any KEEP threshold (see below) will be applied across all strings from all input files specified in this file and all PO files in this -directory. The directory does not need to be called 'po'. +directory. The directory does not need to be called 'po'. Please +note, however, that some statistic tools expect the name to be +'po', therefor it is recommended to keep this name. # po directory for manpages/docs PODIR=po/pod Index: doc/po4a.7.pod === --- doc/po4a.7.pod (Revision 2505) +++ doc/po4a.7.pod (Arbeitskopie) @@ -80,7 +80,7 @@ =head1 Why should I use po4a? What it is good for? I like the idea of open-source software, making it possible for everybody to -access to software and to their source code. But being French, I'm well +access software and its source code. But being French, I'm well aware that the licensing is not the only restriction to the openness of software: non-translated free software is useless for non-English speakers, and we still have some work to make it available to really @@ -320,10 +320,9 @@ confusion with the translation of the program messages, but this your call. Don't forget to update the PO file headers, they are important. -The actual translation can be done using the Emacs' PO mode or Lokalize (KDE +The actual translation can be done using the Emacs' or Vi's PO mode or Lokalize (KDE based) or Gtranslator (GNOME based), or whichever program you prefer to use -them. A good ol' vi could do the trick too, even if there is no specialized -mode for this task. +for them (e.g. Virtaal). If you wish to learn more about this, you definitively need to refer to the gettext documentation, available in the Bgettext-doc package. Index: lib/Locale/Po4a/Po.pm === --- lib/Locale/Po4a/Po.pm (Revision 2505) +++ lib/Locale/Po4a/Po.pm (Arbeitskopie) @@ -44,7 +44,7 @@ This module is part of the PO4A project, which objective is to use PO files (designed at origin to ease the translation of program messages) to translate everything, including documentation (man page, info manual), -package description, debconf templates, and everything which may benefit +package descriptions, debconf templates, and everything which may benefit from this. =head1 OPTIONS ACCEPTED BY THIS MODULE @@ -695,7 +695,7 @@ a reference in the given file will be placed in the resulting catalog. This function parses its argument, converts it to a Perl function definition, -eval this definition and filter the fields for which this function returns +evals this definition and filters the fields for which this function returns true. I love Perl sometimes ;) Index: lib/Locale/Po4a/TransTractor.pm === --- lib/Locale/Po4a/TransTractor.pm (Revision 2505) +++ lib/Locale/Po4a/TransTractor.pm (Arbeitskopie) @@ -51,7 +51,7 @@ =item - -a document to translate ; +a document to translate; =item - signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Sat, Nov 19, 2011 at 11:08:54PM -0400, David Prévot wrote: On 19/11/2011 09:48, Helge Kreutzmann wrote: On Tue, Nov 08, 2011 at 12:56:23PM -0400, David Prévot wrote: 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-de...@lists.alioth.debian.org (it's a low traffic list you may consider subscribing to). I just checked in a new version (which seems to have caused a problem[1]?) and have found some more typos/improvement possibilites. However, this raises two problems: a) Often I would like to explain the change (e.g. I'm unsure or merge with or ...), how should I do this in the patch? That's the beauty with patches series: it's possible to actually prepare atomic commits, with one change by commit, and a meaningful commit message for each change. Other people can then acknowledge (or not) the whole series, or each individual commit, eventual amending those some of them, making quite easy the task to apply them ones agreed. You mean I should create a patch for each single typo/change? That's to much work, I guess. That's actually one of the reason why I use “git svn”: it allows to prepare the changes, eventually reorder them (and even merge similar ones) with “git rebase -i”, and propose them (or directly commit them as I did with your previous proposals I had no doubt with). It makes it easier to revert a specific commit if someone disagrees afterward too. Fine, but currently I've no time to learn git svn. You can then prepare the patch series with “git format-patch” and send them directly to the list or the bug report with “git send-email” (no attachment needed ;-). You know much more git than me. I'm happy with the basic commands and an occasional swiching of a branch (in case I need to apply a fix to a previous version as well). [ I must admit that I'm still discovering Git, which seems like a pretty efficient toy, and I can't stop playing with it. ] I'd like too, but time constrains. Even after a simple “svn diff fixes.patch”, one can add comments in the mail or bug report, quoting part or all of the diff in the message, and also attach the file in order to ease the reviewing process. I'll probably go this route. I guess you could even prepare a review branch in the po4a tree (I did something like that a year ago, when I prepared a huge review of typographic and convention stuff of the documentation). Nope, branching in CVS (and svn for that matter) is way out of my knowledge pool. I'm not sure I can dig out all commenting methods properly? Do you think keeping the previous style would be possible? I'm not sure I understood, could you please rephrase? The easiest way for me is to copy the strings/lines which require changes from de.po and add an explanation. Quick and simple for me, but more cumbersome for you. I just commited the latest de.po and will try to send you the diff later today with my suggested fixes. Anyway, we'll send a mail to translators with incomplete translation at least ten days before the next release. This is great. Well, it's quite self explained: too big messages don't go to the commit list. I don't think it's really an issue: too big changes are generally No problem for me, I just wanted to let you know. 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, as requested, the diff is attached. Additionally, the following issues are unclear to me: po4a:500 This string has explicit line breaks in the pot file (\n) but I cannot see anything special in the original file. E.g. po4a:518 The order of the SEE ALSO entries is not according to the man page specification, which says to order by section and within a section by alphabet. However, I assume this different order is on purpose? doc/po4a-build.conf.5.pod:139 I do not fully understand why this paragraph ends in a colon and why there is no language prefix in the example following (as I understood, the documents are the translated ones, right?) lib/Locale/Po4a/Sgml.pm:150 I would do a s/valid/invalid/, however, I might not understand the content 100%. 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: scripts/msguntypot === --- scripts/msguntypot (Revision 2505) +++ scripts/msguntypot (Arbeitskopie) @@ -57,7 +57,7 @@ mkdir po_fridge; cp *.po po_fridge -=item - Fix your typo +=item - Fix your typo. $EDITOR the_file_in_which_there_is_a_typo @@ -77,7 +77,7 @@ cp po_fridge/*.po . -=item - Manually merge the PO files with the new POT file, but taking the useless fuzzy into account +=item - Manually merge the PO files with the new POT file, but taking the useless fuzzy into account. msguntypot -o myfile.pot.orig -n myfile.pot *.po Index: po4a === --- po4a (Revision 2505) +++ po4a (Arbeitskopie) @@ -392,7 +392,7 @@ =item B--translate-only Itranslated-file Translate only the specified file. It may be useful to speed up -processing if configuration file contains a lot of files. Note that this +processing if a configuration file contains a lot of files. Note that this option does not update PO and POT files. This option can be used multiple times. @@ -474,7 +474,7 @@ [type: man] man/foo.1 $lang:man/translated/$lang/foo.1 \ add_$lang:?man/po4a/add_$lang/$lang.add opt:-k 80 -In this example we assume that your generated man pages (and all PO and add +In this example we assume that your generated man pages (and all PO and addendum files) should be stored in Fman/translated/$lang/ (respectively in Fman/po4a/po/ and Fman/po4a/add_$lang/) below the current directory. In our example the Fman/po4a/po/ directory would include Fde.po, Fpt.po and Fsv.po, Index: lib/Locale/Po4a/Man.pm === --- lib/Locale/Po4a/Man.pm (Revision 2505) +++ lib/Locale/Po4a/Man.pm (Arbeitskopie) @@ -157,7 +157,7 @@ It selects a stricter support of the mdoc format by telling po4a not to translate the 'NAME' section. -mdoc pages whose 'NAME' section is translated won't generate any header of +mdoc pages whose 'NAME' section is translated won't generate any header or footer. According to the groff_mdoc page, the NAME, SYNOPSIS and DESCRIPTION @@ -175,7 +175,7 @@ The following options permit to specify the behavior of a new macro (defined with a .de request), or of a macro not supported by po4a. -They take in argument a coma separated list of macros. +They take as argument a comma separated list of macros. For example: -o noarg=FO,OB,AR -o translate_joined=BA,ZQ,UX @@ -207,7 +207,7 @@ =item Bno_wrap -This option takes in argument a list of coma-separated couples +This option takes in argument a list of comma-separated couples Ibegin:Iend, where Ibegin and Iend are commands that delimit the begin and end of a section that should not be rewrapped. @@ -220,7 +220,7 @@ =item Binline -This option specifies a list of coma-separated macros that must +This option specifies a list of comma-separated macros that must not split the current paragraph. The string to translate will then contain Ifoo Elt.bar baz quxEgt quux, where Ibar is the command that should be inlined, and Ibaz qux its arguments. @@ -230,7 +230,8 @@ This option indicates how po4a should behave when an unknown macro is found. By default, po4a fails with a warning. It can take the following values: Ifailed (the default value), -Iuntranslated, Inoarg, Itranslate_joined, Itranslate_each. +Iuntranslated, Inoarg, Itranslate_joined, Itranslate_each (see above +for an explanation of these values). =back @@ -278,7 +279,7 @@ .splitfont .Sx .T .TF .The .TT .UC .ul .Vb .zZ -=head2 Hiding text to po4a +=head2 Hiding text from po4a Sometimes, the author knows that some parts are not translatable, and should not be extracted by po4a. For example, an
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Tue, Nov 08, 2011 at 12:56:23PM -0400, David Prévot wrote: 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-de...@lists.alioth.debian.org (it's a low traffic list you may consider subscribing to). I just checked in a new version (which seems to have caused a problem[1]?) and have found some more typos/improvement possibilites. However, this raises two problems: a) Often I would like to explain the change (e.g. I'm unsure or merge with or ...), how should I do this in the patch? I'm not sure I can dig out all commenting methods properly? Do you think keeping the previous style would be possible? b) As upstream is using an e-mail list on alioth, I cannot mail them (cf. bug #582765, hopefully the maintainer of courier-mta somewhen talks to me :-((). For your planning, I hope to get another batch done during December, so depending on your next targetted upload I can provide a significant bunch of the German translation by then. However, after that translation probably will slow down quite a bit, though. Greetings Helge [1] I got an e-mail with Your mail to 'Po4a-commits' with the subject r2495 - /trunk/po/pod/de.po Is being held until the list moderator can review it for approval. The reason it is being held: Message body is too big: 99476 bytes with a limit of 40 KB Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://lists.alioth.debian.org/cgi-bin/mailman/confirm/po4a-commits/294e04dcf4ae36665d769845022cff68959e512d -- 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hi Helge, On 19/11/2011 09:48, Helge Kreutzmann wrote: On Tue, Nov 08, 2011 at 12:56:23PM -0400, David Prévot wrote: 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-de...@lists.alioth.debian.org (it's a low traffic list you may consider subscribing to). I just checked in a new version (which seems to have caused a problem[1]?) and have found some more typos/improvement possibilites. However, this raises two problems: a) Often I would like to explain the change (e.g. I'm unsure or merge with or ...), how should I do this in the patch? That's the beauty with patches series: it's possible to actually prepare atomic commits, with one change by commit, and a meaningful commit message for each change. Other people can then acknowledge (or not) the whole series, or each individual commit, eventual amending those some of them, making quite easy the task to apply them ones agreed. That's actually one of the reason why I use “git svn”: it allows to prepare the changes, eventually reorder them (and even merge similar ones) with “git rebase -i”, and propose them (or directly commit them as I did with your previous proposals I had no doubt with). It makes it easier to revert a specific commit if someone disagrees afterward too. You can then prepare the patch series with “git format-patch” and send them directly to the list or the bug report with “git send-email” (no attachment needed ;-). [ I must admit that I'm still discovering Git, which seems like a pretty efficient toy, and I can't stop playing with it. ] Even after a simple “svn diff fixes.patch”, one can add comments in the mail or bug report, quoting part or all of the diff in the message, and also attach the file in order to ease the reviewing process. I guess you could even prepare a review branch in the po4a tree (I did something like that a year ago, when I prepared a huge review of typographic and convention stuff of the documentation). I'm not sure I can dig out all commenting methods properly? Do you think keeping the previous style would be possible? I'm not sure I understood, could you please rephrase? b) As upstream is using an e-mail list on alioth, I cannot mail them (cf. bug #582765, hopefully the maintainer of courier-mta somewhen talks to me :-((). Wow, that's annoying (glad to use Dovecot on my servers, It seems like I'm not the only one [0]), I'm surprised to discover this issue only now: if Alioth is affected, a lot of people might be in a black hole… I guess you can always send unsigned mails without attachment, and eventually provide an URL to the files, but that may be boring for you. O: http://qa.debian.org/popcon-png.php?packages=dovecot-common%20courier-baseshow_installed=onwant_legend=on For your planning, I hope to get another batch done during December, so depending on your next targetted upload I don't know, there has not been a lot of changes recently, but Nicolas added a feature this summer (in order to translate control files), and I would love to see the po4a package in the Debian archive in order to provide a patch for debtags to include tags descriptions. Some translations are already available on package.d.o, my wish would be, once include in debtags, to offer the translated tags descriptions in various front-ends like aptitude… Sadly, I haven't prepared any debtag patch yet to include those translations, but when I'll find some time to do so, I'll ask for a revision release of po4a (if the German translation is not complete then, we'll upload another revision before or during the freeze to make it complete anyway). Nicolas, in case you've read so far, could you please remind me the needed commands to generate the PO and control files for debsums from the packages.d.o PO files (just in case you still have them handy, I'll reproduce something if I've been silly enough not to save my history). Anyway, we'll send a mail to translators with incomplete translation at least ten days before the next release. [1] I got an e-mail with […] The reason it is being held: Message body is too big: 99476 bytes with a limit of 40 KB Well, it's quite self explained: too big messages don't go to the commit list. I don't think it's really an issue: too big changes are generally update translations (so it should not really need any review from the po4a developers, given that such review would already have happen in a translation coordination mailing list, and that po4a developers might not be qualified in $language anyway ;-), or PO and POT update after some massive change, so a call for translation will follow anyway. Regards David signature.asc Description: OpenPGP digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Tue, Nov 08, 2011 at 12:56:23PM -0400, David Prévot wrote: 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 filenamepo4a.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. Ok, once I reveive the answer I'll incorporate/update that in the German man page translation, thanks. 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 Bmsgmerge. +msgid Extra options for Bmsgmerge(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. Fine with me, it is just very common, but IMHO usually not needed. -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. Yes, a better fix is clearly desired. I just tried to propose the minimal fix obvious to me. 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-de...@lists.alioth.debian.org (it's a low traffic list you may consider subscribing to). For me it is easier to work on the pot file, but I understand your view point, it's just more inconvenient for me (and in case strings are reused, I'll have to point that out as well). I'll already have a few more in the pipeline, but I'll gather some before reporting. Thanks again for applying the fixes. 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
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 filenamepo4a.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 Btest, based on the Bman module, with +This defines a module alias named Btest, based on the Bman 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 Bmsgmerge. +msgid Extra options for Bmsgmerge(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-de...@lists.alioth.debian.org (it's a low traffic list you may consider subscribing to). Regards David signature.asc Description: OpenPGP digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, a few more strings, a few more typos: First a typo/question: The configuration file consists of several sections, general, XML/XSL support, POD support and HTML support. 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 filenamepo4a.config/filename), the po directory ... So, does case matter and if yes, which is the proper captialization? If lower case, maybe -General includes the name and location of the po4a config file (probably +\general\ includes the name and location of the po4a config file (probably would be an approriate fix. -This define a module alias named Btest, based on the Bman module, with +This defines a module alias named Btest, based on the Bman module, with 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 Bmsgmerge. +msgid Extra options for Bmsgmerge(1). Btw. you use different markup for denoting programs, e.g. in po4a-translate:30 you use L. 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. 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 See also above: -msgid List the documentation format handled by po4a. +msgid List the documentation formats handled by po4a. -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 As long as this bug is open, I can continue filing the typos found here, how would you like to proceed in the future? 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hello David, On Sat, Oct 22, 2011 at 08:43:55PM -0400, David Prévot wrote: Le 21/10/2011 16:42, Helge Kreutzmann a écrit : - de:doc/de/mein_cram.sgml\n + de:doc/de/mein_cram.sgml\n What is the fix supposed to be? Ggr, it should've read: - de:doc/de/mein_cram.sgml\n + de:doc/de/mein_kram.sgml\n 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/ signature.asc Description: Digital signature
Bug#646173: Typos found while translating the po4a documentation into German
Hi Helge, Le 29/10/2011 15:31, Helge Kreutzmann a écrit : On Sat, Oct 22, 2011 at 08:43:55PM -0400, David Prévot wrote: What is the fix supposed to be? Ggr, it should've read: - de:doc/de/mein_cram.sgml\n + de:doc/de/mein_kram.sgml\n Thanks for the follow up, fixed in r2483. Regards David signature.asc Description: OpenPGP digital signature
Bug#646173: Typos found while translating the po4a documentation into German
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 tags 646173 pending thanks Hi Helge, Le 21/10/2011 16:42, Helge Kreutzmann a écrit : While starting the German translation the following typos were found: Thanks for your report. not all of them needs to be applied: -(filenamepo4a-build.conf/filename) and supply your own. +(filenamepo4a-build.conf/filename) and supply your own. The double (more actually) space is in the po4a-build(1) XML source file, but does not appear in the generated man page, so nothing needs to be fixed here. -First, you have to specify where the translator input files (ie, the files +First, you have to specify where the translator input files (i.e., the files Thanks, I fixed it without the comma, and some similar ones on other pages. - de:doc/de/mein_cram.sgml\n + de:doc/de/mein_cram.sgml\n What is the fix supposed to be? -(which was done in a PO file) under the documentation format back. The +(which was done in a PO file) back into the documentation format. The -Locale::Po4a::Chooser is a module to manage po4a modules. Before, all po4a +Locale::Po4a::Chooser is a module to manage po4a modules. Previously, all po4a -add of a new module boring, to make sure the documentation is synchronized +addition of a new module boring, to make sure the documentation is synchronized Thanks, wording fixed in po4a-translate(1) and Locale::Po4a::Chooser(3). # I also don't understand the paragraph from which the following fix is taken: -available format and exits on the value passed as argument. +available formats and exits on the value passed as argument. Fixed too, thanks. About what it means, if I understand correctly, the list function exits with: exit shift; so the return value is the same as the input one, e.g.: $ perl -e 'use Locale::Po4a::Chooser; Locale::Po4a::Chooser::list(10)'\ /dev/null ;echo $? 10 $ perl -e 'use Locale::Po4a::Chooser; Locale::Po4a::Chooser::list(0)'\ /dev/null ;echo $? 0 I took care of unfuzzying existing translations. Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOo2NKAAoJELgqIXr9/gnyXdAQAI01DOHiYUuRC3zw5zNgpERO o4bNkVQPIy2KnvQ4RLHCjNWJZHmKRdkXSjQ662nfTrU+KxGRmhK8POxevjSstZLP d7O4vPdwAlYuHdUgbyX7R4ZxYddVPc9BbTr22uloFRE//68IClsxYMEfyv/o4BTz x4Kt7hBzzKBk996s9X1yKZIlD/EVa+Cu89MY4FJsGLOfJWOWU7UxgqG+guRQm3p6 491IE0Mpdz7bgEfrYvNhVk9s55KN20iM1bwBzB8XPAxJZh7RYhH5yt/2vhN9qqVO JhQF0IZmrSSR8doAiyv7cjg1dyUqN4gZw4VruaAY3WujcXEESQpu/KWTTSJbZTaQ ZORwCcqoxH737k5yoFryrHC6WqbSe63TUcHCXYc+6Rh/ncwSXtcpCscUW5PUgV28 yPlCjpN98TibZ3pcCzboxaC+PsEXZGeOMzHjGDKhFsrOZ8T/W5eedRdKiUfPaUMj GO4vFFSR8xhOZZmSzYLESYLB25ZH7bOkPW9XDfwnSZXeG963Jop3nz1YYsgodQJ0 xVQRrFkhIkcRVMVOF5ZZBXvpSrw85L6vHS1Ddn6DBrvkP0R2nI5B2lpdWDnVPLx0 0jtDmBwE6laUIIZxxQsCd6NolIKufvkSvvY75yukOscFm1n65EHqWeehPt0sRNq4 klJJPCAnW9DvAZA0Dnsj =nfDc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646173: Typos found while translating the po4a documentation into German
Package: po4a Severity: minor Tags: patch While starting the German translation the following typos were found: -(filenamepo4a-build.conf/filename) and supply your own. +(filenamepo4a-build.conf/filename) and supply your own. -First, you have to specify where the translator input files (ie, the files +First, you have to specify where the translator input files (i.e., the files - de:doc/de/mein_cram.sgml\n + de:doc/de/mein_cram.sgml\n -Minimal threshold for translation percentage to keep (ie, write) the +Minimal threshold for translation percentage to keep (ie, write) the -resulting file (default: 80). Ie, by default, files have to be translated at +resulting file (default: 80). Ie, by default, files have to be translated at -(which was done in a PO file) under the documentation format back. The +(which was done in a PO file) back into the documentation format. The -Locale::Po4a::Chooser is a module to manage po4a modules. Before, all po4a +Locale::Po4a::Chooser is a module to manage po4a modules. Previously, all po4a -add of a new module boring, to make sure the documentation is synchronized +addition of a new module boring, to make sure the documentation is synchronized # I also don't understand the paragraph from which the following fix is taken: -available format and exits on the value passed as argument. +available formats and exits on the value passed as argument. -- 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/ signature.asc Description: Digital signature
