Re: SQL Server UTF-16 characters with FreeTDS 0.91

[email protected]
Newsgroups gmane.comp.db.tds.freetds
Message-ID <trinity-c7b11983-bee3-4dc8-a055-601f2b22acc4-1393533337740@3capp-gmx-bs49>
(resending as plain text - used HTML before which seemed to cause problems)

Hello,
 
A few years ago (time flies), I got a very helpful suggestion from this list on how to patch freetds 0.82 in order to handle UTF-16 characters in BMP-1 correctly (i.e. characters outside the UCS-2 two byte range). See http://lists.ibiblio.org/pipermail/freetds/2010q3/026240.html .
 
This has been working well for me since then. Now, I need to upgrade to 0.91, and I'm seeing that the problem still exists. There have been some changes to iconv.c in the meantime. Is it still safe to make the changes to 0.91 in a way similar to what you suggested back then for 0.82?
 
In this quarter's mailing list archive, I'm seeing that just a few days ago you have been discussing changes to the iconv related code in freetds. Maybe this could be a good time also to integrate a change related to this problem?
 
Best Regards,
  Burkhard
 
 

Gesendet: Donnerstag, 27. Februar 2014 um 21:23 Uhr
Von: [email protected]
An: [email protected]
Betreff: [freetds] SQL Server UTF-16 characters with FreeTDS 0.91
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.