On 10/25/14, 2:10 AM, "Maxim Solodovnik" <solomax...@gmail.com> wrote:

>I was not able to run 3.2.0 (due some certificate issues)
>Russian translation was available in 3.1.0 but not all screens are
>translated (I have translated all ~200 strings) for ex. "select
>component/licence" screen contains all license descriptions and component
>names in english
>Additionally log entries are in english (was also translated)
Ah yes, I forgot, strings are in 3 places.

The en_US.properties you translated to ru_RU.properties are the strings
displayed by the Installer, but for new SDK releases, the Installer
displays license choices from the file
apache-flex-sdk-installer-config.xml.  Link to it in the repo is here [1].

Then, once the licenses are accepted, the Installer basically runs the
installer.xml in the release package, which is an Apache Ant script.  Some
strings in the script are localizable, the en_US version is here [2].

Testing new localizations for these files requires that e commit them to
the repo and then you can try them in a nightly build.

And it is certainly possible that something is still not localizable.

Oh and if you’re feeling really energetic, the FlexJS and FalconJX install
scripts have their own pair of these files.

Thanks,
-Alex

[1] 
https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=blob
_plain;f=apache-flex-sdk-installer-config.xml;hb=develop

[2] 
https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-sdk.git;a=blob
_plain;f=installer.properties/en_US.properties;hb=develop

Reply via email to