[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OpenType Features
From: |
Simon Albrecht |
Subject: |
Re: OpenType Features |
Date: |
Sun, 31 Jan 2016 14:52:07 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
On 31.01.2016 07:14, Jay Anderson wrote:
An update for those interested. I got something working.
Brilliant! Looking forward to have this in LilyPond :-)
The attached
patch is certainly not ready to be merged, but I'm curious if the
chosen interface seems reasonable (see smallcaps.ly which is
attached). It adds a new 'font-features' property to the
font-interface (at least that's what I think I'm doing
http://www.lilypond.org/doc/v2.18/Documentation/internals/font_002dinterface).
It definitely looks like a good way to go, except that I wouldn’t know
how to use multiple features at the same time. Would it be possible to
input font-features as a symbol list, i.e. (random example)
{ \override TextScript.font-features = onum.smcp 4-"foo" }
ossia
\markup { \override #'(font-features . (onum smcp)) "foo" } ?
Or at least as a list of strings.
Even better would be a possibility to accumulate features, like in
%%%%%%%%%%%%%%%%
\version "2.19.36"
\useFontFeatures #'(ss01 onum)
\score {
\new Staff \with { instrumentName = \markup { \use-font-features
#'(dlig) Th09 } }
{ 1-\markup { \concat { C \use-font-features #'(subs) 1 } or C1 } }
}
%%%%%%%%%%%%%%%%
I don’t quite know how to implement that in a way which offers full
flexibility, though.
Best regards, Simon