Re: OpenType Features

2016-01-31 Thread Werner LEMBERG
> Reading the docs for [...] Note that a new fontspec release (version 2.5) is available since today on CTAN; it may take one or two days until it appears at all CTAN mirrors. Werner ___ lilypond-devel mailing list

Re: OpenType Features

2016-01-31 Thread Simon Albrecht
On 31.01.2016 16:45, Simon Albrecht wrote: we might even use an alist to allow for things like \override font-features.ligatures = #'(clig dlig hlig) or \override font-features.number-case = #'onum This is also inspired by the list in

Re: OpenType Features

2016-01-31 Thread Simon Albrecht
On 31.01.2016 16:39, Jay Anderson wrote: On Sun, Jan 31, 2016 at 6:52 AM, Simon Albrecht wrote: 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 exampl

Re: OpenType Features

2016-01-31 Thread Jay Anderson
On Sun, Jan 31, 2016 at 6:52 AM, Simon Albrecht wrote: > 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-featu

Re: OpenType Features

2016-01-31 Thread Simon Albrecht
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

Re: OpenType Features

2016-01-30 Thread Jay Anderson
tally sure what to believe.). OpenType features were added >> in pango 1.18 (assuming I'm reading this correctly: >> https://developer.gnome.org/pango/unstable/api-index-1-18.html). Are >> there known issues with making this the new minimum version? > > I was a little wrong her

Re: OpenType Features

2016-01-18 Thread Simon Albrecht
On 18.01.2016 18:40, James wrote: I'll make a patch Good! TIA, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: OpenType Features

2016-01-18 Thread James
Hello On 18/01/16 17:18, Simon Albrecht wrote: > On 18.01.2016 17:59, Jay Anderson wrote: >> This is the lilypond issue: >> https://code.google.com/p/lilypond/issues/detail?id=1388 (What's the >> new issue location? > > > >> I couldn't find it in

Re: OpenType Features

2016-01-18 Thread Jay Anderson
On Mon, Jan 18, 2016 at 9:59 AM, Jay Anderson wrote: > First issue: It appears that lilypond is dependent on pango 1.6 > (pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so > I'm not totally sure what to believe.). OpenType features were added > in pango 1.18 (ass

Re: OpenType Features

2016-01-18 Thread Simon Albrecht
s to google code (http://www.lilypond.org/bug-reports.html). Yes, that’s embarrassing – we’re somewhat stuck in the transition, so this is semi-permanent. It would be great to have OpenType features supported! Many thanks if you can tackle this – and I’m sorry to be of no help ther

Re: OpenType Features

2016-01-18 Thread James
Hello Jay, On 18/01/16 16:59, Jay Anderson wrote: > I'm interested in seeing what it would take to add OpenType features > -- specifically old style number figures (onum) and small caps (smcp). > > First issue: It appears that lilypond is dependent on pango 1.6 > (pango

OpenType Features

2016-01-18 Thread Jay Anderson
I'm interested in seeing what it would take to add OpenType features -- specifically old style number figures (onum) and small caps (smcp). First issue: It appears that lilypond is dependent on pango 1.6 (pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so I'm not totally