关于Unicode 和 MBCS的一个简单问题

[boge]

要编制国际化的软件，用Unicode 和 MBCS的方法都可以达到。
MSDN也说了如何用。但是，在选择两者之一时，有什么标准呢？
一般规范的程序，包括VC例子都提供了上述两种编译版本，那么，生成的执行程序
在应用范围上有什么区别呢？
是不是跟平台有关，如NT?

谢谢！

[softdoctor]

对不起，贴错地方了

[littletao]

对，nt使用了unicode编码，而98是dbcs+sbcs。

[boge]

也就是说，如果你的程序要在windows和NT两个平台都支持的话，必须有两个版本？
unicode 版本难道不能在windows运行吗？
或者说unicode 版本的性能不如MBCS?
在WIN2000，应该用何版本？

[Deling]

最好是使你的source完全可以移植。以下是几条建议
1.定义所有的string的时候用_TEXT 宏
2.字符型数据用TCHAR,字符指针用LPTSTR
3.所有的字符串函数都用_tcs...宏，而不用str...函数
例如，用_tcscpy代替strcpy，用_stprintf 代替 sprintf

[lgzmlh]

These are my report about using Unicode, I'd like to have it shared with you, do please point out directly what's wrong or correct, hope to help you and me. thanks



The Different Support of Using Unicode on Win95, WinNT Win98, and Win2000

1. Win 95:

Advantage:
· Limited Unicode functionality
· Application based on Unicode can run on Win 95 only after some programming work for Translation.
· When application based on Unicode can run on Win 95, it can run all kinds versions of Windows OS.

Disadvantage:
· Processing default character set only, none internal support of Unicode.
· Programming for translating string parameters to local character sets each time before calling API function.
· None support of crossing language character input.
· Compared with on Win98 and WinNT, much more programming work will be needed.

Solution 1: Based on Win32 API
· Win 32 API contains wide data type support to allow Unicode compliance, call TxteOutW, ExtextOutW, GetCharWithW, GetTextExtentW, GetTextExtentPointW for handling Unicode.
· Call WideCharToMultiByte and MultiByteToWideChar for translation.
· Programming for using Active IMM (Active Input Method Manger) for crossing-language character input.

Solution 2: Based on MFC
· Using provided built-in support for Unicode, define _UNICODE macros to convert generic text to Unicode data types.
· Programming for using Active IMM crossing language character input.


2. Win NT

Advantage:
· Internal support for Unicode as well as for ANSI.
· Support two flavors of the Win32 API--'W' or wide character entry points, for string parameters encoded in Unicode, and 'A' or ANSI entry points, for string parameters encoded in local character sets. That means it is possible to design the application based on Unicode running on Win 95 as well as on Win NT, and the application based on ANSI running on Win 95 as well as on Win NT.
· Compared with Win95, Win98, it is easier to make application based on Unicode.


Disadvantage:
· Not all of user’s OS are Win NT.

Solution 1: Based on Win32 API
· Call the A entry points, Windows NT will automatically convert the string parameters into Unicode before calling the W version of the same function.

Solution 2: Based on MFC
· Same as it is talked on Win 95

3. Win 98

Advantage:

· Wide-byte support.
· Windows 98 has added support for a few more functions and there are techniques to implement additional Unicode support

Disadvantage:
· Win98 are not internally Unicode based.
· No support of crossing language character input.
· More programming work compared with Win NT.

Solution 1: Based on Win32 API
· Win 32 API contains wide data type support to allow Unicode compliance, call TxteOutW, ExtextOutW, GetCharWithW, GetTextExtentW, GetTextExtentPointW for handling Unicode.
· Programming for using Active IMM (Active Input Method Manger) for crossing-language character input.

Solution 2: Based on MFC
· Same as it is talked on Win 95



4. Win2000

Totally support Unicode. When application based on Unicode can run on Win95, Win98, WinNT, it do run on Win2000.