Package: po4a Version: 0.41 [ msguntypot issue described in the last paragraph ]
Hi Helge, Le 28/12/2011 07:07, Helge Kreutzmann a écrit : > 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) : >>> 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. All right, let me try in verbose mode. The source text is something like: Some text, with more than one line and an example: -rm -rf man/translated In order to keep the formating of the example in the last line, a newline (\n) must follow the colon (:) and some spaces must precede the “-rm -rf man/translated”). So the complete paragraph needs to be in “no-wrap” mode. Of course, the “\n” inside the paragraph are useless since perldoc or man will take care of the formating so the previous text will be displayed as: Some text, with more than one line and an example: -rm -rf man/translated in a screen large enough, but the example will still be in a new line, so the only important newline (\n) is before “-rm -rf man/translated”. > So far, whenever the original > file had explicit line breaks I also inserted them faithfully in the > translation as well. As long as you take care of the “important” ones everything should be OK (you can easily build the pages in order to make sure of that). >> 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). “Documentation”, “man page”, and “info manual” are singular, only templates is plural, which makes sense since there is usually (if not always) more than one template by package (using debconf). If we use plural for description, I guess we should use it for man page and info manual too, but since you didn't initially proposed it, I was unsure of the rationale. Anyway, please note that currently, po4a is not used to translate package descriptions, so maybe we should just remove this part. On the other hand, Nicolas added this summer the “control” option to the Text module, in order to allow us to translate debtags directly in its source package (I should go prepare a patch for that), and since the package descriptions are handled in the same file format, we could actually begin to use real PO file to handle translations of package descriptions (but that implies more work to integrate this to the DDTP)… > Now the new stuff: Applied in r2523. > --- 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: This one did not apply (a space was missing after “document.”, probably a copy and paste issue on my side, but I removed it too), so I change it manually, and changed “parsers” to “parser” (“every” should be followed by a singular if I'm not mistaken). I also took care of the trivial unfuzzy, using msguntypot (I usually used the old “manual” sed way), that's a nice tool! ;-). It changes a bit the formatting (so msgcat is needed after it to minimize the actual changes in the PO files), and it removes the useless and old strings from the PO file (maybe this should only be optional). I noticed it removed a lot of stuff at the end of your PO file, that's why I mention it: you may wish to restore those from your last r2522 commit. Regards David
signature.asc
Description: OpenPGP digital signature
