XML rendering [IRC Channel]

Zack Rusin zack at kde.org
Sat Jun 5 21:49:27 CEST 2004


On Saturday 05 June 2004 15:44, Leo Savernik wrote:
> Am Samstag 05 Juni 2004 20:45 schrieb Zack Rusin:
> [...]
>
> > Essentially, that would be ideal, but it won't work because Qt SAX
> > parser feeds us XML attributes with an empty namespace if they're
> > not explictely prefixed. [...]
>
> Hasn't khtml switched to libxml? I remember there was a discussion
> about it.

Well, that's also yours truly :)

IIRC Safari team wanted to switch their QXML over to libxml2 from Expat, 
I'm not sure if they're done.

As far as we go, I wrote XMLLibXMLHandler (using libxml2 sax push 
parser) and made XMLTokenizer use it. I'm running it locally without 
any problems. I wrote it because I thought (proly like you :) ) that it 
will magically resolve a lot of our problems. It doesn't because we 
have a lot of problems in other areas (i think Safari team did a good 
job of finding a lot of them).
I'm reluctant to commit the libxml2 stuff right now though. Lars tells 
me that Qt SAX might improve up to 2x sometime soonish and if it 
doesn't it would make more sense to merge in Apple changes then use our 
own libxml2 implementation of qxml. 
Either way until we resolve the very basic bugs with XML it makes little 
sense to worry about performance :) So if you're a brave man I can send 
you the two files and a patch needed to make khtml use libxml2 sax push 
parser instead of Qt SAX parser, but right now it won't make too much 
of a difference :) 

Zack

-- 
"The number of UNIX installations has grown to 10, with more
expected." (6/72) 


More information about the Khtml-devel mailing list