Robert Savage

The content proposed an excellent solution. With a wrapper class.

How to handle a string which need unicode treatment in Flex,
At present in Flex SDK there is no API where I can specify the local and string to display it in UI, we need to call resource manager to handle it.

My problem:

Flex Compiler verson : flex_sdk_3.3.0.4852_mpl

In Flex Application I am receiving Unicode result from back end ( web service) an displaying it in Flex Label component

Storing event.result in to a string Eg. Response string = [\u8868\u7af9\uff5eFulfillment~~~~ja]

I am binding response to label component When I am displaying it in label its not showing me Japanese character .

Note : Storing this information in properties file works
Eg.
Result.properties
Res=[\u8868\u7af9\uff5eFulfillment~~~~ja]

In side flex component

1. define a metadata tag for Result.properties file
2. call it in Label component as resourceManager.getString(‘Result’,,’Res’)

This show the japaness data in UI
Result ==[\u8868\u7af9\uff5eFulfillment~~~~ja]
Need API to support for unicode string ; eg : resourceManager.getString(Result,”ja”);
Presently there is no api to display unicode string in UI

Actual Results:
[\u8868\u7af9\uff5eFulfillment~~~~ja]

Expected Results:
[表竹～Fulfillment~~~~ja]

Please let me know how to over come this problem

Hi Robert,

A nice solution, I’ve found however that any bindable properties propogated through a repeater seem to return null to the label and button classes. e.g.

It’s been quite frustrating as to why, a nod in the right direction would be appreciated.

Also what attribution are you happy with, is your name in the header of the classes sufficient?

Cheers

Nice writeup!

I thinks the standard way to localize an application using “mxmlc” to create the bundles is not a good solution for many usage scenarios. With that model, the product has to be shipped with swf’s embedded with resource bundles or swf’s that load compiled resource “modules”. Both of which require a mxmlc compilation step…

What is you want to do things without going through the compilation step? That can be done by dynamically creating a Resource Bundle and adding resources using action script code shown below

var moreResources:ResourceBundle = new ResourceBundle(“fr_FR”, “moreResources”);
moreResources.content["OPEN"] = “Ouvrez”;
moreResources.content["CLOSE"] = “Fermez”;
resourceManager.addResourceBundle(moreResources);
resourceManager.localeChain = [ "fr_FR" ];
myLabel.text = resourceManager.getString(“moreResources”, “OPEN”);

That solves part of the problem but in my case the perfect solution would be as follows
1. Use your technique to create custom components, trap appropriate events, handle label assignments etc
2. Create Resource bundles for certain parts of the application and embed it in the swf.
3. Create Resource bundles dynamically (using code snippet shown above) and
4. Hydrate the dynamic resource bundles by reading data from a “properties” file using a URLLoader. This data can be changed on the fly without recompiling the application.

Essentially there is a static resource bundle and a dynamic resource bundle. The dynamic one can be changed by “field engineers” and applied to the application with a re-compile. Additional logic is required in the component to figure out whether to either give precedence to data in the static or dynamic bundle.

The dynamic one can be changed by “field engineers” and applied to the application with a re-compile.
SHOULD READ
The dynamic one can be changed by “field engineers” and applied to the application WITHOUT a re-compile.

I found that addEventListener(Event.ADDED,resources_LocalizationHandler); is terribly inefficient. Breakpointing this handler I saw it getting hit 5-7 times. So instead I added the initial seed of .text/.toolTip value to commitProperties

So my setters are:

public function set resourceBundle(value:String):void
{
// set new resource bundle
if (_resourceBundle != value)
{
_resourceBundle = value;
_resourceBundleChanged = true;
invalidateProperties();
}
}

And

override protected function commitProperties():void
{
super.commitProperties();

if(_resourceNameChanged && resourceBundle)
{
resourcesLocalizationHandler();
}
}