Michael,
ps, eps and pdf output are generated using the cairo library. This library is/will be also used for gui rendering. For us developer this means one code for different output targets. And so consistent outputs. Also there where a lot of trouble with fonts in PS files. The library rasterizes when the vectors can not translated into the target format because of (blur) filters or transparency.
Hope you understand this.
Pls communicate features that you are missing and files that you think are translated not correctly.
Regards,
Adib.
On Thu, Feb 17, 2011 at 5:35 PM, Michael Palmer <mike4561@...400...> wrote:
Hi,
This message was sent previously but bounced because the attachments were to big, and then apparently got lost. Apologies in case this gets double-posted.
To the issue: if I understand it correctly, the eps and pdf export was switched in the transition from version 0.46 to 0.47. In my experience, the new eps export doesn't work well, producing larger files and also converting some vector elements to raster in an unpredictable way. The new pdf export seems to produce less rasterization but also produces large files that can take a very long time to render in a pdf viewer.
I suppose there was a reason for this transition, maybe gradients, transparency and such. However, where these features are not required, the old export routines produce more compact output and avoid wanton rasterization. Also, the old-style eps files can be used with LaTeX' psfrag mechanism, whereas the new-style ones cannot.
So, my question is, could we please have the old eps export back - as an additional option, or maybe as a user-installable extension?
Thanks for consideration, best, Michael
PS Example files produced from the same svg file and exported with versions 0.46 and 0.47, respectively, are not attached (the 0.47 ones are too big and blow the message size limit) but can be viewed at http://watcut.uwaterloo.ca/_files/
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel