Re: FSS-UTF, UTF-2, UTF-8, and UTF-16

From: Jianping Yang (Jianping.Yang@oracle.com)
Date: Mon Jun 18 2001 - 21:35:10 EDT

Next message: Carl W. Brown: "Needs Analysis for UTF-8s"
Previous message: Markus Scherer: "Re: FSS-UTF, UTF-2, UTF-8, and UTF-16"
In reply to: Markus Scherer: "Re: FSS-UTF, UTF-2, UTF-8, and UTF-16"
Next in thread: Carl W. Brown: "UTF8 encoding - What should I tell my customers?"
Reply: Carl W. Brown: "UTF8 encoding - What should I tell my customers?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Mail actions: [ respond to this message ] [ mail a new topic ]

Markus Scherer wrote:

>
> This means that Oracle mis-implemented the UTF-8 standard as it was specified at that time, starting at least with Unicode 2.0.
>

No, Oracle does not mis-implement the UTF-8 standard but only limit its support to BMP only. Except the backward compatibility reason, Oracle also needed to be compatible with other database vendors such as IBM and
Sybase's UTF-8 support up to BMP only and Microsoft SQL Server Unicode support to UCS2 then.

Regards,
Jianping.

text/x-vcard attachment: Card for Jianping Yang

Next message: Carl W. Brown: "Needs Analysis for UTF-8s"
Previous message: Markus Scherer: "Re: FSS-UTF, UTF-2, UTF-8, and UTF-16"
In reply to: Markus Scherer: "Re: FSS-UTF, UTF-2, UTF-8, and UTF-16"
Next in thread: Carl W. Brown: "UTF8 encoding - What should I tell my customers?"
Reply: Carl W. Brown: "UTF8 encoding - What should I tell my customers?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:17:18 EDT