Bug #101538 for Pod-Usage: Pod::Usage doesn't handle E<copy> correctly

Pod::Usage uses Pod::Text for formatting the output, including the translation of E<...> to the output stream. When redirecting the output to a file (pod2usage -out ...), and opening the file in a good editor, at least some of the entities are shown correctly. It's still not perfect, but it shows that some results also depend on the capabilities of the terminal emulator... and that will be hard to fix, since it requires exact knowledge of the capabilities of all possible terminal emulators out there... ouch! @podlators: would you care to take this ticket? Cheers, Marek

"Marek Rouchal via RT" <bug-Pod-Usage@rt.cpan.org> writes: Show quoted text
Show quoted text
Show quoted text
Well, from the perspective of podlators, it's up to the caller to say what output character set you want. There is unfortunately no really great way to detect the desired output character set; the default is to use the same output encoding as was used for the input encoding, for historical reasons and backward compatibility. So, basically, podlators has the same problem that you have, and I don't think is really in a better place to address it. If you want UTF-8 from Pod::Text, just construct the Pod::Text object with utf8 => 1. (Command line: pod2text -u.) You may want to consider adding such an option to Pod::Usage and pass the buck up an additional level, although I admit that's rather unfortunate. (That said, there isn't a generalized capability to specify the output encoding at present, just utf8 or the default passthrough behavior. That's something I'd like to add.) -- #!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker $^=q;@!>~|{>krw>yn{u<$$<[~||<Juukn{=,<S~|}<Jwx}qn{<Yn{u<Qjltn{ > 0gFzD gD, 00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{ rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print