>> It is a technical detail that LilyPond primarily communicates with
>> OTF fonts via glyph names: this is necessary only because LilyPond
>> natively emits PostScript code, which predates the invention of
>> OpenType and thus doesn't use character codes.
>
> it's not just a historical
Hi,
Am 28.05.20 um 06:44 schrieb Werner LEMBERG:
>> This would mean every user would need to learn the new vocabulary if
>> they want to reference glyphs in their scheme code.
> Definitely not :-) However, I can imagine that LilyPond provides an
> option to *also* allow Bravura glyph names (or
On Thu, May 28, 2020 at 6:44 AM Werner LEMBERG wrote:
> I think there is a fundamental misunderstanding. Bravura is an
> OpenType font, and the only intended communication with such fonts is
> via character code values and *not* glyph names. It is a technical
> detail that LilyPond primarily
It seems to me that if you are going to use SMuFL fonts, you're either going to
have to completely rewrite every lilypond glyph-name lookup (which should
probably be phase 3 of the project) or you're going to have to have a
lilypond-glyph-name-to-smufl-code-point lookup.
If I were doing it as
> It seems to me that if you are going to use SMuFL fonts, you're
> either going to have to completely rewrite every lilypond glyph-name
> lookup (which should probably be phase 3 of the project) or you're
> going to have to have a lilypond-glyph-name-to-smufl-code-point
> lookup.
To decide
> I do believe I've finally tracked down the place where lilypond
> glyph names are turned into character codes:
> Open_type_font::name_to_index. I can add a ternary operator here
> based on whether the Open_type_font is_smufl (a new property that,
> in the future, should be detected and set
Hi all,
I do believe I've finally tracked down the place where lilypond glyph names
are turned into character codes: Open_type_font::name_to_index. I can add a
ternary operator here based on whether the Open_type_font is_smufl (a new
property that, in the future, should be detected and set when
