Skip Menu |

This queue is for tickets about the Pod-Perldoc CPAN distribution.

Report information
The Basics
Id: 72425
Status: resolved
Priority: 0/
Queue: Pod-Perldoc

People
Owner: bdfoy [...] cpan.org
Requestors: Ben Bullock (no email address)
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 3.15_09
Fixed in: (no value)



Subject: groff produces many errors with Unicode output.
With the old version, $ perl -MPod::Perldoc -e 'print "$Pod::Perldoc::VERSION\n"'; 3.15_02 $ perldoc /home/ben/projects/Lingua-JA-Moji/lib/Lingua/JA/Moji.pod gives XXX where the Unicode characters occur: ----------------- SYNOPSIS Convert various types of Japanese characters into one another. use Lingua::JA::Moji qw/kana2romaji romaji2kana/; use utf8; my $romaji = kana2romaji ('XXXXX'); # $romaji is now 'aiueo'. my $kana = romaji2kana ($romaji); # $kana is now 'XXXXX'. =============== With the new version, installed from github, and run via the following script in the top directory, #!/home/ben/software/install/bin/perl use warnings; use strict; use lib 'lib'; use Pod::Perldoc; my $dir = '/home/ben/projects/Lingua-JA-Moji/lib/Lingua/JA'; my $file = "$dir/Moji.pod"; @ARGV = ($file); Pod::Perldoc->run (); the Unicode characters are appearing: --------------- =head1 SYNOPSIS Convert various types of Japanese characters into one another. use Lingua::JA::Moji qw/kana2romaji romaji2kana/; use utf8; my $romaji = kana2romaji ('あいうえお'); # $romaji is now 'aiueo'. my $kana = romaji2kana ($romaji); # $kana is now 'アイウエオ'. ================ However, there is a stream of errors from groff like this: ----------------- <standard input>:99: warning: can't find character with input code 151 <standard input>:99: warning: can't find character with input code 147 <standard input>:140: warning: can't find character with input code 158 <standard input>:246: warning: can't find character with input code 146 <standard input>:265: warning: can't find character with input code 143 <standard input>:265: warning: can't find character with input code 145 <standard input>:297: warning: can't find character with input code 142 <standard input>:361: warning: can't find character with input code 149 <standard input>:367: warning: can't find character with input code 144 <standard input>:367: warning: can't find character with input code 153 <standard input>:452: warning: can't find character with input code 148 <standard input>:478: warning: can't find character with input code 155 <standard input>:479: warning: can't find character with input code 156 <standard input>:515: warning: can't find character with input code 150 <standard input>:615: warning [p 7, 10.2i]: can't break line troff: Failed assertion at line 510, file `/usr/src/gnu/usr.bin/groff/src/roff/troff/../../../../../../contrib/gro ff/src/roff/troff/input.cpp'. grotty:<standard input>:6282:warning: no final `x stop' command groff: troff: Signal 6 (core dumped) =============== The "can't find character with input code" error originates from groff in file /usr/src/contrib/groff/src/roff/troff/node.cpp on FreeBSD. The above pod file is available on cpan as http://cpansearch.perl.org/src/BKB/Lingua-JA-Moji- 0.10/lib/Lingua/JA/Moji.pod if it is required for checking.
I'm working on this in the podman branch. I have no idea how I'm going to fix it. I think it's going to be a hard, cross-platform problem with different groff implementations.
I've patched this in the podman branch. You need a recent groff and we add the right switches now. Mark Allen tracked down the right things.
This is as good as it can be for the moment. A lot of systems have *roffs that don't support UTF8 input unfortunately.