On Thursday, 25. September 2003 17:06, Ralf Ullrich wrote:
> 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.
> I certainly dont want to do this neither in XSP-pages that use ESQL. The
> only thing I can do is to choose a different character-encoding in my
> browser, which shows the right result. I know from perldoc that all data
> in taglibs is always returned in UTF-8, so it doesnt seem to make any
> sense to change encoding to ISO in XSP-Pages, or am I wrong?
> Is there anybody on this list who experienced the same problems and
> found a working solution to this?
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. Note, however, that your DB is
probably going to migrate to UTF-8 over time, as storing back the data won't
convert it back (yet).
--
CU
Joerg
PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc
PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
