It seems that somehow gdiplus dll and PDFNet built-in PDF rasterizing
dll are inter-replaceable, could you provide more detailed
- How to configure the app to use GDI plus or built-in?
- Pros and cons of each option?
'e_GDIPlus' rasterizer is using GDI+ graphics library (which is not
fully compatible with PDF graphics model), whereas 'e_BuiltIn' fully
supports PDF graphics model. As a result some PDF documents will
render properly using e_BuiltIn rasterizer, but not using e_GDIPlus.
e_BuiltIn rasterizer is also cross-platform (i.e. it is available on
Mac, Linux, Solaris, etc), whereas GDI+ is only available on Windows.
Another advantage of e_BuiltIn rasterizer is that you can build a
stand-alone executable/DLL that don't have any other DLL dependencies
(such as GDIPLUS.DLL). This can simplify deployment on Windows 2000
and older Windows platforms.
The advantage of e_GDIPlus is that it can be used to send vector
output to any device context (e.g. metafile, printer, etc). Sometimes
this will result in smaller spool files for high-resolution printing.
Also e_GDIPlus rasterizer can be used to convert PDF pages to EMF/WMF
Although both e_BuiltIn and e_GDIPlus support anti-aliasing, e_BuiltIn
can produce higher quality raster output.
- how to configure the app to use GDI plus or built-in
You can switch between the two using pdfrasterzer/pdfdraw/