lilypond-user
[Top][All Lists]
Advanced

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

Re: Emmentaler unicode value


From: Pierre Perol-Schneider
Subject: Re: Emmentaler unicode value
Date: Fri, 8 Nov 2019 21:33:07 +0100

Hi Aaron,
You're absolutely right, I've uploaded the wrong file, sorry for the noise.
Cheers,
Pierre

Le ven. 8 nov. 2019 à 21:10, Aaron Hill <address@hidden> a écrit :
On 2019-11-08 10:00 am, Pierre Perol-Schneider wrote:
> Hi,
> In the Emmentaler font, the "G.clef" Unicode value is: U+e17b.
> However, after Unicode hexadecimal values being entered, it shows
> another
> glyph:
>
> \version "2.19.83"
>
> \markuplist {
>   \line {
>     \italic "Unicode" \typewriter "U+e17b" \italic "shows" \typewriter
> "clefs.tenorG_change:"
>     \override #'(font-name . "emmentaler-20") \char ##xe17b
>   }
>   \line {
>     \italic "Unicode" \typewriter "U+e176" \italic "shows" \typewriter
> "clefs.G:"
>     \override #'(font-name . "emmentaler-20") \char ##xe176
>   }
> }
>
> Any reason why?

Your initial assertion regarding the codepoint would appear to no longer
be correct based on the version of the font I have:

%%%%
\version "2.19.83"

#(format #t "~:{\n~a = ##x~x~}"
   (let ((font (ly:system-font-load "emmentaler-20")))
     (map (lambda (x)
            (list x (ly:font-glyph-name-to-charcode font x)))
          '("clefs.G" "clefs.tenorG_change"))))
%%%%

====
GNU LilyPond 2.19.83
Processing `glyphname.ly'
Parsing...
clefs.G = ##xe176
clefs.tenorG_change = ##xe17b
Success: compilation successfully completed
====

Consider using \musicglyph to look up a glyph by name instead of futzing
with codepoints.


-- Aaron Hill


reply via email to

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