XHTML 1.0 validation

Friday 19 December 2003 3:47:23 am

1. I _did_ search but found no answers.

I use ez3.2.3 but it generates many errors with the w3c validator.
ez doesn't convert &s right according to the validator and the attribute xmlns isnt valid on the tag section to which ez applies it.

Any fixes or ideas or blames :) Thanks, Dominik

Monday 22 December 2003 3:03:27 am

Line 77, column 83: character "&" is the first character of a delimiter but occurred as data

...rig/" title="Musikverlage Hans Gerig & Carlton Musikvertrieb Startseite" />
^
Line 80, column 113: character "&" is the first character of a delimiter but occurred as data

...title="Suche Musikverlage Hans Gerig & Carlton Musikvertrieb" />

---

Line 351, column 22: there is no attribute "CLASS" (explain...).

<TH CLASS="title" STYLE="background-color:#DF0023;">
^
Line 351, column 36: there is no attribute "STYLE" (explain...).

<TH CLASS="title" STYLE="background-color:#DF0023;">
^
Line 351, column 63: element "TH" undefined (explain...).

... <TH CLASS="title" STYLE="background-color:#DF0023;">
^
Line 353, column 21: there is no attribute "xmlns

<section xmlns:image="http://ez.no/namespaces/ezpublish3/image/"
^
Line 354, column 21: there is no attribute "xmlns

xmlns:xhtml="http://ez.no/namespaces/ezpublish3/xhtml/"
^
Line 355, column 22: there is no attribute "xmlns

xmlns:custom="http://ez.no/namespaces/ezpublish3/custom/">
^
Line 355, column 66: element "section" undefined (explain...).

...custom="http://ez.no/namespaces/ezpublish3/custom/">
^
Line 356, column 12: element "paragraph" undefined (explain...).

<paragraph>Dezember &apos;03</paragraph>

---

ez still generates wrong xhtml... any options I need to tweak?

Tuesday 23 December 2003 12:49:04 am

the intro attribute - is a non-xml text field.
NOT displayed with attribute_view_gui

Tuesday 23 December 2003 4:27:42 am

<p class="news_intro">
{$node.data_map.intro.data_text}
{section show=$node.data_map.has_more.data_int|eq(1)}
 (<a class="more" href={$node.url_alias|ezurl}>mehr...</a>)
{/section}
</p>

If I use wash XML is converted but is plainly visible, if I dont wash, above code is generated.