[Top][All Lists]

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

[Groff] improved PS font support

From: Werner LEMBERG
Subject: [Groff] improved PS font support
Date: Mon, 10 Mar 2003 23:03:33 +0100 (CET)

Finally, finally!  Full support for URW fonts and other Type 1 fonts
which have more than 256 glyphs!  grops can now generate multiple
encoding vectors on the fly.  afmtodit has been extended also to
produce such fonts using the new rules for naming composite glyphs.

A simple test with standard Type 1 fonts: Just create a file which
accesses characters `a' and `\[u2026]' (`ellipsis', having glyph index
256 in TR).  If you look into the created PS file you can see a second
encoding vector of Times-Roman for \[u2026].

grops has also been extended to accept lines of any length.  While
this violates Adobe's DSC standard (which allows only lines shorter
than 255 characters) it doesn't seem to do much harm.  For example,
dvips doesn't emit a warning either.  Main reason for the change was
ghostscript's pfbtopfa program (coming with gs 6.51) which produces a
single very long line for the eexec part instead of splitting into
multiple shorter lines (basically, this looks like a bug to me).  But
even groff's pfatops fails to convert the URW fonts properly to pfa
since they contain overlong /Notice strings which should be broken
into multiple lines (each ending with `\').



reply via email to

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