Configuring Project for Flex I18n

Egor Malyshev

Meet another fresh demo about IntelliJ IDEA Flex support. This time we’re showing how to quickly setup and configure a project for using Flex I18n. In this example we’re creating a multilingual Flex application with the use of advanced features like run-time locale switching.

You can watch this demo right now or download it for offline viewing as a zip archive.

Comments below can no longer be edited.

6 Responses to Configuring Project for Flex I18n

  1. Simon Tiffert says:

    June 8, 2009

    If working with Flex and Maven (Flex Mojo plugin), just re-import your project after adding languages.
    Don’t spend time in trying to configure it for yourself.

  2. dongyang says:

    April 25, 2013

    How to setup in version 12.1?

  3. Alexander Doroshko says:

    April 26, 2013

    Flex/ActionScript project structure is significantly changed since that time [1]. But the main idea of this tutorial is still the same. Configure source roots for the Flash module, set locales at Compiler Options tab of the Flash build configuration (Project Structure dialog) and enjoy.
    [1] http://blogs.jetbrains.com/idea/2012/02/new-flex-project-setup/

    • Colin Kershaw says:

      August 29, 2013

      The important point for me from this video was that the actual resource folder needs to be marked as Sources, not its parent folder. For example, “en_US” is flagged as Sources, not “locale” for the folder structure:

      locale
      \–en_US (contains .properties files)

      This may save someone else a bit of time watching the entire video.

  4. Jake says:

    May 23, 2014

    One issue I am having is that I cannot prioritize which language is put at the front of of the list. For example I have an app that is compiled for english and german. If someone from Brazil tries to use my app I’d like to have them get english by default but as it sits now they will get German. Is there any way to have english be the first in the list of localization priorities?

    • Jake says:

      May 23, 2014

      I found a workaround.. which feels like a bit of a hack. So in the “compiler options” tab there is a field called “additional compiler options” which you can use to specify locale order. In the “Locales” option just set it to “en_US” but then in the “additional compiler options” field put in the following with the order of the languages you want:
      “-locale=en_US,de_DE”

      That will prioritize english over german in the language order. I hope we have a way to order localization prioritization in a future build.

Subscribe

Subscribe for updates