forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manuel Mall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-592) Pelt skin not HTML 4.01 compliant
Date Tue, 02 Aug 2005 01:45:36 GMT
    [ http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317385 ] 

Manuel Mall commented on FOR-592:
---------------------------------

I tried David's suggestion, that is enabling
    project.i18n=true
in forrest.properties and the generated site is now HTML 4.01 compliant!!!

This seems to indicate there is a problem in handling the <i18n:...> tags in pelt/xslt/html/site2xhtml.xsl
when the feature is not enabled in the forrest.properties file.

> 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


Mime
View raw message