#2337: Groff-1.20.1 doesn't display line-breaking characters correctly in UTF-8
environments
------------------------------------------+---------------------------------
 Reporter:  matt...@…                     |       Owner:  lfs-b...@…            
       
     Type:  task                          |      Status:  new                   
       
 Priority:  normal                        |   Milestone:  7.0                   
       
Component:  Book                          |     Version:  SVN                   
       
 Severity:  normal                        |    Keywords:                        
       
------------------------------------------+---------------------------------

Comment(by k...@…):

 Replying to [comment:1 matt...@…]:
 > This isn't actually a Groff issue, it's just the fact that my font,
 lat1-16, doesn't contain the symbol U+2010 (UTF-8 \xe2 \x80 \x90).
 >
 > If I am reading
 http://homepage.ntlworld.com/zarniwhoop/consolefonts/sigma.html correctly,
 a console font can only contain 512 glyphs (including bold variations of
 the same character).
 >
 > Ken, any ideas if it's possible to work out from the .psfu file, whether
 there's space to add another couple of glyphs to lat1-16?  GCC spits out
 some '?' too, when it prints some fancy warnings out, so it'd be nice to
 get that symbol added, while we're at it.
 >
 > Or maybe we should add sigma-consolefonts to the book (assuming it
 contains the correct glyphs)? :)

 I no longer remember how to look at .psfu files - in the past, I googled
 for something like "psf file format" and found enough to be able to read
 whatever I was looking for.  I know that the current kbd maintainer takes
 patches, but I don't know how to edit these fonts. I'm guessing fontforge
 might be the right tool.

 Sigma-consolefonts maps U+2010 (hyphen), as well as U+2012, U+2013,
 U+2212, to U+002D (minus sign) in all of the screen font maps except
 'drdos'.  Possibly, you can do the same addition of multiple characters
 for the same glyph using 'dd' once you've worked out the format ;-)

 The attachment is the prog I wrote to list what was in a psf.  Dunno if it
 will help.

 As to whether the book should use sigma-consolefonts, I have no idea.  I'm
 sure many people will hate the output, either because it is a lot less
 bold, or because the more useful mappings are 512-byte and that screws up
 their bold colours.

 I haven't looked at the trunk version of the book yet, but previously we
 used to do
 {{{
 sed -i -e 's/2010/002D/' -e 's/2212/002D/' \
        -e 's/2018/0060/' -e 's/2019/0027/' font/devutf8/R.proto
 }}}
 before we configured groff to get rid of these awkward characters.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2337#comment:2>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to