Your message dated Tue, 08 Nov 2011 11:17:42 -0400 with message-id <4eb94816.5090...@tilapin.org> and subject line Re: Bug#647608: po4a: Quote signs in C<> are not correctly translated (at least in German) has caused the Debian Bug report #647608, regarding po4a: Quote signs in C<> are not correctly translated (at least in German) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 647608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: po4a Version: 0.41-1 Severity: normal While working on the German man page translation for po4a, I noticed that C<> is not translated correctly. Take, e.g., #. type: textblock #: lib/Locale/Po4a/Sgml.pm:144 msgid "" "The problem is that I have to \"protect\" the conditional inclusions (i.e. " "the C<E<lt>! [ %foo [> and C<]]E<gt>> stuff) from nsgmls. Otherwise nsgmls " "eats them, and I don't know how to restore them in the final document. To " "prevent that, I rewrite them to C<{PO4A-beg-foo}> and C<{PO4A-end}>." msgstr "" "Das Problem liegt darin, dass ich die bedingte Einbindung (d.h. das Zeug " "C<E<lt>! [ %foo [> und C<]]E<gt>>) vor Nsgmls »schützen« muss. Andernfalls " "futtert Nsgmls das auf und ich weiß nicht, wie ich das im letztendlichen " "Dokument wieder herstellen kann. Um das zu vermeiden, schreibe ich sie in " "C<{PO4A-beg-foo}> und C<{PO4A-end}> um." The version as shown by man is as follows: Das Problem liegt darin, dass ich die bedingte Einbindung (d.h. das Zeug "<! [ %foo [" und "]]>") vor Nsgmls »schützen« muss. Andernfalls futtert Nsgmls das auf und ich weiß nicht, wie ich das im letztendlichen Dokument wieder herstellen kann. Um das zu vermeiden, schreibe ich sie in "{PO4A-beg-foo}" und "{PO4A-end}" um. The first (manual) quote around "protect" is manually translated and looks fine (i.e. »«). The strings with C<>, however, retain their characters as is (which are neither quotes in English nor in German). A side issue (though not part of this bug): What are the rules for manual quotes vs. C<>? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4sneo.01-grsec (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages po4a depends on: ii gettext 0.18.1.1-5 ii libsgmls-perl 1.03ii-32 ii perl 5.12.4-6 ii perl-modules 5.12.4-6 ii sp 1.3.4-1.2.1-47.1 Versions of packages po4a recommends: ii liblocale-gettext-perl 1.05-7 ii libterm-readkey-perl 2.30-4+b1 ii libtext-wrapi18n-perl 0.06-7 po4a suggests no packages. -- no debconf information -- 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
--- End Message ---
--- Begin Message ---Hi Helge, Le 04/11/2011 09:57, Helge Kreutzmann a écrit : > While working on the German man page translation for po4a, I noticed > that C<> is not translated correctly. It's not supposed to be translated. > What are the rules for manual quotes vs. C<>? It's a POD feature, and manual pages are not supposed to mess with the original POD source. If you really believe it's a bug, maybe should it be filled against perl (where /usr/bin/pod2man is shipped). $ man perlpod […] "C<code>" -- code text Renders code in a typewriter font, or gives some other indication that this represents program text (""C<gmtime($^T)>"") or some other form of computerese (""C<drwxr-xr-x>""). FWIW, in French, when I'm bored with these ugly quotes (e.g. if no translated POD is shipped, only the resulting translated manual page), I prefer using the manual page conventions, i.e. using B<> for commands. $ man -LC man […] *bold text* type exactly as shown. /italic text/ replace with appropriate argument. Regards David
signature.asc
Description: OpenPGP digital signature
--- End Message ---