[Groff] Broken chars

5 tty1 terminal), it does not even show any apostrophe, but a block to indicate that 0x2018 is not available in this font. Is this a (big) bug in groff, or intention? Jan Engelhardt -- ___ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff

Re: [Groff] Broken chars

l ;). It has a plain |, but still gets a vertical bar. >PS: Why the heck is `perlcheat.man' and all other non-program man >pages of perl in man section 1? All manpages of "core perl" are in section 1. All *Perl module* manpages are in section 3pm. Well,

[Groff] Re: Broken chars

>But apparently many man-pages (not only the perl ones) do not do that >right. So what to do? Spank the manpage authors to do it the right way? Add another ton of hackish exceptions? All seems to be a cul-de-sac. Jan Engelhardt -- ___

About verbatim dashes in PostScript output

A recent LWN.net article (paywalled for a while) pointed at https://bugs.debian.org/1041731 and the topic of "-" vs "\-". Given the following input: -\-\[u002D]\[u2013]\[u2014]+\[u2212] Feeding it through `groff -Tutf8`, I get ‐−-–—+−