1) Also, it's important to remember that any SpecialCharacters member is implemented as a pure Number:
'number' == typeof SpecialCharacters.INDENT_HERE_TAB; // true
And, in this case:
1397319796===SpecialCharacters.INDENT_HERE_TAB; // true
So there is a potential issue in just using == or != when dealing with text contents. Suppose that a textual object (story, textframe, line, word, etc.) contains the string "1397319796". Then the test:
myText.contents == SpecialCharacters.INDENT_HERE_TAB;
will return true, which is not exactly what you expected! Indeed, JavaScript considers that:
"1397319796" == 1397319796;
So, when you compare a contents property and a SpecialCharacters member, it's recommended to use a triple-equal sign (===), or the opposite !==, to prevent any surprising conclusion.
// Here we are sure that .contents is an actual IndentHereTab
myText.contents === SpecialCharacters.INDENT_HERE_TAB;
(Note that myText.contents, here, is a Number, not a String.)
2) Another dangerous issue is that every SpecialCharacters member is silently converted into a String object (a simple character) when myText.contents contains *other* characters. For example, if myStory contains "A" followed by an IndentHereTab, then myStory.contents returns a string of two characters:
myStory.contents === "A\x07";
because SpecialCharacters.INDENT_HERE_TAB is internally translated into U+0007.
But of course, you still have:
myStory.characters[1].contents === 1397319796; // true
and not:
myStory.characters[1].contents === "\x07"; // false
myStory.characters[1].contents == "\x07"; // false
See also:
http://www.indiscripts.com/post/2009/07/idcs4-special-characters
@+
Marc
