Hi,

I took a quick look at the Locale code and the Resource Manager code and as far 
as I can see Flex already supports language only locales (see comments in 
Locale.as).

So possibly all that is requires to fully support an language locale is to:
1. add it as an ultimate fall back (as required) in sortLocalesByPreference, eg 
if you specify -locale=en_US the locale chain would become en_US,en
2. Compile both the en locale and en_US locale (which would be empty) into the 
swf, hopefully with you just specifying -locale=en_US

This mean it will be much simpler to support new locales that have the same 
language as previous supported languages as the differences between en_AU and 
en_GB and en_US (or even  fr_CA and fr_FR) are fairly minor. When switching 
between multiple locale of the same language the compiled resources would be a 
lot smaller and have no duplication.

This would carry on from the framework resources to user resources as well 
means a lot less duplication in resource files and mean you don't have to fully 
translate a locale in order to start working with it.

This would also require a bit of a cleanup of the current resource files. 
Initially setting the "en" locale to have the same resource files as en_US (via 
the copylocale utility) so all applications are not suddenly speaking the 
Queen's English :-)

Anyone see any issue with this? There probably a few other things that may need 
to change to support this but probably worth an experiment.

Thanks,
Justin

Reply via email to