Re: Changes in notation font in 2.25

2024-07-16 Thread Werner LEMBERG
>> Note, however, that a lot of Emmentaler glyphs have been renamed >> since the original release of the cadence fonts, and these glyphs >> will certainly fail because LilyPond won't be able to find them.  >> In other words, your simple example works by chance only. > > Were that many glyphs rena

Re: Changes in notation font in 2.25

2024-07-14 Thread Jean Abou Samra
Le dimanche 14 juillet 2024 à 03:41 +, Werner LEMBERG a écrit : > > No, it is not correct.  Option `-I` is for LilyPond input files and > not for basic resource files like the music fonts.  Please follow the > instructions given in the NR section 'Replacing the notation font'. Right. The alt

Re: Changes in notation font in 2.25

2024-07-14 Thread Jean Abou Samra
Le samedi 13 juillet 2024 à 06:03 +, Werner LEMBERG a écrit : > Note, however, that a lot of Emmentaler glyphs have been renamed since > the original release of the cadence fonts, and these glyphs will > certainly fail because LilyPond won't be able to find them.  In other > words, your simple

Re: Changes in notation font in 2.25

2024-07-13 Thread Werner LEMBERG
> In this example, I cloned the directory of the git repository, then > included the /otf directory like this: > > ~/lilypond-2.25.17/bin/lilypond -I /path/to/cadence/otf/ -dcrop -o > cad_new cad.ly > > Does this look correct? No, it is not correct. Option `-I` is for LilyPond input files and

Re: Changes in notation font in 2.25

2024-07-13 Thread William Rehwinkel via LilyPond user discussion
Dear Jean, In this example, I cloned the directory of the git repository, then included the /otf directory like this: ~/lilypond-2.25.17/bin/lilypond -I /path/to/cadence/otf/ -dcrop -o cad_new cad.ly Does this look correct? Thanks, -William On 7/13/24 06:18, Jean Abou Samra wrote: Le ven

Re: Changes in notation font in 2.25

2024-07-13 Thread William Rehwinkel via LilyPond user discussion
I see, thanks for letting me know. I'll see if this is something I can contribute to in the future, but for now I don't have any experience in modifying old fonts or creating new ones. Thanks, -William On 7/13/24 02:03, Werner LEMBERG wrote: The reason is, it appears that old notation fonts

Re: Changes in notation font in 2.25

2024-07-13 Thread Jean Abou Samra
Le vendredi 12 juillet 2024 à 19:06 -0400, William Rehwinkel a écrit : > The reason is, it appears that old notation fonts have become slightly > broken, especially glyphs relating to numbers (time signatures, > multi-measure rests, figured bass).  This is almost certainly a setup issue. Please

Re: Changes in notation font in 2.25

2024-07-12 Thread Werner LEMBERG
> The reason is, it appears that old notation fonts have become > slightly broken, especially glyphs relating to numbers (time > signatures, multi-measure rests, figured bass). The attached files > are rendered in 2.25.2 and .16 using > https://github.com/OpenLilyPondFonts/cadence . I've just tri