[+Cc: linux-media, -Cc: lkml]
Hi Mauro,
In case you are wondering what is going on in the update of
selection.svg, here is a status report.
On Mon, 13 Dec 2021 16:53:07 +0900, Akira Yokosawa wrote:
> On Mon, 13 Dec 2021 07:33:27 +0100, Mauro Carvalho Chehab wrote:
[...]
>> No matter if this is merged or not, if you find an issue at the images
>> at the media docs, please send them to linux-media@xxxxxxxx.
>
> OK. I'll compose a proper change log for it and post it later this
> week or next.
> (I'm not a type of person who is good at doing several things in
> parallel.)
I started the patch preparation, but I found the patch would be
quite large in size (~500kB).
This is because current selection.svg consists of pretty high-
resolution raster images.
I see you had done several attempts to reduce the complexity of
the SVG, but it is still large (> 200kB) and conversion to PDF by
convert(1) generates a PDF of more than 1MB!
Even inkscape(1) generates a larger PDF (>1.3MB) with embedded
raster images.
I don't believe what the figure wants to explain deserves such
a large size.
So, from my POV, adding another bitmap image to the SVG for the
sake of browser compatibility is *not* the right thing to do.
Instead, my suggestion would be to get rid of the embedded raster
images and to draw some simple vector-graphics-based figure
instead.
Am I missing something here?
Thanks, Akira
>
> And the most easy fix is to install Inkscape on your system for
> the daily build.
> Then, convert(1) picks inkscape(1) for SVG rendering and you will
> see right ones (of raster images, though).
>
> You know, ImageMagick prefers inkscape over rsvg-convert.
> I think it is the right thing to do in kfigure.py as well.
>
[...]
