Cairo PDF export cuts last characters from strings containing ligatures

Bug #218045 reported by Asbjørn Clemmensen
46
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
Unassigned
Nominated for 0.46.x by Frédéric Grosshans
Nominated for 0.47.x by Frédéric Grosshans
Nominated for Old by Frédéric Grosshans

Bug Description

When exporting a drawing to PDF in Inkscape 0.46, the last character gets chopped off some strings. I can't seem to come up with a reasonable explanation for this. I've tested this error in Evince and Acrobat.

This error does not occur when converting strings to paths, but then the PDF grows huge.

I've made a screenshot showing this occuring, with the PDF on one side and the Inkscape view on the other. Sorry about the blurriness of the Inscape example.

Revision history for this message
Asbjørn Clemmensen (func) wrote :
Revision history for this message
Frédéric Grosshans (fgrosshans) wrote :

I also have been bitten by this bug. I a small svg text with this bahaviour, as well as the corresponding Cairo-exported pdf. The SVG is fairly minimal (default empty document + a short string "amplifier", which becomes "amplifie" in the pdf)

Revision history for this message
Frédéric Grosshans (fgrosshans) wrote :
Revision history for this message
Frédéric Grosshans (fgrosshans) wrote :

I just did further tests : The proble seems to be linked to ligatures (ff and fi). See attached files

Revision history for this message
Frédéric Grosshans (fgrosshans) wrote :
Revision history for this message
Vianney le Clément (vleclement) wrote :

I've got this problem too. I don't recall seeing this in inkscape 0.45.

The problem indeed seems to be linked with ligatures. If a line contains a ligature with 2 letters (ff, fi, fl, etc.), the last character is missing in the pdf export. If a line contains a ligature with 3 letters (ffl), the 2 last characters are missing in the pdf export. One workaround for now is to add a space or two at the end of those lines.

Any progress?

BTW, I'm using ubuntu hardy amd64 (but it also happened on 32 bits), inkscape 0.46-0ubuntu2 and cairo 1.6.0-0ubuntu2.

Revision history for this message
Frédéric Grosshans (fgrosshans) wrote :

This bug is still present in Intrepid.

I suspect this bug to be related to Cairo more than Inkscape, since it comes through Cairo's pdf export. Is it possible to test Cairo svg2pdf algorithm without Inkscape to be sure ?

Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed in 0.46, but it works well in build 20997 and svg2pdf (cairo 1.8.0), Ubuntu 8.10.

Could someone confirm a fix in Inkscape or Cairo?

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
theAdib (theadib) wrote :

higher severity because of duplicates and the fact that this issue destroys information (text) in the output.

Changed in inkscape:
milestone: none → 0.47
Revision history for this message
theAdib (theadib) wrote :

can reproduce in version 0.46 but it does not exists in current devel revision 21257.
I don't know who fixed this.
Adib.

Changed in inkscape:
status: Confirmed → Fix Committed
tags: added: exporting text
removed: ligature
Revision history for this message
Frédéric Grosshans (fgrosshans) wrote :

It is solved in Inkscape 0.47 in karmic. Thanks to the anonymous developper(s) who fixed this !

Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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