The Global workbench is a bit dated. And in Europe internationalization is a real important issue. Lots of mergers over language borders and even inside companies its quite usual that some folks doesn't speak the language of the country they are working very good.
Ulrich Krause has a propal, which I will link. Mine is more radical.
What about a new design element called "Internationalization table"?
A simple table with a key as first column and one column for each language.
New @functions, Lotus-Script functions and java-methods needed to call the new Designelment.
So in column headers, labels, error-messages, etc. the proper key can be easily accessed and the proper entry for the language returned.
This table would be easily exportable as xml (or optionally csv for those folks who do not like xml). A client for editing this table outside Notes is a snap, so that even traduction experts without Notes client can easily work the stuff.
Internationalization is used in a lot of places spread around the code (some jergon aficionados might call it cross functional concern, but thats not the point here). The functionality is actually simple. So Lotus could create a design element with opportunities for performance enhancements deep in the system. Developers would use a simple, streamlined approach and not everyone had to invent his own code to support internationalization.