--- Bill Dargel <[EMAIL PROTECTED]> wrote:
> At 11:00 08/20/2001 -0300, Alejandro F. Reimondo
> The idea of using #translated inspired me. How about
> using
> 'That is not a valid value for logging'
> translated
> instead? Using the actual English message as a
What if you have a spelling error in the key. You
have to change ALL specific catalog files for every
language involved for a single spelling error? Worse,
you have to repackage the app. In the case of an
external text file, only the English catalog file
would be fixed and it would involve NO change in the
CODE.
> *) Reading both the code and the translation files
> would make a lot more
> sense, compared to just seeing keywords like
> "Kom0002". *) It would be an
Just do like VisualAge. Put the original english
string in comment just besides the catalog key. e.g.
prompter title:
(messageOrNil isNil
ifTrue: [MxEMTsES13] "$NLS$ Enter a file name."
ifFalse: [messageOrNil]).
Really, using a string and translate it has one big
disadvantage : if you have a spelling (or whatever )
error in the text, you have to touch the code. In the
case of an external text file that refers to a key, no
source code change is required. Nice, clean, soft and simple.
=====
Benoit St-Jean
[EMAIL PROTECTED]
http://cactus.swiki.net
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
