Home Dashboard Directory Help
Search

ODBC / SQL Native Client doc: UNICODE description is out of date by FLAESCH Sebastien


Status: 

Closed
 as Fixed Help for as Fixed


9
4
Sign in
to vote
Type: Suggestion
ID: 761063
Opened: 9/4/2012 2:58:03 AM
Access Restriction: Public
1
Workaround(s)
view

Description

I believe the ODBC manual section about "UNICODE" support needs some review:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms709439%28v=vs.85%29.aspx

The first sentence is wrong: UNICODE is described as a two-byte encoding (i.e. UCS-2), which is false. UNICODE refers to a mapping between characters and integers, it's not a specific encoding of integers, as a sequence of bytes in memory...

I am not sure that in the ODBC world (including other platforms as Microsoft Windows), Wide-Char API functions expect only the UCS-2 character set... So far I could not find any clear documentation about that, and reading this section did not help much.

What encoding should I use when writing a "UNICODE" ODBC application, that is supposed to be portable over different platforms, like Windows and UNIX? Can it be UTF-16 today?

To me this section needs some clarification, even in the Microsoft-only world...
Details
Sign in to post a comment.
Posted by Microsoft on 11/6/2012 at 2:25 PM
I reviewed this with members of the feature team. We made some changes to the content. You can see the updates on MSDN now.

Feel free to send me an email if you want to iterate on this.

Thanks,
David Schwartz
SQL Server documentation
dschwart@microsoft.com
Sign in to post a workaround.
Posted by Malik Qadeer 11 on 12/12/2012 at 5:03 AM
hello