freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>
- To: "Freetds (E-mail)" <freetds AT franklin.metalab.unc.edu>
- Subject: Unicode - UCS2, UTF8 present and future...
- Date: Mon, 19 Aug 2002 16:38:37 +0200
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."
=================================
-
Unicode - UCS2, UTF8 present and future...,
ZIGLIO Frediano, 08/19/2002
- <Possible follow-up(s)>
- Re: Unicode - UCS2, UTF8 present and future..., Brian Bruns, 08/19/2002
- Re: Unicode - UCS2, UTF8 present and future..., Mark J. Lilback, 08/19/2002
- Re: Unicode - UCS2, UTF8 present and future..., Lowden, James K, 08/19/2002
- Re: Unicode - UCS2, UTF8 present and future..., Mark J. Lilback, 08/19/2002
- RE: Unicode - UCS2, UTF8 present and future..., Lowden, James K, 08/19/2002
Archive powered by MHonArc 2.6.24.