[Development] Implementing small SVG 1.1 features (as opposed to SVG Tiny 1.2)

Albert Astals Cid albert.astals.cid at kdab.com
Wed Oct 13 11:43:50 CEST 2021


I understand that the current QtSVG support is clearly stated to be SVG Tiny 

We have some clients that would like to add some rendering features from the 
non Tiny variant.

For example supporting x,y attributes in tspan. This would help fixing the 
rendering of the attached SVG (compare inkscape where it's vertical text vs 
QtSVG where it's not).

Implementing support for this doesn't seem like it should be "super hard" 
(famous last words) and would help rendering some SVG files that are out there 
in the wild.

I know this would be confusing as to being able to document exactly what QtSVG 
supports, but it seems to me that if we allow bit by bit small improvements we 
could eventually end up with more of the SVG specification supported, since it 
seems unlikely that someone will have the time to work on a "mega merge 
request" which implements all of the specification.

What do you think? 

Should we allow some small features outside of the declared SVG Tiny 1.2 

Best Regards,

Albert Astals Cid | albert.astals.cid at kdab.com | Senior Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - The Qt, C++ and OpenGL Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: multiline.svg
Type: image/svg+xml
Size: 497 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20211013/8dd5a44f/attachment.svg>

More information about the Development mailing list