Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 9 of 9 total
Thread ElevateDB Unicode
Sat, Mar 11 2006 2:04 AMPermanent Link

"Surjanto"
Hi,

May I know what kind of unicode will be supported by ElevateDB ? UCS-2,
UTF-16 or UTF-8  ?

Will it support Unicode Queries and searching ?

I need Unicode and Full Text Search in Unicode.

And any prediction when it will be released ?

Regards,


Surjanto

Sun, Mar 12 2006 11:35 AMPermanent Link

Dan Rootham
Surjanto,

<< May I know what kind of unicode will be supported by ElevateDB ?
 UCS-2,  UTF-16 or UTF-8  ? >>

Tim has previously mentioned only UCS-2 support, in other words no
specific support for the surrogate pairs in UTF-16. I'd really like to
see UTF-8 support as well, but that requires a variable number of
bytes per Unicode character. I can guess that we might have to wait
for UTF-8 in a subsequent release.

<< And any prediction when it will be released ? >>
All you'll ever get from Tim is "when it's ready". Smiley

Regards,
Dan
Sun, Mar 12 2006 9:11 PMPermanent Link

"Surjanto"
Dan,

I will need it for Chinese language, does it mean that I can not use
ElevateDB for this ?

Thanks,


Surjanto

Mon, Mar 13 2006 8:39 AMPermanent Link

Dan Rootham
Surjanto,

<< I will need it for Chinese language, does it mean that I can not use
ElevateDB for this ? >>

On the contrary, the use of UCS-2 in ElevateDB ver 5 will make it much easier
to handle multiple languages. In particular the use of Unicode will enable
us as developers to make applications displaying 2, 3 or more languages
at the same time.

The only part not covered by ver 5 (as far as I know) is the handling of
"surrogate pairs". This is a requirement for full UTF-16 compliance, and it
covers some rarely-used characters which are outside the Unicode BMP
(basic multilingual plane). As far as I'm concerned, we can do everything
we need in our dictionary applications using only the characters contained
in the Unicode BMP.

No doubt Tim can comment in more detail as the release date gets nearer...

Regards,
Dan
Mon, Mar 13 2006 12:08 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Surjanto,

<< May I know what kind of unicode will be supported by ElevateDB ? UCS-2,
UTF-16 or UTF-8  ? >>

UCS-2.  Also, there will be separate ANSI and Unicode versions so those that
don't want the extra space consumption, etc. with Unicode won't need to use
it, but those that do can use it.  However, you won't be able to use a
Unicode version to access an ANSI database or vice-versa.

<< Will it support Unicode Queries and searching ? >>

Yes.

<< And any prediction when it will be released ? >>

I won't discuss the release date until it's ready.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Mar 13 2006 12:26 PMPermanent Link

Michael Baytalsky


> UCS-2.  Also, there will be separate ANSI and Unicode versions so those that
> don't want the extra space consumption, etc. with Unicode won't need to use
> it, but those that do can use it.  However, you won't be able to use a
> Unicode version to access an ANSI database or vice-versa.
So, there won't be two separate data types varchar and nvarchar?
Do I understand you correctly, that depending on the version of server
varchar fields will either be varchar or nvarchar?


Michael
Mon, Mar 13 2006 4:34 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Michael,

<< So, there won't be two separate data types varchar and nvarchar? Do I
understand you correctly, that depending on the version of server varchar
fields will either be varchar or nvarchar? >>

Correct.  And eventually even the ANSI stuff will be gone in favor of
all-Unicode.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Mar 14 2006 10:29 AMPermanent Link

Dan Rootham
Tim,

<< And eventually even the ANSI stuff will be gone in favor of all-Unicode. >>

I think that many of us have been well and truly confused about Unicode and its
various representations. One of the best descriptions I have found is on the
Microsoft Internationalization website on a page titled ""Supplementary Characters,
Surrogate Pairs and SQL":

  http://www.microsoft.com/globaldev/DrIntl/columns/021/default.mspx#ECAA

I hope this helps others as much as it helped me, at least in terms of defining
UCS-2, UTF-8, UTF-16 and UTF-32. (The parts about SQL Server and its SQL are
less useful for a DBISAM newsgroup!)

Regards,
Dan
Tue, Mar 14 2006 1:00 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dan,

<< I think that many of us have been well and truly confused about Unicode
and its various representations. One of the best descriptions I have found
is on the Microsoft Internationalization website on a page titled
""Supplementary Characters, Surrogate Pairs and SQL": >>

Thanks for the link.  I'm sure it will be very helpful for others.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image