Slaven Rezic <[EMAIL PROTECTED]> writes:
> I just checked: only named entities are recognized by pod2man. For
> example "�" is converted to "i\*:". This causes groff to render this
> character as "ie". The groff_char manpage suggests to use "\(:i"
> instead, which is rendered correctly.
By groff. It won't work at all with vendor nroff.
windlord:~> cat foo.n
..TH TEST "1"
..SH TEST
This is a test: \(:i Did you see that?
windlord:~> /usr/bin/nroff -man foo.n | uniq
TEST(1)
User Commands
TEST
This is a test: Did you see that?
windlord:~> uname -a
SunOS windlord.stanford.edu 5.8 Generic_111850-02 sun4u sparc SUNW,Ultra-60
You will discover that the source of most issues like this is that the
intention of pod2man is to generate man pages that are portable, and
vendor nroff often simply does not handle non-ASCII characters, period.
Displaying � as ie is rather far from ideal, but it's marginally better
than displaying it as ? or as nothing at all, at least for some languages.
It's on my to-do list to add an option to pod2man to allow you to generate
groff-specific man pages. Whether or not that's the right thing to do
when generating Perl's own man pages probably will depend on what platform
Perl is built on.
> Hexadecimal entities are not recognized at all by pod2man.
Yup, this is a relatively minor fix once pod2man has full mapping tables
available, which is something I plan on working on as soon as I have the
time (and in particular, setting up the infrastructure so that they can be
regenerated automatically rather than maintained by hand). Since right
now, non-ASCII characters aren't handled at all well period, I haven't put
the effort into this yet, but once there's some way of handling them
properly at least for groff, I will definitely look at this.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
