-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
during the first testing with real data (meaning data as it will occur in real-life deployment) of a ESQL-driven XSP data-generation a came across the following problem:
Data coming from the database (MySQL 4.0.13) is not UTF-8 encoded which (as AxKit excepts UTF-8 input) is a problem if it contains Umlaute or similar chracters.
The solution I found is to use
<esql:row-results>
<item>
<title><xsp:logic>
use XML::LibXML;
my $utf8 = XML::LibXML::encodeToUTF8('iso-8859-1', <esql:get-string column="title"/>);</xsp:logic><xsp:expr>$utf8</xsp:expr></title>
</item>
</esql:row-results>
instead of
<esql:row-results>
<item>
<title><esql:get-string column="title"/></title>
</item>
</esql:row-results>in my XSP-Page.
My question is: Is there a simpler way to do that?
Would it be appropriate to use AxExternalEncoding (as the MySQL content is not external but is generated within the page)?
Also I saw some unimplemented features about encoding in the latest ESQL.pm sources. Is there any way I can contribute to find a solutions within ESQL?
I am looking forward to your answers.
Thanks a lot in advance,
Benne
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (Darwin)
iD8DBQE/XKrRR5U9XkJXZKwRApnHAJ9Au8tBmAAuwOa03PWl9Fg/3kSe3wCfVaRZ h+WSKDhXiLZWtSGWnr84Gd8= =6dYd -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
