On Nov 25, 2008, at 03:31, Peter Dyballa wrote:
Am 25.11.2008 um 00:23 schrieb Jeremy Huddleston:
Again, the application you need to run is sudo /usr/X11/bin/ font_cache ... which I just realized wouldn't be on your system. Grab it from here:
http://www.opensource.apple.com/darwinsource/10.5.5/X11fonts-5.1/font_cache....
That takes care of running your mkfontdir, mkfontcache, etc...
I added sym-links to /sw/lib/fontconfig2/bin/fc-cache to /usr/X11/ bin, then the script ran successfully:
font_cache: Scanning user font directories to generate X11 font caches font_cache: Making fonts.dir for updated directories. font_cache: Updating FC cache font_cache: Done
<snip>
Could not init font path element /usr/X11R7.4/lib/X11/fonts/misc/, removing from list!
run: sudo font_cache -s -v -f
After I've added the X11 and X11R7.4 font paths to my ~/.fonts.conf I get after the "Build Date:..." line an extra:
Thread Assertion Failed: self=Unknown Thread, expected=Xserver Thread xprFrame.c:xprInit:448
That is fine.
There is no other change, the same font path elements are reported missing.
BTW, "Xquartz --help" launches the server visibly, i.e., a form pops up for a few seconds, partially obscured by Cocoa Emacs.app in which I am working, and X11.app starts to leap in Dock.
Fc-list lists a "Times" font. "Xquartz :0 -fn Times" brings at the end a little change:
Fatal server error: could not open default font 'Times'
Yeah, that's because fontconfig is not used for server fonts. There are 2 font systems in X11. You need to make your xfs font caches by doing the: sudo font_cache -s -v -f