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

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 761063 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 9/4/2012 2:58:03 AM
Access Restriction Public


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


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...
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.

David Schwartz
SQL Server documentation