Stroke-Width incorrectly applied if between 0 and 1 or if using percentage

[RMY1]

Hi guys.

It seems stroke-width is ignored when it has value between 0 and 1.
Stroke-width value, in that case, is taken by default and is equal to 1.

Does anyone else experience that behavour ?
Thanks.

[heindlalex]

I was not able to reproduce this.
My test image shows with stroke-width="0.5" half the width (second circle) as with stroke-width="1" (default) - first circle.
Although a stroke-width with percentage seems to be calculated wrong (3rd circle):

Testfiles:
__issue-338-01_stroke_width.zip

Output png IE:

[mrbean-bremen]

Thanks, @heindlalex - I updated the title accordingly.

[mrbean-bremen]

Just noticed that the original issue is still there for paths. This can be seen in the test image __issue-323-01.svg after the crash is fixed (will do that in a moment).

[mrbean-bremen]

Looks like the problem occurs if the physical line width is between 0 and 1 due to missing anti-aliasing.
I found a reference to a respective bug in GDI+ - so the only viable option seems to be to adapt the color (make it more transparent?). I tried this, and the result looks better, though not perfect, but I'm unsure if this is the way to go... Any ideas are welcome.

[mrbean-bremen]

@H1Gdev - this is to be expected - anti-aliasing "smears" the lines a bit by design. The problem here is with lines with a width less than 1 pixel. This can be seen in the mentioned example image (Bolivian flag). This is the expected image:

And this is rendered by the SVG lib:

Note the black lines, which all have a width of less than a pixel. Anti-aliasing doesn't help here.

[Seb-Eck]

This issue still persists on Ubuntu with libgdiplus. I use SVG.Net to render SVGs to PNG files. The images below display a path with stroke-width="0.2" as seen in Chrome, rasterized on Windows and rasterized on Ubuntu:

Chrome:

Windows:

Ubuntu: