Re: Broken ligatures in recent LilyPond versions

[Jim Long]

On Fri, Feb 13, 2015 at 12:36:10AM +0100, Noeck wrote:
> Hi Jim,
> 
> concerning ligatures, you can forget about my paper block. It was just there,
> because I know this font has ligatures. This markup line should be all you 
> need:
> 
> >> \markup "Ligatures: The Que fi fl"
> 
> > What is special about that markup syntax that tells lily that
> > there are any ligatures present in the markup?
> 
> There is nothing special in the syntax. The backend should know itself, that 
> the
> font has some ligature defined which means f and i following one another are 
> not
> separate letters fi but combined into a combined symbol: ???
> And (if defined in the font) the same holds for: f + l = ??? and others.
> 
> Is it clearer now?
> 
> Here is more about it: http://en.wikipedia.org/wiki/Typographic_ligature
> 
> Cheers,
> Joram

Thanks for the reply.  So do I understand you correctly, that if
a font contains a ligature for a given sequence of characters,
then Lilypond will always typeset that character sequence using
the ligature, and it is not possible to typeset them as separate
glyphs?

That is to say, the following naive example is not possible to
implement, because if FontA defines that f followed by i will
always be ligatured, it is not possible (at least in Lilypond) to
typeset them separately?  And if there is a ligature for AE, then
likewise for the capitalized vowels?

\markup "this is FontA with a ligature: fi"
\markup "this is FontA without a ligature: fi"
\markup "capitalized vowels: AEIOU"

Thanks!

Jim