From 72857b1207600b10bd73e9b1fee479438aae3ac9 Mon Sep 17 00:00:00 2001
From: scuri
The main motivation for the use of Cairo was transparency for all the primitives. Beyond that we got other features like anti-aliasing, gradient -filling, transformations and back-ends (support to rendering: PDF, PS, SVG and -PNG surfaces).
+filling, transformations and other back-ends (support to rendering: PDF, PS, SVG and +IMAGERGB surfaces).This driver still does not completely replace the X-Windows and GDI Windows base drivers, because Cairo does not have support for bitwise XOR operations and for complex clipping regions.
@@ -38,9 +38,12 @@ for complex clipping regions. This function affects only the cdCreateCanvas function call, once created the canvas will be always a Cairo canvas. In fact the function affects primary the definitions CD_NATIVEWINDOW, - CD_IMAGE and + CD_IMAGE, + CD_PRINTER and CD_DBUFFER, because they are - function calls and not static defines. + function calls and not static defines. + CD_PRINTER can only + be used along with GDK base driver in UNIX.Using Cairo it is allowed to create more that one canvas at the same time for the same Window. And they can co-exist with a standard GDK, Win32 or X-Windows canvas.
To enable the use of Cairo based drivers you must call the initialization function @@ -60,7 +63,8 @@ used.
Similar to CD_PS, uses the same creation parameters. But margins are not supported and Postscript level can be 2 (parameter -2) - or 3 (parameter -3).
+ or 3 (parameter -3). The "CMD" attribute is not supported, and the new + attribute "DSCCOMMENT" accepts a string that is saved as a DSC comment.