Your message dated Thu, 9 Oct 2008 15:52:16 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#500210: perldoc perlrun spits out junk in synopsis
has caused the Debian Bug report #500210,
regarding perldoc perlrun spits out junk in synopsis
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.)
--
500210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500210
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: perl-doc
Version: 5.10.0-14
Severity: normal
Hi!
When running perldoc perlrun I have strange characters in the output of
it, and I managed to pin it down to a short POD snippet like this:
#v+
=head1 SYNOPSIS
B<perl> S<[ B<-sTtUWX> ]>
#v-
The S<[ ]> does strange stuff with the spaces it has in there. For
LC_ALL=C it puts a [C2] infront of the space, which turns into an LATIN
CAPITAL LETTER A WITH CIRCUMFLEX in my usual utf8 locale.
Hope this can get easy fixed, it really looks ugly.
Rhonda
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.26-1-powerpc
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages perl-doc depends on:
ii perl 5.10.0-14 Larry Wall's Practical Extraction
perl-doc recommends no packages.
Versions of packages perl-doc suggests:
pn groff <none> (no description available)
ii konqueror [man-browser] 4:3.5.9.dfsg.1-5 KDE's advanced file manager, web b
ii man-db [man-browser] 2.5.2-3 on-line manual pager
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.10.0-16
On Wed, Oct 01, 2008 at 02:50:57AM +0100, Colin Watson wrote:
> found 500210 5.10.0-15
> thanks
> For me, this fixed the case where a 0xA0 byte is embedded essentially
> accidentally in the middle of a UTF-8 stream (as happened with debconf's
> Russian translations), but it broke the case where 0xA0 is actually
> being used as a non-breaking space. Note that I'm using the new 'pod2man
> --utf8' option, although presumably so is Gerfried since perldoc now
> uses that option automatically.
Both this and the perlrun junk should be fixed in -16, uploaded today.
Closing again. Thanks to everybody involved.
--
Niko Tyni [EMAIL PROTECTED]
--- End Message ---
