Path doesn't handle correctly <text> tag.
Bug #595428 reported by
Andrea Gasparini
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
A4 |
Triaged
|
High
|
Unassigned |
Bug Description
Using text ids inside a4 information metadata broke the presentation.
Traceback (most recent call last):
File "/home/
self.
File "/home/
end_props = self.svg_
File "/home/
target_
TypeError: float() argument must be a string or a number
Changed in a4: | |
assignee: | Andrea Gasparini (gaspa) → A4 Developers (a4-dev) |
Changed in a4: | |
assignee: | A4 Developers (a4-dev) → nobody |
To post a comment you must log in.
Svg text elements are quite complex, and I'm asking if we really want to specifying text tags as point of an A4 presentation.
First of all, they don't have width/height attributes, so we'd want to calculate them from other properties of the text inside the tag ( in first instance you'd need to know the starting point of the text [x,y] and the size of the text [font size * lenght in chars?] )
Moreover, they can be combined with <tspan> et similia, they can be many lines of text (each of them can have modifiers of the size and whatever...).
So, I'm just guessing if we can ignore <text> and surrender all the region of interests of an A4 presentation with a rectangle, even transparent/ hidden/ whatever , at least until we have to directly handle SVG internals.