I'm adding some glyphs to an existing font and am trying to better undestand how the set up of the OTF font effects finding characters in PDF files generated by InDesign.
When adding glyphs I use Adobe's list (http://www.adobe.com/devnet-archive/opentype/archives/glyphlist.txt) to name the glyphs.
Currently I'm adding the ae dipthong character with a macron (unicode code point 01E3) as well as a the thorn with a cross stroke (unicode code point A765). The ae IS in Adobe's list, the thorn is NOT. In my liga feature I added the following:
sub f i by fi;
sub Thorn macron by Thornmacron;
sub thorn macron by thornmacron;
sub AE macron by AEmacron;
sub ae macron by aemacron;
As far as I knew this provided everything necessary so that when I export from InD to PDF I can search for a regular ae (with no macron) or a regular thorn (with no stroke) and my new glyphs will get found as well as the "regular" ones.
If I insert either glyph using the InDesign glyph palette, InD inserts them as a single character. If I insert the main character (the ae or the thorn WITHOUT the macron/stroke) followed by the macron, InDesign puts in the two characters and dutifully uses the glyph as it should.
When searching an exported PDF, however, ALL the occurances of ae are found regardless of how they were inserted, but the thorn characters that were inserted by using the glyph palette (and are a single glyph in InD) are NOT found. Only the "regular" thorns (with no cross stroke) and the ones that are in InD as two characters are found.
Does anyone know whether this is because InD and possibly Acrobat don't "know" what the thorn with the stroke because it's not in Adobe's list? Other than being from two different unicode sets, I don't why there would be a difference with the ae versus the thorn.
Thanks for any insight anyone can offer and thanks for reading a marathon post!