Adrian Aichner <aichner(a)ecf.teradyne.com&gt; wrote: [speaking of retrieving the DTD declaration from a document:] Oh, now I see what you are trying to do. Well, since the information you want doesn't appear to be stored anywhere, how about parsing it out of the buffer again? Something like this should do the trick: (save-excursion (goto-char (point-min)) (sgml-with-parser-syntax (let (start) (sgml-skip-upto "MDO") (setq start (point)) (sgml-skip-upto-mdc) (forward-char 1) (buffer-substring start (point))))) It has some XML support. The XHTML 1.0 DTD is included in the package. You could try using that to get a feel for it. [The next part deals with using (sgml-next-trouble-spot) to get a list of problems in a document.] Have you considered using (sgml-validate (sgml-default-validate-command)) to invoke a real SGML validator (say nsgmls)? That would put all the error messages in a buffer, ready for parsing by compilation-mode. It also would eliminate the false positives that sgml-next-trouble-spot tends to generate in some situations. (PSGML isn't a full SGML parser, although it does a pretty good job.) I think that would be a lot easier. On the other hand, nsgmls doesn't have DTDDECL support, so it generates lots of bogus messages, too. You'd have to throw away or ignore every message containing the string DTDDECL. Or fix nsgmls. :-) -- Jerry James Email: james(a)eecs.ukans.edu WWW: http://www.eecs.ukans.edu/~james/