GMF Internationalization [message #68198] |
Mon, 23 October 2006 16:00  |
Eclipse User |
|
|
|
Originally posted by: leonardo.coelho.siliconstrategy.com.br
At this moment, I´m internationalizing my RCP app based on GMF.
And I´m facing the following problem: there are a lot of hardcoded
strings marked by //$NON-NLS-1$
Some of these strings refers to errors and failures. Some of them are
related to interface.
Why is it hardcoded? And what is the best way to surpass this?
Well... I´ve chosen some important files and I´m refactoring them,
moving the references to a resource bundle.
I hope you can give me a better idea.
Regards,
--
=============================/============================== ====
Leonardo Coelho
=============================/============================== =====
|
|
|
Re: GMF Internationalization [message #70252 is a reply to message #68198] |
Thu, 26 October 2006 10:38  |
Eclipse User |
|
|
|
Leonardo,
Are you referring to strings in generated code or runtime code? Could
you give an example of a string that is causing you a problem?
Thanks,
Cherie
Leonardo Coelho wrote:
> At this moment, I´m internationalizing my RCP app based on GMF.
>
> And I´m facing the following problem: there are a lot of hardcoded
> strings marked by //$NON-NLS-1$
>
> Some of these strings refers to errors and failures. Some of them are
> related to interface.
>
> Why is it hardcoded? And what is the best way to surpass this?
>
> Well... I´ve chosen some important files and I´m refactoring them,
> moving the references to a resource bundle.
>
> I hope you can give me a better idea.
>
> Regards,
|
|
|
Powered by
FUDForum. Page generated in 0.02922 seconds