Re: RFC: require librsvg to implement SVG image support

[Jean Abou Samra]

Le 09/01/2023 à 19:44, Jonas Hahnfeld a écrit :
> On Sun, 2023-01-08 at 23:18 +0100, Jean Abou Samra wrote:
> > In order to keep support for vector graphics, even if not
> > with EPS, we can add support for embedding SVG images.
> Are we sure that this is actually what the users need? If everybody
> just cares about including PDF (for logos), I'm not sure if we need to
> implement support for SVG.



I'm not really sure how to get factual data about this (a straw poll
on the user list?).

In my experience, for things like logos, SVG is more common (there *are*
logos in PDF, they're just less common as far as I know, but again this is
only my experience).



> Another question would be about support in the default PS backend: Is
> this feasible for SVGs? Would we again export the rendering from Cairo
> and then paste into the output PS?



Yes, that would be the idea. I don't know another way.


> Cross-compilation is always difficult, and what I was trying to say is
> that the scripts in release/binaries/ currently don't support CMake.
> Cross-compilation with CMake is sometimes a pain because IIRC it
> doesn't really support the notion if different targets for host and
> build, so something like a tools build for execution during the build
> is not really possible. I don't know about Poppler, maybe it doesn't
> have any such problems.


I didn't try thus far because I thought SVG would be better
anyway, see above.



> Rust is actually a pretty big dependency here. How are we going to
> install this for the build? Especially on CentOS 7, I would be
> surprised if it can be installed from the distro repository. Would we
> have to go for the "official" binaries? That's a "meeh" from my side...


Why "meeh"? In my (limited) experience, it is actually most common
to install Rust via rustup, because many crates pin their compiler
version and some require a nightly compiler, so you can't do with
a single globally installed compiler, while rustup arranges so that
the version of Rust used in each project is the one specified in
Cargo.toml.

librsvg requires Rust 1.63, released last August, so whatever the
distro version unless very recent, we cannot use the Rust compiler
packaged by the distro. But unlike C++, this is considered normal
(which is IMHO a relief ...) in the Rust world.

OpenPGP_signature
Description: OpenPGP digital signature