[unixODBC-dev] Unicode support
Uma.SHANKAR at 3ds.com
Tue Aug 18 20:28:03 BST 2009
Is there some clear documentation what this build time option is? I would like to read up before deciding whether to make code changes by using iconv() or use this build option. I am also a bit unclear on the Unicode driver part.
We are towards the end of our development cycle, and this is holding things up. Given that we have had several exchanges since y;day, here are what I seem to have as options:
1) Use iconv() for linux to convert to UCS-2
2) Use SQLWCHAR
3) Use the build time option.
Given the above 3 options, it seems to me that the build time option would be the easiest given where we are now. If it is, then could you explain the Unicode driver comment that you made? Like I said we are building the unixODBC drivers ourselves, so we do have control over how we build it.
From: unixodbc-dev-bounces at mailman.unixodbc.org [mailto:unixodbc-dev-bounces at mailman.unixodbc.org] On Behalf Of Nick Gorham
Sent: Tuesday, August 18, 2009 3:11 PM
To: Development issues and topics for unixODBC
Subject: Re: [unixODBC-dev] Unicode support
SHANKAR Uma wrote:
> Another question Nick. I was up on the unixodbc website, and for the 2.0.9 release , it says the following was fixed:
> - Add build time option to select wchar_t UNICODE (4 bytes) as opposed to signed short UNICODE (2 byte)
> I believe we build unixODBC ourselves. Does this mean that I could actually build unixODBC on unix boxes for the different sizes of wchar_t on unix v/s windows? And this would require no code changes on my part? And I could use wchar_t's the way it is being used now?
> Please clarify.
Yes, but if you wanted to connect to unicode ODBC driver they would also
need to use 4 byte UNICODE. Can be done, but beware the driver.
unixODBC-dev mailing list
unixODBC-dev at mailman.unixodbc.org
More information about the unixODBC-dev