Agreeded that it would be nice, but to implement NLS (National Language Supprt) within an application such as this is would be a tremendous undertaking coding-wise, nevermind the cost.
Maybe HiTech has already done this, but every literal that has been hardcoded would have to be externalized and tagged. The text in the file(s) that contain the tags would then have to be translated for every country that he decides to support.
Starting 2 years ago, we went global with the product that I work on, and we still struggle with it for every new country we implement, so I speak from experience. GUI interfaces that have been originally designed in English, will have problems with the GUI "real estate" when trying to display in different languages.
Example: English to German (translation from a Translation Lab)
Card credits - non-reimbursable
Gutschriften mit Kartenzahlung - nicht erstattungsfähig
As you can see, the difference in the amount of texstual space for some translations is significant.
What we did, rather than re-design all our panels (huge cost), was to realize in the code when an overrun would appear and then display the above translation to something like this :
Gutschriften mit Kartenzahlung ...
The '...' idicates that there is more text and when you hover the mouse cursor over the line of text, a fly-over will display the complete line.
