WIN98不支持UNICODE~~~ Differences Between Windows NT and Windows 98 The implementation of international support in Windows 98 and Windows 2000 differs. Both operating systems support the NLSAPI and the MLAPI, both handle input locale switching and multilingual fonts, and both will be released in multiple language versions (Windows 98 will ship in a few more languages than Windows 2000). However, key architectural differences mean that Windows 98 will not support multilingual applications to the same degree that Windows NT does.Since Windows 98 has evolved from the Windows 3.x code base, it does not contain native Unicode support, but instead uses ANSI character encodings. The lack of native Unicode support makes sharing data between machines running different character encodings more difficult. It is still possible to write a Unicode-based application that runs on Windows 98 (Word 97, for example), but with the exception of a small subset of wide-character APIs that Windows 98 supports, Unicode data must be translated before it is sent to system calls. One of the wide-character APIs, TextOutW, allows applications to display Unicode-encoded data. This is the API that Internet Explorer uses, for example, to display Japanese text on an English system. Windows 98 and Windows NT share a common resource file format. It is therefore possible to create applications that can run on Windows 98 and change UI language. However, Windows 98 does not support multilingual user profiles or thread locales, so some mechanisms for automating the change of an application's UI language do not exist. In addition, Windows 98 does not support the ability to change the UI of the system itself.Unlike Windows NT, localized editions of Windows 98 do not share a single binary. Asian and Middle Eastern editions are still supersets of the European editions of the system. Input Method Editor support is limited to Asian editions of Windows 98.
98对unicode本身是不支持
Differences Between Windows NT and Windows 98
The implementation of international support in Windows 98 and Windows 2000 differs. Both operating systems support the NLSAPI and the MLAPI, both handle input locale switching and multilingual fonts, and both will be released in multiple language versions (Windows 98 will ship in a few more languages than Windows 2000). However, key architectural differences mean that Windows 98 will not support multilingual applications to the same degree that Windows NT does.Since Windows 98 has evolved from the Windows 3.x code base, it does not contain native Unicode support, but instead uses ANSI character encodings. The lack of native Unicode support makes sharing data between machines running different character encodings more difficult. It is still possible to write a Unicode-based application that runs on Windows 98 (Word 97, for example), but with the exception of a small subset of wide-character APIs that Windows 98 supports, Unicode data must be translated before it is sent to system calls. One of the wide-character APIs, TextOutW, allows applications to display Unicode-encoded data. This is the API that Internet Explorer uses, for example, to display Japanese text on an English system. Windows 98 and Windows NT share a common resource file format. It is therefore possible to create applications that can run on Windows 98 and change UI language. However, Windows 98 does not support multilingual user profiles or thread locales, so some mechanisms for automating the change of an application's UI language do not exist. In addition, Windows 98 does not support the ability to change the UI of the system itself.Unlike Windows NT, localized editions of Windows 98 do not share a single binary. Asian and Middle Eastern editions are still supersets of the European editions of the system. Input Method Editor support is limited to Asian editions of Windows 98.