Warn­ing: techy post for once; sorry about that reg­u­lar folks. Look­ing for some­thing nicer than cryp­tic bug fixes? Have a look around here!

So here we go: I’m work­ing on a big multi-lingual AIR app within Flash Builder and just received the locale files from my client today (made with Lupo).

Couldn’t wait to see what it looked like in Japan­ese and in all other lan­guages sup­ported (13, to be pre­cise) so I copied the “locale” folder into my project, updated the “Addi­tional com­piler argu­ments” with “–locale de_DE en_GB en_US es_ES fr_FR it_IT ja_JP pl_PL pt_BR pt_PT ru_RU tr_TR zh_CN –allow-source-path-overlap=true –source-path=locale/{locale}” and refreshed the project. Which broke, say­ing “unable to open ‘[blablah]\frameworks\locale\en_GB’”.

“Ouch”, I thought. Flex doesn’t sup­port Great Britain’s English?

In fact en_GB was not the only locale to break the project, so I Googled around and found that copy­ing your Flex frame­work en_US direc­tory and renam­ing it to the miss­ing locale could do the trick. For exam­ple I copied “C:\tools\flex4-air1.5.3\frameworks\locale\en_US” to “C:\tools\flex4-air1.5.3\frameworks\locale\en_GB” (I also did that for tr_TR, pt_PT and pl_PL)… Not the nicest solu­tion but lookin’ good anyways!

Almost.

I then stum­bled upon a lovely “Inter­nal build error”. But that’s cool.

I can’t explain how I found how to fix this but I did: some of the locale files (named Main.properties) where hav­ing lines with only a back-slash in them (\). I sim­ply removed those lines every­where I found them and that was it.

I don’t know if this has any­thing to do with Lupo, or else; but it’s fixed and yes: the app looks nice in Japan­ese, thank you.