Re: SVG pixelation (was pdfcairo terminal seams between bars in the colorbox)

[Dima K. <gn...@di...>]

Ethan A Merritt <me...@uw...> writes:

> I looked into it a bit further.
>
> The thing is, the two hinting properties you found are not part of the
> SVG standard (version 2).  They are instead CSS style hints to the browser.
> Chrome and Firefox apparently dive into an included SVG file and extract
> the CSS style hints from there. SVG-aware programs that are not browsers,
> like inkscape or gimp, could do the same but the motivation for doing
> so would come from imitating Chrome or Firefox rather than adhering to
> the SVG standard.  Inkscape does, but gimp doesn't. 
>
>> I'll file feature-request bug reports for those two projects.
>> But the patch should probably still go in: supporting firefox and chrome
>> is much better than supporting nothing.

> For me personally, the support from inkscape is just as important as
> from the browsers.  I use it to prepare figures for publication.
> And it's still true that you can work around this
> by using "with image pixels" for gnuplot heat maps. 
>
> What about lobbying the SVG working group to add an equivalent
> to the SVG spec?  All the various support libraries would then
> eventually fall in line.  As of SVG 2.0 you only get a choice
> between "optimizeSpeed" and "optimizeQuality", both of which
> are so vague as to be useless for our purpose.
>
>     https://svgwg.org/svg2-draft/painting.html#ImageRendering

That's interesting. Not sure what it means for us in practical terms.
The patch in this thread should cover most browsers. Most non-browser
applications I've seen use rsvg: bug report here

  https://gitlab.gnome.org/GNOME/librsvg/-/issues/985

I guess QT has its own implementation too; I ran out of steam, and
haven't pestered them. I don't know what libreoffice does, but it does
the right thing on my machine. And I don't know how to lobby the SVG
working group.

I would merge the patch in this thread, maybe file a bug report against
QSvg, and move on.