Re: [Lilypond-auto] Issue 2656 in lilypond: some LilyPond builds don't produce font ligatures

[lilypond]

Comment #39 on issue 2656 by address@hidden: some LilyPond builds  
don't produce font ligatures
http://code.google.com/p/lilypond/issues/detail?id=2656

Folks, it could well be a known limitation of Pango.

See http://www.linuxlibertine.org/index.php?id=87&L=1

Relevant excerpt:
The Scribus-Developers work at a wider support. The OpenOffice-Website  
mentions first steps to support OTFs. The Gimp already knows automatic  
ligature-substitution, but more complex support of OpenType lacks because  
of too simple implementations in the Pango-library.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings