Martin Cooper wrote:
Ah - so the tag would serve to say "This is XHTML-compliant" so that you could then say "Wait a sec - you asked for an XHTML document - but you included this and it's not XHTML". I think I understand the reasoning better now. Sorry about being so thick-headed.On Wed, 13 Nov 2002, Eddie Bush wrote:<big-snip/>If the outermost document is meant to enforce XHTML, how can an included
piece *not* conform to XHTML and the entire document still be XHTML? I
... feel like we're attempting to over-design - but maybe I'm just
showing my own ignorance (which is something I don't think I'll ever
learn not to do - I learn way too much from being willing to do it).
It can't, and that's in part what Craig pointed out. Since each included page must also be XHTML, each of those pages should state explicitly that it is XHTML, instead of having the decision about whether or not to generate XHTML be made externally (i.e. on the topmost page). Given that the non-Struts tags on the page must also be explicitly XHTML, that makes sense.
I figured I was confuzzled, but I wanted to be clear. Thanks Martin ;-)
-- Martin Cooper-- Eddie Bush
-- Eddie Bush -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
