Re: (font-related) \caps \fontCaps and \smallCaps

[Xavier Scheuer]

On 6 November 2010 17:49, Werner LEMBERG <address@hidden> wrote:
>
> The whole issue is VERY problematic.  Today, many fonts already
> contain glyphs for small caps, however, lilypond isn't able to access
> them!  Reason is that lilypond currently misses an interface to
> OpenType layout tables.
> [...]

Thank you very much Werner for taking the time to explain these
issue considerations.


> Before having access to OpenType features, I consider any change in
> the font interface premature.

OK, but I have other font-related issues I wanted to report.
Maybe I could report them anyway, so people know developers are aware
of these issues (and in the same time devs could think at these issues
while implementing this access to OpenType features).
What do you think?


> Please read the documentation of the `fontspec' package (for both
> XeTeX and luatex), which provides a user-friendly LaTeX interface to
> OpenType fonts.  The documentation also shows many OpenType features
> in action, including caps related ones.
>
> http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf

That seems really interesting... and also quite "complete", not that
easy to tackle for a newbie (I mean, it would require a certain amount
of time to understand really what's going on... at least for me!).


> I suggest that we develop (after release of 2.14) a not-yet-written
> API similar to the fontspec interface.

Sounds fair.  :)
(although I'm a "never-satisfied-enough" user ;p )


> Do we have a bug tracker item about it?  If not, we certainly should
> add one.

I don't think there is something about this on the bug tracker.
I checked before posting (although I may have missed a related issue)
but I did not want to make a bug report directly, since I thought it
would have been more interesting to discuss first with the font-expert
devs — which was, IMO.

Werner, I don't want to take advantage of your kindness, but since
you are certainly the best skilled person here concerning this topic,
could you make a nice bug report to add to the tracker —with a proper
description—, so we can keep track of this?

Thanks!

Cheers,
Xavier

-- 
Xavier Scheuer <address@hidden>