Comment 13 for bug 388257

Another test case: the pixelated text output quality in PDF depends on
the sequence of the SVG elements in the SVG file, at least when viewing
the PDF file with 'Preview' on OS X. Can you confirm that the issue is
independent of the PDF viewer (Adobe, evince,… )?

Save the attached file as PDF with
a) keep text as text
b) convert text to path
and compare the results.

I see the last elements (bottom right within group) of a previously
grouped and duplicated array of text boxes rendered close to the
original whereas the first elements (upper left within group) appear
pixelated and not anti-aliased.

@skam - I tried to create a simpler clipped text example - can you help
me out with this: I could not figure out from your sample svg file, what
effect you achieve with clipping a text with an unfilled, stroked
rectangle as clipping path. The only (side-)effect I get is that the
clipped text isn't exported as text when saving as PDF (instead it's
rendered as bitmap or converted to path?). What do I miss here? Your
file exports correctly to PDF when keeping text as text (without clipping).