forrest-dev mailing list archives

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

David Crossley commented on FOR-592:
------------------------------------

Our homepage did validate recently.

You would need to track down which stylesheets are injecting these problems. Here is an example
of how i find such things ...

cd main
find . -type f | xargs grep "Last Published" | grep -v "\.svn"
... shows that it is .../pelt/xslt/html/site2xhtml.xsl

However, i suspect that it might be something to do with the internationalisation support.
There were recently some changes for that. It seems like it is not transforming the i18n:text
elements properly. Maybe because for the forrest/site-author/ we don't have i18n switched
on. Try doing that by setting it on in forrest.properties and doing 'forrect run' and see
what the difference is.
The project.i18n property is described in ../main/fresh-site/forrest.properties

To find out what changes were related to "i18n" recently, search the svn@forrest mail archives
for the commit messages. One way is via http://mail-archive.com/  and perhaps th edev list
too.

To find out which sitemaps deal with i18n, do ...
cd main/webapp
grep i18n *.*

There is not a lot of documentation about i18n on the forrest website (search via our Google).
Cheche has a document about it some )search full Google for "cheche i18n".

Hope that all helps.

> 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