Skip to Content.
Sympa Menu

freetds - RE: [freetds] UCS-2, UTF-16...does it work?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] UCS-2, UTF-16...does it work?
  • Date: Wed, 10 Dec 2003 17:05:59 -0500

> From: Rogers, Tom [mailto:tom.rogers AT ccur.com]
> Sent: December 10, 2003 1:20 PM
>
> FreeTDS is our trump card and we are hoping that
> NVARCHAR/UCS-2 will work
> for us, though I have read the FAQ and users guide and see
> that it probably won't.

Tom,

The status indicated in the UG and FAQ on www.freetds.org reflects the
current release, 0.61. A lot has changed since then. The UG bundled with
the snapshot should give you more optimism. :-)

We have unit tests for UTF-8 clients, and we definitely transport UCS-2
data. The question I'd have would regard any encoding for Japanese other
than UTF-8. What client encoding do you hope to use?

We received a patch from a Japanese speaker for 0.61. Some of his ideas got
applied to the current release. I'd be hopeful that our Japanese support --
if not 100% on Day One of 0.62 -- is near enough the mark that we can fix
anything you need. If you include us in your testing cycle, I think we'll
be able to iron out whatever wrinkles are left

If you require a two-byte client encoding (UTF-16, UCS-2), we're not there
yet. AFAIK, neither is anyone else on any Unix or similar platform. I'm
not even sure any of the APIs is entirely free of ASCII-isms.

Version 0.62 will go out the door with a blanket claim to support UTF-8
clients. That will happen Real Soon Now. If you encounter problems with
our UTF-8 support and don't mind building from successive snapshots, I'll
certainly do what I can to fix whatever's wrong.

In sum, for 0.62 clients:

* Expect UTF-8 to work.
* Be optimistic (and flexible) about SHIFT-JIS.
* UCS-2 is a nonstarter for the time being.

Regards,

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page