Exporting simple diagram to PDF results in mangled stroke line

Bug #1580042 reported by Nutchanon Wetchasit
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

I have used Inkscape to draw a simple electronic schematic diagram,
consisting of lines, closed paths, rectangles, circles, arc, and text.
When I tried to save the diagram as PDF format (with File > Save a Copy),
the output PDF file looked OK for the most part, but it have some lines
placed at where it shouldn't be, making the diagram look confusing.

The original SVG drawing is attached as `schematic.svg`.
The exported PDF file is attached as `schematic.pdf`.
 ^ You'd see that there is a vertical line connecting "D1" and "D2"
   while the original SVG drawing didn't have it.
A correct reference rendering is attached as `schematic.150dpi.png`.

Inkscape: 0.91 portable 32-bit
System: Microsoft Windows XP Professional SP3

Notes:
The SVG drawing is originally made with Inkscape 0.48.2 (Windows 32-bit),
and doesn't use any SVG filters (although it does use SVG transformations).

Following configuration is used in PDF exporting dialog:
- Restrict to PDF version: PDF 1.4
- Convert text to paths: No
- PDF+LaTeX: Omit text in PDF, and create LaTeX file: No
- Rasterize filter effects: Yes
- Resolution for rasterization (dpi): 90
- Output page size: Use document's page size
- Bleed/margin (mm): 0.0
- Limit export to the object with ID:

Tags: exporting pdf
Revision history for this message
Nutchanon Wetchasit (nutchanon-wetchasit) wrote :
Revision history for this message
Nutchanon Wetchasit (nutchanon-wetchasit) wrote :
Revision history for this message
Nutchanon Wetchasit (nutchanon-wetchasit) wrote :
Revision history for this message
su_v (suv-lp) wrote :

Known issue (upstream bug) with old cairo version bundled with Inkscape 0.91 32bit for Windows (cairo 1.11.2), already tracked for Inkscape in
* Bug #759154 “Open paths with aligned endpoints are closed in cairo-based exports (PDF/PS/EPS)”
  https://bugs.launchpad.net/inkscape/+bug/759154

Proposing to link as duplicate to bug #759154.

Revision history for this message
Nutchanon Wetchasit (nutchanon-wetchasit) wrote :

This PDF export issue is reproducible on:
- Inkscape 0.48.2 (Microsoft Windows XP Professional SP3)
   - libcairomm-1.0-1.dll (unidentified version)
   - libcairo-2.dll 1.10.2 (identified from PDF output)
- Inkscape 0.48.5 (portable, Microsoft Windows XP Professional SP3)
   - libcairomm-1.0-1.dll (unidentified version)
   - libcairo-2.dll 1.11.2 (identified from PDF output)
- Inkscape 0.91 (portable, Microsoft Windows XP Professional SP3)
   - libcairomm-1.0-1.dll (unidentified version)
   - libcairo-2.dll 1.11.2 (identified from PDF output)

And not reproducable on:
- Inkscape 0.46-2.lenny2 (Debian GNU/Linux 5.0 Lenny i386)
   - libcairomm-1.0-1 1.6.0-1 (Debian)
   - libcairo2 1.6.4-7 (Debian)
- Inkscape 0.48.3.1-1.3 (Debian GNU/Linux 7.0 Wheezy i386)
   - libcairomm-1.0-1 1.10.0-1 (Debian)
   - libcairo2 1.12.2-3 (Debian)

Revision history for this message
Nutchanon Wetchasit (nutchanon-wetchasit) wrote :
Revision history for this message
su_v (suv-lp) wrote :

As discussed in the comments of bug #759154, the known affected cairo releases are >= 1.10.0 and <= 1.12.0, which is again confirmed by the results listed in comment 5.

Linking as duplicate to bug #759154.

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

Other bug subscribers

Remote bug watches

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