Re: [Jmol-users] update of documentation

[Daniel L. <dan...@gm...>]

Am Freitag, den 16.09.2005, 09:14 -0500 schrieb Bob Hanson:
> That's fixed. Check now. I do think in general the XHTML parser at
> 
> http://validator.w3.org/
> 
> is far more friendly, by the way.

IMHO not really. But the killer argument: This validator is not able to
validate XHTML. The w3c mentions all limitations on their site
(http://openjade.sourceforge.net/doc/xml.htm). IIRC you could also use
xmllint to validate the files locally.

> 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/

This one was written by Christoph Schneegans to have a fully functional
XHTML validator. The main focus is functionality, not a colorful
interface :)

> 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.)

Of course. But this is a limitation in general.

> 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, do let me know! (Right now I write this 
> "pseudo code" that looks something like this:
> 
> s=s.replace(/\&lt/g,"&amp;lt")
>     .replace(/\<\/)/g,"&lt;/")
>     .replace(/\</g,"<br />&lt;")
> 
> 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?

I am sorry. Any chance to move to PHP instead of using Javascript (which
is also a limitation to the user and text browsers)?

Regards, Daniel