[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2656 in lilypond: some LilyPond builds don't p
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2656 in lilypond: some LilyPond builds don't produce font ligatures |
Date: |
Sat, 22 Nov 2014 23:03:18 +0000 |
Comment #40 on issue 2656 by address@hidden: some LilyPond builds
don't produce font ligatures
https://code.google.com/p/lilypond/issues/detail?id=2656
I managed (out of desperation) to get ligatures to appear. It was on
accident. I built LilyPond 2.18.2 (standard) on OSX Yosemite (10.10.1)
64-bit using MacPorts, changed the font.scm as advised on
fonts.openlilylib.org, and then installed some optional fonts (Junicode,
Linux Libertine, et al). I got this.
I don't think it is a limitation of Pango (unless something changes Pango
in building it).
HTH.
Attachments:
ligaturetest.png 1.9 KB
--
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Lilypond-auto] Issue 2656 in lilypond: some LilyPond builds don't produce font ligatures,
lilypond <=