DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42144>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42144


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20399|0                           |1
        is obsolete|                            |




------- Additional Comments From [EMAIL PROTECTED]  2007-08-09 04:09 -------
Created an attachment (id=20621)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20621&action=view)
patch file

This patch depends upon the new safe set page device postscript macro being
applied to XmlGraphicsCommons (see
http://issues.apache.org/bugzilla/show_bug.cgi?id=43069).

* Adds new <ps:ps-setpagedevice/> extension to the postscript renderer
(see http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPostScript for
details).
* Adds safe-set-page-device and dsc-compliant configurations options.

The default value for the "safe-set-page-device" setting is "false". Setting it

to "true" will cause the renderer to invoke a postscript macro which guards
against the possibility of invalid/unsupported postscript key/values being
issued to the implementing postscript page device. 

The default value for the "dsc-compliant" setting is "true". Setting it
to "false" will break DSC compliance by minimizing the number of setpagedevice
calls in the postscript document output.  This feature may be useful when
unwanted blank pages are experienced in your postscript output.  This problem
is caused by the particular postscript implementation issuing unwanted
postscript subsystem initgraphics/erasepage calls on each setpagedevice call.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to