On 22 Nov 2010, at 18:55, Asmus Freytag wrote:
> That seems to be true for IPA as well - because already, if you use the font
> binding for IPA, your a's and g's will not come out right, which means you
> don't even have to worry about betas and chis.
Not so. There is already a convention (goi
On 11/23/2010 1:58 AM, sowmya satyanarayana wrote:
This what I am actually looking for. My ODBC application supports
UTF-16, which is 2 byte width characters. This application is
completely oriented around using _T(x) macro as Asmus Freytag figured out.
Yeah, it's nice when you can do witho
>>> Asmus Freytag wrote
> TCHAR x = _T('x');
> TCHAR * x = _T("x");
>
> that is to wrap a string or character literal so that it can be used either
> as
>Unicode literal or as non-Unicode literal, depending on whether some global
>compile time flat (usually UNICODE or _UNICODE) is set or
>
> n
3 matches
Mail list logo