[claudiobosticco]

I can confirm it's working in 8.1, thanks :-)

BTW, the freeze/unfreeze on a headerSpan it's not localized, maybe it's hard coded?

[smartgwt.dev]

not exactly! the DateRangeDialog remains not-localized!

This has been fixed. Try the latest nightly.

[Isomorphic]

All the translations are maintained at 99translations.com - see the sticky thread in the SmartGWT forums.

[pavel.tavoda@f4s.sk]

We are using latest night builds of SmartGWT and we have similar problem. Attached you can find two dialogs which we see. They are partially translated. Interesting is that for example buttons are in english and they are for sure translated. Or translation file is incomplete? Where can I fix that?

[claudiobosticco]

The issue you're seeing with the SmartClient showcase and locales had to do with the was it was loading the resource bundles using isc.FileLoader.

Actually I get better results loading the resource bundle with a static <script> tag (it'll be nice if <loadISC> tag could load it).
But the DateRangeDialog still doesn't pick up localized messages.

[claudiobosticco]

SC_SNAPSHOT-2011-06-12/PowerEdition

DateRangeDialog: localized messages are not picked up.

MultiSortDialog: multiSortDialog_levelUpPrompt and multiSortDialog_levelDownPrompt are not picked up.

the others messages are correctly picked up.

but there is another regression on this sample: context click on the grid editor does not open context menu.

[sjivan]

I tried it out using the Smart GWT Grid DateRange Filter showcase sample. The issue you're seeing with the SmartClient showcase and locales had to do with the was it was loading the resource bundles using isc.FileLoader. This has been corrected so please try it out using the next build.

Sanjiv

[claudiobosticco]

I tested it out using the fr_FR locale and it seems to be fine.

which version/sample did you try?

[claudiobosticco]

Then, if I switch to js tab, and then click "try it", then all the localization messages are picked up!

not exactly! the DateRangeDialog remains not-localized!

[claudiobosticco]

besides, also isc.DateRangeDialog.askForRange() gives me a non-localized Dialog.
But, if I add
isc.DateRangeDialog.addProperties({headerTitle: isc.i18nMessages.dateRangeDialog_headerTitle});
to the .properties file, then it picks up the correct header title (but not the DateRangeDialog created as the Dialog for the filter column on the grid).

[claudiobosticco]

I just "discovered" something strange...in the localization sample (snapshot 2011-06-09), if I change to french or other locale, at least those messages not picked up:

multiSortDialog_levelUpPrompt
multiSortDialog_levelDownPrompt
dateItem_pickerIconPrompt
dateItem_daySelectorPrompt
dateItem_monthSelectorPrompt
dateItem_yearSelectorPrompt
and the filter builder messages already displayed. But if I add another filter condition, the messages are picked up.

Then, if I switch to js tab, and then click "try it", then all the localization messages are picked up!

Why? There's something special I must know in loading the localization properties file? I load it after the modules and skin.

verified in "Localization" sample, snapshot 2011-06-09

[claudiobosticco]

snapshot 2011-06-09

see attached image, I have a French DateChooser with an English DateRangeDialog !

[sjivan]

I tested it out using the fr_FR locale and it seems to be fine.

[claudiobosticco]

I can see it in SC_SNAPSHOT-2011-06-07

[Isomorphic]

The website does not reflect the latest nightly builds. Please let us know if you're seeing this in the latest.