Ove Kaaven <[EMAIL PROTECTED]> writes:
> Well, the SBCS codepage NLS files, yes. The other files (toupper/tolower
> in l_intl.nls, which I did figure out recently by looking at YAW sources,
> the locale files, and especially the sorting tables, which is still a
> mystery to me) are not quite as simple.
I think we are better off doing our own format. This way we can keep
it simple, and avoid trouble when Microsoft changes the format between
releases.
> Loading them is obviously best done with mmap()-ing (known as
> MapViewOfFile in the win32 API) to save memory. Perhaps it could search
> for these files in places like
> -the system dir
> -nls/*.nls from the program dir (if the user didn't make install)
> -$libdir/wine/*.nls or $libdir/wine/nls/*.nls or whatever
> ($libdir == $prefix/lib, $prefix == /usr/local or /usr)
We probably shouldn't call them .nls to avoid conflicts with Windows
files (unless we want to support loading Windows files too, but this
doesn't seem really necessary).
--
Alexandre Julliard
[EMAIL PROTECTED]
