3 Apr 2012 6:54 AM #1
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')
3 Apr 2012 7:09 AM #2
Localization support is something that we intend to tackle post GA.Aaron Conran
3 Apr 2012 12:46 PM #3
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?
22 Apr 2012 7:52 AM #4
Any more news.. we are starting a big project in two weeks and I would like to know how to handle it...
3 May 2012 8:21 AM #5
- Join Date
- May 2010
- Guatemala, Central America
- Vote Rating
6 May 2012 11:22 PM #6
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
7 May 2012 6:08 AM #7
6 Feb 2013 4:04 AM #8
Any news on this feature?
6 Feb 2013 4:51 AM #9
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,... )
6 Feb 2013 11:12 AM #10
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.Aaron Conran