Or you can use SQL Server w/o upgrading your exist databases. SQL Server
7.0 supports two character sets - CHAR for legacy character set and NCHAR
for Unicode (UCS-2). SQL is surrogate safe. You can store surrogates in
the NCHAR data column.
From: Edward Cherlin [mailto:firstname.lastname@example.org]
Sent: Saturday, July 29, 2000 2:33 PM
To: Unicode List
Subject: Re: FW: Oracle and Surrogate Pairs
At 2:41 AM -0800 7/25/2000, email@example.com wrote:
> I have been developing/convering a software to support multiple
>languages, especially Japanese, Korean and later on French etc.
>i have increased all the required fields by a factor of 3. Keeping "True,
>but within a year or so, there *will* be surrogates assigned in Unicode. "
>in mind what do you think i should be the value of this "factor" i should
I think you should upgrade to software that handles variable length
fields, or to programming practices that make use of them.
>Thanks & Regards,
>i-flex Solutions Limited,
>a CitiCorp venture capital company
>at SEI-CMM level 5.
>> -----Original Message-----
>> From: John H. Jenkins [SMTP:firstname.lastname@example.org]
>> Sent: Tuesday, July 25, 2000 8:12 AM
>> To: Unicode List
>> Subject: Re: Oracle and Surrogate Pairs
>> > Does the field in question need to support literally any possible
>> > in Unicode 3.0 and beyond (since 3.0 does not have any surrogates
>> > assigned!)?
>> True, but within a year or so, there *will* be surrogates assigned in
>> Unicode. One cannot be premature in supporting them at this point.
>> John H. Jenkins
Edward Cherlin Generalist "A knot!" exclaimed Alice. "Oh, do let me help to undo it." Alice in Wonderland
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:06 EDT