I understand the difference between wire and infoset, but they're just not relevant to me. If I write a document that contains:
<script src="..."></script> I don't want my template processor to change that to: <script src="..."/> While I'm well aware that both forms are legal XHTML and are basically the same, one works in all browsers and one doesn't. So suggesting that I change the kid.outputformat to xhtml-strict doesn't change the fact that KID will change my file for no good reason and will therefore make it *not* work with all browsers. Whereas it would have worked prior to processing (exempting the processing stuff). Thanks for suggesting Hickson's article. I've read it, and while I appreciate his concerns and look forward to the day when UAs actually support XHTML instead of HTML4 with clever hacks, I don't need to make a stand and refuse to publish anything as XHTML until they do. I'll leave the ideology of the issue for others to worry about. I actually agree with Kevin: it's a nice feature that Kid is able to translate from XHTML to HTML4. It's just not a feature that I'm interested in using. And naturally I expect a template processor to modify the parts of my file that require processing -- that's what they do. I just don't like it when it changes the parts that *don't* require processing. (Apparently, either Google is not delivering messages from this list or my mail server is ignoring them. So if there are other messages which are waiting for a response from me, I'll try to get to them as I can.)
