Re: Missing items to make Cairo ready

[Jonas Hahnfeld]

On Wed, 2023-01-04 at 14:00 +0100, Jean Abou Samra wrote:
> Le 29/12/2022 à 01:53, Jean Abou Samra a écrit :
> > Hi,
> > 
> > I have just opened issues for the missing features of
> > the Cairo backend that I am aware of.
> > 
> > https://gitlab.com/lilypond/lilypond/-/issues/6500
> > https://gitlab.com/lilypond/lilypond/-/issues/6501
> > https://gitlab.com/lilypond/lilypond/-/issues/6502
> > https://gitlab.com/lilypond/lilypond/-/issues/6503
> > https://gitlab.com/lilypond/lilypond/-/issues/6504
> > 
> > Are there any others?
> 
> The topic of this thread has deviated somewhat from the original
> question, and I don't really mind, but I would still like to tackle
> the original question.
> 
> Here are a few things that can't be supported in Cairo:
> 
> - -dfont-export-dir=...
> - -dfont-ps-resdir=...
> - -dgs-api (but makes no sense in Cairo)
> - -dgs-load-fonts
> - -dgs-load-lily-fonts
> - -dgs-never-embed-fonts
> - -dno-include-eps-fonts
> 
> AFAICS, these only make sense if you're using GS to convert
> the PS output to PDF yourself manually, so they're obviated
> in Cairo, but I would like to check that this is the case.

Right: as far as I understand, these are also crucial for our own
documentation build to end up with reasonably sized PDFs. Did you check
what the situation is if we used snippets compiled with Cairo?

Jonas

signature.asc
Description: This is a digitally signed message part