Thread: non-unicode app reading unicode texts

Hi all,

i'm working on a simple script compiler that reads sort of *.ini files.
The app is compiled on a win98 with non-unicode options.

Is there a clean way how to recognize that someone has written a *.ini file on a Win2000/NT/XP ?

I though of simply test the 1st 16bit if the upper byte is 0x00.

How would you do it ?
Is there a more generalized way ?

-
Robert

Hi Fordy,
but when editing something on Win2000/NT/XP aren't the files saved as UNICODE text files.
Depends the format of the text on the filename suffix ??

I don't have a Win2000 at home.

-
Robert

Files are only written in UNICODE if you specify that when you save it. Default is normal ASCII.

Although, if you use Unicode characters, it will warn you to save it as Unicode if you don't.

In Win2K, it's perfectly legal for .INI files to be either in ANSI or Unicode. Or even in a non-ANSI code page.

Thanks a lot guys.
It helped me much.

Regards,
Robert