-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pstops filter gets disturbed by Adobe PostScript write though from Windows applications #1085
Comments
CUPS.org User: h.blischke This issue may easily cured by treating the mentioned comments as follows by the pstops (1) treat "%ADO_BeginApplicationHeaderComments" the same way as This has been verified today with CUPS 1.1.19 . |
CUPS.org User: h.blischke Sorry, forgot to mention two things: (1) The Adobe pass through stuff looks for a dictionary named NTPSOct95 which (2) The said pass through stuff ends with an %%EOF comment line just after I did my tests on this issue with the attached perl script as an additional filter, but I had |
CUPS.org User: mike Couple things:
|
CUPS.org User: h.blischke You DO know that the W2K/XP PostScript driver has severe issues with Type1 fonts |
CUPS.org User: mike Fixed in Subversion repository. We've never run into that problem with the Win2k/XP driver, nor is it likely that we will be able to fix it... |
Version: 1.1-current
CUPS.org User: h.blischke
Some of the Adobe applications on Windows XP (from the "creative suite")
produce their own PostScript instead of relying on the Windows GDI
(what is a good thing in principle).
When printing to a printer, they use the printer driver's write through
capability but behave strangely:
(1) the DSC comments in the write through snippets are much the same
as if the app directly writes a PostScript file bypassing the
printer driver stuff.
(2) the snippets are bracketed with comments on a per page basis:
%ADO_BeginApplicationHeaderComments
at the begin of the snippet,and
%ADO_EndApplicationTrailerComments
at the end of the snippet.
In between there are the usual comments like %%BeginSetup, %%EndSetup,
%%Page: x y, and even %%EOF.
As the pstops filter does not know of these weird comments, it gets
disturbed by the DSC comments of the included snippets, especially the
%%EOF comments act as a premature EOF condition, so nothing comes out of
the
printer.
The text was updated successfully, but these errors were encountered: