Interesting idea. In my experience this sort of thing is not necessary, but if you have continued problems it might be worth doing. Bear in mind that I think that will slow things down a bit. The AdobeFnt file seems to be some kind of cache that, when not corrupted, helps the PDF system start up faster. So it would be a shame to delete it all the time if it was really fine.

Geoff

try
	set bad_file to (path to application support from user domain as string) & "Adobe:TypeSpt:AdobeFnt08.lst" as alias
	set theTrash to path to trash
	tell application "Finder"
		move bad_file to theTrash
	end tell
end try

Thanks for stopping by the booth. Hope we cleared up the mystery

Geoff

Hmm… Bummer. It has always worked for me, so I’m not sure what to say. One time I thought I was on v3, removed the mystery file, and still had crashing. But when I looked to be sure, it was actually not v3. Maybe it is worth a second check? Otherwise, let us know if you make any progress.

Geoff

——- strip ——
So we are all guessing about Lumen, my guess is that it is an interface for RadiantCMS.

——- strip ——
-Brian

It will always be automatically recreated when you make a PDF, but in my experience, that is not a problem. The presence of this file is not a problem in itself. It is when you have a corrupted version of the file that you get crashing. In my experience, the one that is auto-created is problem free, so you don’t have to worry about it anymore.

It is possible it will get corrupted again, and you’ll have to re-do the fix. But so far, in my experience, this has not happened. I suspect the corruption may have arrived from some older version of Acrobat, and stuck around until FileMaker made it obvious because in every case, for me at least, deleting this file once was a permanent fix.

Geoff