Re: fontconfig caches

[Bailey James E .]

Ah, that's a bit closer. I have fonts.conf in /usr/local/etc/fonts/  
but it tells me that editing it would be pointless, since it will be  
overwritten the next time the fontconfig cache is built, and I should  
instead use local.conf. I assumed I could just add local.conf to my ~/ 
etc/fonts/, and that the lilypond fonts.conf would be sufficient for  
my new local.conf. Unfortunately, I still get the fontconfig cache  
built in each directory I run lilypond in. I thought maybe because  
normal users don't usually have access to write to /usr/local/ that  
might be a problem, but even when I have fontconfig write the default  
cache to ~/etc/fonts/ it rebuilds the font cache in the working  
directory, and I even tried making myself an administrator, but that  
didn't help either. Ah well, at its longest, rebuilding the cache  
takes 10 seconds. I can live with that once per directory. I just wish  
I didn't have the annoying NONE/ all the time.

Am 13.11.2008 um 20:25 schrieb Patrick McCarty:

> Hi James,
>
> On Thu, Nov 13, 2008 at 6:15 AM, Bailey James E.
> <address@hidden> wrote:
> > what am I looking for? I don't have /etc/fontconfig. BTW, I'm using  
> > osx 10.5
> > and I build lilypond from sources.
>
> The location of my fontconfig configuration file is
>
> /etc/fonts/fonts.conf
>
> This is on a GNU/Linux system.
>
> Built from source, and installed as a local user in $HOME/usr, my
> fontconfig cache resides in ~/.fontconfig.
>
> HTH,
> Patrick