Thanks very much for the XHTML tips of late. I would like to hear from others who are working on moving in this direction. Have you figured out some effective tricks for making the transition to XHTML Strict? How would one ever replace iframes? (I'm guessing their's an iframe-like object, but I don't know.) I've been pointed to two different parsers: http://validator.w3.org/ and http://schneegans.de/sv/ The first is far more friendly, by the way. See: http://validator.w3.org/check?uri=www.stolaf.edu/people/hansonr/jmol/docs vs. http://schneegans.de/sv/?url=http://www.stolaf.edu/people/hansonr/jmol/docs I should point out, though, that neither of these really checks the validation for this page. In this case the page is produced by browser-based JavaScript, so true validation requires validating the FINAL "rendered" HTML, not just the <script> tags. (This is mentioned in the XHTML specs.) In order to do this, I had to add additional flags in the code to deliver "source" rather than "actual" HTML. This was important - when I did that the first time (my first XHTML page ever) I was greeted by the message: "Failed validation, 3161 errors" I still don't know if there is a simple way to do this; you can't just "look at the source" anymore, even with Netscape, to see how your code is writing. If anyone knows a good solution to this -- validating browser-generated XHTML code, do let me know! Right now I write this "pseudo code" that looks something like this: s=s.replace(/\</g,"<") .replace(/\<\/)/g,"</") .replace(/\</g,"<br /><") prior to writing, and then clip the screen, run a little batch DOS job that wraps it into an XHTML strict framework, and then upload it to w3c for validation. Is there a simpler way to do this? -Bob Hanson -- Robert M. Hanson, hansonr@stolaf.edu, 507-646-3107 Professor of Chemistry, St. Olaf College 1520 St. Olaf Ave., Northfield, MN 55057 mailto:hansonr@stolaf.edu http://www.stolaf.edu/people/hansonr