You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Manuel Mall <mm...@arcus.com.au> on 2005/08/01 01:28:48 UTC
Re: FOP Compliance Page was: getPageCount and FOP 1.0dev
Clay,
On Mon, 1 Aug 2005 02:39 am, The Web Maestro wrote:
> Manuel,
>
> First of all, thanks loads for helping out with this!
>
> On Jul 30, 2005, at 11:32 PM, Manuel Mall wrote:
...
>
> We currently use Forrest 0.6. Forrest 0.7 was recently released, and it
> was on my personal ToDo list to convert to 0.7.
>
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.
>
> > Another observation: FOP being a project under the XML family
> > shouldn't we
> > have an XHTML compliant site? I am guessing that this is a Forrest
> > skin issue
> > as well?
>
> That would be great. I believe that 0.7 brings Forrest closer to that
> XHTML reality. In order to make the site XHTML compliant, we may have
> to convert the site to either forrest 0.7 or 0.8-dev (not yet
> released).
>
There is no effort involved in converting the site to 0.7. I just seems to
work. Making it XHTML would probably involve even more skin and possibly XSLT
tweaking. Again, may be thats better left to the Forrest team?
> > Last observation: The compliance page (table columns) looks ugly under
> > Firefox. Its fine under IE 6, Opera, Konqueror. The problem is the
> > right
> > floating background image under external links which Firefox seems to
> > ignore
> > when calculating cell widths causing cells to overflow into their
> > neighbours.
> > Not sure what we can do about that its just a bit sad if our site
> > looks bad
> > under the most popular open source browser.
>
> 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.
> > 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.
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.
> > Manuel
>
> Thanks again, Manuel!
>
> Regards,
>
> Web Maestro Clay
Re: FOP Compliance Page was: getPageCount and FOP 1.0dev
Posted by Manuel Mall <mm...@arcus.com.au>.
On Mon, 1 Aug 2005 09:09 am, The Web Maestro wrote:
> On Jul 31, 2005, at 4:28 PM, Manuel Mall wrote:
...
> > 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/)
>
Do you mean src/documentation/content/xdocs? I can't find a compliance.xml
there in SVN. Never mind, I'll take your advice that its broken any way and
will edit the compliance.ihtml.
Re: FOP Compliance Page was: getPageCount and FOP 1.0dev
Posted by Manuel Mall <mm...@arcus.com.au>.
On Mon, 1 Aug 2005 09:09 am, The Web Maestro wrote:
> On Jul 31, 2005, at 4:28 PM, Manuel Mall wrote:
...
> > 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.
>
Had a first go and just changed the "XSL-FO Object Support Table" table.
Removed the 3 columns 'Basic', 'Extended', and 'Complete' and replaced them
with a column 'Compliance Level' instead. The 0.20.5 and 1.0dev have been
given their own column. Can you guys have a look
(http://www.arcus.com.au/fop/compliance.html) and see if that format is OK
before I apply it to the properties section.
Obviously the whole site as generated with Forrest 0.7 is available from
http://www.arcus.com.au/fop. While I am at it if anyone has suggestions for
other changes apart from the compliance page post it on the list.
Manuel
Re: FOP Compliance Page was: getPageCount and FOP 1.0dev
Posted by The Web Maestro <th...@gmail.com>.
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
--
<th...@gmail.com> - <http://homepage.mac.com/webmaestro/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet