FontNuke & Caches

msmiths12 March 2009 · 19:25

Is the consensus around here, when going through test edits with a newly exported font that the only way to ensure against corruption, and problems is to use some type of cache clearing program (such as FontNuke).

I've run into some strange glitches such as missing glyphs showing up in my Illustrator glyph palette today… but I've also resisted clearing my cache every time and have just been deleting from FontExplorer X and re-importing…

Is there a faster way than having to clear caches with either FontNuke, FE X, and restarting?

Thanks,

Mike

blank12 March 2009 · 20:01

I find that as long as I get the naming right, and the Adobe apps don’t crash while I’m working, I don’t need to clear the caches at all. If you do find yourself needing to clear system caches and reboot, don’t load the test fonts in Fex, just output them directly to ~/Library/Application Support/Adobe/Fonts and restart the Adobe app to get the new fonts. If you have problems just delete the fonts, clear the application caches, and you won’t have to reboot.

Obviously this strategy works better on a desktop with a fast drive than on a laptop where program loading is slower.

Jason Pagura13 March 2009 · 01:01

I've had no trouble with just outputting the new font version with another name. It doesn't matter what you call it while you're doing development testing, so I just append a revision number to the name, written out in English, and I haven't had any font conflicts that way. It also allows me to keep the earlier versions installed so I can easily make comparisons.

msmiths19 March 2009 · 16:03

Thanks for the replies, that's great to hear, I wondered if anyone else did that… I realized at some point just changing the name effectively does the same thing and saves a lot of time and hassle…

Claus Eggers Sø...21 March 2009 · 12:17

If you output / generate to Applications:Adobe InDesign CSX:Fonts and overwrite the old versions, then the new fonts are loaded by InDesign instantly. No need to even close and re-open the current document(s). I newer had a problem with that procedure.

Claus Eggers Sø...21 March 2009 · 12:18

sorry, double clicked the post button

msmiths22 March 2009 · 21:11

Yeah I'm coming to find that the overwrite process works well and Adobe seems to load the overwrite as you said, instantly… although I have the fonts activated through FontExplorer… It's nice to see the change happen immediately within the application without having to clear caches and restart…

blank22 March 2009 · 21:43

I had no idea I could do that without reloading. Thanks for the tip, guys!

Captured from web.archive.org on 3 Feb 2010. view this capture