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