Re: Prioriziting a directory
On Tue, Dec 20, 2022 at 1:50 PM Jean Abou Samra wrote: > > > Le 18/12/2022 à 22:27, Jean Abou Samra a écrit : > > Le 18/12/2022 à 22:22, Abraham Lee a écrit : > >> > >> By the way, is there already an issue for your request in the > >> LilyPond > >> tracker? > >> > >> > >> No, I haven't submitted an issue about this. I've tolerated it for > >> long enough that I just keep forgetting about it lol. > > > > > > Then I suggest to create one. > > Well, I ended up creating it. > > https://gitlab.com/lilypond/lilypond/-/issues/6486 Thanks so much, Jean! It's been too long since I posted an official "issue" as the place has moved around over the years and I lost track. Best, Abraham
Re: Prioriziting a directory
Le 18/12/2022 à 22:27, Jean Abou Samra a écrit : Le 18/12/2022 à 22:22, Abraham Lee a écrit : By the way, is there already an issue for your request in the LilyPond tracker? No, I haven't submitted an issue about this. I've tolerated it for long enough that I just keep forgetting about it lol. Then I suggest to create one. Well, I ended up creating it. https://gitlab.com/lilypond/lilypond/-/issues/6486 Best, Jean OpenPGP_signature Description: OpenPGP digital signature
Re: Prioriziting a directory
Le 18/12/2022 à 22:22, Abraham Lee a écrit : By the way, is there already an issue for your request in the LilyPond tracker? No, I haven't submitted an issue about this. I've tolerated it for long enough that I just keep forgetting about it lol. Then I suggest to create one. Best, Jean OpenPGP_signature Description: OpenPGP digital signature
Re: Prioriziting a directory
On Sun, Dec 18, 2022 at 2:16 PM Jean Abou Samra wrote: > Le 18/12/2022 à 22:03, Abraham Lee a écrit : > > Great questions, Jean. > > > > As a font creator (both text and music) and semi-power user, I've > > always hated that LilyPond only looks within its own data folder for > > music fonts. This has required me to duplicate all my fonts to the > > data directory of every new version of LilyPond I install to make them > > accessible to that version. It's tolerable, yes, but feels a bit > > needless duplicating the same files over and over, IMHO. So, while > > we're on this topic, is there any chance the music fonts can get the > > same treatment as text fonts? In other words, if the music font family > > doesn't exist in the data directory, search the system's folder? Would > > love to be able to install them like a normal font and use them > > with any version. Pretty sure I wouldn't be the only one who > > appreciates that. My two cents. > > > > > Abraham, this is a sensible request that I have thought about at times, > but the context of my question is very different. LilyPond uses > Fontconfig only to look up glyphs in Emmentaler if the font-encoding is > 'fetaText, for dynamic texts, fingering digits and the like, but for > most glyphs it uses an entirely different internal mechanism. Here, I am > concerned with fixing the problem reported at > https://lists.gnu.org/archive/html/lilypond-devel/2022-12/msg00024.html, > which means preventing LilyPond from finding its fonts externally in > 'fetaText (and hopefully there is a way to do this and still make the > music font searched elsewhere if it's *not* in the datadir). Satisfying > your request would mean touching a different area, the code that looks > up music fonts in 'fetaMusic and 'fetaBraces encoding. > Appreciate the quick reply and I apologize for not realizing the difference between your original question and my semi-related request. > By the way, is there already an issue for your request in the LilyPond > tracker? > No, I haven't submitted an issue about this. I've tolerated it for long enough that I just keep forgetting about it lol. Best, Abraham
Re: Prioriziting a directory
Le 18/12/2022 à 22:03, Abraham Lee a écrit : Great questions, Jean. As a font creator (both text and music) and semi-power user, I've always hated that LilyPond only looks within its own data folder for music fonts. This has required me to duplicate all my fonts to the data directory of every new version of LilyPond I install to make them accessible to that version. It's tolerable, yes, but feels a bit needless duplicating the same files over and over, IMHO. So, while we're on this topic, is there any chance the music fonts can get the same treatment as text fonts? In other words, if the music font family doesn't exist in the data directory, search the system's folder? Would love to be able to install them like a normal font and use them with any version. Pretty sure I wouldn't be the only one who appreciates that. My two cents. Abraham, this is a sensible request that I have thought about at times, but the context of my question is very different. LilyPond uses Fontconfig only to look up glyphs in Emmentaler if the font-encoding is 'fetaText, for dynamic texts, fingering digits and the like, but for most glyphs it uses an entirely different internal mechanism. Here, I am concerned with fixing the problem reported at https://lists.gnu.org/archive/html/lilypond-devel/2022-12/msg00024.html, which means preventing LilyPond from finding its fonts externally in 'fetaText (and hopefully there is a way to do this and still make the music font searched elsewhere if it's *not* in the datadir). Satisfying your request would mean touching a different area, the code that looks up music fonts in 'fetaMusic and 'fetaBraces encoding. By the way, is there already an issue for your request in the LilyPond tracker? Jean OpenPGP_signature Description: OpenPGP digital signature
Re: Prioriziting a directory
Hi all, > As a font creator (both text and music) and semi-power user, I've always > hated that LilyPond only looks within its own data folder for music fonts. OMG YES As someone with multiple installations of Lilypond, and multiple custom fonts, managing this is more than a small PITA… > Would love to be able to install them like a normal > font and use them with any version. pretty please…? K
Re: Prioriziting a directory
Great questions, Jean. As a font creator (both text and music) and semi-power user, I've always hated that LilyPond only looks within its own data folder for music fonts. This has required me to duplicate all my fonts to the data directory of every new version of LilyPond I install to make them accessible to that version. It's tolerable, yes, but feels a bit needless duplicating the same files over and over, IMHO. So, while we're on this topic, is there any chance the music fonts can get the same treatment as text fonts? In other words, if the music font family doesn't exist in the data directory, search the system's folder? Would love to be able to install them like a normal font and use them with any version. Pretty sure I wouldn't be the only one who appreciates that. My two cents. Much thanks, Abraham On Sun, Dec 18, 2022 at 12:22 PM Jean Abou Samra wrote: > Hi, > > Is there a way to express this in a Fontconfig configuration > file: "If you find a matching font in this directory given > as relative path, ignore other matches and choose that one"? > > Context: LilyPond (the GNU music typesetter) uses Fontconfig via > Pango for finding text fonts, but also for music fonts in some > cases. The music fonts are developed together with LilyPond, > and a given LilyPond installation should never look outside > of its data directory for finding music fonts. However, text > fonts should be findable on the system. > > If this isn't possible, I'll use two FcConfigs with Pango, > and restrict one of them to LilyPond's datadir only, but > currently LilyPond sets up a fallback to normal text fonts > for its special fonts, and it would be nice to preserve > that. I hope that's clear. > > Thanks, > Jean > >
