Re: FOP status

2005-01-27 Thread The Web Maestro
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 importa

Fwd: FOP status

2005-01-27 Thread Ilya Khandamirov
s 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

DO NOT REPLY [Bug 22027] - FOP Status graphic needs update

2003-08-01 Thread bugzilla
gzilla/show_bug.cgi?id=22027 FOP Status graphic needs update [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 22027] - FOP Status graphic needs update

2003-07-31 Thread bugzilla
gzilla/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 laye

DO NOT REPLY [Bug 22027] New: - FOP Status graphic needs update

2003-07-31 Thread bugzilla
gzilla/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 Se

cvs commit: xml-fop STATUS CHANGES

2002-11-11 Thread jeremias
ision 1.47.2.3 +27 -53 xml-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

cvs commit: xml-fop STATUS

2002-05-05 Thread jeremias
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

cvs commit: xml-fop STATUS

2002-05-05 Thread jeremias
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

RE: FOP Status

2002-04-11 Thread Arved Sandstrom
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 -

FOP Status

2002-04-11 Thread Keiron Liddle
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

cvs commit: xml-fop STATUS

2002-03-05 Thread keiron
keiron 02/03/05 06:39:45 Modified:.STATUS Log: updated current status Revision ChangesPath 1.48 +14 -29xml-fop/STATUS Index: STATUS === RCS file: /home/cvs/xml-fop/STATUS,v

FOP Status

2002-03-05 Thread Keiron Liddle
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. A

Re: FOP status

2001-08-20 Thread Randall Parker
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 mon

FOP status

2001-08-20 Thread Keiron Liddle
This is the current status of FOP. Improvements in the right areas should make it much easier for people to understand the code without in depth knowledge. For the current aim of FOP, basic conformance, the layout is very important. To keep the product usable for users we need better communicatio