>>

I wrote...

>>The difference is actually that UNICODE-FSS is guaranteed not to have
>>null bytes within a string - making it file system safe. The internal
>>null bytes in UTF-8 are causing the truncation.
>
> Brad Pepers wrote:

> UTF-8 doesn't have internal null bytes.

Which is of course right - and I mean to type UTF16, which was the
source of the original question and the original error.

Spastically,


Ann