[Top][All Lists]

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

[Groff] PFB->PFA and overlong lines

From: Werner LEMBERG
Subject: [Groff] PFB->PFA and overlong lines
Date: Tue, 11 Mar 2003 14:59:33 +0100 (CET)

Dear maintainers of T1 utilities, 

the DSC standard from Adobe requires that no input line is longer than
255 characters.  In case a PFA file is included as a resource, this
requirement should hold also.

Now consider the URW font corresponding to Times Roman, n021003l.pfb,
distributed with gs (I have NimbusRomNo9L-Regu 1.05).  It contains an
overlong /Notice string.  The pfbtopfa script of ghostscript (tested
with 6.51 and 8.00) works worst: It creates an overlong /Notice string
and a single long line for the eexec data.  Two other converters,
pfbtops from groff and a pipe through t1disasm and t1asm, don't have
overlong lines in the eexec section but didn't catch the /Notice
problem.  Neither does type1fix from the textrace package.

This looks like a bug to me.  Fixing it should relatively simple by
splitting the lines with a final `\' if in a string (at least this is
what I will do in pfbtops).


reply via email to

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