On 04/17/2018 06:57 AM, Jan Nijtmans wrote:
> 2018-04-16 23:55 GMT+02:00 Kevin Kenny:>> I'm also not sure about the missing API's. I'm looking at what,>> for instance, tdbc::odbc will have to do. It has code that calls>> Tcl_UniCharToUtf and Tcl_UtfToUniChar repeatedly to convert>> Tcl's string representation to a sequence of 16-bit code points.> Well, this is what needs to be done to make tdbcodbc TIP #389-> compatible:> <https://core.tcl.tk/tdbcodbc/info/584efa4a8e0e24a7>>
Neither Oracle nor SQL Server offer any protection against unpaired
surrogates in the data base, so surely the buffer at
https://core.tcl.tk/tdbcodbc/artifact?udc=1&ln=786&name=6ce9986a10 must
also be initialized with a zero background. With that done, the
remaining issue is that unpaired high surrogates will be swallowed
silently and unpaired low surrogates will be substituted with \uFFFD,
leaving applications no way to deal with them. For example, it will
become nearly impossible to write a TDBC application fo delete or repair
the misencoded data in the database.
The same problem exists in dealing with the WIndows file system, as I
mentioned in an earlier message.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
Tcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcl-core