Re: OpenType in LilyPond

Am 03.03.2018 um 22:15 schrieb Malte Meyn: Am 03.03.2018 um 20:47 schrieb Noeck: Am 26.08.2017 um 13:16 schrieb Malte Meyn: In case someone is interested: here comes the adapted snippet (with usage example). Hi Malte, this is great news! Can this be also applied to the default font

Re: OpenType in LilyPond

Am 03.03.2018 um 20:47 schrieb Noeck: Am 26.08.2017 um 13:16 schrieb Malte Meyn: In case someone is interested: here comes the adapted snippet (with usage example). Hi Malte, this is great news! Can this be also applied to the default font (outside the score)? For markup in general? I

Re: OpenType in LilyPond

Joram (et al.), > On Mar 3, 2018, at 2:47 PM, Noeck wrote: > > And for anyone who is interested in real small caps, here is how this > can be used produce them and also old style numbers: > > \markup \override #'(font-features . ("onum" "smcp")) "SmallCaps 1569" HOLY

Re: OpenType in LilyPond

Am 26.08.2017 um 13:16 schrieb Malte Meyn: > In case someone is interested: here comes the adapted snippet (with > usage example). Hi Malte, this is great news! Can this be also applied to the default font (outside the score)? For markup in general? And for anyone who is interested in real

Re: OpenType in LilyPond

Am 26.08.2017 um 11:28 schrieb Malte Meyn: I just realised I can override grob the grob property font-features, not only markups. So I’ll adapt snippet 443 from the LSR for now (http://lsr.di.unimi.it/LSR/Item?id=443). In my use case I don’t have markups, headers, page numbers etc. so this

Re: OpenType in LilyPond

Am 12.08.2017 um 08:15 schrieb Jay Anderson: On Fri, Aug 11, 2017 at 7:10 AM, Malte Meyn <lilyp...@maltemeyn.de> wrote: if I understand correctly LilyPond already supports OpenType features and this will be documented in the next version (changes already have been pushed to

Re: OpenType in LilyPond

On Fri, Aug 11, 2017 at 7:10 AM, Malte Meyn <lilyp...@maltemeyn.de> wrote: > > if I understand correctly LilyPond already supports OpenType features and > this will be documented in the next version (changes already have been > pushed to master). Is this only for use in markup

Re: OpenType in LilyPond

Am 11.08.2017 um 16:10 schrieb Malte Meyn: #:roman "Vollkorn" % Can this be Vollkorn with OT feature ss13? This should be a scheme comment (; instead of %) ___ lilypond-user mailing list lilypond-user@gnu.org

OpenType in LilyPond

Hi list, if I understand correctly LilyPond already supports OpenType features and this will be documented in the next version (changes already have been pushed to master). Is this only for use in markup \overrides or can you select features document-wide? This would be nice: \paper