> Firstly, it's Kersh - not Keith.
> It's a nickname. My Surname is 'Kershaw'.
> OK dude. I didn't want to get into a discussion. You don't know how to
> alter the HTML output from Server Controls in an ASP.NET page? That's
> OK then.
> I don't have time for a crusade to get Microsoft to standardise the
> output of ASP.NET WebControls to XHTML. We simply live in hope.
> And here's the definition of Arbitrary for you:
> Determined by chance, whim, or impulse, and not by necessity, reason,
> or principle: stopped at the first motel we passed, an arbitrary
> ALL my HTML AND ASP.NET server controls are inserted by a team working
> to the same XHTML principles, and we have examined the controls to
> determine exactly which ones will produce me a few non-XHTML
> tags/attributes and which won't. NOTHING chance, random, or impulsive
> about that mate, it's all cause, effect, & logic. I.e. NON-ARBITRARY
> no matter how many pages & controls I develop, because we work to
> standards and procedures.
> NO RANDOM FACTORS in there at all. I can also clearly identify 5-6
> modifications to the HTML produced by them that would make ANY GENERIC
> PAGE that uses these controls XHTML compliant. So if there isn't an
> algorithm, I'm going to write a basic version of it.
> OK - maybe I'd have to modify the algorithm if I upgraded to ASP.NET
> 2.0, but I'll do that when I come to it. As for your error text
> example - don't take me for a total amateur - I would be writing a
> sort of crude but generic XHTML pr - but it would never be that
> To be honest John I'd quite like an answer - not a lecture about why I
> shouldn't be asking the question. But you don't have an answer for me,
> do you?