This question is probably best answered by Om, but I think it would be better to replace RuntimeLocale.as with a simple but extensible properties files that get loaded as needed based on the locale. That way, new locales can be added without re-compiling the installer. Is there some aspect of RuntimeLocale that will be hard to replace?
My plan would be to: 1) convert RuntimeLocale.as to a set of Ant-compatible .properties files (id=string). 2) the installer would load the selected locale's .properties files and the en_US.properties from our website like we currently load sdk-installer-config.xml Thoughts? -Alex
