see http://forums.adobe.com/message/2397025#2397025

and http://forums.adobe.com/message/4154758#4154758

in short not so easy

Trevor

@Pete – just a thought:

if we are looking for all none-white space characters and try to convert  character by character to outlines, and this convertion will fail, would that be the proof that we found a unassigned glyph?

Here an example. Characters that cannot converted to outlines will be formatted with the character style "NotDefinedGlyph", that you have to prepare before running this snippet:

//Very slow. Don't try this on large stories:
var d=app.documents[0];
 
var sChars=d.stories[0].texts[0].characters;
var sCharsLength = sChars.length;
 
//Not foolproof!
//False positives with ligatures like "fi" or "ffi":
for(var n=0;n<sCharsLength;n++){
    
    //Do not create outlines on white space characters:
    if(sChars[n].contents.match(/\S/)){
        try{
            var myOutlineArray = sChars[n].createOutlines(false);
            try{
            myOutlineArray[0].remove();
                }catch(e){};
            }catch(e){
                //Let's mark it with a character style in case it cannot be converted to outlines:
                sChars[n].appliedCharacterStyle = "NotDefinedGlyph";
                $.writeln(sChars[n].contents);
                };
        };
    
    };

Downside: this code would run very, very slow…
And: it's NOT foolproof. There are false positives with ligatures like "fi" or "ffi" etc.pp.

Uwe

Easy to spec out: a method that works at document level and lists glyphs/characters used in the document which are not present in the used fonts. For example, myDocument.missingGlyphs() would return an object that in some way tells you what glyphs are missing from which font. Something along these lines:

missing = app.activeDocument.missingGlyphs();

for (m in missing)

   $.writeln (m, missing[m])

So the keys would be the font names (Times-Bold, Arial-Italic) and the values, the missing glyphs in those fonts. But the data model doesn't matter, as long as you get a list of missing glyphs per font.

Would be great if you could write such a plug-in.

Peter

For CS4 (and hopefully newer): create a preflight profile that checks just the bad'uns, then flesh out the relevant details. The scripting engineers went a little bit crazy on making this scriptable, it seems.

(This code only returns the results after 2 minutes, and it only shows them. So please none of that "plz can u send ur complete script" crap if you plz.)

if (!app.preflightProfiles.item("Check glyphs only").isValid)
{
          glyphsOnlyProfile = app.preflightProfiles[0].duplicate();
          glyphsOnlyProfile.name = "Check glyphs only";
          for (i=0; i<glyphsOnlyProfile.preflightProfileRules.length; i++)
                    glyphsOnlyProfile.preflightProfileRules[i].flag = PreflightRuleFlag.RULE_IS_DISABLED;
          glyphsOnlyProfile.preflightProfileRules.itemByName("ADBE_MissingGlyph").flag = PreflightRuleFlag.RETURN_AS_ERROR;
}
 
 
glyphsOnlyProfile = app.preflightProfiles.itemByName("Check glyphs only");
 
 
activeProcess = app.preflightProcesses.add (app.activeDocument, glyphsOnlyProfile);
activeProcess.waitForProcess(120);
 
 
result = {};
for (i=2; i<activeProcess.aggregatedResults[2].length; i++)
          if (result[activeProcess.aggregatedResults[2][i][1]])
                    result[activeProcess.aggregatedResults[2][i][1]]++;
          else
                    result[activeProcess.aggregatedResults[2][i][1]] = 1;
alert (result.toSource());

That is very neat!

Thanks, that has let me off the plugin.

P.

@Pete – Wow! That is working. Just tested in InDesign CS5.5,

At least with my sample document I put up very fast.

"app.findGlyphPreferences.glyphID = 0" seems to be the proof…

Just one thing:

Instead of "allFound = app.findGlyph();" I would change the scope to one document:
"allFound = myDocument.findGlyph();"

Thank you a lot!

Uwe

@Pete – another thing: don't know why, but with that method you cannot find unassigned glyphs in overset texts.

Wheras  in the UI that is possible…

Example inDesign CS5.5:

if you are searching for "ID: GID/CID" value "0" in the UI Glyph search, for a given font you can find all the unassigned glyphs of that font even in overset text.

With your script snippet this is not possible.

Strange…

Sorry. I was too fast in testing…
Same in UI with glyph search: you cannot find glyphs with "ID: GID/CID" value "0" in overset text…

Uwe

Message was edited by: Laubender

Message was edited by: Laubender

Very nice, works on CS5

It would be useful to be able to find missing font styles as well.

If one of you bright guys could add that to the script it would be apreaciated

Trevor

In the meantime mark your answer as correct, helps with the forum search.

Good luck with the extension

Trevor

David wrote:

> For obvious reasons, "toString(16)" messes up 2nd-plane Chinese (e.g. U+2A64A, available in MingLiU-ExtB), but on my system (IDCS4 under Win7) the console still shows the correct character.

Just for added clarification: the "obvious" (grin) reason is that Plane 2 characters consist of not one Unicode, but TWO! And Pete's great discovery -- thinking well outside of the box! -- will probably report them, but it only sees one character at a time.

InDesign correctly handles the two successive Unicode character, although it's weird you can move your cursor "between" the two and then accidentally mess up your text.

For an example w/o being able to read Chinese, Check out the Apple Color Emoji font. You won't see the colors in InDesign, for unrelated reasons, but if you insert one of the icons into ID using the Glyphs palette, you can see it actually consists of two codes.

I'd only tried "regular" font styles, and didn't have occasion to notice the regular/roman bug, so I really appreciate Peter K.'s going back and ferreting this out. For those who know even less about scripting than I do, I got his fix to work in the code presented earlier in this thread by adjusting the three "doc." references in his before and after lines to "myDocument."

David

Pete,

This is the only way I can contact you. Hope you don't mind that I tarted up the script based on your excellent method with an interface and posted it on my site at http://www.kahrel.plus.com/indesign/missing_glyphs.jsx

Peter