Read this: Ignore warnings on open() (especially the part on restoring it a.s.a.p. to catch real errors -- an often-heard related symptom is "Dialogs in ID refuse to show up", and now you know why).
The real problem for me is that I can't use the font-check ID perform on my document because it resolve all missing instances. The good thing about that warning is that it display PDF files and their missing fonts, a very useful thing for me because I need to write those informations in a log file.
I will try to use the ignoreWarning method hoping to solve this problem.
Thanks a lot.
Okay, I see (now) what the problem is.
Switching the warnings off only helps you if you really want that file exported, missing fonts or not. The Scripting interface does not list anything for checking missing fonts inside a PDF. And I cannot try without a "bad" file, but I am not sure if the fonts "in" a PDF (missing or present) are even listed in the active document's Fonts list. (I don't think so, because in that case you would have to have a font.status value of "Embedded" -- which is not in the list.)
I compose my document dinamically so I only get errors when exporting it inPostScript.
This is the warning panel I have when a PDF file is missing some fonts:
It says: "Following fonts are not found:", and give me the name of the PDF document and the missing font.
If I check through Find fonts command I also get the PDF attachment missing fonts, but I get any instance (the one following is another document missing other fonts...):
The good thing for me in order to create a log file is to be able to read and use the informations I get from the first warnig panel.
P.S. If you try to place a PDF file whose missing fonts ID gives you the same warning panel.