- From: Cory Nelson <phrosty@gmail.com>
- Date: Wed, 14 Jul 2004 06:20:28 -0700
- To: Tommi <tommiweb1@q1b.com>
- Cc: html-tidy@w3.org
ASP.NET's controls are all written for HTML 4 so don't translate them into XHTML just yet, I'm pretty sure that'd come back to bite you in the ass. ASP.NET 2.0 is written to use XHTML 1.1, you can get a free beta from the MSDN Express website. The <asp:*> controls won't be recognised and afaik there currently isn't a way to get around that. Reading wild cards would probably slow things down a lot, a better solution would be to: make a --aspnet switch (or whatever) that makes it recognize all the asp:* tag names. assuming the parser won't complain about the : in the tag, a patch for this could be easy... read in the Register tags to see what user controls are allowed. <%@ Register TagPrefix="uc1" TagName="WebUserControl" %>, make it recognize <uc1:WebUserControl>. This will be a bit more complex. On Wed, 14 Jul 2004 14:50:46 +0200, Tommi <tommiweb1@q1b.com> wrote: > > I'm trying to format ASP.NET source code files to be xhtml compliant and > the problem rises in how html-tidy wants to manage new-xxx-tags > (block-level, inline). > > It want's me to specify each ASP.NET control type as it's own tag: > asp:literal asp:placeholder and so on. Now for some weird reason all of > the asp tags I have inside the documents <head></head> portion get moved > inside the <body></body> tag after tidying. Am I missing something? > > And then a feature suggestion: Wouldn't it be easier if new-xxx-tags > accepted wildcards? > asp:* would match all tags that start/close with asp: > This would be -really- helpfull for other script languages as well. > > Cheers, T > >
Received on Wednesday, 14 July 2004 09:21:02 UTC