To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=65491





------- Additional comments from [EMAIL PROTECTED] Wed May 17 11:50:09 -0700 
2006 -------
The PPD API is documented here:

    http://www.cups.org/documentation.php/api-ppd.html

The ppdEmit*() functions handle embedding printer-specific commands in your PS
file - use ppdMarkDefaults and ppdMarkOption (and/or cupsMarkOptions) to select
the options to emit.

As for replacing feature code, we *don't* do this because the spec doesn't
provide sufficient information to reliably implement it for all types of
options. Specifically, custom page sizes (and now custom options) cannot be
substituted (all you get is %%BeginFeature: *CustomPageSize True) and it only
works for PostScript options.  That is one of the reasons we added support for
"%cupsJobTicket: option=value" lines in the document header in CUPS 1.1.x, and
we now also support %%IncludeFeature: in CUPS 1.2.x.

Like I said, what you are doing now is OK - the only changes you need to make
are to put the document-wide options in the setup section and/or put the
page-specific options at the beginning of each page in the page setup section.
Otherwise, your pages are not independent, which prevents us from doing ordering
and page ranges properly. As I mentioned before, CUPS 1.2 and beyond strips the
feature code when a user prints N-up or scaled-to-fit.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to