Inkscape

stroke on text rendered as non-closed path

Bug #445790 reported by Thomas Holder on 2009-10-07

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Inkscape	Fix Released	Undecided	Johan Engelen

Bug Description

stroke around text is rendered as a non-closed path.

In Inkscape 0.46 the path is closed, so this is a regression bug. I'll attach a screenshot with comparision of 0.46 and current svn build.

Tags:

Revision history for this message

Thomas Holder (speleo3) wrote on 2009-10-07:

screenshot.png Edit (116.2 KiB, image/png)

Revision history for this message

su_v (suv-lp) wrote on 2009-10-08:

reproduced with Inkscape 0.46+devel r22413 on OS X 10.5.8

related bugs (only cairo export):
Bug #168129 “stroke not closed on letters in cairo export”
Bug #178825 “TEXT stroke bug”

Changed in inkscape:
status:	New → Confirmed
tags:	added: regression text

Revision history for this message

Johan Engelen (johanengelen) wrote on 2009-10-25:

if the text is converted to a path ('object to path'), then the resulting path *is* closed...

Revision history for this message

Johan Engelen (johanengelen) wrote on 2009-10-26:

patch445790-partlyrevert20436.patch Edit (1.0 KiB, text/plain)

Svn rev 20436 introduced the bug. By fixing some other bug, I bugged text rendering. :-(
The attached patch reverts this change.

Revision history for this message

Johan Engelen (johanengelen) wrote on 2009-10-26:

I guess we have to wait for a proper fix (that renders paths-data-10-t.svg correctly)

Revision history for this message

Johan Engelen (johanengelen) wrote on 2009-10-26:

I guess we have to wait for a proper fix (that renders paths-data-10-t.svg correctly) until we switch to cairo/2geom paths for rendering (not just for outline viewmode like we do now).

Revision history for this message

su_v (suv-lp) wrote on 2009-10-27: Re: [Bug 445790] Re: stroke on text rendered as non-closed path

445790-stroked-text-2.svg Edit (29.2 KiB, image/svg+xml; name="445790-stroked-text-2.svg")
445790-stroked-text-2.png Edit (108.5 KiB, image/png; name="445790-stroked-text-2.png")
445790-stroked-text-2-patched.png Edit (84.8 KiB, image/png; name="445790-stroked-text-2-patched.png")

Patch tested and fix confirmed for stroked text and stroked
'text-to-path' objects with Inkscape 0.46+devel r22544+patch on OS X 10.5.8

Changed in inkscape:
status:	Confirmed → In Progress

Johan Engelen (johanengelen) on 2009-11-03

Changed in inkscape:
assignee:	nobody → Johan Engelen (johanengelen)

Revision history for this message

ScislaC (scislac) wrote on 2009-11-08:

Committed in 22565, Thanks Johan!

Changed in inkscape:
status:	In Progress → Fix Released

Revision history for this message

su_v (suv-lp) wrote on 2009-11-09:

445790-168129-A-test.svg Edit (3.6 KiB, image/svg+xml)

I noticed a small regression when exporting stroked text that has been converted to path using the menu command 'Path > Object to Path'. See attached SVG file and the PDF export with Inkscape r22566.

(test case is from originally from related bug #168129)

Revision history for this message

su_v (suv-lp) wrote on 2009-11-09:

#10

445790-168129-A-test.pdf Edit (7.3 KiB, application/pdf)

Revision history for this message

su_v (suv-lp) wrote on 2009-11-09:

#11

445790-168129-A-test-inkscape.png Edit (32.1 KiB, image/png)

note: the SVG file renders perfect in Inkscape, but for example Firefox 3.5.5 also shows not-closed strokes for the 'A' on the right side...

Revision history for this message

su_v (suv-lp) wrote on 2009-11-09:

#12

445790-168129-A-test-t2p.pdf Edit (7.0 KiB, application/pdf)

note 2: the PDF export option 'Convert texts to paths' does keep all stroked text paths closed - i.e. now with the fix for bug #388257 the rendering glitch of texts converted before exporting is less of a problem.

Attaching PDF exported with the option 'texts to paths': the 'A' on the left side looks exactly like on-canvas in Inkscape even though it has been converted to a path.

Revision history for this message

su_v (suv-lp) wrote on 2009-11-09:

#13

*blush* - it's not a regression, my apologies to Johan for implying that!

The issue with stroked converted text objects in cairo exports just wasn't visible as separate issue before. Now that both stroked text-object and stroked-text-object-to-path are rendered identically on-canvas the difference in cairo exports (PDF, Cairo PNG) - where the stroked-text-object-to-path is rendered as on-canvas in unpatched Inkscape - is more obvious and unexpected.