Skip Menu |
 

This queue is for tickets about the podlators CPAN distribution.

Report information
The Basics
Id: 55574
Status: rejected
Priority: 0/
Queue: podlators

People
Owner: RRA [...] cpan.org
Requestors: nog [...] mpa-garching.mpg.de
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Problems with latin-1 characters in POD files under Perl 5.10.0
Date: Sat, 13 Mar 2010 09:39:01 +0100
To: bug-pod-man [...] rt.cpan.org
From: Norbert Gruener <nog [...] MPA-Garching.MPG.DE>
Download (untitled) / with headers
text/plain 1.8k
I am running This is perl, v5.10.0 built for i486-linux-gnu-thread-multi with Name: Pod::Man Version: 2.16 I have poblems when I convert the example POD file "latin1.pod" containing latin-1 characters to MAN. The latin1 character "copyright" is converted to "X" ~>/usr/bin/pod2man latin1.pod \" ======================================================================== .\" .IX Title "LATIN1 1" .TH LATIN1 1 "2010-03-12" "perl v5.10.0" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "COPYRIGHT AND DISCLAIMER" .IX Header "COPYRIGHT AND DISCLAIMER" .Vb 2 \& X 2001\-2008 Norbert E. Gru\*:ner <nog@MPA\-Garching.MPG.de>. \& All rights reserved. .Ve I have also upgraded the module "Pod::Man" to Version 2.23 but there is no difference. When I convert the example POD file to TEXT everything is fine. ~>/usr/local/bin/pod2text latin1.pod COPYRIGHT AND DISCLAIMER © 2001-2008 Norbert E. Grüner <nog@MPA-Garching.MPG.de>. All rights reserved. When I do the same under Perl 5.8 This is perl, v5.8.8 built for i486-linux-gnu-thread-multi Name: Pod::Man Version: 1.37 it looks as I have expected it. ~>/usr/bin/pod2man latin1.pod .\" ======================================================================== .\" .IX Title "LATIN1 1" .TH LATIN1 1 "2010-03-12" "perl v5.8.8" "User Contributed Perl Documentation" .SH "COPYRIGHT AND DISCLAIMER" .IX Header "COPYRIGHT AND DISCLAIMER" .Vb 2 \& © 2001\-2008 Norbert E. Grüner <nog@MPA\-Garching.MPG.de>. \& All rights reserved. .Ve Cheers, Norbert -- Ceterum censeo | PGP encrypted mail preferred. Redmond esse delendam. | PGP Key at www.MPA-Garching.MPG.de/~nog/
Download latin1.pod
text/x-pod 115b

Message body is not shown because sender requested not to inline it.

Subject: Re: [rt.cpan.org #55574] Problems with latin-1 characters in POD files under Perl 5.10.0
Date: Mon, 15 Mar 2010 00:16:36 -0700
To: bug-podlators [...] rt.cpan.org
From: Russ Allbery <rra [...] stanford.edu>
Download (untitled) / with headers
text/plain 1.7k
"nog@mpa-garching.mpg.de via RT" <bug-podlators@rt.cpan.org> writes: Show quoted text
> I am running > This is perl, v5.10.0 built for i486-linux-gnu-thread-multi > with > Name: Pod::Man > Version: 2.16
Show quoted text
> I have poblems when I convert the example POD file "latin1.pod" > containing latin-1 characters to MAN. The latin1 character > "copyright" is converted to "X"
Yes, this is intended behavior. See the documentation for the -u option to pod2man: -u, --utf8 By default, pod2man produces the most conservative possible *roff output to try to ensure that it will work with as many different *roff implementations as possible. Many *roff implementations cannot handle non-ASCII characters, so this means all non-ASCII characters are converted either to a *roff escape sequence that tries to create a properly accented character (at least for troff output) or to "X". This option says to instead output literal UTF-8 characters. If your *roff implementation can handle it, this is the best output format to use and avoids corruption of documents containing non- ASCII characters. However, be warned that *roff source with literal UTF-8 characters is not supported by many implementations and may even result in segfaults and other bad behavior. Be aware that, when using this option, the input encoding of your POD source must be properly declared unless it is US-ASCII or Latin-1. POD input without an "=encoding" command will be assumed to be in Latin-1, and if it's actually in UTF-8, the output will be double-encoded. See perlpod(1) for more information on the "=encoding" command. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
Per discussion, the behavior is at this point intentional. Resolving accordingly.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.