I would think about whether you're willing to play with beta software in the next month or so that has solved this problem within the framework :-) Runtime localization is one of our features in Flex 3. Matt
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of gary_mangum Sent: Wednesday, May 23, 2007 10:51 AM To: [email protected] Subject: [flexcoders] Internationalization using Modules? I am trying to figure out the best way to allow my app to support i18n. My first approach was to put all strings into separate ResourceBundles and complile separate SWF files for each language. In other words my entire application is inside of one SWF file and I have one for each language. The web site hosting the SWF file must decide which language to use and load the appropriate SWF. Then I learned about Modules and wondered if it would be possible to compile my ResourceBundles into separate SWF modules (en_US.swf, de_DE.swf, etc), one for each language. Can my main application decide which language SWF Module to load and bind all of the text fields to the ResourceBundle coming from the dynamically loaded SWF module? If this is possible, it would be a great way to allow one main application SWF file to dynamically load the language of choice. I played around with this a little and couldn't figure out how to reference ResourceBundles inside of a Module after it was loaded. Can I load a Module and access it's public members? In general, I am pretty new to Flex and wanted to throw this idea out to the group to get your opinion on whether or not this is a reasonable approach. What do you think? Thanks
