[Top][All Lists]

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

Re: [Groff] Re: PFB->PFA and overlong lines

From: Werner LEMBERG
Subject: Re: [Groff] Re: PFB->PFA and overlong lines
Date: Wed, 26 Mar 2003 15:14:48 +0100 (CET)

> > 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.
> First off the 255-character limit is over 10 years old.

My printer too.

> Second off, t1asm/t1disasm does not claim to generate
> "DSC-conforming" PostScript; neither do most of these tools.  We
> don't check whether DSC comments are present, or whether they
> conform to the DSC spec. We don't check even whether the included
> PostScript is valid (whether saves and restores match up, for
> example).  And we shouldn't; these tools are meant to replicate
> their input, with only those changes the user explicitly requested.
> Garbage in garbage out.  A tool that claims to "DSC-ify" PostScript
> might check line lengths as you suggest, but my feeling is that
> t1asm/t1disasm should not.

Perhaps a warning could be emitted...

Anyway, groff's pfbtops utility program for converting PFB into PFA
now folds overlong lines; additionally, I've removed the 255-char
limit in the PS resource manager of grops.


reply via email to

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