Re: is this a slashed grace?
That's all I want to know, thanks! On Wed, Aug 24, 2022 at 8:36 PM Andrew Bernard wrote: > Yes. > > What is the problem? > > On 25/08/2022 12:35 pm, Kenneth Wolcott wrote: > > Is this a slashed grace? See attached screenshot. > > > >
Re: is this a slashed grace?
Yes. What is the problem? On 25/08/2022 12:35 pm, Kenneth Wolcott wrote: Is this a slashed grace? See attached screenshot.
is this a slashed grace?
Is this a slashed grace? See attached screenshot.
Re: LilyPond 2.23.12
Le 25/08/2022 à 00:00, CieMaKat a écrit : Out of couriosity - does the introduction of Cairo bring us any closer to rendering LilyPond directly in web browser (i.e. with WebAssembly)? Have anyone considered that? I don't think so — how would it bring us closer? As far as my understanding goes (but my knowledge of Web programming is extremely limited), to run LilyPond in a browser from the client side (i.e. the LilyPond compilation happens in the user's computer, not on the server), what you would need is to compile LilyPond (with all of its dependencies) to WASM with the Emscripten compiler. Cairo would just spare you building GhostScript for WASM in exchange for building Cairo and LibPNG for WASM. Jean
Re: LilyPond 2.23.12
Out of couriosity - does the introduction of Cairo bring us any closer to rendering LilyPond directly in web browser (i.e. with WebAssembly)? Have anyone considered that? W dniu środa, 24 sierpnia 2022 Jean Abou Samra napisał(a): > Le 24/08/2022 à 09:49, Andrew Bernard a écrit : > >> Is Cairo related to producing PDF or only SVG? >> > > > Both, but its advantages are the most shiny on SVG output, where it > produces output enormously faster, and embeds fonts in the SVG file which > ensures they can be viewed on any browser without getting fallback fonts. > > PDF output is also faster, but the difference is not very noticeable for > normal use (although it is noticeable when compiling lots and lots and lots > of snippets, like when compiling the LilyPond documentation), whereas SVG > output in the current default SVG backend is really slow, and gets just as > fast as PDF output with Cairo. > > The PDF Cairo backend currently doesn't support all features of the > traditional PS backend (-dembed-source-code for example). > > Jean > > >
Re: LilyPond 2.23.12
Le 24/08/2022 à 09:49, Andrew Bernard a écrit : Is Cairo related to producing PDF or only SVG? Both, but its advantages are the most shiny on SVG output, where it produces output enormously faster, and embeds fonts in the SVG file which ensures they can be viewed on any browser without getting fallback fonts. PDF output is also faster, but the difference is not very noticeable for normal use (although it is noticeable when compiling lots and lots and lots of snippets, like when compiling the LilyPond documentation), whereas SVG output in the current default SVG backend is really slow, and gets just as fast as PDF output with Cairo. The PDF Cairo backend currently doesn't support all features of the traditional PS backend (-dembed-source-code for example). Jean
Re: LilyPond 2.23.12
Is Cairo related to producing PDF or only SVG? Andrew On 24/08/2022 3:35 pm, Jonas Hahnfeld via LilyPond user discussion wrote: Starting with this version, the official binaries support the experimental Cairo backend.
Re: LilyPond 2.23.12
Thanks a lot to all the Lily developers for their continuous work! JM > Le 24 août 2022 à 07:35, Jonas Hahnfeld via LilyPond user discussion > a écrit : > > We are happy to announce the release of LilyPond 2.23.12. This is > termed a development release, but these are usually reliable. However, > if you require stability, we recommend using version 2.22.2, the > current stable release. Please refer to the Installing section in the > Learning Manual for instructions how to set up the provided binaries: > https://lilypond.org/doc/v2.23/Documentation/learning/installing > > Starting with this version, the official binaries support the > experimental Cairo backend. Please give it a try with the command line > option -dbackend=cairo and see if it works for you. In case of > problems, please report back to us so it can be worked on.
