Internationalization

[Dumas]

Hello!

The new model of Sencha Designer seems to be that you don't export once and then code, but continuously build your app in Designer.

So how should I handle internationalization of text in Ext Designer?

Is there maybe some way to apply non-strings to string configs? I would like to apply text configs like:

title: Localize.t('Hello %s!','Roland')

thanks
Roland

[aconran]

Localization support is something that we intend to tackle post GA.

[Dumas]

What's GA?

Will you provide a whole set a features for locaizing or how will it look like? What's the best I can do now to make it later easy for me to localize?

thanks
Roland

[Dumas]

Any more news.. we are starting a big project in two weeks and I would like to know how to handle it...

[ssamayoa]

Any more news.. we are starting a big project in two weeks and I would like to know how to handle it...

Me too...

[intellix]

This is also something I'm going to need for my large project so I guess if I can 1up this feature. It was heavily requested at SenchaDevCon as well

[aconran]

This is also something I'm going to need for my large project so I guess if I can 1up this feature. It was heavily requested at SenchaDevCon as well

Noted.

[hotdp]

Any news on this feature?

[afro]

I'm interested too, as currently, half of my JS code is getting localized strings from server and "setText" lines
And the slowest part is to find which property to use (text, fieldLabel, boxLabel,... )

[aconran]

Architect 2.2 introduces the ability to "process" configurations. This allows you to run arbitrary JS to set particular configurations. This will certainly aide in internationalization although we have yet to put any formal mechanism in place yet for this purpose.