Many thanks for the clarification that this approach will not work and alternative suggestions.
I presume that /image will only include PNGs in a SVG output and not EPS (the documentation reads a little unclearly on this as the section on backends is elided with comments on coloured backgrounds)? For context I am using SVG output because my display target is a custom IOS app that uses skia as a backend. SKIA can be used to display SVGs easily within the context that I am working. SKIA does have a pdf backend but it isn’t exposed directly by the framework I’m using. The reason to use EPS is that I want to bring in vector graphics made in Inkscape using a graphics tablet. It is a little frustrating that I can’t get these vector graphics into Lilypond SVG output, as they are basically SVG in the first place, but from what I understand so far that isn’t possible. Therefore, if I understand correctly my current options would be: - render to pdf and work on a system to render pdfs within the framework I’m using (this is probably possible, but involves lots of unknowns) - rasterise the images and display as PNG, thus include the rasterised version in the SVG (not optimal in terms of file size or speed of render, but possible) - work on a system to convert SVG paths to Lilypond/Scheme paths in order to be able to draw in a vector within Lilypond to any backend. Have I missed anything? Alex > On 10 Apr 2024, at 12:33, Jean Abou Samra <j...@abou-samra.fr> wrote: > >> An alternative, if you can use raster graphics, would be a PNG file added >> with the \image command. > > > P.S. \image is new in 2.25 > https://lilypond.org/doc/v2.25/Documentation/notation/graphical-markup > (and I remember now that I wrote down what does and doesn't > support EPS in the 2.25 documentation, in the description of \image)
