How about the following method?

* configure script checks whether Pango's version is 1.38 or above.
* If Pango's version is 1.38+, configure makes that `config.hh` defines 
something like `HAVE_PANGO_1_38`.
* In `lily/pango-font.cc`, enclose around `pango_attr_font_features_new ()` 
with `#ifdef HAVE_PANGO_1_38` and `#endif`.
    * In the else clause it may be better to show a warning message that this 
binary cannnot use OpenType font features.

In this method, the binary that is builded by GUB can use OpenType font 
features since GUB has Pango 1.40.1.
So you can use OpenType font features in the binary distributed by lilypond.org.

LilyDev 4.1 also can compile it.
However, the binary cannot use OpenType font features.
If you compile .ly file that uses OpenType font features by the binary, you 
would see the warning message that this binary cannot use OpenType font 
features.



---

** [issues:#1388] Support OpenType font features**

**Status:** Started
**Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous
**Last Updated:** Thu Jun 08, 2017 06:54 AM UTC
**Owner:** horndude77


*Originally created by:* *anonymous

*Originally created by:* 
[lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/)

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](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf)


---

Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • Re: [... Auto mailings of changes to Lily Issues
    • Re: [... Auto mailings of changes to Lily Issues
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto

Reply via email to