internationalization support?

[ihhur]

I'm not using "externalize string" feature of eclipse because it has some problem making properties file(code conversion problem -> it is unreadable!!)

instead, I'm using a string resource file like following;

public final class Resources extends BaseResources {

// resource strings
private static final Object[][] contents = addResources(new String[][]{
{"property_getuserid_error", "localized message blah 1"},
{"property_getcontentsitem_error", "localized message 2"},


and I access the resource like;
BaseResources.getResourceString(RepositoryNode.class, "property_getuserid_error");


I'd like to know if swt-designer will support this way of internalization. If it can be done in 2 months, I would be more than happy. If not, I may be in a big trouble designing dialogs blind.

[Eric Clayberg]

I'd like to know if swt-designer will support this way of internalization. If it can be done in 2 months, I would be more than happy. If not, I may be in a big trouble designing dialogs blind.

We will certainly consider it. We do plan to enhance our internationalization support in the near future, so supporting different patterns (like yours) is quite possible.

[ihhur]

I really appreciate it!