Jspresso Translation 2.5.2
Markets
- Tools (1409)
- Application Development Frameworks (86)
- Application Management (65)
- Application Server (75)
- BIRT (23)
- Build and Deploy (131)
- Business Intelligence, Reporting and Charting (16)
- Code Management (134)
- Collaboration (32)
- Database (65)
- Database Development (30)
- Database Persistence (36)
- Documentation (65)
- EclipseRT Target Platform Components (9)
- Editor (269)
- Entertainment (23)
- General Purpose Tools (63)
- Graphics (46)
- IDE (313)
- J2EE Development Platform (90)
- J2ME (18)
- Languages (146)
- Linux Tools (8)
- Logging (17)
- Mobile and Device Development (43)
- Modeling (64)
- Modeling Tools (175)
- Mylyn Connectors (31)
- Network (26)
- Other (87)
- Process (36)
- Profiling (25)
- Programming Languages (49)
- Reporting (41)
- Rich Client Applications (72)
- SCM (27)
- Search (40)
- SOA Development (14)
- Source Code Analyzer (94)
- Systems Development (73)
- Team Development (81)
- Testing (110)
- Tools (570)
- UI (118)
- UML (75)
- Web (116)
- Web Services (59)
- Web, XML, Java EE and OSGi Enterprise Development (45)
- XML (54)
- RCP Applications (159)
- Training & Consulting (109)




Reviews
Nice idea, but too simple
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).
Multiple file location
Hello
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_
Regards,
Maxime