Re: SVG output: Bad \smallCaps kerning
With the symbolic link solution, I'm "content" on the command line. As to Frescobaldi, I just tried again with the same results. > Le dimanche 27 août 2023 à 19:30 -0400, Kevin Cole a écrit : >> Mixed results... So, this is a "thanks, but..." >> >> The Frescobaldi .deb suggested by those instructions is 3.2. The Flatpak is >> 3.3. >> >> Using the Flatpak Frescobaldi, clicking the pull-down menu "Lilypond -> >> Engrave (Custom)" and explicitly selecting SVG is ignored. Frescobaldi >> produces a PDF. (Maybe there's some non-obvious way to use the pull-down >> menu?) > It works for me. > > To be sure, you're engraving each time from this "custom" menu, right? This > menu is *not* a set of options that are used every time you compile in the > "normal" way. If you want to make Frescobaldi compile all files into SVGs, > you should set that in Edit > Preferences > LilyPond Preferences > Default > Output Format. Odd. Yes, I understood that it wasn't a permanent setting... I tried it twice and both times it gave me a PDF. Maybe I missed something. (All I did was > LilyPond -> Engrave (Custom) > Output format: SVG > Engraving mode: Publish > [X] Delete intermediate output files > [X] Run Lilypond with English messages > [Run LilyPond] (I tried it with Engraving mode: Preview as well.) The output was: > Starting lilypond 2.24.2 [cruiscin_lan.ly]... > Processing > `/home/kjcole/gits/websites/pages.codeberg.org/dmc_songbook/source/cruiscin_lan.ly' > Parsing... > Interpreting music...[8] > Preprocessing graphical objects... > Interpreting music...[8][16][24][32] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `cruiscin_lan.midi'... > Calculating line breaks... > Fitting music on 1 page... > Layout output to `cruiscin_lan.pdf'... > Success: compilation successfully completed > Completed successfully in 0.8". Examining the output file, it shows that it is, indeed, a PDF.
Re: SVG output: Bad \smallCaps kerning
Adding back the list. Le dimanche 27 août 2023 à 19:30 -0400, Kevin Cole a écrit : > Mixed results... So, this is a "thanks, but..." > > The Frescobaldi .deb suggested by those instructions is 3.2. The Flatpak is > 3.3. > > Using the Flatpak Frescobaldi, clicking the pull-down menu "Lilypond -> > Engrave (Custom)" and explicitly selecting SVG is ignored. Frescobaldi > produces a PDF. (Maybe there's some non-obvious way to use the pull-down > menu?) It works for me. To be sure, you're engraving each time from this "custom" menu, right? This menu is *not* a set of options that are used every time you compile in the "normal" way. If you want to make Frescobaldi compile all files into SVGs, you should set that in Edit > Preferences > LilyPond Preferences > Default Output Format. > The instructions for installing the command-line version offers a tarball that > lives in a vacuum: Rather than integrating with /usr, /usr/local or ~/.local/ > the attitude appears to be "Screw that. I'm fiercely independent, and you'll > need to go through additional, unnecessary hoops to get me to play nicely with > all of the other children, fussing with new paths, aliases, or whatever." But why do you want to fuss with anything? Why not just run LilyPond as "~/.../bin/lilypond" ? Zero setup required. > Among the questionable choices is assuming I need yet another version of > Python (I already have 3.10) -- though LilyPond wouldn't be the first to do > that. Call it questionable or not, but it's not really a choice. These binaries do what's necessary to be able to run on about any reasonably recent Linux distro (namely only requiring a reasonably recent version of the fundamental system library, glibc). We can't assume that Python is installed, much less that the version we want is installed, and there's the "python3" vs "python" problem too. > That said, running LilyPond from the command line did produce the correct > output when asked, and it kerned properly. So, really, thanks for that. Good. > Is there a place to file feature requests like "Integrate with the operating > system?" Maybe a Bash script that moves everything to the appropriate > /usr/local/ or ~/.local/ subdirectories? That's exactly what was done in LilyPond ≤ 2.23.6. The result? I've helped people who had gotten utterly confused because they removed the ~/lilypond directory (or whichever it was) but did not remove the symlinks or wrappers (I don't remember) in ~/bin, and thought LilyPond was still installed because of these, or got them to mix up with a different installation, etc. etc. This list is the right channel for feature requests, but I suspect we would not implement this particular request. On the other hand, it's noteworthy that the (not yet released) master branch of Frescobaldi implements automatic installation of LilyPond (in a directory internal to Frescobaldi, for use inside Frescobaldi, not on the command line). IMHO, auto-management of LilyPond versions is more in scope for Frescobaldi than LilyPond itself. Jean signature.asc Description: This is a digitally signed message part
Re: SVG output: Bad \smallCaps kerning
> Le 27 août 2023 à 21:52, Kevin Cole a écrit : > > That just leads to: > > fatal error: compiled without CAIRO_BACKEND > > which means I will have to install and keep track of yet another version of > LilyPond -- this one compiled from scratch... Compiling from scratch is (of course) not needed -- just follow https://lilypond.org/doc/v2.24/Documentation/learning/installing to get the official binaries. (The error means your LilyPond distro package doesn't compile with Cairo, which was still possible for 2.24 though not really recommended.) > (I begin to understand why there needs to be 15 versions of documentation > now.) ? There is no separate version of the documentation for Cairo support.
Re: SVG output: Bad \smallCaps kerning
On Sun, Aug 27, 2023 at 12:09 PM Jean Abou Samra wrote: Try the Cairo backend, adding -dbackend=cairo on the command line or > #(ly:set-option 'backend 'cairo) in the file. It is partly because of font > issues like this that the legacy SVG backend is usually inferior to the new > Cairo backend. > That just leads to: fatal error: compiled without CAIRO_BACKEND which means I will have to install and keep track of yet another version of LilyPond -- this one compiled from scratch... (I begin to understand why there needs to be 15 versions of documentation now.)
Re: SVG output: Bad \smallCaps kerning
Try the Cairo backend, adding -dbackend=cairo on the command line or #(ly:set-option 'backend 'cairo) in the file. It is partly because of font issues like this that the legacy SVG backend is usually inferior to the new Cairo backend.
SVG output: Bad \smallCaps kerning
% SVG output looks more like "English lyrics by ROBERTB RYAN"
% with the whitespace in the wrong place, after the "B" in "Bryan"
% rather than before.
%
% PDF output produces correctly "English lyrics by ROBERT BRYAN"
%
\version "2.24.2"
\language "english"
\header {
poet = \markup { "English lyrics by " \smallCaps "Robert Bryan" }
}
