FreeTDS Development Group

["Brian Bruns" <camber AT ais.org>]

These are known limitations and are addressed in the User Guide.  There is
really not a whole lot we can do about inconvertable data, truncation at
that point seems like a reasonable fallback to me.

The UTF8 stuff needs works, specifically some of the applications out
there may assume 1 byte = 1 char and there is the possibility of buffer
overflows.  So, it is not safe to use UTF8 unless you know the application
is not broken.  I had planned on testing some popular applications to see
how they handled it but never got the chance.  If we did, we could at
least have a list of where it is and is not ok to use UTF8.

> It seem that working with unicode is a bit... broken!
> - conversion from ucs2 to single-byte charsets are not tested.
>   What happen if a unconvertible character is encountered? I think iconv
>   stop at that character and C conversion return truncated bytes..
>   some garbage data
> - conversion from ucs2 to utf8 have a small problem. We assume conversion
>   convert from a character to a byte but a UCS2 character can produce
>   up to 3 utf8 bytes... (from2 byte to 3). So many time string are just
>   trimmed. Many unix do not use ucs2 but utf8 so fix for this would be 
>   useful more than ucs2 handling
> 
> I think fix for this can't be in 0.6 (too place to correct...) but surely
> will be an improvement in next version...
> 
> freddy77
> 
> =================================
> "STRICTLY PERSONAL AND CONFIDENTIAL
> 
> This message may contain confidential and proprietary material for the sole
> use of the intended recipient. Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient please contact
> the sender and delete all copies.
> The contents of this message that do not relate to the official business of
> our company shall be understood as neither given nor endorsed by it."
> 
> =================================