[cairo-bugs] [Bug 34560] path operator fixup incorrectly applied to stroked paths in pdf/ps backends

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=34560

--- Comment #4 from Andrea Canciani <ranma42 at gmail.com> 2011-03-08 02:39:01 PST ---
(In reply to comment #3)
> (In reply to comment #1)
> > I believe we can just emit explicit move_to/line_to commands to describe
> > rectangles in ps/pdf and get rid of _cairo_path_fixed_is_rectangle().
> 
> It is better to have a few extra lines of code to keep this optimization. It
> makes a big difference to the PDF file size when there is a very large number
> of rectangles. eg the test cases in bug 13433.

Currently we only optimize paths composed of a single rectangle. Is this enough
or should we also optimize paths composed of multiple rectangles and/or
rectangles and other path elements?

If we want this optimization in the most generic form (rectangles in a generic
ops sequence), we might want to have a fill-path-interpreter and a
stroke-path-interpreter which optionally support additional operations, like
rectangles.

If we just want to optimize multiple-rectangles paths, we probably want
_cairo_path_fixed_iter_is_stroke_box()

If we just want to optimize paths with a single rectangle, we can fix
_cairo_path_fixed_is_rectangle().

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.