[ http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317337 ]
Ross Gardler commented on FOR-592: ---------------------------------- Gavin, are you on the dev mailing list? If not please join us there (see http://forrest.apache.org/mail-lists.html) In our current development drive for 0.8 we are planning a move to a new way of doing our output. Now is an ideal time to jump in and help as we have a proof of concept of what is to come next and are currently discussing exactly how to go about implmenting it. I imagine, since the current skinning system is to be deprecated, this issue will be solved as part of this new approach. To get you started on the background for this new system take a look at http://forrest.apache.org/docs_0_80/views.html I don't know if anyone has tried validating the output from this new technique yet. Perhaps that would be a good first step. > Pelt skin not HTML 4.01 compliant > --------------------------------- > > Key: FOR-592 > URL: http://issues.apache.org/jira/browse/FOR-592 > Project: Forrest > Type: Bug > Components: Skins (general issues) > Versions: 0.7, 0.8-dev > Reporter: Manuel Mall > Fix For: 0.8-dev > > Just go to the Forrest home page and click the HTML 4.01 Compliance button. > The page doesn't validate. Other sites, e.g. Apache FOP, created with the > same skin have the same problem. One issue I could identify is that in the > site2xhtml.xsl there are tags like: > <input type="submit" value="Search" name="Search" i18n:attr="value"/>. > The 'i18n:attr="value"' bit creates a non HTML 4.01 compliant attribute. > Other problems are related to Javascript not being escaped correctly, e.g. > document.write("<text>Last Published:</text> " + document.lastModified); > should be written as > document.write("<text>Last Published:<\/text> " + document.lastModified); > I assume a requirement of being allowed to put the W3C HTML 4.01 Compliant > logo on the site is that the pages correctly validate. Pages based on this > skin don't validate but do carry the logo. Sounds like a problem to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
