the output of: \markup \roman "fi"
is in the attachment. It does not produce the ligatures - both in standard and a testing font of mine containing ligatures (otf). In the word "leer", the letter e and r should be connected. I stumbled over this (2015): http://lilypond.1069038.n5.nabble.com/Broken-ligatures-in-recent-LilyPond-versions-td171760.html It's said, that as of 2.18.2 and newer, ligatures are broken in lilypond. Doesn't seem to be the case for everybody though... I've updatet my system, running Debian Stretch 9.9 now. Lilypond is no longer in the standard-repository in this updated version, so I've installed the generic package "2.18.2" from lilypond.org. *** www.marcobaumgartner.com On Fri, Jul 5, 2019 at 12:35 PM Marco Baumgartner <vonbaumgart...@gmail.com> wrote: > Thanks Aaron for your help! > > %%%% > \version "2.18.2" % tested on lilybin.org > \markup \roman "fi" > %%%% > > That's what I'm going to test next. Unfortunately, I'm facing some > installation issues. I somehow messed up the original package, > while trying to install a newer unstable version. Now I can't re-install > 2.18.2 from Debian repository as it's missing. Let me figure this out. I'll > let you know, > when I'm back with a running version and tested the above code. > > *** > www.marcobaumgartner.com > > > On Thu, Jul 4, 2019 at 7:33 PM Aaron Hill <lilyp...@hillvisions.com> > wrote: > >> On 2019-07-04 6:29 am, Marco Baumgartner wrote: >> > Although my font (otf) HAS ligatures (and show up if the font is used >> > on my >> > system in other programs) - it >> > doesn't show ANY ligatures in lilypond... Can't make it work as of now. >> > >> > I searched about it, and stumbled across people saying, that this was >> > like >> > an official bug. Others saying, >> > that it should be all working instead... >> >> Well, I would put my vote on the side of "should be working". Consider >> the following simple example: >> >> %%%% >> \version "2.18.2" % tested on lilybin.org >> \markup \roman "fi" >> %%%% >> >> You *should* get the "fi" as a ligature in the output. It would be good >> to verify this on your system. Then, use \override #'(font-name . "Your >> custom font") and test your font. >> >> > I'm using 2.18.2 on Debian Linux with Frescobaldi. >> > And: The ligatures I'm talking about are not standard ligatures (tied >> > to a >> > specific language), they're everything but standard. >> > But like I said, a normal Text-Editor (and even used on the web >> > via @font-face) can render the ligatures just fine. >> >> This may have more to do with Pango than LilyPond, since it is Pango >> that is the one dealing with fonts. If there is something wrong with >> how it handles OpenType ligatures, that could certainly end up affecting >> what you see in LilyPond. >> >> > Any tips on: >> > - where to install the font (not so sure about that anymore...) >> >> You can install fonts wherever your fontconfig is set up to load them. >> For instance, I have my custom fonts installed in my home directory: >> >> ~/.local/share/fonts >> >> I did this as to not conflict with any font packages that are normally >> written to /usr/local/share/fonts. >> >> > - how to encode the font in a way that lilypond recognizes ligatures >> >> Unsure, but as I indicated above, I think this is on the Pango side, not >> LilyPond. >> >> > - just pointing out, that I'm stupid (that would be at least a valid >> > excuse) :-) >> >> If I did that, I would have more fingers pointing back at myself. You >> would not have to dig too far in the mailing list archive to find proof >> of my lapses into incompetence. >> >> >> -- Aaron Hill >> >> _______________________________________________ >> lilypond-user mailing list >> lilypond-user@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-user >> >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
