>> I was playing for few days already, trying to use UNICODE_FSS... No
>> UNICODE_FSS... No
>> success - the data simply is inserted incorrectly..
> Yep - I'll agree with that :(

Count me in, been playing with FSS for days.

>> P.S. If someone here knows where definition of the 'UNICODE_FSS'
>> format can be found, please send a link..
> I'll second that - I've got the UTF-8, UTF-16 and UTF-32 stuff and now
> *I* understand better what is going on. But the problem *I* seem to be
> seeing is that the string content is changed before being sent

This is what I have found:
-there's a src\intl\cv_unicode_fss.c in the 1.5.2.4731 source code, go to
line 72 and you'll see
"File System Safe Universal Character Set Transformation Format (FSS-UTF)"
-Glossary in Unicode.org (http://www.unicode.org/glossary/#FSS_UTF) says
that FSS-UTF is now known as UTF-8.
-What does File System Safe means? I guess it's because FSS (ie UTF-8) is
interpreted as a sequence of bytes, and there is no endian problem.