|amikael66 on Apr 12, 2006 at 2:01:25 AM (# 1)|
Thats what xin does for asp/asp.net.
frumbert on Apr 19, 2006 at 12:23:00 AM (# 2)
no, actually it's not. Say I take an HTML file I made 10 years ago with badly nested markup, tags that are no longer supported, and so on. I don't want to load it on the client at all, ever, I want to load it internally on the server and parse it as if it were running on the client.
Ok can't be done.
bod1467 on Apr 19, 2006 at 1:27:07 AM (# 3)
Looks like you might have to write your own custom script to analyse files versus the W3C standards. Is there a W3C database that can be accessed (via script or XML) that would define the valid tags per a given doctype? That might give the starting point for you to create such a utility.
And if you did create such a utility, and it was proven to be robust, you may even find a market to sell it. :-)
MHenke on Apr 19, 2006 at 1:47:51 AM (# 4)
frumbert on Apr 19, 2006 at 3:43:13 PM (# 5)
nah. In asp, jscript can be used to build the resulting page, but there isn't a "html dom" to the page as such (if it was valid xhtml then it could be loaded into an xml object though, but unfortunately that isn't the case for the documents I needed this for).
I'll revise my "can't be done" and append "easily or cheaply".
BachusII on Apr 19, 2006 at 10:50:05 PM (# 6)
There is an IE ActiveX isn't there? One which you can control from within your asp.
MHenke on Apr 20, 2006 at 1:05:36 AM (# 7)
This message has been edited.
A search for ASP HTML parser shows some interesting hits, e.g. MIL (a "non-well-formed HTML parser for .NET").
Given that I don't got your requirement wrong, frumbert, that seems to be something in the right direction.