unable to change fonts - indesign 6
Hi,
I am trying to work on an indesign file, every time I try to open the file it gives msg saying missing fonts. Unfortunately the typesetter who sent the file dint package the necessary fonts. We tried replacing the fonts it worked fine. After the holidays, I saw this updates waiting to be installed, after installing the update we get this message 'missing fonts' 406 missing fonts but I replaced 404 fonts leaving 2 of them which we couldn't replace at all.
At first I thought it was the updates I did to the system - I lost connectivity to networks for a while there - but have since fixed that. I also updated my entire Adobe suite and that hasn't done anything either
I tried to export it as an IDML and it crashes. The 'missing' fonts are: Clarendon BT Heavy and Minion Pro Heavy. They should be Minion Pro Regular, which is what our designer changed it to before she left
So I tried to trash the preferences, but nothing happened
Also now when I try to change the fonts (with or without the old preferences), all of the type around it changes to Batang Regular and I can't change it back. I have no idea why, possibly this is also what the typesetter originally used?
The whole document is 200 pages long,
I am trying to work on an indesign file, every time I try to open the file it gives msg saying missing fonts. Unfortunately the typesetter who sent the file dint package the necessary fonts. We tried replacing the fonts it worked fine. After the holidays, I saw this updates waiting to be installed, after installing the update we get this message 'missing fonts' 406 missing fonts but I replaced 404 fonts leaving 2 of them which we couldn't replace at all.
At first I thought it was the updates I did to the system - I lost connectivity to networks for a while there - but have since fixed that. I also updated my entire Adobe suite and that hasn't done anything either
I tried to export it as an IDML and it crashes. The 'missing' fonts are: Clarendon BT Heavy and Minion Pro Heavy. They should be Minion Pro Regular, which is what our designer changed it to before she left
So I tried to trash the preferences, but nothing happened
Also now when I try to change the fonts (with or without the old preferences), all of the type around it changes to Batang Regular and I can't change it back. I have no idea why, possibly this is also what the typesetter originally used?
The whole document is 200 pages long,
Ugo Mena
are you using a pc or mac?
if the file was packaged in InDesign, you should have a folder named Document Fonts in the same folder as the INDD file. That folder has all of the fonts that were used in the document. You should see those in the Type menu as Document Fonts. This folder also includes the Adobe font cache .lst file.
If you are not able to see the correct fonts and/or cannot successfully change the fonts then you either don't have the Document Fonts folder in the same folder as the InDesign file (necessary for the packaged fonts to activate) or your machine's font caches are messed up.
If your fonts caches are messed up, I would recommend using one of the various free font cache cleaners out there for your particular OS
If you are not able to see the correct fonts and/or cannot successfully change the fonts then you either don't have the Document Fonts folder in the same folder as the InDesign file (necessary for the packaged fonts to activate) or your machine's font caches are messed up.
If your fonts caches are messed up, I would recommend using one of the various free font cache cleaners out there for your particular OS
ASKER
@ ultralites,
It is Mac 10.6.8
It is Mac 10.6.8
OK.
Use Font Nuke (http://www.jamapi.com/pr/fn/) to clear your font caches first, then double check to see if the Document Fonts folder is there.
Use Font Nuke (http://www.jamapi.com/pr/fn/) to clear your font caches first, then double check to see if the Document Fonts folder is there.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The problem is left unresolved as the user has created the whole document again.