[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-2969) i18n support in xmodel
i18n support in xmodel
----------------------
Key: JBIDE-2969
URL: https://jira.jboss.org/jira/browse/JBIDE-2969
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Reporter: Sean Flanigan
Snjezana Peco wrote in
<http://lists.jboss.org/pipermail/jbosstools-dev/2008-August/001811.html>;:
I believe that xmodel will make a problem during the
internationalization process because it contains hard-coded constants. I
am not sure if there is any way to internationalize those constants (the
org.jboss.tools.common.model/meta/studio_eclipse_option.meta file
contains the Visual/Source, Source, Preview constants, for instance. I
can't find a way to localize them).
That's
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbosstools/trunk/common/plugin...
I suggested merging a template with translated strings during the build process, but then
Denis Golivin wrote:
IMO That can be fixed. Now names from .meta files are used during
rendering trees, names from .meta files come straight to tree node
label. They cannot be just translated because somewhere in the code name
can be used to obtain object from model. That names are rather keys or
IDs, that should be rendered right with i18n support.
I CCed Viacheslav Kabanovich, he is the right guy to find the way to fix
i18n problem in XModel.
That file still appears to contain embedded English strings, so I don't think this
problem has been solved yet. I don't fully understand the details of the issue, but
since I'm raising i18n jiras, I thought I'd better bring it up again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira