Le mercredi 29 mars 2023 à 13:46 +, Werner LEMBERG a écrit :
> AFAICS, the only limitation is that an
> ordinary text font with a family name 'music' cannot be used.
No :-) unlike what its name suggests, the `font-family` property is a family
symbol, not a font string (yes, it's another
>
>> AFAICS, the only limitation is that an ordinary text font with a
>> family name 'music' cannot be used.
>
> No :-) unlike what its name suggests, the `font-family` property is
> a family symbol, not a font string (yes, it's another misnamed thing
> in font handling). The `font-family`
Hi,
Warning: start by taking a cup of coffee, this is all a bit headache-giving.
Sorry for the long post.
Currently, the algorithm to select a font for normal markup (i.e., I'm not
talking about music glyphs here) is roughly this:
1. Check the `font-encoding` property. If it's `fetaText`, use
Werner LEMBERG writes:
>>
>>> AFAICS, the only limitation is that an ordinary text font with a
>>> family name 'music' cannot be used.
>>
>> No :-) unlike what its name suggests, the `font-family` property is
>> a family symbol, not a font string (yes, it's another misnamed thing
>> in font
> 1. Look up `font-family`. If it's `music`, then use the music font,
>otherwise use a text font as appropriate for the `font-family`.
I'm all for your changes. AFAICS, the only limitation is that an
ordinary text font with a family name 'music' cannot be used. I think
we can live with
Here is the current countdown report.
The next countdown will begin on March 31st.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1889 Reuse \left-brace for SystemStartBrace - Jean Abou Samra
Le mercredi 29 mars 2023 à 17:05 +0200, David Kastrup a écrit :
> A default conversion of \text to \roman would likely match more than 90%
> of the current uses.
Yes, agreed. We could make convert-ly change \text to \roman, and emit a
warning that this might be wrong in a few cases.
