From: SourceForge.net <no...@so...> - 2006-02-11 15:43:41
|
Feature Requests item #1357947, was opened at 2005-11-16 09:59 Message generated for change (Comment added) made by maxberger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373750&aid=1357947&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: XSL Group: output: print/FO/PDF Status: Open Resolution: None Priority: 5 Submitted By: Jens Stavnstrup (stavnstrup) Assigned to: Nobody/Anonymous (nobody) Summary: Add new FOP processer extension Initial Comment: In a few days FOP 0.90a1 is going to be released. Amnong other things, the bookmark have been implemented as described in the latest XSL 1.1 draft. It would be nice, if we could start experimenting with the latest FOP as soon as it is being released. ---------------------------------------------------------------------- Comment By: Max Berger (maxberger) Date: 2006-02-11 16:43 Message: Logged In: YES user_id=99210 Jens, could you please submit your current patch (the one implementing the xsl 1.1 bookmarks) so that I could test / use it? Thank you! ---------------------------------------------------------------------- Comment By: Michael Smith (xmldoc) Date: 2005-11-21 08:41 Message: Logged In: YES user_id=118135 We have a "testdocs" module -- a suite of test documents -- in our project CVS repository. You can check it out via anonymous CVS by doing the following: cvs -d:pserver:ano...@cv...:/cvsroot/docbook co -P testdocs You can browse the testdocs content online at: http://cvs.sourceforge.net/viewcvs.py/docbook/testdocs/tests/ ---------------------------------------------------------------------- Comment By: Jens Stavnstrup (stavnstrup) Date: 2005-11-21 08:02 Message: Logged In: YES user_id=261049 Sort of. There is a compliance document, which describes what is new at http://xmlgraphics.apache.org/fop/compliance.html I have started looking at the issue. My approach is looking at each fo file, where changes was necessary for the current version of fop, and the test if it still necessary or what to do, Have so far implemted Bookmarks. I have tried using the test cases, but there are quite a few and it is a bit cumbesome using those. Do you have a test document, which covers most of the aspect of Docbook, which I could use for testing putposes ? ---------------------------------------------------------------------- Comment By: Michael Smith (xmldoc) Date: 2005-11-21 07:41 Message: Logged In: YES user_id=118135 Is there a documentation anywhere describing the changes to the public API? ---------------------------------------------------------------------- Comment By: Jens Stavnstrup (stavnstrup) Date: 2005-11-16 10:31 Message: Logged In: YES user_id=261049 Besides creating a new FOP processor extension, while keeping the old (for the time beeing). It will also require cahnges to a lot of other files. Current the FOP processer extensions are used by: admon.xsl, autotoc.xsl, block.xsl, callout.xsl, docbook.xsl, fo-patch-for-fop.xsl, footnote.xsl, formal.xsl, graphics.xsl, htmltbl.xsl, inline.xsl, pagesetup.xsl, pi.xsl, qandaset.xsl, table.xsl xref.xsl and profile-docbook.xsl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373750&aid=1357947&group_id=21935 |