Yeah, that's a good way to solve this issue, include the internal PDF exporter and the Cairo PDF exporter too, for the print-monkeys it's not problem to have 2 "PDFs" in the save list (even with an "old" and "new" indicator for the newcomers).
Anyway thanx ^_^
On 10/17/07, jiho <jo.irisson@...400...> wrote:
On 2007-October-17 , at 15:01 , Jaime Martínez-Figueroa wrote:
I'm using both Inkscape 0.45.1.1 and a snap from this monday in Win32 (but with older snaps was the same).
There is a huge difference when saving in PDF files, other users reported an issue with the size of the files but the biggest difference is the quality, with 0.45.1.1 the PDF file is vectorial (~18kb) and with the snap it's a bitmap (~315kb)! BTW, the source SVG was http://en.wikipedia.org/wiki/Image:YamahaMotorCo.svg
Please note that I tried replacing the new libcairo2.dll with the older file and the result was the same.
This is because in 0.45.1 Inkscape used its own internal PDF renderer to save as PDF while the development snapshots use Cairo. Cairo still rasterizes many things when writing its PDFs indeed and handles groups in a strange way. However, from what I've heard, the Cairo guys are working hard on the PDF part so these improvements should end up in Inkscape in the end.
However I agree that having a better functionality in the old release than in the dev builds feels strange. I have had to keep a copy of 0.45.1 at hand to export some of my PDFs which were fine in 0.45.1 but mostly rasterized by Cairo. Why should these two PDF exporters be exclusive? Couldn't we have _both_ in the dev builds? Furthermore, if Cairo does not progress on this side before 0.46, one should probably have to re-enable the internal PDF exporter and it would be good to test it a bit before release IMHO.
Could someone re-enable the old PDF exporter? Pleaaase ;)
JiHO