ihhur wrote:I've read on this forum as following;
Yes, Designer will support internationalization, but we don't know yet how. Here are some ideas:
1. It will not support complex expressions like you show, i.e. only single expression will be supported;
2. Most probably it will support "Externalize string" feature of Eclipse, i.e. will look for something like Messages.getString("Test.0"), parse class Messages and then read real strings from property file.
This is very enough for me, and I'm wondering when I will be able to use it!
Support for externalized strings. If you used "Externalize strings"
action in Eclipse, Designer will parse access to method "getString",
parse class with messages for property file name and read needed
strings from property file.
ihhur wrote:I tried to use Eclispe "externalize string" feature but it changed local strings(korean) into unicode which is not recognizable by developers.
ihhur wrote:Would you please explain how can I accomplish this?
as the button text, instead of the replacement string.Messages.getString("foo.1")
pcarmichael wrote:When I tried to view it in Designer it showed a button withas the button text, instead of the replacement string.Messages.getString("foo.1")
Users browsing this forum: No registered users and 1 guest