> (And though I think KoXmlReader is _very_ impressive, I think it will be good for
> maintainability if we can drop it. It's very hairy code full of warnings for the unaware.)

I take the blame :)

Maybe I shall refactor it, e.g. taking out the compression part and
separate it? It was one-file-to-rule-them-all for the sake of getting
it to work, but as of today obviously it can use some clean up.


-- 
Ariya Hidayat
http://www.linkedin.com/in/ariyahidayat
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel