[wp-hackers] WP issues

[Sam Angove]

On 6/3/07, Geoffrey Sneddon <foolistbar at googlemail.com> wrote lots of things.
>
> Well, why not use HTML? That gets around both this and the above.

Judging by your responses, we seem to be talking at cross purposes. I
assume you mean, use @type="html" instead of "xhtml", in which case,
yes -- there's no reason at all to be producing malformed Atom feeds.

In your original point 5, you complained that WordPress offers no
guarantee of producing well-formed, valid XHTML. I assumed you were
advocating such a guarantee.

To avoid further confusion, it would be helpful if you could outline
exactly what it is that you would like to happen. I am specifically
interested in points 1, 5 and 6. Jargon is better than imprecise
simplification.


> And suffer how browser makers have for years? "This feed works in x
> aggregator, but it doesn't work in your aggregator. Please fix this
> bug." — So then you go off and do more reverse-engineering of
> malformed XML.

To be fair, you'd have to do it anyway. :) WordPress isn't the only
fish in the sea.


> Using SAX would allow us to behave in similar ways as we already do.
> Tag-balancing issues would never arise with a serialiser.

The tag balancing problem arose in the context of a function to
correct constructions like `<p><blockquote></p></blockquote>`. I don't
see how a serialiser is relevant.