On Sat, 20 Jul 2002 10:37:34 +0200, [EMAIL PROTECTED] wrote:

>> >>2All: NLS support too stupid. I'm planning to migrate to native msg
>> >>files instead if resources. Any comments?
>> >don't know, what's the problem with NLS?
>> Well. All messages placed in resources (as for class libs, as for
>> ide). So, if I want change language then I must recompile code or
>> reload resources. I prefer make this thing:
>> 
>> 1) All english messages must be placed in sources (or in resources)
>> 2) All foreign messages must be placed in msg files.
>> 3) Program must automatically detect locale and output messages in native language.
> My suggestions:
> 1) All messages (including the English ones) should be stored 
>identically (so you can distribute just, say, Russian version if 
>nothing else is needed).
Then we can use classic messages files without any magic. We can bind any required 
message file (as english as any onther). Or can distribute as external file(s).

> 2) I propose to use resourcestrings stored in DLLs (dynamically 
>loaded, of course).
And now required at least resource compiler and linker.

> 3) You should make it possible to use some language without changing 
>system configuration (i.e. at least make it possible to get the 
>language from environment variable like LANG, since this one can be 
>changed locally). However, it would be probably better to declare 
>some variable that would become initialized from LANG, or whatever, 
>but a program could change it "on-the-fly" using some dialog window, 
>or whatever, if needed and the programmer wants to take care about 
>this.
Of couse. Such things must be implemented.

>> Disadvantages:
>> 1) msg compiler required to make locales
> Not really good, IMHO.
But for your approach required linker and resource compiler.

>> 2) external msg files required
> The same is true for resourcestrings stored in DLLs, of course, but 
>I don't see any real problem with this.
I'm too.

But really I prefer gnu gettext method, but I don't want use intl(libintl, gnuintl) 
lib. I prefer to have english (international) messages stored into executable and, as 
optional, 
external message files. Native msg files allows to use as external as binded message 
files (refer to os2tk).


-----------
To unsubscribe yourself from this list, send the following message
to [EMAIL PROTECTED]

     unsubscribe sibyl
     end

Reply via email to