Description: ------------ In SVG.php, there is a line in the addText function: htmlspecialchars($text) . Unfortunately, this prevents the use of svg elements such as <tspan>. Removing the htmlspecialchars fixes the problem, but I do see why you added it, so there might be a better way to fix the problem. Expected result: ---------------- SVG elements such as <tspan> should be applied to the text Actual result: -------------- the elements themselves are actually printed along with the text

In general, when it's an XML document and the method is named 'addText' or similar, it implies a TextNode to me. Perhaps you could make use of _addElement() if it were public.

But when using _addElement() (if it were public) he'd need to apply positioning, rotation etc. himself as well, since that's used around the text (see call to _addElement() in addText()). So how about we introduce some kind of param for "pre-encoded text" that points out it's already HTML/SVG-encoded and doesn't try to convert with htmlspecialchars again? Question remains however if somebody might want to some different kind of text/object or other attributes for the text? In that case we'd maybe need some general "addSVGObject()" that adds an object but takes care of tranformation (rotation, moving, ...) for the user? About your original inquiry: Since addText() is the same for all output-drivers, it's expected functionality that it usually encodes all special characters - so that part "works as designed". Marking this as feature-request.