I'm using localization on a flex project for a slightly different use. We have 2 projects that share the same code base, but we want to change some UI text that's displayed. So, we're using localization to swap certain text strings to be project specific.
Everything works fine for the web version, but if I try to take that same localization setup and use it in our AIR version, it cannot find the required resource bundles. I've looked and they(web/AIR) appear to be set up identically. My locales are: en_US_ProjA and en_US_ProjB. The AIR compiler argument is "-locale=en_US,en_US_ProjA". I only put the one project in to test getting the proper resource. My directories are: projRoot.src.locale.en_US.* projRoot.src.locale.en_US_ProjA.* projRoot.src.locale.en_US_ProjB.* When I debug a piece of localization code I see that the localeMap has 2 entries, en_US and en_US_ProjA. Both contain the same entries, but the properties files are pointing to different Obects. For example: en_US_ProjA$CairngormMessages_properties (@c3547b9). I should be seeing a UI_Text property file in the list of resource bundle objects, but it's missing. I'm stumped as to why it works just fine from a browser, but pukes in AIR. Thanks, Geoff
