On Wed, 17 Oct 2007 15:17:33 -0300, "bulia byak" wrote:
On 10/17/07, jiho <jo.irisson@...400...> wrote:
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.
Definitely, though which exporter to ship with depends on when we release and how much progress cairo will have by then. I suggest we revisit this issue closer to our release, and if latest cairo is still not good enough by then, we'll have to reenable the old one exactly as Mental did for 0.45.
Our strategy with cairo has been to make things correct first, (even if ridiculously inefficient---see PDF files with mega-rasterization), and then to incrementally improve the performance while maintaining correctness.
That is, we've tried very hard to avoid regressions. And, during the 1.5 series there have been a *lot* of great optimizations to cairo's PDF output.
Now, I'm coming in to the middle of this conversation, (thanks for CC'ing me), but what are the current issues being faced? Are the regressions that you have found in cairo's PDF output? If so, I definitely want to get these fixed before cairo's 1.6.0 release.
Thanks,
-Carl