Search document for SpecialCharacters Enumerator

To complete my previous post:

1) Given a Character myChar whose contents property returns a SpecialCharacter enumerator, you can still retrieve the Unicode codepoint using myChar.texts[0].contents instead of myChar.contents:

alert( myChar.texts[0].contents.charCodeAt(0).toString(16) ); // => Unicode CP (hexa)

2) Since ID CS5 the Enumeration objects (Locale, SpecialCharacters, etc.) describe a set of Enumerator objects rather than a set of numbers. An Enumerator is a special native object which converts itself into either a String or a Number depending on the context:

// ID CS5+
alert( SpecialCharacters.emDash ); // => EM_DASH (string)
alert( +SpecialCharacters.emDash ); // => 1397058884 (number)

In fact, these respectively correspond to myEnumerator.toString() and myEnumerator.valueOf():

// ID CS5+
var myEnumerator = SpecialCharacters.emDash;
alert( myEnumerator.toString() ); // => EM_DASH (string)
alert( myEnumerator.valueOf() ); // => 1397058884 (number)

But every Enumerator has its == and === operators overriden so as we can still compare it with a number:

alert( SpecialCharacters.emDash==1397058884 ); // => true
alert( SpecialCharacters.emDash===1397058884 ); // => true

Also, an Enumeration object see both the camelcase and the uppercase name of an enumerator as a regular own property:

// ID CS5+
alert( SpecialCharacters.hasOwnProperty('emDash') ); // => true
alert( SpecialCharacters.hasOwnProperty('EM_DASH') ); // => true

Both are [[enumerable]] but the for-in loop only collects the uppercase forms ('EM_DASH', etc.).

@+

Marc

Hi Ariel,

Use the Unicode code point in the GREP F/R field this way:

\x{200E}

See also:

http://www.indiscripts.com/post/2009/07/idcs4-special-characters

@+

Marc