Hi,
perhaps I miss a new or hidden feature, but I've a massive issue with
encodings and e.g. german umlauts.
Database is mySQL 5.0.x and the encoding of the table and the column
is set to "utf8_unicode_ci" if I insert an umlaut using phpMySQL then
they appear in correct encoding in the database and could also be
exported in correct encoding e.g. to a UTF-8 textfile.
Using RB the encoding of rs.StringValue is always set to US-ASCII and
of course the resulting String is damaged. If I only use RB and
Econding-Functions then everything seems fine on the first look, but
in the database all umlauts are replaced by "funky two char"-chars
and so of course I'm not able to export anything using e.g. a
database dump.
IMHO RB is missing an ".Encoding" function here as e.g. the
TextInputStream do have.
Using e.g. ISOLatin1-Encoding in the database an changing the
enconding Methods in my code, everything is fine, but I'v the need to
store Unicode and not ISOLatin1 chars only, so that's not a real option.
If I miss something here, I'm really happy that someone can advice me
to the right direction.
regards
Thorsten Hohage
--
objectmanufactur.com - Hamburg,Germany
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
