[JBoss JIRA] Created: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
2:27 a.m.
Externalise English strings (move them from source code into .properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files, and
replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
2:31 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-3557:
--------------------------------------
These svn changesets belong to this issue:
http://fisheye.jboss.org/changelog/JBossTools/trunk?cs=13030
http://fisheye.jboss.org/changelog/JBossTools/trunk?cs=13031
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
12:25 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3557:
--------------------------------------------
looks good - first I couldn't understand why the MessagesUI.getString("bla
blah") was used over NLS.bind(MessagesUI.BLA_BLAH) but I now understand you just used
whatever "standard" was already in use in that plugin - much appreciated.
I guess we should do a round after GA about getting all these cleaned up to use the
Eclipsy-way to get the best automated tooling support from both worlds.
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
12:46 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-3557:
--------------------------------------
I think the Externalize Strings wizard defaults to the getString way (even for new
ResourceBundles) which doesn't help! But just to be sure, I just checked my patch
again, and all the getString()s are for existing bundles. I can tell because I named all
the new bundles Messages, not UIMessages/HibernateConsoleMessages/etc.
Refactoring the Messages classes sounds like a good idea. I don't suppose there is a
refactoring which converts from getString to the Eclipse mechanism? I can't find it.
It would require renaming some of the property keys, eg to eliminate full stops (dot
characters).
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
11:04 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3557:
---------------------------------------
Fix Version/s: 3.0.0.GA
3.1.0
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.0.0.GA, 3.1.0
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
2:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-3557:
--------------------------------------
http://wiki.eclipse.org/Message_Bundle_Conversion_Tool should help with the cleanup (from
getString to Eclipse mechanism)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.0.0.GA, 3.1.0
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
1:56 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen resolved JBIDE-3557.
----------------------------------------
Fix Version/s: (was: 3.1.0)
Resolution: Done
assumed done - at least enough for GA ?
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.0.0.GA
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
12:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-3557:
--------------------------------------
I wouldn't say done, but we did decide to postpone until after GA. Perhaps we should
put the fix version as 3.0.1?
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.0.0.GA
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
12:54 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Sean Flanigan updated JBIDE-3557:
---------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0.GA)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.0
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
12:56 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Sean Flanigan reopened JBIDE-3557:
----------------------------------
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.0
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
9:13 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3557:
---------------------------------------
Fix Version/s: 3.1.0.M3
(was: 3.1.0.M2)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.0.M3
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
12:26 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-3557:
---------------------------------
Fix Version/s: 3.1.0.M4
(was: 3.1.0.M3)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.0.M4
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
7:41 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-3557:
---------------------------------
Fix Version/s: 3.1.0.CR1
(was: 3.1.0.M4)
bulk move from M4 to CR1
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.0.CR1
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
6:31 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3557:
---------------------------------------
Fix Version/s: 3.1.0.GA
(was: 3.1.0.CR1)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.0.GA
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
6:55 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3557:
---------------------------------------
Fix Version/s: 3.1.1
3.2.next
(was: 3.1.0.CR2)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.1.1, 3.2.next
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
11:45 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://jira.jboss.org/jira/browse/JBIDE-3557?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3557:
---------------------------------------
Fix Version/s: (was: 3.1.1)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://jira.jboss.org/jira/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Fix For: 3.2.next
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
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
5:54 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3557) Externalise English strings (move them from source code into .properties)
[
https://issues.jboss.org/browse/JBIDE-3557?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick updated JBIDE-3557:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 3.3.x
(was: 3.2.x)
Externalise English strings (move them from source code into
.properties)
-------------------------------------------------------------------------
Key: JBIDE-3557
URL: https://issues.jboss.org/browse/JBIDE-3557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Reporter: Sean Flanigan
Assignee: Sean Flanigan
Labels: i18n
Fix For: 3.3.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Much of the English text in JBoss Tools is already externalised into .properties files,
but my pseudolocalisation testing [1] shows that there is still some hard-coded English
text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java
source.
Any such English text needs to be moved out of the source code into .properties files,
and replaced by ResourceBundle lookups.
- In the case of plugin.xml or Java source, Eclipse's "Externalize Strings"
wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance
org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating
another one for each package in the bundle. (More bundles create more work for
translators.)
- In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so
externalisation has to be done by hand.
[1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools
langpacks. http://www.jboss.org/community/docs/DOC-13256
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4707
days inactive
5645
days old
jbosstools-issues@lists.jboss.org
16 comments
4 participants
participants (4)
-
Brian Fitzpatrick (JIRA) -
Denis Golovin (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Sean Flanigan (JIRA)