"Jim Starkey" <jas@...> wrote:

>
> >If you use UTF-8 for everything internally though but allow the client
> >using the API to specify a different charset, then you need to convert
> >any text you get into UTF-8 using the character set the client specified
> >and you need to convert any text you send to the client's specified
> >character set.
>
> Yes, one the client side. In the scheme under discussion, all character
> data is transfered as utf-8.

And this is what I don't like. Doesn't it require the INTL stuff be
installed on the client side? With Vulcan, we don't have a single DLL client
any more. With the proposal being discussed, we must have the INTL
configuration files and libraries on the client side too. This is starting
to remind me Oracle.


Dmitry