[ZPT] Is PageTemplates doing xhtml conversion? Should it?

[Dieter Maurer]

John Morton writes:
 > ....
 > A quick glance at the 
 > source showed that the select tags had both onchange and onChange attributes, 
 > the first being the source version, and the second being the attribute that 
 > was supposed to replace the source version....
 > I consider this a bug....
I was hit by this behaviour, too.
Like you, I consider it a bug.

By definition, HTML tag and attribute names are case insensitive.
ZPT should respect this and replace attributes independent
of case.

 > Some possible solutions:
 > 
 >  1) Turn off the case munging inside the METAL code. Leaving people's html 
 >  alone won't cause any harm.
I am for this solution.

 >  2) If TAL statements won't be processed unitl after METAL statements and the
 >  METAL code converts elements and attributes to lower case, then it's 
 >  reasonable to require tal:attributes statement to only use lower case
 >  attribute arguments, and throw an error, or at least a warning, if the are 
 >  supplied something else.
Please no!

METAL must not touch attribute and tag names for XML (as XML
names are case sensitive). Its best not to touch the names at all.

 >  3) Create a munging property that template users can set to 'none',
 >  'transitional' and 'full'. None will leave the template alone, transitional 
 >  will do the case munging done now, while 'full' will try to convert the  
 >  document to xhtml, doing things like complaining about images without
 >  alt tags, tables without summaries, spans when you should be using the
 >  appropriate grouping tag and so forth.
Please no!

Let ZPT keep simple.
Do not reinvent the wheel (you have tidy, already).



Dieter