Description of Problem:
When viewing a man page, I see a question mark wherever man has hyphenated a
word, instead of a hyphen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. man man (for example)
2. scroll down to where a word is hyphenated
question mark displayed
stock limbo2 install
This is no longer a problem since I installed null.
Probably a dup of Bug 75089
This is NOT a duplicate of Bug 75089. (But 80030 and 80931 are.) That bug was
complaining about xterm not displaying correctly. They are related, but 75089
addressed the wrong component. The problem is in man, not in xterm. Xterm is
actually displaying what man is giving it.
The problem is that man (actually the nroff macro) is outputting an incorrect
character. As mentioned in Bug 75089 comment #8, the nroff macros should be
outputting 0x2d (HYPHEN-MINUS), not 0x2212 (MINUS SIGN). Why? Because that's
what the user types when he is entering the character on the command line, and
what he enters to search the man pages. Outputting 0x2d would allow users to
keep the UTF-8 encoding, which (as Havoc points out in 80936) is the proper
thing to do.
As mentioned in comment #3 groff generates 0x2212 (MINUS SIGN) instead of
0x2d (HYPHEN-MINUS). This comes from the file usr/share/groff/1.18/font/devutf8/R
which has the following definition (similar for B,BI, and I files):
\- 24 0 0x2212
which is used in the man definition for ls(1) option -l:
use a long listing format
This will generate:
\u2212l use a long listing format
rather than the prefered (that could be searched for):
\u002dl use a long listing format
Since large numbers of man pages use \- to denote - for parameters
(including groff itself), \- should be mapped to 0x002D rather than
This can be fixed by changing:
\- 24 0 0x2212
\- 24 0 0x002D
in the files B,BI,I, and R in /usr/share/groff/1.18/font/devutf8 directory.
I think this is fixed in rawhide with Bug 79102 ?
confirmed. U+2212 is changed back to plain ascii minus in rawhide. Will go in