Inkscape

Pattern fill on text elements not exported to PDF

Bug #1314720 reported by Wout Fierens
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Medium
Unassigned

Bug Description

Inkscape 0.48.2 r9819 (Jul 15 2011)
OS X 10.9.2

We use Inkscape via the command line to generate PDF's and PNG's form SVG's created with our online print editor. This works brilliantly, although recently we discovered a bug. When text elements have a fill pattern with an image and their tspan's do not have the same fill attribute defined, the generated PDF will output the text element without the fill pattern, thus rendering them black. This is not the case for PNG's where the fill pattern is exported correctly. So the fill attribute is not correctly inherited by the tspan elements when the svg is exported as PDF.

We solved this problem by applying the fill pattern to all the tspan elements as well, but I suppose that shouldn't be necessary.

Revision history for this message
su_v (suv-lp) wrote :

Could you attach a sample SVG file and the generated PDF file, to ease testing with different inkscape versions on different systems? Ideally also the modified version of the SVG with the workaround as described … thx.

tags: added: exporting pattern pdf text
Revision history for this message
Wout Fierens (wout-f-deactivatedaccount) wrote :

Thanks for the quick reply!

I attached an zip file with the "faulty" svg and its results, the "fixed" svg and its results and of course the image used in the pattern. To reproduce the faulty pdf (on a Mac):

/Applications/Inkscape.app/Contents/Resources/bin/inkscape faulty.svg --export-pdf=faulty.pdf

Revision history for this message
su_v (suv-lp) wrote :

<off-topic>
> /Applications/Inkscape.app/Contents/Resources/bin/inkscape faulty.svg --export-pdf=faulty.pdf

This is not the best way to use inkscape from the app bundle on the command line (it won't be able to find any of the bundled inkscape resources, which might matter depending on what operations are executed via command line).

Better to use the outer wrapper script, and always reference input and output files with absolute paths (not really an issue e.g. in scripts):

$ /Applications/Inkscape.app/Contents/Resources/script "$PWD/faulty.svg" --export-pdf="$PWD/faulty.pdf"
</off-topic>

Revision history for this message
su_v (suv-lp) wrote :

On OS X 10.7.5, reproduced (via GUI and CLI export) with
- Inkscape 0.48.2 (official stable package, cairo 1.10.2)
- Inkscape 0.48.4 (r9939, cairo 1.12.2, cairo 1.12.16)
- Inkscape 0.48.x r10025 (cairo 1.12.16, cairo git master)
- Inkscape 0.48+devel r13328 (cairo 1.12.16, cairo git master)

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Wout Fierens (wout-f-deactivatedaccount) wrote :

Thanks for the wrapper scrip suggestion!

Revision history for this message
Joachim Breitner (nomeata) wrote :

Might be a duplicate of #1390569

Revision history for this message
su_v (suv-lp) wrote :

On 2015-04-13 14:09 (+0200), Joachim Breitner wrote:
> Might be a duplicate of #1390569

Bug #1390569 did not reproduce with cairo 1.10.2 (comment #5), this one did (comment #4).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.