lilypond-user
[Top][All Lists]
Advanced

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

Re: Unicode accidentals vs. Markup accidentals


From: Werner LEMBERG
Subject: Re: Unicode accidentals vs. Markup accidentals
Date: Mon, 16 Jan 2023 05:56:01 +0000 (UTC)

> IMO Lilypond should render musical Unicode characters using the same
> font as the music itself,

No, it should not.  If you select font 'foo' for text rendering,
everything should come from that font.  If a certain character is not
in 'foo', it is the FontConfig library rather than LilyPond that
selects a fallback font – and it is more or less unpredictable which
fallback is actually used due to the way how FontConfig works.  If you
want LilyPond glyphs you have to explicitly select them.

In general, I strongly suggest that you *always* select the correct
font for text rendering to assure that your document stays portable
and can be reliably compiled on other systems. 

> and the default size/alignment of the glyphs within text markup
> should not require adjustment to look correct.

How do you want to adjust the size in an automated way?  Just think of
using Times New Roman together with Courier, as shown in the image –
what size should the LilyPond glyphs have?  And the default
positioning is not too bad, as demonstrated in the other image.

```
\markup { "foo" \number "♭♯♮" "bar" }
```


    Werner

PNG image

PNG image


reply via email to

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