Two comments on this:

1)  Doesn't HTML Tidy already validate and aid in correcting problems?
2)  Why HTML 4.01?  Why not XHTML which is the newer emerging standard, but 
close enough to HTML 4.01 that the differences are moot?

If a developer knows what they are doing (i.e. read that as experienced and 
good at testing), then such a tool has little value.  By all means, if you're 
developing on Front Page, or some other obscure editor - the tool  can be 
used to capture/identify problems.  But a decent developer should be able to 
identify the problems simply by looking at the code (presumably while they 
are writing it), and doing proper testing (Test in IE, Firefox, Konqorer, 
etc. - to identify non-standards based issues).

My thoughts.

Shawn

On Tuesday 11 January 2005 02:46, dave wrote:
> if anyone wants to try this with cfm support please contact me off list and
> i will send u a beta as long as u give feedback
>
> http://www.anetto.com.ru/ahc.php
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190012
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to