lilypond-devel
[Top][All Lists]
Advanced

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

Re: Accidentals' font


From: Paolo Prete
Subject: Re: Accidentals' font
Date: Fri, 3 Jul 2020 20:09:51 +0200

On Fri, Jul 3, 2020 at 6:05 PM Xavier Scheuer <x.scheuer@gmail.com> wrote:

> On Fri, 3 Jul 2020 at 16:54, Paolo Prete <paolopr976@gmail.com> wrote:
> >
> > They are good, but not GPL/open source...
>
> Hello Paolo,
>
> Most of them were open source initially (Open Font License).
> There are repositories with the OFL-licensed versions here:
> https://github.com/OpenLilyPondFonts
>
> Recently Daniel Benjamin Miller shared (on lilypond-user mailing list) his
> work for a better support for Bravura (also OFL) in LilyPond:
> https://github.com/dbenjaminmiller/bmusicfonts
>
> In the past talented developers (sorry, I do not remember who exactly but
> thanks!) implemented a simple way to replace the music font, see NR 3.4.4
> Replacing the notation font
>
> http://lilypond.org/doc/v2.21/Documentation/notation/replacing-the-notation-font.html
>
> And presently Owen Lamb is implementing (GSoC 2020) SMuFL support in
> Lilypond.
>
> I mean, it can always be improved but I am grateful for the work people
> have done so far.
>
> Cheers,
> Xavier
>
> --
>

Hello Xavier,

Thank you for the links.
However, from what I see, they are more or less a "stylistic" choice.
Instead, the Gonville font has a *functional* point of view that solves
many issues of the Feta Font.
If you look at its glyphs you can see that there's a meticulous work of
making them optimized for *reading*.
I don't understand why this is not part of Lilypond's project.
I would use it as default. But, at least, it should be added as a
ready-to-use option.

Best,
P



>


reply via email to

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