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 Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Associated Messages, from the most recent to the oldest:
>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 Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Grant Hulbert
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Not sending email !!! (2002)
problem with dates, NT version (1997)
[SearchString] problem with [search] context (1997)
Carts & Refering URLs (1997)
Using [sendmail] for mass mailings (2001)
Server Load Tester (2000)
Security & Query Strings (2004)
Deleting Orders (1998)
WCS Newbie question (1997)
Fun with dates (1997)
Mail going nowhere (2003)
Carrying over data? (1997)
Plugin or CGI or both (1997)
[OT] Theiving B*****ds (2004)
real beginner stumped (2000)
[text] doesn't change [formvariables] (1999)
Dreamweaver UltraDev (2000)
Not reading code (1997)
[WebDNA] New Webdna framework (2012)
[OT] DOD again (2003)