> I don't understand this. How could you globally convert everything to UTF8
> when nobody makes any statements about the character set it's converting
> _from_?
Sorry, I didn't explain the assumption that I make.
The XSP document has to be in a certain encoding.
The assumption I make is that if the XSP document says
<?xml version="1.0" encoding="XXXX"?>
Then the external data should be the same as the encoding specified for
the document. If you want to use, say, an UTF encoded string in a EUC-JP
encoded document, then that's your perogative ( in which case
AxKit::XSP::CharsetConv will do ).
The gripe that I had was that the document was encoded in EUC-JP, and
the data I was importing was guaranteed to be EUC-JP, and I had no way
of forcing that assumption throughout the XSP document. So I thought, if
the string conversion is going to give an error, it might as well assume
that all strings, including those imported from outside source, be the
same encoding as the document itself.
Like I said, I think this is really naive, so if somebody can do
something about having to convert every variable imported from the
database, that's better...
--d
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
