Your message dated Sun, 9 Jun 2013 20:11:37 +0100 with message-id <[email protected]> and subject line Re: Bug#492037: Bug#500210: perldoc perlrun spits out junk in synopsis has caused the Debian Bug report #492037, regarding incorrect behaviour of perldoc with UTF-8 texts 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 [email protected] immediately.) -- 492037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492037 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: perl Version: 5.10.0-10 Tags: l10n Severity: important In attache You can found pod with russian symbols in utf-8 charset. This file is showed incorrectly: =begin of cut EXAMPLE_RUSSIAN(1) User Contributed Perl Documentation EXAMPLE_RUSSIAN(1) XXXXXXXXX1 N~XX N~XN~XN~XN~XXXX N~XXXN~XN~X N~XXXXXXN~X N~XXXN~XXX 1 N~XXXN~XN~X XN~XXXN~XXXXXN~XX =end cut Perldoc from Etch works fine. pod2text works tolerably, but letters 'Э' (1069 == ord 'Э'), 'И' (1048 == ord 'И') will be replaced to symbol 'Ð' pod2man works as perldoc pod2html works fine PS: apache:[~]$ zcat /usr/share/doc/perl/changelog.Debian.gz|dpkg-parsechangelog -l- Source: perl Version: 5.10.0-10 Distribution: unstable Urgency: low Maintainer: Niko Tyni <[email protected]> Date: Thu, 08 May 2008 14:32:30 +0300 Closes: 479460 479762 479863 Changes: perl (5.10.0-10) unstable; urgency=low . * Integrate NMU, thanks Bastian. * Make h2ph allow the quote mark delimiter also for those #include directives chased with "h2ph -a". (Closes: #479762) * Adjust manual page sections in Module::Build::Base for the Debian Perl policy. (Closes: #479460) * Disable the "v-string in use/require is non-portable" warning again. (Closes: #479863) apache:[~]$ zcat /usr/share/doc/perl-doc/changelog.Debian.gz|dpkg-parsechangelog -l- Source: perl Version: 5.10.0-10 Distribution: unstable Urgency: low Maintainer: Niko Tyni <[email protected]> Date: Thu, 08 May 2008 14:32:30 +0300 Closes: 479460 479762 479863 Changes: perl (5.10.0-10) unstable; urgency=low . * Integrate NMU, thanks Bastian. * Make h2ph allow the quote mark delimiter also for those #include directives chased with "h2ph -a". (Closes: #479762) * Adjust manual page sections in Module::Build::Base for the Debian Perl policy. (Closes: #479460) * Disable the "v-string in use/require is non-portable" warning again. (Closes: #479863) -- ... mpd playing: Manowar - Today Is A Good Day To Die . ''`. Dmitry E. Oboukhov : :’ : [email protected] `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537=head1 заголовок1 Это русский текст =over =item элемент списка 1 текст привязанный к элементу списка 1 =item элемент списка 2 текст привязанный к элементу списка 2 =back просто параграф текста И снова русский текст. Это опять русский текст. =head1 Это русские заглавные буквы: Й Ц У К Е Н Г Ш Щ З Х Ъ Ф Ы В А П Р О Л Д Ж Э Я Ч С М И Т Ь Б Ю =head1 А это маленькие буквы: й ц у к е н г ш щ з х ъ ф ы в а п р о л д ж э я ч с м и т ь б ю =cut
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---On Thu, Jun 06, 2013 at 11:29:42AM +0100, Dominic Hargreaves wrote: > Tags: -1 - patch > > On Mon, May 23, 2011 at 04:05:11PM -0700, Russ Allbery wrote: > > Niko Tyni <[email protected]> writes: > > > > > It's clearly still true, and I can't see any fix for it other than > > > adding =encoding utf8 lines in the POD files where necessary. > > > > > However, I think all the documents that are rendered incorrectly with > > > --utf8 are already rendered incorrectly now, albeit in a different > > > way. See below. > > > > Yes, without the --utf8 option, pod2man assumes that it can only use 7-bit > > ASCII, and hence mangles non-ASCII characters pretty badly. This is > > required for completely portable *roff output, since high-bit characters > > can even cause segfaults on some really old, broken *roff implementations. > > But this is probably now too conservative. > > > > I think the default, if --utf8 is not given, should probably be to just > > encode output in whatever the default local locale is and assume that > > people will do something else if they have to generate *roff that works on > > old, broken systems. I'm not sure what to do if that locale is C, though. > > Niko's patch to use pod2man --utf8 was applied (and then the code was > rewritten...). As we have seen during the perl 5.18 rebuild testing, > missing =encoding is now a fatal error. > > I think these points mean that this bug is essentially fixed with Debian > (experimental) and should be closed. I will aim to verify this using the > test case provided by the original submitter before closing this bug > (I don't have access to a suitable test system at the moment, but I > wanted to record this on the bug report whilst at least some of the > details were in my head). I've just tested and the original example_russian.pod now renders okay with =encoding UTF8 and pod2man --utf8. So I think this particular bug report can be resolved, finally. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--- End Message ---
