Comment 15 for bug 284680

Let me rephrase my previous comment and add a summary of the findings in bug report #388257:

The fix committed in rev 21337 solved the issue with omitted text objects when exporting to PS/EPS/PDF using the (cairo) 'text to path' option. At the same time it revealed another bug within this routine:

Text objects are converted and added to the document several times, stacked in place (on top of each other), thus increasing the overall size of the exported drawing and decreasing the rendered quality of text objects converted to paths (not anti-aliased 'pixelated' appearance). The effect only gets visible when exporting documents with several lines of text. Small drawings like logos or buttons with single words don't expose this bug, maybe that's why it was not noticed when testing rev 21337.

examples illustrating this effect:

<http://launchpadlibrarian.net/28012678/test.47.svg>
<http://launchpadlibrarian.net/28012660/test.47.pdf>
<http://launchpadlibrarian.net/28815267/388257-test.47-reimported-and-ungrouped.svg>

<http://launchpadlibrarian.net/28831387/O_clone.svg>
<http://launchpadlibrarian.net/28831394/O_clone.ps>
<http://launchpadlibrarian.net/28833163/388257-O_clone-ps-reimported.svg>

In comment 26 of bug #388257, I tried to describe it like this:
'attaching another example trying to illustrate what happens. Somewhere
while parsing the svg-tree for text objects or in a loop (calling the
cairo_glyph_path() function in 'cairo-render-context.cpp'?) a counter
seems not getting reset or updated properly, thus the current text/path
object is appended instead of replacing with every loop.'
<http://launchpadlibrarian.net/28833164/2009-07-08--2-ps-reimported.svg>

My apologies to 'theAdib' for badly wording my observations and using the unfounded phrase 'and created a related [bug]'!