Scott Morgan wrote:

>
> UNICODE_FSS is basicly UTF-8 (UTF-FSS was an old name for what became
> UTF-8 [0], File System Safe or something like that, basicly because it
> doesn't have the endian issue that UTF-16/32 have)

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.

>

Regards,


Ann