_UNICODE affects the C runtime libraries that get compiled and linked in.
UNICODE affects the Win32 API calls in your code. During compile time,
these manifests cause the wide character (Unicode) versions of the APIs to
be used.
You don't need to use either to get Japanese support. However, you may want
to use the _MBCS manifest instead. This will cause your compile and links
to use "multi-byte enabled" libraries for so-called ANSI applications.
If you use UNICODE in your application, you have made the choice to not run
on Windows 95/98 since those platforms do not support most of the Unicode
versions of the Win32 API.
Regards,
John O'Conner
Venkatesh Murthy N G <vmurthy@teil.soft.net> on 01/26/99 10:54:56 PM
To: Unicode List <unicode@unicode.org>
cc: (bcc: John O'Conner/QAD1)
Subject: _UNICODE
Hi,
what is the difference between #define UNICODE and #define _UNICODE.
To support application to be run with Japanese language support do we
need to include both ?
I need reply soon because some of the API's are giving error if I include
this line i.e. #define UNICODE
venky
---------------------------------------
N G Venkatesha Murthy
Specialist-D&D(Design and Development)
---------------------------------------
TATA Elxsi India Limited
Whitefield Road,Mahadevapura Post
Hoody,Bangalore-560 066.
Tel : 91-080-845 2016/2017/2185,8410148/8410148.
Fax : 91-080-8452019
E-mail : vmurthy@teil.soft.net
---------------------------------------
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:44 EDT