Incorrect handling of <text> without <tspan>
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Invalid
|
Low
|
Unassigned |
Bug Description
The attached file contains three text objects:
"breakable text"
is a usual piece of text, created in inkscape that
behaves fine
"broken text"
is a two-line text object that works fine as well
"unbreakable text" is a piece of text that was created
by matplotlib. It looks identical to the breakable text
but behaves very strangely on editing:
* when the cursor is at the end of the text, one cannot
insert spaces
* pressing newline within the text breaks the text in
two lines that are placed *on top of each other*
Internally, the "unbreakable text" is correct SVG, that
does not use the <tspan> tag. Inkscape never produces
such text objects itself, but when importing, it seems
to preserve the internal structure and then has
problems with it.
Changed in inkscape: | |
assignee: | nobody → Jimmy Varvaro (supershospy) |
Changed in inkscape: | |
status: | Confirmed → In Progress |
tags: | added: text |
Changed in inkscape: | |
assignee: | Jimmy Varvaro (supershospy) → nobody |
Further explanation:
Inkscape obviously expects all text object to be wrapped by
<tspan>. SVG does not require this for single-line,
single-format text elements.
In other words: Objects like
<text x="0" y="0">Hello world!</text>
can never occur in Inkscape-created documents, but they may
be imported as legal SVG and are then incorrectly handled by
Inkscape.