forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <>
Subject Re: xml-fop Compliance Page (was Re: xml-fop Build Failed)
Date Wed, 10 Nov 2004 06:23:29 GMT
I've spent a fair amount of time playing around with the compliance* 
files over the last few days, and although I haven't gotten it to work 
as it should, I may have a suitable workaround.

xml-fop includes the following 'compliance' files:

[clay@Clay-Leeds-Computer xml-fop]$ find . -iname *compliance*

The only stylesheet which specifies the CSS for the table-cells is 
'compliance2html.xsl' and the relevant xsl:template doesn't appear to 
be processed:

<xsl:template match="head">
   <meta http-equiv="Content-Language" content="en-us"/>
   <meta http-equiv="Content-Type" content="text/html; 
   <link type="text/css" href="skin/page.css" rel="stylesheet"/>
   .yes         { background-color: #99FF99 }
   .no          { background-color: #FF9999 }
   .partial     { background-color: #FFFFCC }
   .category    { /*background-color: #CFDCED;*/
                  font-size: 1.2em }

(BTW, I the colors changed to light green - yes, light red - no, yellow 
- partial)

However, if I use Xalan to transform compliance.xml using 
compliance2html.xsl, the output is almost correct (@class='yes' doesn't 
work, but class='no' & class='partial' do?):

./ -IN compliance.xml -XSL compliance2html.xsl -OUT 

The result:

I just tried transforming:

./ -IN compliance.xml -XSL compliance2document.xsl -OUT 

The result:

When processed with Forrest, this xdoc file provides the same output 
we've been dealing with (table is OK--without the styles--but it's 
missing the mini-TOC & citation links).

Unless anyone has any better ideas, I'm about ready to settle for using 
the HTML file output by ./ above. I'll have to generate that 
file by hand for the time being, and I'll have to skin it, but that 
shouldn't be too bad. I think we all were hoping for a better way, 

Now all I/we have to do, is figure out the directory structure for RAW 
files & images (a moving target these days... ;-)), so I can get the 
links to the raw SVG & FO (and possibly PDF) files to resolve.

Web Maestro Clay
Clay Leeds - <>
Webmaster/Developer - Medata, Inc. - <>
PGP Public Key: <>

View raw message