Re: Using/requiring Cairo

k...@aspodata.se writes: > Werner: >> >> "taking care of PostScript" is not related to converting LilyPond's >> >> graphics internals to Cairo since LilyPond's graphics internals are >> >> not written in PostScript. >> > >> > Ok, forget it then, you are not listening. [...] >> >> Why such a

pdfsizeopt can now handle lilypond PDFs

Folks, the author of pdfsizeopt https://github.com/pts/pdfsizeopt has recently applied some bug fixes to make it work with lilypond documentation files (cf. https://github.com/pts/pdfsizeopt/issues/11). Using trueroad's approach (i.e., using `extractpdfmark'), `lilypond-notation.pdf'

Mac OS X executable

Is there a 64 bit OS X version of the lilypond application? If not, is there any reason for that? Andrew ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: I'm to teach LilyPond officially again

As the maintainer of LilyBin, I'll be interested in knowing if you encounter any issues, especially with reliability of the service! Last year, I and another developer did some work to get LilyBin running on AWS Lambda especially to handle the load of classroom situations where many people use are

Re: Using/requiring Cairo

Werner: > >> "taking care of PostScript" is not related to converting LilyPond's > >> graphics internals to Cairo since LilyPond's graphics internals are > >> not written in PostScript. > > > > Ok, forget it then, you are not listening. [...] > > Why such a hostile tone, Karl? There is no

Re: Using/requiring Cairo

>> "taking care of PostScript" is not related to converting LilyPond's >> graphics internals to Cairo since LilyPond's graphics internals are >> not written in PostScript. > > Ok, forget it then, you are not listening. [...] Why such a hostile tone, Karl? There is no reason for this. I have

Re: Using/requiring Cairo

David Kastrup: > k...@aspodata.se writes: > > David Kastrup: ... > "taking care of PostScript" is not related to converting LilyPond's > graphics internals to Cairo since LilyPond's graphics internals are not > written in PostScript. Ok, forget it then, you are not listening. ... > When

Re: Using/requiring Cairo

k...@aspodata.se writes: > David Kastrup: >> k...@aspodata.se writes: >> >> > Han-Wen Nienhuys: >> >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: > ... >> > If no one else like to care for postscript, I can step in to handle it. >> >> I don't know what that means. > >

Re: Using/requiring Cairo

David Kastrup: > k...@aspodata.se writes: > > > Han-Wen Nienhuys: > >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: ... > > If no one else like to care for postscript, I can step in to handle it. > > I don't know what that means. It's like english, I am willing to take

Re: Using/requiring Cairo

k...@aspodata.se writes: > Han-Wen Nienhuys: >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: >> > What does that mean? Mainly a viable migration strategy where we might >> > be able to drop catering for a whole lot of graphics programming >> > ourselves by introducing a

Re: Using/requiring Cairo

Han-Wen Nienhuys: > On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: > > What does that mean? Mainly a viable migration strategy where we might > > be able to drop catering for a whole lot of graphics programming > > ourselves by introducing a dependency on Cairo. I am not

Re: Using/requiring Cairo

David Kastrup: ... > The main question mark would concern font handling > but I think it integrates with FreeType as well as Pango. ... cairo has support for freetype https://cairographics.org/manual/cairo-FreeType-Fonts.html pango has support for cairo:

Re: Using/requiring Cairo

Han-Wen Nienhuys writes: > On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: >> What does that mean? Mainly a viable migration strategy where we might >> be able to drop catering for a whole lot of graphics programming >> ourselves by introducing a

Re: Using/requiring Cairo

On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: > What does that mean? Mainly a viable migration strategy where we might > be able to drop catering for a whole lot of graphics programming > ourselves by introducing a dependency on Cairo. I am not overly what "catering for

Re: Using/requiring Cairo

Werner LEMBERG writes: >> The first step would likely just involve moving to Cairo data >> structures while keeping most of the current code except where the >> code would duplicate Cairo API calls in a reasonably straightforward >> way. > > Sounds very sensible. Looking around

Re: Using/requiring Cairo

> The first step would likely just involve moving to Cairo data > structures while keeping most of the current code except where the > code would duplicate Cairo API calls in a reasonably straightforward > way. Sounds very sensible. Looking around for other PDF generation libraries, we don't

Using/requiring Cairo

Hi folks, last time I looked at Cairo, its PDF generation was not really suitable for use in LilyPond. I have now updated my Cairo repository and saw that there are commits for its PDF backend supporting hyperlinks, document outlines, document metadata as of last October. What does that mean?