I really do like the previous import tools that only create one SVG text tag without tspan
The original SVG importer did not support tspans, it just read the text from the child nodes and inserted it in the element. The old behavior might be desirable in this instance... but what about
<text><tspan stroke="green">some green text</tspan> <tspan stroke="red">some red text</tspan></text>
the old importer would result in <text>some green text some red text</text>
the good news is the fix for the other text path issue should fix this so that
<text><tspan stroke="green">some green text</tspan> <tspan stroke="red">some red text</tspan></text>
is retained