lilypond-user
[Top][All Lists]
Advanced

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

Re: Unicode code points


From: Freeman Gilmore
Subject: Re: Unicode code points
Date: Thu, 27 Feb 2020 04:12:48 -0500



On Thu, Feb 27, 2020 at 2:09 AM Torsten Hämmerle <address@hidden> wrote:
Freeman Gilmore wrote
> That is interesting, it is in the Private Use Area of Unicode, same area
> as
> Bravura.

Yup. In Emmentaler, there is one big exception I forgot to mention (but this
has nothing to do with accidentals):

The dynamic characters (f, m, p, etc.) are part of Emmentaler's text
encoding and can be found in their "proper" places (just as ordinary text)
so that you can use them directly by typing something like
  \markup { \dynamic sms }
Yes i found that in the Notation Manual 3.3.3 in my search. 

The other glyphs are considered non-standard and therefore, all of them have
been stowed away into the Private Use Area, just one after the other. Mostly
encoding vector after encoding vector, sorted in alphabetical order (by
glyph name) or, more precisely, just as they are generated in
metafont/metapost:
  rests, accidentals, dots, arrowheads, scripts, trills, clefs, etc., etc.

Every time a new glyph joins the party, they all get shifted around from
release to release.
The accidentals in 2.20 will have moved compared to 2.18.2, because new rest
symbols (256th, 512th, 1024th rests!) have been shoved in in front of the
accidentals.  This way, the sharp glyph will have moved from U+E110 to
U+E113.  And that's just one out of many examples.
SMuFL uses a name ans code point that does not Chang.    It leave plenty of room along the way for adding similar glyph. 
Thank you, ƒg


Cheers,
Torsten














--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html


reply via email to

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