Thank you, this worked. So, do I have to delete the .fontconfig file
everytime I use a new version? I mean, is this going to be a regular
part of the update process? 'cause the average macintosh user doesn't
know how to find hidden files.
Am 26.02.2007 um 15:42 schrieb Graham Percival:
James E. Bailey wrote:
Odd, 2.10.15-1-2.10.17-1 don’t error, but it also don't output a
file. The file goes as far as pre-processing graphical objects and
then nothing. And to be clear, I’m using the file that opens with
the program as my test file. I don't know if this matters, but the
most recent version I can compile is 2.10.13-1.1
Unfortunately I don't have this problem anymore. Could you try
removing any ~/.font* directories you have, and then try with
2.11.20? ( ~/.fonts, ~/.fontcache, ~/.fonts.cache-1 )
If it works like that, then try removing all those directories
again and trying the latest 2.10 version.
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
