Adrian Aichner <aichner(a)ecf.teradyne.com> wrote:
[Speaking of the XHTML DTD:]
 Look good.  I have to manually switch to xml-mode though, to get the
 DTD parsed.  Is this right? 
Yes, unfortunately.  I think I remember seeing somebody submit a patch
to add a .xml -> xml-mode mapping to auto-mode-alist, but you'll also
need an .xhtml -> xml-mode mapping for this, I guess.  Ooh, html3-mode
is still listed in auto-mode-alist.  That doesn't exist anymore.  Can
somebody rip that out of there?
 Will XML documents eventually use a .xml extension? 
In general, yes.  However, specific XML DTDs (such as XHTML) may have
more logical file extensions.  Maybe we should have something like this
in auto-mode-alist (although I'm not sure it would help):
("\\.x.*ml\\'" . xml-mode)
 I have yet to find an instance where PSGML screws up. 
It messes up on some of the <link> and <meta> tags on some of my pages.
I've never tried to track down why, though.  It might be easy to fix.
I'll admit that I've never had PSGML give a false warning on the body of
a document (although the HTML I write tends to be extremely simple in
form).
Anyway, back to the topic of making PSGML's warnings parseable by
compilation-mode.  Have you tried trapping them with (current-message)?
-- 
Jerry James
Email: james(a)eecs.ukans.edu
WWW:   
http://www.eecs.ukans.edu/~james/