On Thursday, 25. September 2003 17:06, Ralf Ullrich wrote:Thanks a lot, that works. But then my initial asssumption seems to be rigth: if you dont use ESQL for database access, you have to care about encoding yourself, right?
I use AxKit::XSP::ESQL and My::AdressManager (which @ISA
Apache::AxKit::Language::XSP::TaglibHelper) to generate output.
When I use encoding="UTF-8" I get all my umlauts as '?' (using mozilla).
replacing UTF-8 with ISO-8859-1 produces the same result. In my
home-grown AdressManager Taglib I convert the dbdata before presenting
it with something like
s/�/encode('UTF-8','�')/, and this works of cource event though I#m
still looking for a better way to do this.
There is a helper function AxKit::ToUTF8($string) which will convert your data from AxExternalEncoding to UTF-8.
You can try ESQL from CVS. It has experimental support for automatic conversion of your DB data to UTF-8 (unless it detects it is already UTF-8). Set AxExternalEncoding ISO-8859-15 (or whatever the correct value is), and go for it - your data will appear as UTF-8.I tried it and it works great. Think I really should use ESQL then instead of my own taglib.
ralf
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
