2009/08/18 - Apache AxKit has been retired.

I'll bet money that is exactly the problem. Although, this sorta makes me
ask; doesn't this make the process of specifying encoding in all the
xml/xsl docs pointless?

In case anyone is curious... http://today.icantfocus.com/
It's not much yet, but it's built entirely in AxKit.

-=Chris

In the last exciting episode of Das Internet, Piers Harding sent forth the
following words of wisdom:
> This might have something to do with the fact (?) that the parser
> reduces everything to utf-8 internally for it's workings.  The AxKit
> then has to translate the final output back to your chosen delivery
> encoding via the AxOutputCharset I think.
>
> Cheers.
>
>
> On Sun, Oct 06, 2002 at 03:27:28AM -0400, Christopher H. Laco wrote:
>> I'm in the process of setting up my website using AxKit. Everything is
>> working great so far with one little quirk.
>>
>> I was in the process of running all the pages through the W3C
>> validators, and got the following message on all my pages:
>>
>>
>>     *  Warning: Character Encoding mismatch!  The character encoding
>> specified in the HTTP header («utf-8») is different from the one
>> specified in the META element («iso-8859-1»). I will use «utf-8» for
>> this validation.
>>
>>
>> Now, here's what I don't understand. All of my XSP and XSL pages have
>> their encoding set to iso-8859-1 via the encoding attribute. I have no
>> idea where to go from here.
>>
>> Here's the vitals..
>>
>> FreeBSD 4.7-RC
>> Perl 5.005_3
>> AxKit 1.6
>> libxml2-2.4.24
>> libxslt-1.0.20
>>
>> -=Chris
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axkit-users-unsubscribe [at] axkit.org
>> For additional commands, e-mail: axkit-users-help [at] axkit.org


-- 
/^Mic(ro|key)(shaft|slothe|suck): Wh(ere|at|o) Do You Want To
(BSOD|Extend|Extinguish|Overcharge|Purchase) Today?$/