🚀 go-pugleaf

In article <805@aut.UUCP>, nbladt@aut.UUCP (Norbert Bladt) writes:
|> cca13@seq1.keele.ac.uk (G.D. Pratt) writes:
|> 
|> >Hi,
|> >I've been using xfig v2.0 to create a diagram and whenever I convert
|> >the *.fig file to a *.ps file via f2ps or with the latest version of
|> >transfig I get this error from the PostScript printer (Agfa PS400) 
|> 
|> >> psif: seq1:gerry ps start - Mon Sep 24 16:28:26 1990
|> >> %%[ Error: undefinedresult; OffendingCommand: arcto ]%%
|> >> %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
|> >> psif: end - Mon Sep 24 16:29:31 1990
|> 
|> >*but* when I preview it with ralpage or GhostScript 2.0 it's OK.
|> >Is this PostScript right or wrong? I've included a very
|> >shortened version of the PostScript which displays the same symptom:-
|> 
|> I saw the same problems with laser printers connected to a VMS
|> system. The printers can be configured to, e.g., 80 characters
|> per line (or 132). Now, Postscript is a progamming language
|> and not simply text to print ! So, if long lines get truncated (or wrapped,
|> which doesn't matter in this case) the result is an illegal
|> Postscript program ! I didn't count the number of characters up to
|> your "arcto" command, but isn't it possible ?
|> 
|> (This is just speculation:
|> What about a stupid PS Interpreter cutting off lines at 80 (or
|> whatever fixed number) of columns ?
|> >Any help welcome in this my darkest hour -):
|> Hope this helps.

I have emailed the solution to Mr. Pratt.
The problem is that he has drawn an arc-box with zero width AND height.
The postscript command that is generated from that object will give
undefined results.

--
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL; they don't pay me enough for that.