--- In Firebird-Architect@yahoogroups.com, Nickolay Samofatov wrote:
> BTW, don't you remember that Firebird already implements UCS2 charset
> under name UNICODE in standard fbintl.dll ? It should already
> have all problems including efficient on-page data compression
> solved.

Just started browsing the code. No wonder this charset is
never actually used except as intermediate in charconvs.

Biggest offender:
Uppercasing is done byte by byte by the ASCII routine. Ouch.

Usual suspect:
Endianity, no real concept to handle this

IMHO it seems better to leave CS_UNICODE101 in its state
as charconv intermediate step and define two character sets
UTF16LE and UTF16BE as (pseudo-)MBCS.

Regards,
Peter Jacobi