Fwd: FOP status
Dear FOP Developers, I'm re-posting this mail from the user list, because there was no clear answer there. The main questions are: - what are the plans concerning the future FOP releases? Is there a defined timeline? - what are the plans concerning the spec conformance? Your answers are greately appreciated. It would help me to decide, if i should go FOP. Regards, Ilya --- Weitergeleitete Nachricht / Forwarded Message --- Date: Tue, 25 Jan 2005 14:16:54 +0100 (MET) From: Ilya Khandamirov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: FOP status Hi, I need a possibility to generate PDF from my XML. I've heard many good things about FOP, and i would use it, but... After having a quick look at the home page i got an impresion, that the project is dead. Last release is already 1.5 years old, and it is a bug fix only release. No information about upcoming features/releases. Dev and user mailing lists do not seem to be very busy. Hopefully my impression is wrong. Could someone please clarify, what are the current plans regarding the future FOP development? What are the plans concerning FOP 1.0? What are the plans concerning the spec conformance? Regards, Ilya -- GMX im TV ... Die Gedanken sind frei ... Schon gesehen? Jetzt Spot online ansehen: http://www.gmx.net/de/go/tv-spot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 10 GB Mailbox, 100 FreeSMS http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse für Mail, Message, More +++
Re: FOP status
Ilya, NOTE: This message does not reflect a decision of the FOP Development Team. Rather it is my own thoughts on the subject. If there are any mistakes or inaccuracies in my thinking or reasoning, I hope the FOP Team will let us know. My goal is to give Ilya and other an answer on this important subject. The FOP Development Team is actively diligently working to achieve a 1.0 release of Apache FOP. As with many open source projects with limited resources (i.e., a small number of active volunteer developers[1]), release schedules suffer. It has been 18+ months since the most recent release of 'maintenance' branch of FOP (fop-0.20.5). As you are probably aware, there were problems with meeting the requirements of the XSL-FO 1.0 Spec via the 'maintenance' branch, so it was frozen. The hope was that a re-design could be released relatively quickly, which would enable the FOP Team to meet the needs of the XSL-FO Spec. This hasn't happened yet, but we haven't stopped working towards that goal. Although there are Status[2], Change[3], ToDo[4], News[5] and other pages, a TIMELINE unfortunately is not presently on the site. Possible release dates and timelines for FOP 1.0 have been unofficially bandied about on the mailing lists. The most 'relevant' date I've seen is summer of 2005. This is not any sort of a 'promise' of a release date. It's just what I've seen in the mailing lists. In the not-too-distant future, I suspect the FOP Development Team will discuss a timeline schedule for release. Perhaps we may even add info on the FOP 'home' page or add a new page to the site, to communicate better with the FOP community. I apologize I/we cannot provide more specific information. Web Maestro Clay [1] Who we are http://xml.apache.org/fop/team.html [2] Status http://xml.apache.org/fop/status.html [3] Changes http://xml.apache.org/fop/changes.html [4] Todo http://xml.apache.org/fop/todo.html [5] News http://xml.apache.org/fop/news.html On Jan 27, 2005, at 6:35 AM, Ilya Khandamirov wrote: Dear FOP Developers, I'm re-posting this mail from the user list, because there was no clear answer there. The main questions are: - what are the plans concerning the future FOP releases? Is there a defined timeline? - what are the plans concerning the spec conformance? Your answers are greately appreciated. It would help me to decide, if i should go FOP. Regards, Ilya 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
DO NOT REPLY [Bug 22027] - FOP Status graphic needs update
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027 FOP Status graphic needs update [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-01 15:16 --- Committed to CVS, along with updates to the statistics. Thanks, Clay. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22027] New: - FOP Status graphic needs update
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027 FOP Status graphic needs update Summary: FOP Status graphic needs update Product: Fop Version: all Platform: All URL: http://xml.apache.org/fop/status.html OS/Version: All Status: NEW Severity: Normal Priority: Other Component: documentation AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The FOP Status Graphic needs to be updated to have 0.20.5 relevant information. I have created a graphic and will attach it to a PATCH. The language also needs to be updated. I've changed lines 76-78 (give or take) to what is below. I did not do a DIFF for a couple of reasons: 1) I've been having problems with my CVS app (I've still got that weird, double-menu bug on my MacCVSX program); and 2) the file sizes and other reference info need updating. Latest maintenance release is FOP 0.20.5, released on July 18th, 2003. See link href=relnotes.htmlrelease notes/link for more details. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22027] - FOP Status graphic needs update
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027 FOP Status graphic needs update --- Additional Comments From [EMAIL PROTECTED] 2003-07-31 16:27 --- Created an attachment (id=7607) FOP Status img track.png updated (includes layers--edit at will!) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop STATUS CHANGES
jeremias2002/11/11 02:26:24
Modified:.Tag: fop-0_20_2-maintain STATUS CHANGES
Log:
Updated committer list, todo for maint branch and changes (mine and Oleg's)
Revision ChangesPath
No revision
No revision
1.47.2.3 +27 -53xml-fop/STATUS
Index: STATUS
===
RCS file: /home/cvs/xml-fop/STATUS,v
retrieving revision 1.47.2.2
retrieving revision 1.47.2.3
diff -u -r1.47.2.2 -r1.47.2.3
--- STATUS5 May 2002 15:49:50 - 1.47.2.2
+++ STATUS11 Nov 2002 10:26:24 - 1.47.2.3
@@ -1,72 +1,46 @@
COMMITTERS
-Arved Sandstrom (release coordinator)
-James Tauber (started it all and wrote most of the code)
+(in strict alphabetic order)
+
+Active committers
+
+Bertrand Delacretaz
+Christian Geisert (release coordinator)
+Karen Lease
+Keiron Liddle
+Jeremias Maerki
+Joerg Pietschmann
+Arved Sandstrom
+Oleg Tkachenko
+Peter B. West
+
+
+Emeritus committers
+(They have not committed anything for six months, and so are considered
+to have retired from active duty. We wish them well and hope to see
+them return.)
Kelly Campbell
Steven Coffman
-Bertrand Delacretaz
Tore Engvig
-Christian Geisert
Stanislav Gorkhover
Fotis Jannidis
-Karen Lease
-Keiron Liddle
-Jeremias Maerki
Jordan Naftolin
-Joerg Pietschmann
Eric Schaeffer
Jon Smirl
+James Tauber (who started it all)
Art Welch
-Peter B. West
- THINGS WORKED ON *
+ THINGS WORKED ON *
-redesign/refactoring - layout [Karen Lease]
-redesign/refactoring - page layout [Arved Sandstrom]
-svg, testing [Keiron Liddle]
+This is the FOP maintenance branch. We currently build releases from
+here but only bugfixing is done. FOP is currently being redesigned and
+all new functionality should go into the main branch.
+- Bugfixing
THINGS TO DO
-
-1)
-The immediate list of things that need to be done. These include things
-that may prevent other activity or could be done independantly.
-
-* Redesign of flow layout handling, breaks keeps, spacing etc.
-* Redesign/factoring of line area handling.
-* Testing system, moving old tests to new system etc.
-* SVG
-- integrating Avalon and Fop
-- Documentation / website needs to better help users understand how to use FOP
-- examples (a separate set of user fo examples)
-
-(* being worked on, - no current activity)
-
-2)
-After the the layout handling is redesigned then these items should be
-promoted to first priority.
-These should be done with the aim of getting to basic conformance.
-
-- Implement all remaining formatting objects
-- improve property handling for types not currently supported (eg. 'large' font)
-- implement all required properties
-
-3)
-Nail down external interfaces (the main part is fairly stable).
-Setting base directory, using config, logging, extensions etc.
-
-Interfaces to include:
-how does FOP get called
-how does the formatter interface to renderers
-how do people write new plug-ins: handlers for new image types
-processors for fo:instream-foreign-object
-
-4)
-Improve the code. Follow the Sun Java coding guidelines.
-Have better comments and correlation between spec terms
-and methods etc.
-
-
+- Bugfixing
+- Improving documentation
1.10.2.24 +19 -0 xml-fop/CHANGES
Index: CHANGES
===
RCS file: /home/cvs/xml-fop/CHANGES,v
retrieving revision 1.10.2.23
retrieving revision 1.10.2.24
diff -u -r1.10.2.23 -r1.10.2.24
--- CHANGES 12 Aug 2002 17:05:51 - 1.10.2.23
+++ CHANGES 11 Nov 2002 10:26:24 - 1.10.2.24
@@ -1,6 +1,25 @@
==
Done since 0.20.4 release
+- Removed the necessity for a buildtools.jar (Jeremias Maerki)
+- Updated several JARs: Ant 1.5.1, Xerces 2.2.0, Xalan 2.4.1 (Jeremias Maerki)
+- Fixed some multi-threading issues (NPEs)
+ Submitted by: Joachim Unger [EMAIL PROTECTED]
+- Improved registration of ImageReader implementations (Jeremias Maerki)
+- Refactored baseDir stuff. Internally most code has been changed to work on
+ URLs instead of filenames. The baseDir property is evaluated to a baseURL
+ which can be accessed through Configuration.getBaseURL() (Jeremias Maerki)
+- Added a fontBaseDir property (similar to baseDir) which represents a base
+ dir/URL for fonts. If this property isn't set, a fallback is made to
+ baseDir. (Jeremias Maerki)
+- Fixed some javadoc warnings
+ Submitted by: Victor Mote [EMAIL PROTECTED]
+- Added translation for GoToPageDialog and update for czech translations
+ Submitted by: Michal
cvs commit: xml-fop STATUS
jeremias02/05/05 08:49:50
Modified:.Tag: fop-0_20_2-maintain STATUS
Log:
Updated committer list.
Revision ChangesPath
No revision
No revision
1.47.2.2 +3 -0 xml-fop/STATUS
Index: STATUS
===
RCS file: /home/cvs/xml-fop/STATUS,v
retrieving revision 1.47.2.1
retrieving revision 1.47.2.2
diff -u -r1.47.2.1 -r1.47.2.2
--- STATUS18 Feb 2002 18:27:36 - 1.47.2.1
+++ STATUS5 May 2002 15:49:50 - 1.47.2.2
@@ -12,10 +12,13 @@
Fotis Jannidis
Karen Lease
Keiron Liddle
+Jeremias Maerki
Jordan Naftolin
+Joerg Pietschmann
Eric Schaeffer
Jon Smirl
Art Welch
+Peter B. West
THINGS WORKED ON *
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop STATUS
jeremias02/05/05 08:52:35 Modified:.STATUS Log: Updated committer list. Revision ChangesPath 1.49 +8 -3 xml-fop/STATUS Index: STATUS === RCS file: /home/cvs/xml-fop/STATUS,v retrieving revision 1.48 retrieving revision 1.49 diff -u -r1.48 -r1.49 --- STATUS5 Mar 2002 14:39:45 - 1.48 +++ STATUS5 May 2002 15:52:34 - 1.49 @@ -4,16 +4,21 @@ James Tauber (started it all and wrote most of the code) Kelly Campbell -Steven Coffman +Steven Coffman +Bertrand Delacretaz +Tore Engvig +Christian Geisert Stanislav Gorkhover Fotis Jannidis Karen Lease Keiron Liddle +Jeremias Maerki Jordan Naftolin +Joerg Pietschmann Eric Schaeffer Jon Smirl -Christian Geisert -Bertrand Delacretaz +Art Welch +Peter B. West Initial development of new layout managers, area tree and renderers. Altered xml handling. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FOP Status
Fop Status - April 10 The layout process remains the critical path to the further development of properties and elements. Many other areas are getting attention, such as configuration and documentation. Development --- done: understanding docs - Cyril, Peter, Keiron, Karen added portuguese hyphenation - Paulo Soares implemented simple vertical alignment for line area - Keiron working on (if any details are incorrect or someone feels left out give us a yell :) image handling - Arved line area layout, understanding - Keiron avalon/configuration - Nicola properties/build/configuration/design - Peter FAQ - Joerg, Alex features/limitations list - Chuck Paussa and others documentation - Cyril rtf renderer - Bertrand PDF Forms extension - Hansuli Anderegg Things to do: Apart from the things that are being done there are a number of areas we can work on to create a better FOP. In general we have: Get a solid understanding and basis for the layout process. structure renderer simple examples testing Maintenance releases done: russian for AWTViewer - Alex V. Alishevskikh Updated Ant - Christian Use ant style task for build - Christian A maintenance release will be required. This will be after batik1.5 is released. working on: maintenance updates - Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP Status
This is still accurate as far as I am concerned, although I have not done much yet. However I have to look at images anyway with respect to my other project so it will definitely happen and happen soon. I am also transitioning my FOP development setup from Linux over to Win2K so I can get more productive. I just need to get my SSH set up (new password, basically) and I'll be ready to develop on FOP in short order. :-) Arved -Original Message- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: April 10, 2002 6:33 AM To: [EMAIL PROTECTED] Subject: FOP Status Fop Status - April 10 The layout process remains the critical path to the further development of properties and elements. Many other areas are getting attention, such as configuration and documentation. Development --- done: understanding docs - Cyril, Peter, Keiron, Karen added portuguese hyphenation - Paulo Soares implemented simple vertical alignment for line area - Keiron working on (if any details are incorrect or someone feels left out give us a yell :) image handling - Arved line area layout, understanding - Keiron avalon/configuration - Nicola properties/build/configuration/design - Peter FAQ - Joerg, Alex features/limitations list - Chuck Paussa and others documentation - Cyril rtf renderer - Bertrand PDF Forms extension - Hansuli Anderegg Things to do: Apart from the things that are being done there are a number of areas we can work on to create a better FOP. In general we have: Get a solid understanding and basis for the layout process. structure renderer simple examples testing Maintenance releases done: russian for AWTViewer - Alex V. Alishevskikh Updated Ant - Christian Use ant style task for build - Christian A maintenance release will be required. This will be after batik1.5 is released. working on: maintenance updates - Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP Status
Maintenance Branch Thanks to the good work by Christian we have a maintenance release incorporating fixes and various patches. The final version of 0.20.3 will be announced soon (I think). Development Initial development of new layout managers, area tree and renderers. Altered xml handling. Added User Agent. Made the image package thread safe and now has a caching system. Added extension example, of the type xml-svg. THINGS WORKED ON * layout manager design documentation - design and developers understanding maintenance branch THINGS TO DO 1) The main list of things that need to be done. - design of line area handling. - design of flow layout handling, breaks keeps, spacing etc. - integrating Avalon and Fop 2) These should be done with the aim of getting to basic conformance. - Implement all remaining formatting objects - improve property handling for types not currently supported (eg. 'large' font)- implement all required properties 3) Nail down external interfaces (the main part is fairly stable). Setting base directory, using config, logging, extensions etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP status
On Mon, 20 Aug 2001 12:36:51 +0200, Keiron Liddle wrote: Fonts - some improvements in font handling, naming I think PDFGraphics2D may need methods added to it that allows a user to specify: 1) Which True Type fonts to map to which Type 1 fonts. A user might want to display on his local monitor in Coolvetica rathan than Arial and then generate to PDF using Helvetica. So it isn't enough simply to add a mapping from Arial to Helvetica in FontInfo/FontSetup. 2) To embed particular fonts (whether True Type or Type 1) in the generated PDF. For some fonts the user might want to map to some core PDF font. But for other fonts the user might want to do embedding. I also think this embedding ought to be smart: Only embed those characters that are used. I foresee myself wanting to generate the same basic document but in different sizes. So for people who want small fast downloads I'd want to map to the core Type 1 fonts of PDF. But for people who want a nicer looking document I can foresee wanting to embed a lot of TT fonts in the PDF. Also, the same user might want to get drafts that are with core fonts so that the document is small. But then in the final production run of the document the user may then want to ask for embedding to get more preferred fonts used in final production. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
