The only thing I can think of is that while you may not have activated the font, in order for a font to appear, and indeed be chooseable in InDesign, it has to be activated SOMEWHERE. Depending on your OS, it could be in different folders on your system. I'm on OS X, and there are actually three places the font can reside and be available to applications. /Library/Fonts, ~/Library/Fonts, and System/Library/Fonts are folders which will allow fonts to be active on a system-wide basis. BE VERY CAREFUL with moving fonts from these locations, as doing so has the potential of causing issues. Especially with the System/Library/Fonts folder; if a particular font is moved from this folder it may make your computer unbootable. If you use a font manager, it may be auto-activating the font when InDesign sends a call for it. Hope this helps...
No, definitely not activated anywhere.
I control all the fonts and know exactly where they all are, which ones have to stay, which ones the OS tries to repair when moved even though they are not crucial, etc etc.
It's odd because, if as I mentioned above, if we "save as.." and then reopen the file, the dialogue box comes up alerting the user that the fonts are indeed missing.
Also, if I drag the font frame to a new window or copy and paste to a new document, I can see in "Normal" mode the fonts become highlighted in pink, indicating of course that the font is actually missing.
We can reproduce this on all the Macs here regardless of the font(s) being used.
I wish it was as simple as a font being activated somewhere.
Thank you for the attempt though.
No one else that has read this question has seen this? If so, that is really odd since we see it on 3 of the Macs here that we do most of the work in InDesign on.
Have you tried clearing the font caches and resetting the ID prefs (see Replace Your Preferences ). I have to say it sounds very much like these files are packaged and the package includes a Document Fonts folder. InDesign WILL automatically use any fonts contained in a Document Fonts folder that resides in the same location with a document, regardless as to whether these fonts are also installed elsewhere. This feature was added in CS5
Peter, I was not aware that CS5 added that feature. Do you have a link to documentation for this specific feature?
I would like to read more about it.
I don't have a link, but the feature is called Document Installed Fonts and it would probably be described in the What's New articles for CS5.
Thanks. I looked it up as well as ways to disable it. I did not see any. I've told the people in the department to move or rename the Documents Fonts folder.
We don't want fonts automatically being enabled. We want to have full control over it.
Thanks for the help.
For anyone else interested in disabling this feature, I found a script that renames the Document Fonts folder using a startup script.
The question was raised elsewhere in the forums
Keep in mind that the reason this feature was added is that many service providers asked for it. Its purpose is to be sure that you are always using the exact version of a font that your customer was using, whether you have a version installed or not.
Oh I am sure it was requested and for many who do not control the fonts, as we do, it probably works fine for them.
I disable all but required system fonts including going into the system and removing self healing fonts.
We, as many printers do, use font activation software and temporarily activate only the fonts provided by the customer for their particular file.
Thanks again for your assistance. Have a great weekend.
That is exactly what this feature does, but without need for you to constantly activate and deactivate fonts manually. And it should even insure that client fonts are used instead of installed system fonts if they are in the folder.
Yes, it's a good feature. I don't disagree with that.
I want one workflow though and with what we do it works regardless of whether the customer has packaged the project or if the folder is called Document Fonts or not.
I always try to minimize the variables and have one standardized workflow.