lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Supp


From: Xavier Scheuer
Subject: Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
Date: Mon, 26 Jun 2017 09:32:49 +0200

Hello,

Sorry, I come after the push.

A. In order to give this nice and long-wanted (also by users other
than me) feature some visibility, could it be documented in the
Notation Reference as well (NR 1.8.3 Fonts)?

So the users will not only be able to use it, but also know how it
(finally) exists.  :D

B. Furthermore, as an advanced improvement, it would be nice if the
\smallCaps command would behave like this :

1. if the font have real small caps, \smallCaps should use them
(font-features . ("smcp")) ,
2. else : fake it (like \smallCaps nowadays).
However I do not know if it would be possible for LilyPond to
*determine* if the font used possesses real small caps.

C. Introducing an \oldstyleNumbers command would be great (with as
advanced improvement the same idea as for B.1. and 2.).

Thank you in advance again for this nice feature Jay!

Cheers,
Xavier


On 19 June 2017 at 17:01, Auto mailings of changes to Lily Issues via
Testlilyissues-auto <address@hidden> wrote:
>
> labels: --> Fixed_2_19_63
> status: Started --> Fixed
> Patch: push -->
> Comment:
>
> I've pushed to staging.
>
> commit 8cf69a467ad7650f5ca9da6fe2dfd4c7c088b239
> Issue 1388: Initial work to support opentype font features.
>
> Thank you.
>
> ________________________________
>
> [issues:#1388] Support OpenType font features
>
> Status: Fixed
> Labels: Fixed_2_19_63
> Created: Mon Nov 08, 2010 10:34 PM UTC by Anonymous
> Last Updated: Mon Jun 19, 2017 11:13 AM UTC
> Owner: horndude77
>
> Originally created by: *anonymous
>
> Originally created by: address@hidden
>
> 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
>
> ________________________________
>
> Sent from sourceforge.net because
address@hidden 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
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
>



--
Xavier Scheuer <address@hidden>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]