kbd-1.15 lat1-16 font issues with groff-1.20.1
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Matthew Burgess
Hi Alexey,
I'm viewing man pages using a combination of groff-1.20.1 and the lat1-16 font from kbd-1.15. You can see the results of this at
http://www.linuxfromscratch.org/~matthew/test-results/preconv.en_utf8.jpg.As you can see, the line-break character (U+2010) isn't displayed correctly.
We used to workaround this with previous versions of Groff by substituting U+2010, U+2212 to U+002D (minus sign). See
It seems that these characters are not mapped at all. At least the U+2010.
Quoted 9 lines
http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/groff.html. Due to a change in Groff, that substitution no longer applies.
Is it possible to map those characters like that in the lat1-16 font itself? That way, if there happen to be any other programs that output the problematic characters, they'll display correctly without any further changes.
If so, how might we go about this, and is this suitable for the upstream Kbd package sources?
I think we can map this characters if they not mapped at all.
P.S. Add CC: kbd@lists.
Anyone have any ideas ?
Signature · 1 line
Rgrds, legion
Στις Thursday 12 February 2009 00:17:54 ο/η Alexey Gladkov έγραψε:
Quoted 17 lines
Quoted 10 lines · Matthew Burgess
Hi Alexey,
I'm viewing man pages using a combination of groff-1.20.1 and the lat1-16 font from kbd-1.15. You can see the results of this at
http://www.linuxfromscratch.org/~matthew/test-results/preconv.en_utf8.jpg.As you can see, the line-break character (U+2010) isn't displayed correctly.
We used to workaround this with previous versions of Groff by substituting U+2010, U+2212 to U+002D (minus sign). See
It seems that these characters are not mapped at all. At least the U+2010.
Quoted 3 lines
http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/groff.html. Due to a change in Groff, that substitution no longer applies.
Quoted 9 lines
Quoted 6 lines
Is it possible to map those characters like that in the lat1-16 font itself? That way, if there happen to be any other programs that output the problematic characters, they'll display correctly without any further changes.
If so, how might we go about this, and is this suitable for the upstream Kbd package sources?
I think we can map this characters if they not mapped at all.
I don't see any problem so I am attaching newlat1-16.psfu with new mappings U+2010, U+2012, U+2013 and U+2212 to U+002d.
If someone wish to play with and change mappings here it is:
$psfgettable lat1-16.psfu > table.txt
Editing table.txt ---> newtable.txt with our preferences and then
$psfaddtable lat1-16.psfu newtable.txt newlat1-16.psfu.
cheers
Lefteris