Thanks VELO and Logan.  This is exact the information I was looking
for.  I know of a company ;) that will be translating the Flex bundles
to 11 languages.  I will push to get them contributed to BabelFlex.

On Mar 15, 11:09 am, Logan Allred <[email protected]> wrote:
> On Mon, Mar 15, 2010 at 9:11 AM, Joe Kutner <[email protected]> wrote:
> > First, upon inspecting the framework ResourceBundles in the Sonatype
> > repository:
> > <http://repository.sonatype.org/content/groups/flexgroup/com/adobe/
> > flex/framework/framework/>
> > I found that many of the locales for the 3.2 version were not
> > correct.  For example, the de_DE (German) bundle has all French
> > strings in it.  I then looked into the 3.4 directory and found that
> > there was only an en_US bundle.
>
> As Velo said, these are broken bundles from BabelFlex. Once these are
> manually fixed, we can put them back in. I haven't had time to
> manually fix them yet. Maybe in another 2-3 months, we'll see.
> In the meantime, if someone would like to do this, it's not hard, it
> just takes several hours.
>
> In the meantime, you would need to use the copylocales script from the
> SDK to create your own bundles and put them in your own maven
> repository.
>
> > Finally, I need to localize the Advanced Data Visualization
> > ResourceBundles that came with FlexBuilder 3.0.  It seems like this is
> > something that should be provided by Adobe, or if not is available to
> > the public in some way.  Am I wrong?  Do I have to localize these
> > bundles myself.
>
> > In short, where can I find pre-translated bundles for these framework
> > level packages.  It seems like I should not be the first person to
> > encounter this problem.  Can someone explain how I can get the
> > different languages?
>
> In Flex 3 SDK, Adobe only provides en_US and ja_JP. All of the other
> languages you must translate yourself using copylocales and put them
> in your own repo.
>
> For Flex 4, Adobe is providing 12+ languages (I assume for dataviz
> too) and they should come in the free SDK, so Flexmojos can put them
> in their repo. BabelFlex was an effort to backport the Flex 4
> localizations back to Flex 3, but no one is taking the time to do it
> correctly. It would be great to have an open source effort to provide
> the SDK translations for the other languages. No one has volunteered
> to lead that effort yet. I was hoping to do it, but I'm swamped for
> another couple months at least.
>
> Logan

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en

http://flexmojos.sonatype.org/

Reply via email to