On Tuesday 26 February 2002 20:18, Daisuke Maki wrote:
> But otherwise, because we already have to assume that external variables
> be in UTF-8 compatible encoding ( and you have to convert every expr to
> your own encoding ) *anyways*, I'm not 100% convinced that this is
> *such* a bad idea... But I'm willing to trust everybody's judgement on
> this.

Well, I've found that the path towards sanity lies in having everything as 
UTF-8. Of course, when it comes to forms and the such it isn't always all 
that easy (but then forms are an encoding bomb).

> Anyway, I just would like to stress that as a multi-byte-character-user
> the fact that I have to enclose every <xsp:expr>values with
> <char:charset-convert> to make my database query results show up in xsp
> is a *royal* pain, and if I weren't so immersed into the world of Perl
> and XML, I'd probably look for another XML Content Delivery framework --
> which is a shame, because in all other aspects I really think AxKit just
> rocks.

Well, the problem is that other XML content delivery frameworks probably 
offer *less* in that regard :-/ Otherwise we'd be stealing ideas left right 
and center. Encodings are always a pain. If you know of other solutions to 
that problem, please post them here.

> So I hope that you guys take a good look at the encoding issues further
> down the line of development of AxKit ;) Let me know if I can be of any
> help...

Would an encoding flag on xsp:expr sound reasonable ? I know that in the full 
XSP area, there are a few flags that aren't implemented, this /could/ be one 
of them, and it probably could be useful.

-- 
_______________________________________________________________________
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
The only sensible way to estimate the stability of a Windows server 
is to power it down and try it out as a step ladder. 
-- Robert Crawford, in the Monastery


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to