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 06:39:19 -0700 2006 ------- > The problem with CUPS is that it does not behave as a print manager should > (by Adobe's definition). CUPS only puts a prolog before a file, CUPS has no > idea at all about pages and therefore no handling for PageSetup. > ... omitted the rest of the incorrect information ... (choking and sputtering!) Um, no. CUPS behaves exactly as a print manager is supposed to according to Adobe's DSC. The only things it doesn't implement are some of the resource inclusion bits which have security and/or usability issues. CUPS also includes EXTENSIVE APIs for embedding PPD-specific printer commands (including the corresponding DSC comments required for conformance), and has done so since CUPS 1.0. You just need to use the APIs... a2ps is a text converter, and CUPS DOES NOT use a2ps for anything. For text printing we have our own texttops filter, and all PostScript documents go through the pstops filter which handles imposition, feature code insertion, and so forth. As for properly supporting printer features, you can continue to insert printer-specific commands (be sure to use the proper Begin/EndFeature comments!), ideally using the CUPS APIs for this or your own PPD parser. Alternately you can just use the IncludeFeature comment to get CUPS to embed the commands for you, or use the cupsJobTicket comment in the document header to embed arbitrary CUPS options in the PostScript file. Regardless, the current CUPS release already seems to work fine with OOo output, so I don't think you need to do anything. N-up and "fitplot" (scale to fit) output automatically strips any Begin/EndFeature code. --------------------------------------------------------------------- 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]
