[Clfs-commits] [CLFS Trac] #182: UTF-8

[CLFS Trac]

#182: UTF-8
--------------------+-------------------------------------------------------
  Reporter:  ken    |       Owner:  clfs-commits at lists.cross-lfs.org.
      Type:  task   |      Status:  new                              
  Priority:  minor  |   Milestone:  CLFS Standard 1.2.0              
 Component:  BOOK   |     Version:  CLFS Standard SVN                
Resolution:         |    Keywords:                                   
--------------------+-------------------------------------------------------
Comment (by willimmen):

 Replying to [comment:27 jim]:
 > Then post the research instead of saying because I say so. The CLFS
 requirements for UTF-8 are no additional packages and no downgrading of
 packages. Stay within these guidelines and show proof that it works along
 with test cases, and I will consider putting it in the book.
 Well, even I admit, there is ONE new package for CLFS to support Man-DB.
 GDBM, which is lightweight and simple to compile, unlike BDB.
 Groff doesn't have to be downgraded no more, thanks to preconv support in
 Man-DB. But there is two minor things:

  1. Man-DB doesn't normaly think Groff 1.20.1 is multibyte capable,
 resulting in messed up man pages. That is a Man-DB issue, reported
 upstream, and for now, use --enable-mb-groff/
  2. Still, many screen fonts don't have Unicode single dashes and quotes
 in them, meaning the ASCII equvilents are needed. This sed worked for
 Groff 1.18.1.4:

 {{{
 sed -i -e 's/2010/002D/' -e 's/2212/002D/' \
     -e 's/2018/0060/' -e 's/2019/0027/' font/devutf8/R.proto
 }}}

 ...but not for 1.20.1, because the format has changed. Something needs to
 be figured out about this.

 And yes, I will show test cases, with a modified CLFS SVN X86_64 Multilib
 system, with Man-DB instead of Man.

-- 
Ticket URL: <http://trac.cross-lfs.org/ticket/182#comment:28>
CLFS Trac <http://trac.cross-lfs.org>
The Cross Linux From Scratch Project.