On Jul 31, 2005, at 4:28 PM, Manuel Mall wrote:
I am using 0.7 and there was no conversion required. I could try to
take the
pelt skin and to modify it to address the HTML 4.01 compatibility
issues.
However, I am not sure if that would be time well spent.
Likely all that is needed to 'convert' to Forrest 0.7 is to ensure that
skinconf.xml & forrest.properties match the 0.7 format (compare against
their counterparts from a 'forrest seed' run).
<snip>
True. The Compliance page is actually an 'ihtml' page. I used this,
because Forrest had significant difficulties with the FOP Compliance
page. I essentially created an HTML page, and then passed it through
Forrest unmodified.
I seems originally the compliance page was created using some XSLT
transformations (see src/documentation/resources/stylesheets). Has this
approach been abandoned? I can't find the input file.
I believe it was originally, however that broke and I wasted many hours
of time trying to get it to work. It's likely that the file
compliance.xml is a good starting point (in xdocs/)
Back to the compliance page. I assume what is required is some
indication of
1.0dev compliance vs 0.20.5 compliance. To achieve that we could:
a) Add extra columns, eg.
Support (0.20.5) | Support (1.0dev)
Basic | Extended | Complete | Basic | Extended | Complete
That is what I originally proposed, and is what I believe makes the
most sense. Doing it this way seems like it'd be the easiest to
separate and compare the differences between 0.20.5 support & 1.0dev
support.
BTW, why do we have the 3 columns Basic | Extended | Complete? Every
row will
only have one cell out of those 3 filled out. Wouldn't it make more
sense to
have a single column called Compliance or Core with the values Basic,
Extended or Complete? That would save valuable screen space and give
us room
to add columns for each release.
Someone else can probably best answer that ;-), but my sense is that
those come from the xsl-fo spec.
We probably also need the comments labelled with the release
identifier so its
obvious where they apply to.
...
BTW, one other option is to convert this page to a OpenOffice.org
Writer format. Forrest has a plugin which converts OpenOffice.org
Writer documents to Forrest HTML/XHTML documents. It's very nifty, and
works fairly well.
Interesting suggestion.
It sure is pretty, but it's got its own little bugs... You can check
the Forrest mailing archives for my problems...
Thanks again!
Regards,
Web Maestro Clay
--
<[EMAIL PROTECTED]> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
