Hey Brian, Thanks for sharing this. This looks really promising. This looks even better than the support Flex 3 will have for localization. What is left on the project? Are there any existing bugs?
I'd really love to get a look at this and see if it's something usable for an upcoming project. I can help work out the kinks as I develop this site. Aaron On 9/24/07, Brian Holmes <[EMAIL PROTECTED]> wrote: > > Hi Aaron, > > As Ben pointed out I'm working on a different way to do localization, > well, actually I just want to do language translation. A blog entry I wrote > about this can be found here > http://brianjoseph31.typepad.com/smashedapples/2007/09/sweet-flex-tr-1.html > And > i'm getting a bit further on it every day. My ultimate goal is to store > translations in a database and not have to deal with any xml files or > properties files. I haven't released the source code of what I got done > because its' not ready, but if you'd like to see it and contribute to it ( > I'm gonna release it open source) I'd be more than willing to send you the > code. just contact me offlist. > > brian.. > > ------------------------------ > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *aaron smith > *Sent:* Sunday, September 23, 2007 8:22 PM > *To:* [email protected] > *Subject:* [flexcoders] localization options in flex 2 > > Quick question. I'm looking into localization for an app, and one of my > concerns is that every piece of text has to be in the correct language for a > region. en, fr, etc. But there is quite a bit of text. So instead of having > a .properties files for all these different languages for every piece of > text. Can I just localize the flex components and just load the > corresponding text from a language XML file. So an english xml, french xml, > etc. That way instead of having to access a resource bundle with a key/val > pair for a specific piece of text, I can just assign the corresponding text > from xml to the .text property or .label, etc? I guess I don't see why I > would absolutely have to use ResourceBundle's except for localizing the flex > components. Any thought? > > ------------------------------ > *** > The information in this e-mail is confidential and intended solely for the > individual or entity to whom it is addressed. If you have received this > e-mail in error please notify the sender by return e-mail delete this e-mail > and refrain from any disclosure or action based on the information. > *** > > >
