Menu
▾
▴
#1388 Support OpenType font features
Originally created by: *anonymous
Originally created by: lemzw...@googlemail.com
Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature (`smcp' in this particular case) so that input character codes get properly mapped to caps glyphs.
I suggest that we implement an interface similar to the `fontspec' package for XeTeX and luatex:
http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf
Originally posted by: pkx1...@gmail.com
(No comment was entered for this change.)
Labels: -Priority-High
Originally posted by: aleksandr.andreev@gmail.com
I'm offering $100 US for the design of an interface that allows stylistic sets to be turned on.
Labels: Bounty
Originally posted by: lemzw...@googlemail.com
The current address of the fontspec document is
http://mirrors.ctan.org/macros/latex/contrib/fontspec/fontspec.pdf
Initial work to support opentype font features
Following up on an old patch I send to the list. One comment was to use a list
for combining multiple font features. This is now implemented. A possible issue
is the pango API needed is somewhat newer. I'll investigate where I need to set
that in an update (pointers and hints welcome).
http://codereview.appspot.com/323850043
Diff:
Passes make, make check and a full make doc.
Patch on countdown for May 23rd
Patch counted down - please push.
Patch counted down - please push.
Patch counted down - please push although you may need to rebase with current master.
Jay, do you need someone else to push this for you (I can not recall who does and who does not have commit access) or is this waiting on something else?
Patch counted down - please push.
Update minimum pango version
http://codereview.appspot.com/323850043
I'd need someone else to push. It'd be useful for is someone to assess the version of pango.
Sorry, I hadn't revisited this earlier (thanks for keeping on top of these things). I updated the code review for the minimum version of pango. At this point I'd expect most linux distributions to include a version of the library with this function, but the hard requirement could potentially cause issues when configuring with distributions not containing this version. 1.38 is the version when pango_attr_font_features_new was added: https://developer.gnome.org/pango/stable/pango-Text-Attributes.html#pango-attr-font-features-new.
Passes make, make check and a full make doc.
As to the Pango version requirements, I am going to have to defer to teh rest of the dev team. My own Ubuntu 16:04 LTS system (I haven't checked my Home Fedora install) is using Pango 1.38.1 so I didn't have to do anything special.
But we would have to update the Contributor's guide
e.g. http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#requirements-for-running-lilypond
If I understand correctly,
Current GUB has Pango 1.40.1.
https://github.com/gperciva/gub/blob/fb232e24ade8a5cdec8bbb46b086bf8e506021a8/gub/specs/pango.py
There will be no problem.
LilyDev 4.1 or Debian jessie has Pango 1.36.8.
https://packages.debian.org/jessie/libpango-1.0-0
We cannot use LilyDev 4.1 after this patch is merged.
LilyDev 5.2 or Debian stretch has Pango 1.40.5.
https://packages.debian.org/stretch/libpango-1.0-0
So we can use LilyDev 5.2 after this patch is merged.
But, it is for Guile 2 migration instead of for ordinary developers.
So developers would need to have LilyDev 4.2 (with some version of Pango 1.40?) before we could push this patch?
Yes, I think so.
Alternatively there is a way to install Guile 1.8 to LilyDev 5.2.
Another solution is to use Ubuntu 16.04 which has Pango 1.38.1 and Guile 1.8.
So as far as I can tell there is nothing wrong with this going on countdown for June 11th (we will have to update LilyDev, but I don't see that as a blocking 'thing' for this patch).
Patch on countdown for June 11th