[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Groff] Composite output regression due to Unicode fonts?

From: Colin Watson
Subject: [Groff] Composite output regression due to Unicode fonts?
Date: Wed, 9 Aug 2006 02:36:09 +0100
User-agent: Mutt/1.5.9i

I've been testing out how 1.19.2 and CVS groff with input files in
various languages and encodings fed through preconv. Using the attached
troff output file generated by:

  zcat /usr/share/man/pl/man1/822-date.1.gz | ./src/preproc/preconv/preconv 
-eISO-8859-2 | ./test-groff -mandoc -Tutf8 -Z

... on a Debian system with manpages-pl installed and with CVS groff, I
found that 1.19.2's grotty correctly renders characters such as U+017C
and U+0105 (which appear as u007A_0307 and u0061_0328 respectively in
the troff output), but CVS's grotty displays these as only the base
character (z and a respectively). Characters not rendered as Unicode
composite characters, such as U+0107 => 'c, display correctly using both
versions of groff. The attached diff should demonstrate the problem

Furthermore, running CVS's grotty with 1.19.2's fonts restores the
previous handling.

It seems as if this problem might be due to Unicode fonts. Is it
possible that libdriver doesn't know how to deal with composite
characters that aren't explicitly listed in the font definition?


Colin Watson                                       address@hidden

Description: Text document

Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]