[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem printing Lout-generated PDF
From: |
Valeriy E. Ushakov |
Subject: |
Re: Problem printing Lout-generated PDF |
Date: |
Tue, 6 Jul 1999 19:21:29 +0400 |
On Tue, Jul 06, 1999 at 06:02:28PM +0400, Vince Levey wrote:
> When I generate PDF output, I can view it with Adobe Acrobat Reader but
> I cannot print it. If I use the acroread "-toPostScript" option to
> convert the file to PostScript, showps/xpsview gives me the following
> when I attempt to display the resultant PostScript file:
>
> The current file contains a PostScript error:
>
> File: test.ps
> Error: nocurrentpoint
> Operator: currentpoint
This error comes from PS implementation of Tf (i.e., setfont) in the
produced PostScript.
PDF spec v1.2 says that text state operators are allowed at the page
decsription level, see figure 8.1 on p.210. Further note in section
8.7.1 "Text State parameters and operators", p.228, states that:
Note: These operators can appear outside of text objects, and the
values they set are retained across text objects on a single
page.
However recently released PDF spec v1.3 is controvercial. The same
figure 8.1 on p.320 in the new spec no longer lists text state
operators at allowed at the page description level. However the
section 8.7.1 have the same note (verbatim) that states that text
state operators "can appear outside of text objects".
It seems that acrobat correctly understand text state operators
outside text objects, but it exports PostScript in such a way, that
text operators assume they are inside a text object and so have the
current point set. The implementation of Tf, in particular ends with
the following code:
currentpoint iTm moveto
exch scalefont setfont
where iTm do text space matrix magic. And BT is defined to perform
0 0 moveto
after it sets up text matrix and other text state parameters.
SY, Uwe
--
address@hidden | Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen