On Wed, 15 Mar 2000, Dmitry Timoshkov wrote:
> Ove Kaaven <[EMAIL PROTECTED]> wrote:
> >RtlInitCodePageTable may depend on the file format, but it just fills in
> >the RTL_NLS_DATA structure, doesn't it? The RTL_NLS_DATA structure is
> >*not* the NLS file format, and who says that you can't make a RTL_NLS_DATA
> >structure directly, instead of going through RtlInitCodePageTable?
>
> Yes, filling RTL_NLS_DATA structure is absolutely no problem. The problem is
> again to introduce Wine-own-internal interface. There are already plenty of
> them. I think that using not exported, own, internal functions from external
> modules such as x11drv is a bad idea. Is it?
Can't data for X11 encodings just be internal to x11drv?
> Even if we would agreed with above thing, I have another question to you.
>
> As I already wrote I have problems in understanding DBCS NT's NLS files.
> The thing I worry about has nothing with NT's file format though.
>
> NT's NLS:s have 32K characters in OEM to Unicode table instead of 64K as
> I expected. What do you think about that?
I don't understand what you mean. OEM characters to Unicode would be 256
characters, wouldn't it? And Unicode to SBCS codepage would be 65536 bytes
(or 32768 words, as offsets and sizes are almost always expressed as words
in NLS files).
