On Tue, Jul 30, 2013 at 3:19 PM, Alex Harui <aha...@adobe.com> wrote:
> Crap, this got stuck in my mailbox. > > On 7/29/13 2:27 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > >On Mon, Jul 29, 2013 at 12:53 PM, Alex Harui <aha...@adobe.com> wrote: > > > >> > >> > >> On 7/29/13 11:32 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> > wrote: > >>Did you look into having the installer pick up the language based on the > >> current locale settings? I saw you set the default to en_US, but maybe > >>I > >> missed the other change. From a look around the internet, it wasn't > >>clear > >> that StringTools would return the current locale if like me, I have an > >> English Max OSX but picked, for example, japanese as the current > >>language. > >> > >> On the other hand, I think it has been this way for a while, so maybe it > >> isn't worth fixing right now. > >> > >> > >We are using StringTools(LocaleId.DEFAULT).actualLocaleIDName right now. > > Which according to the docs [1] seems to be doing what you want, right? > > > >[1] DEFAULT:String - flash.globalization.LocaleID > >Indicates that the user's default linguistic preferences should be used, > >as > >specified in the user's operating system settings. For example, such > >preferences are typically set using the "Control Panel" for Windows, or > >the > >"System Preferences" in Mac OS X. > It is not working for me, at least on Mac OSX 10.6.8. I even built out a > simple test app that calls StringTools and the results do not reflect > System Preferences. The only thing that worked for me was > Capabilities.language. > > If it is working for others then it don't worry about it. > Mind sharing the test app? Perhaps on gist.github.com? Thanks, Om