Jspresso Translation

Add this URL to your Eclipse Installation to reach this solution's update site.

Neon (4.6)
Mars (4.5)
Luna (4.4)
Kepler (4.3)
Juno (4.2, 3.8)
Previous to Juno (<=4.1)
Oxygen (4.7)
Photon (4.8)
2018-09 (4.9)

Learn more...

Details Group Tabs

Monday, October 22, 2018 - 10:16
mberger0ml's picture

Whenever I want to add a string to the resources bundle via "Right click > Jspresso > Translate...", it suggests as key the string i entered as value.

E.g. the key for string "a test string" is "a test string" with spaces in it. This is annoying, because you have to edit the keys afterwards again and remove all spaces.

lpertile158's picture

I tried on Eclipse Neon. Even if I set .properties file positions, pattern name and list of wished language, the plugin doesn't automatically create the real file. Until I manually created it, the plugin didn't give me translations panel.

gbelger's picture

This is a great idea, as it would allow to translate all strings directly on the fly and would avoid the usual messy properties file roundtrip, at least while coding.

Sadly, it works with one fixed message location, so it is not much use for projects consisting of more than one plugin/project. Would be nice if it would use the same mechanism that eclipse uses to show the i18n tooltip (i,e. automatically find the right message bundle).

mmisingnameu3o's picture


In fact it works for multiple property files locations !

You have to set up all locations in the project property page...
For example :
folderX/folderY/Messages_; folderZ/Labels_