While people are working on that, they might want to add some sanity checking
to the multibyte character decoders. Currently they fail to check for
"illegal" character sequences (i.e. sequences with no valid multibyte mapping),
and fail to do something reasonable (like return an error, silently drop the
offending characters, or anything else besides just returning random garbage
and crashing the backend).
The last time this failed to get on the TODO list because Bruce wanted
more than one person to verify that it was an issue. If several people
are going to work on the NATIONAL CHARACTER stuff, maybe they could look
into this issue, too.
-Michael Robinson
>Added to TODO.
>
>> Since there are several people interested in contributing, we should
>> list:
>>
>> Support multiple simultaneous character sets, per SQL92
