Re: Stopping bad HTML propagation ?

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 11525
interpreted = N
texte = >We want to allow the catalog maintainers to use HTML _within_ their >entries so that they can use lists, figures etc at their discretion. This >brings up the problem of how to stop bad HTML from propagating down the >page.>>Just as an example, assume that one of the maintainers puts in an

>but forgets to put in the closing

tag. Unless we do something about >it, the rest of the [founditems] entries on the page would end up as

.That's a tough one. I spent about 1/2 hour looking thru BBEdit 4.0 to see if it can be AppleScripted to check the syntax of a text file. While it can be scripted to do many things, syntax-checking doesn't seem to be one of them.Perhaps you could do a [WriteFile] to render the text out to a URL, then use Chuck Shotton's NetEvents to send the URL to one of those free WebLint web-based syntax checkers. Perhaps you could decode the results and use that information to decide if the HTML is good or not.All of this sounds like too much trouble to be worth it, though.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors =====Pacific Coast Software | WebCatalog Pro, WebCommerce Solution11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

Re: Stopping bad HTML propagation ? (Ed Trefzger 1997)

Re: Stopping bad HTML propagation ? (Sven U. Grenander 1997)

Re: Stopping bad HTML propagation ? (Grant Hulbert 1997)

Stopping bad HTML propagation ? (Sven U. Grenander 1997)

Re: Stopping bad HTML propagation ? (Publisher1 1997)

>We want to allow the catalog maintainers to use HTML _within_ their >entries so that they can use lists, figures etc at their discretion. This >brings up the problem of how to stop bad HTML from propagating down the >page.>>Just as an example, assume that one of the maintainers puts in an

>but forgets to put in the closing

tag. Unless we do something about >it, the rest of the [founditems] entries on the page would end up as

.That's a tough one. I spent about 1/2 hour looking thru BBEdit 4.0 to see if it can be AppleScripted to check the syntax of a text file. While it can be scripted to do many things, syntax-checking doesn't seem to be one of them.Perhaps you could do a [writefile] to render the text out to a URL, then use Chuck Shotton's NetEvents to send the URL to one of those free WebLint web-based syntax checkers. Perhaps you could decode the results and use that information to decide if the HTML is good or not.All of this sounds like too much trouble to be worth it, though.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors =====Pacific Coast Software | WebCatalog Pro, WebCommerce Solution11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

DOWNLOAD WEBDNA NOW!

Re: Stopping bad HTML propagation ?

1997

>but forgets to put in the closing

>but forgets to put in the closing

Top Articles:

Related Readings: