That’s the problem with XML code, there is 50 different ways you can do the same thing.
INK puts out this when you write text.
> font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:1.5875px;line-height:3.30729px;font-family:'Droid Sans';-inkscape-font-specification:'Droid Sans Bold';font-variant-ligatures:none;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1
1.5875 is not the actual height of the text in px, it’s a multiplier of the scale set at the start. You’re an expert and can code directly, but beginners have to use a drawing package, and they don’t care about CSS stds, they just want a drawing that works.
The whole problem is that FZ was written for Illustrator - it probably used the actual px size -, and it needs to be converted to handle INK without those little semantics. These little semantics is what kills it for beginners trying to use FZ, hence why they leave soon after. I can go into KiCAD and Eagle and not have to worry about “px”, quotes on fonts names, transforms, etc, but with FZ you need to expert to use what is essentially an easy to use beginner program. I’ve tried a few times to get INK change over the last 5 years, and no one is interested - they cite a different interpenetration if the CSS std, and that they are correct -, so FZ has to change if INK is to be used. Basically having to explain “px” day on day, is a waste of time for everybody.