NLS should work by SAS formats: English texts are written directly into the programs, a macro looks up the foreign language translation and returns the translated text, if any is being found.
Anonymous
Quote: "English texts are written directly into the programs"
Wouldnt it be better to use language-independent messageIDs in the programs, in combination with the SAS formats?
Or did I get something wrong?
Our colleague AB has developed a messaging framework in this manner, which could be integrated for this purpose.
This approach is most easy to implement and use. A translator function (macro) gets the English text and searches for a translation, if necessary. If none is found, the english text is being returned. The English text is being used as an id. It is not necessary to invent and lookup ids. The programs with their full text messages easy to read.
This request is moved to a later release.
It needs to be checked if there is currently an English word, that has to different transalations. If this is the case we need to invent abbreviations.