I18n Internationalization suggestion

[nathan_clark80]

It would be nice if there was feature were I could rightclick on a String (in the source code) and be able to choose to internationalize it. Then it would add all of the needed stuff in to the properties file and the Constants class, like it does in the designer for every String selected.
I think this would be an awesome feature for folks can cannot use the design view 100% of the time.

Cheers,

[mupf3l]

Yes, and keep the files synced too.

+1

[Eric Clayberg]

We do plan to add some 118n related refactoring and synchronization support in the future.

[paulsschwarz]

I actually visited the forum to ask how to achieve externalising strings that are in your java class but not necessarily used in the UI directly. For eg. think of the standard GWT example app. It contains two strings:
Click me!
and
Hello, GWT World!

It seems like using GWT Designer I can externalise the Click me! string because it belongs to a button. But the Hello, GWT World! string resides in the class code but doesn't show up in the designer view and is therefore not available when I click the externalise globe icon.

Of course I could manually externalise it by putting the entry into the .properties file and AppConstants.java but surely there's a way, or should be a way to do this using GWT Designer?

Is that what you guys are talking about? If so +1!

[Eric Clayberg]

We do plan to support extracting strings that aren't associated with a widget text property in the future.