I'm using "en" because that's the line of code I eventually dug out of the
SDK that was causing the problem. It works fine on all the other
platforms and for English on Chrome. I'm pretty sure it can use many
flavors of the string and if it's invalid or not available it is suppose
to use a fallback locale not RTE.
Carol
On 1/24/13 4 :50PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>HI,
>
>> This is definitely a Flash Chrome issue, not a Flex issue. Here's the
>>code that demonstrates the issue. There seem to be no locales on
>>Chrome. The new on the Collator blows up with the TypeError: Error
>>#2007 error. debug is just a TextArea.
>>
>> private function initApp():void
>> {
>> var locales:Vector.<String> =
>>Collator.getAvailableLocaleIDNames();
>> debug.appendText("locales length is " + locales.length +
>>"\n");
>> debug.appendText(locales.toString() + "\n");
>>
>> try
>> {
>> var sortingCollator:Collator =
>> new flash.globalization.Collator("en",
>>CollatorMode.SORTING);
>> }
>> catch(e:Error)
>> {
>> debug.appendText("new Collator : error = " +
>>e.toString());
>> }
>> }
>
>Probably not the issue but "en" as a locale is a little odd, it usually
>en_us, en_au, en_gb etc etc. You can't compile the Flex SDK with an "en"
>locale for instance.
>
>Justin
