This content has been marked as final. Show 4 replies
That's a magnifique script! Works very well.Just one question: you've hard-coded the unicode ranges for the dropdown--is it not possible to get that information from the font?
You have a point : the glyphs/ranges available in the current font are certainly documented in the font file itself. The problem is that I don't know how to extract and parse this information! For the moment, the glyph-checking process is "empirical", thanks to the Dave Saunder's outline-trick:
[Precision: SpecialCharacters names and id's exposed from the script are also hard-coded, despite of your great method using the array SpecialCharacters.reflect.properties. The point is that I wanted InDiCode to be InDesign CS-compatible.]
I rely on users feedbacks and requests to improve and extend the process in the future. InDiCode has been primarly designed as a library and the script hosts a lot of "sleeping" features (exporting methods, UTF8 translation...).
Great stuff! Thanks for sharing it with the community.
We have some work to do, though--not all special characters can be entered using Unicode, and some ranges cannot be entered via script. I really hope we can provide for Unicode entry of all characters in a future release.
"(...) not all special characters can be entered using Unicode (...)"
Yes, that's one of the problem I focused in the introduction of my paper (http://marcautret.free.fr/geek/indd/unicode/part1.php -- in French, sorry!)
See also this PDF built form CS2 specialchars set:
And a short diagram illustrating how to deal with SpecialChars-vs-Unicode problem:
In CS3, the main innovation is SpecialCharacters.textVariable, which seems to behave as a read-only non-Unicode pseudo-character.