Andy Hassall wrote:
> On Sun, 31 Oct 2004 13:03:38 +0100, Frank van Bortel <fvanbortel_at_netscape.net>
> wrote:
>
>
>>Iirc, somewhere in these manuals, there is a remark,
>>that a scenario as above ('any language'), is best
>>served with AL16UTF16 (not(!) the default AL32UTF8!!!),
>>especially when the clients run Windows.
>>There's even a rationale, which I cannot remember right now.
>
>
> Window's internal Unicode encoding is UTF16, so if the data goes directly into
> a native GUI element or OS function, it'd have to either be converted to UTF16
> by the app, or converted by Oracle using NLS_LANG, or you could have the whole
> lot in UTF16 and cut out the conversions entirely, if it makes sense taking
> into account the points Howard makes in the other reply.
>
Thanks for this - that was what I meant, but missed out.
--
Regards,
Frank van Bortel
Received on Sun Oct 31 2004 - 14:03:58 CST
