Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features

[Xavier Scheuer]

On 26 June 2017 at 09:32, Xavier Scheuer  wrote:
>
> 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)?

It deserves also greatly a mention in the CHANGELOG for the next version.

Cheers,
Xavier

-- 
Xavier Scheuer 
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features

[Xavier Scheuer]

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  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: 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
>
> 
>
> 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
>



--
Xavier Scheuer 
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features

[tisimst]

On Thu, May 18, 2017 at 2:34 PM, Xavier Scheuer [via Lilypond] <
ml+s1069038n203182...@n5.nabble.com> wrote:

> On 18 May 2017 at 07:35, Auto mailings of changes to Lily Issues <
> [hidden email] >
> wrote:
> >
> > 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
>
> Wow!
>

Wow, indeed! This is great news!


> True small caps and old-style numbers coming into Lilypond, this is
> (again) one of my most-wanted features!
>
> How/where do we find the list of font-features? I guess these "terms"
> ("smcp", "onum") are related to Pango and/or OpenType. Or are these
> specific for each font?
>

They are general OpenType glyph categories (i.e., subtables), but the font
designers are the ones who determine whether a font has them or not. So,
trying to use the small-caps glyphs via "smcp" will only work if there are
real small-caps glyphs identified in that subtable. The same is true for
all other subtables.


> For example which term should we use respectively for tabular numbers,
> superior numbers, stylistic alternates, etc.?
>

Here's hoping! This would be brilliant!


> Thank you Jay, you are adding nice and useful features to lily!
>

I'll add my thanks to that. Looking forward to it, Jay!

Best,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Re-Lilypond-auto-LilyIssues-auto-testlilyissues-issues-1388-Support-OpenType-font-features-tp203182p203185.html
Sent from the Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features

[Xavier Scheuer]

On 18 May 2017 at 07:35, Auto mailings of changes to Lily Issues <
testlilyissues-a...@lists.sourceforge.net> wrote:
>
> 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

Wow!

True small caps and old-style numbers coming into Lilypond, this is
(again) one of my most-wanted features!

How/where do we find the list of font-features? I guess these "terms"
("smcp", "onum") are related to Pango and/or OpenType. Or are these
specific for each font?

For example which term should we use respectively for tabular numbers,
superior numbers, stylistic alternates, etc.?

Thank you Jay, you are adding nice and useful features to lily!

Cheers,
Xavier

-- 
Xavier Scheuer 
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel