Sep 03, '03 09:14:00AM • Contributed by: Anonymous
Then I've noticed one web site that uses a specific font was no longer displaying in that typeface, even though I had it installed. Turns out I had recently organized the last few loose fonts I had in my Fonts folder into their proper subfolders - Photoshop could see them, but Safari could not. Moving the font back to the root of the fonts folder, and the page rendered correctly.
Is this inherent to the difference in font handling by Carbon and Cocoa apps?
[robg adds: Based on my testing, it certainly seems that Cocoa apps cannot see fonts in a subfolder within the local Fonts folder. I used TextEdit and moved fonts in and out of the subfolder; any font I moved was not available the next time I launched TextEdit. This is confusing, as Apple themselves claim:
Mac OS X also supports hierarchical font folders so users can create multiple levels of font folders within font directories. Mac OS X makes all fonts installed in any of the font folder locations, or specific application locations, active.I found this quote in Apple's "Using and Managing Fonts in OS X" [3.1mb PDF] ... and yet, it seems it doesn't work properly for Cocoa applications -- in either 10.2.6, or in 10.3 (according to a developer friend). Can anyone shed some light on the issue? Shouldn't this work as described?]
