[Top][All Lists]

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

Planned font-related changes

From: Jean Abou Samra
Subject: Planned font-related changes
Date: Wed, 05 Apr 2023 02:29:41 +0200
User-agent: Evolution 3.46.4 (3.46.4-1.fc37)

As a follow-up to
I thought it might be helpful for reviewers to explain how
the somewhat numerous changes I am submitting and preparing
around fonts are organized and interrelate.

There are several independent fronts:

1. Improving the part of the code that takes an alist chain and
   chooses the basic selection method for the font: simplifying,
   decoupling font families and font sizes. Basically,
   has an important follow-up (renaming 'feta to 'music) that was
   left out of !1888 because it was already large/complex enough.

2. Make Pango font selection more flexible. The first step is
   It depends on !1888, but only because there would otherwise
   be annoying merge conflicts; logically speaking, it is independent.
   There will be a second patch in this series to fix

3. Improve how LilyPond searches for music fonts in the file system.
   Goals are issues [#6485](
   and [#6486](
   A prerequisite is 
   There will be one or two more patches after that.

4. Get rid of the font-encoding property to simplify the internals. This is
   [!1914]( is
   a prerequisite.

I have more ideas, mostly speculative; this is what is relatively settled at 
the moment. 

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

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