Font rendering problem after converting fonts to paths at PDF export

[Marc Aubreville]

Using a drawing imported from a PDF in Inkscape 0.47pre3 on OSX Snow Leopard 10.6.1, I get weird results when using
the "convert fonts to paths" feature of PDF export. Take a look at the attached image to get an idea of the problem. The
fonts seem outlined.

Creating a new drawing and copying all the objects into the file does not produce the error. I compared both SVG files
and found, that the failing one uses <g clip-path="url(#clipPath4107)"> and the other one doesn't.

[Marc Aubreville (marc-aubreville)]

This file produces the error. Even font objects added within this file produce the same strange rendering problems.

[su_v (suv-lp)]

reproduced with Inkscape 0.46+devel r22412 on OS X 10.5.8 and above attached file

> the failing one uses <g clip-path="url(#clipPath4107)"> and the other one doesn't.
I have seen this bug before, see in comments 7-14 in bug #388257. There it was limited to certain fonts (otf) and only when the text object was clipped and exported with the option 'Convert texts to path' set.

> Even font objects added within this file produce the same strange rendering problems.
Because all text objects are inside a clipped group. If I add a text outside the group it is exported as expected (see attached PDF - note: I don't have cmr10 installed on my system).

Workaround: the 'Text to Path' option for PDF export is still partially broken - you can export your files as recommended in bug #388257: convert the text objects to path before the export and save a copy as PDF with 'Convert texts to path' not set.

[su_v (suv-lp)]

related: Bug #462949 '"Save as a pdf file" has serious bug.' (marked as duplicate of bug #388257, but also describes similar issues with outlined text or added transparency when exporting with 'text2path')

[Beluga (buovjaga)]

Not reproduced.

Arch Linux 64-bit, KDE Plasma 5
Inkscape 0.92pre1 15054 (GTK3)

[jazzynico (jazzynico)]

Not reproduced on Windows XP (32-bit), Inkscape 0.46 and 0.47. Apparently a regression affecting the dev version only (and fixed before 0.47).