Re: RFC: require librsvg to implement SVG image support

[Han-Wen Nienhuys]

On Tue, Jan 10, 2023 at 11:32 PM Jean Abou Samra <jean@abou-samra.fr> wrote:
>
> Le 10/01/2023 à 23:25, Han-Wen Nienhuys a écrit :
> > On Mon, Jan 9, 2023 at 7:45 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
> >> 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.
> > PDF has much more features than SVG, so it's not obvious that that
> > will be easier, and if we want to ingest the PDF graphic for output to
> > SVG/PNG/PS, we'll have to interpret the PDF data, basically doing what
> > Poppler does.
>
>
> I don't understand how this is different from SVG.

I was initially thinking there might be a way to avoid a full-blown
parser/interpreter for PDF. But that would not work in all formats, so
it's probably not acceptable. So you're right.

For others following the conversation, the poll is at
https://lists.gnu.org/archive/html/lilypond-user/2023-01/msg00189.html

It's currently 3-0 skewed towards SVG.

Regarding rsvg and rust: maybe we could try with an older version of
librsvg first? Rust was only introduced in 2.41, so if we go with
2.40, we can postpone the worry about compiling Rust.

-- 
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen