tried on inkscape 1.2.2 win10

the output png file is right with all blue 321 on top of red 123

yours, BrightHuang

On 5.15 20:00, Nicolas Graner wrote:

Hello all,

I am new to Inkscape and wonder if what follows is a known bug, or an error of mine. I'm running Inkscape 0.92.4 on Linux Debian 4, so it may well have long been fixed.

Consider this file:

<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">

<svg width="100mm" height="100mm" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 100 100">

<text> <tspan x="10" y="20" fill="red">123</tspan> <tspan x="10" y="20" fill="blue">321</tspan> </text>

<text x="10" y="40" fill="red">123</text> <text x="10" y="40" fill="blue">321</text>

</svg>

When I open it in Inkscape, it correctly shows two lines with a blue 321 on top of a red 123.

When I export it to PNG, the first line appears with the red 123 on top of the blue 321, as if the tspan's had been processed in reverse order. (The second line, without tspan's, remains correct.)

Any thoughts?

Thanks, Nicolas _______________________________________________ Inkscape Users mailing list --inkscape-user@lists.inkscape.org To unsubscribe send an email toinkscape-user-leave@lists.inkscape.org

On Mon, 2023-05-15 at 14:00 +0200, Nicolas Graner wrote:

When I open it in Inkscape, it correctly shows two lines with a blue 321 on top of a red 123.

When I export it to PNG, the first line appears with the red 123 on top of the blue 321, as if the tspan's had been processed in reverse order. (The second line, without tspan's, remains correct.)

This appears to be fixed in the latest developer version.

Can you try https://inkscape.org/release/dev/ and see if it's fixed your side?

If it's not, go ahead and make an issue at https://inkscape.org/report

Best Regards, Martin Owens

Nicolas Graner said on Mon, 15 May 2023 14:00:49 +0200

Hello all,

I am new to Inkscape and wonder if what follows is a known bug, or an error of mine. I'm running Inkscape 0.92.4 on Linux Debian 4, so it may well have long been fixed.

Consider this file:

<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">

<svg width="100mm" height="100mm" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 100 100">

<text> <tspan x="10" y="20" fill="red">123</tspan> <tspan x="10" y="20" fill="blue">321</tspan> </text>

<text x="10" y="40" fill="red">123</text> <text x="10" y="40" fill="blue">321</text>

</svg>

When I open it in Inkscape, it correctly shows two lines with a blue 321 on top of a red 123.

When I export it to PNG, the first line appears with the red 123 on top of the blue 321, as if the tspan's had been processed in reverse order. (The second line, without tspan's, remains correct.)

Any thoughts?

Hi Nicolas,

I copied your file to test.svg, opened it with Inkscape 1.1.1, on an up-to-date Void Linux installation, and confirmed that the blue is printed above the red 123 on both lines of text. In Inkscape I then File=>Export_Png_Image, and clicked the Export button without changing any defaults, in order to create test.png. I viewed the test.png in pqiv, sxiv, imv, qiv -m, gpicview, and Firefox. In all these viewers, the blue 321 was above the red 123 on both lines. Note that your file has a transparent background, which is evident on several of the image viewers.

Following this sentence is the software setup for my Inkscape:

========================================================== Inkscape 1.1.1 (3bf5ae0d25, 2021-09-20)

GLib version: 2.76.1 GTK version: 3.24.37 glibmm version: 2.66.2 gtkmm version: 3.24.5 libxml2 version: 2.9.13 libxslt version: 1.1.37 Cairo version: 1.16.0 Pango version: 1.50.14 HarfBuzz version: 7.1.0 Poppler version: 22.12.0

OS version: Void Linux ==========================================================

You mentioned that your Inkscape is v 0.92.4 on Debian 4 (etch). This version is 13 years old, so every moment you use it you take security risks. You need to install a new OS (don't try to upgrade, you're too far behind). If your motivation is avoiding systemd, I can give you lots of tips how to avoid systemd with modern operating systems.

HTH,

SteveT

Steve Litt Autumn 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm