[ANNOUNCEMENT] FOP 0.20.5 released

2003-07-18 Thread Christian Geisert
Hi all,

the FOP team is pleased to announce the release of FOP 0.20.5

Binary and source distributions are available at:
http://www.apache.org/dyn/closer.cgi/xml/fop
Changes since 0.20.4 include:

- Added support for PDF encryption
- Perfomance tuning
- Fixed link hotspot positioning
- Fixed multi-threading issues
- Added support for CCITT Group 4 encoded TIFF files
- Dynamic JAI support
- Added autoselecting portrait/landscape for PCL and PS Renderer
- Added continued-label extension for tables
- Improved AWT Font-measuring/rendering
- Improved marker handling
- Fixed problem with jpegs with icc profile and acrobat reader 5
- Added a fontBaseDir property
- TXTRenderer output encoding
- border-spacing support
- and a lot more bugfixes
For details see the CHANGES file:
http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.64
For more information about FOP see http://xml.apache.org/fop

Please send feedback/bugreports to the mailing list or enter them
in Bugzilla.
Enjoy,
Christian




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]


cvs commit: xml-fop/src/documentation/content/xdocs faq.xml gethelp.xml

2003-07-18 Thread vmote
vmote   2003/07/18 09:39:18

  Modified:src/documentation/content/xdocs faq.xml gethelp.xml
  Log:
  Recast Understanding FOP's Compliance into a more general discussion of 
limitations in general. Add a When will feature X be implemented FAQ to point to the 
discussion of limitations.
  
  Revision  ChangesPath
  1.38  +6 -0  xml-fop/src/documentation/content/xdocs/faq.xml
  
  Index: faq.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/faq.xml,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- faq.xml   15 Jul 2003 01:12:33 -  1.37
  +++ faq.xml   18 Jul 2003 16:39:17 -  1.38
  @@ -110,6 +110,12 @@
   /p
 /answer
   /faq
  +faq id=when
  +  questionWhen will feature X be implemented?/question
  +  answer
  +pThe short answer is Don't ask. For more details, see link 
href=gethelp.html#limitationsUnderstand FOP's Limitations/link./p
  +  /answer
  +/faq
   faq id=contribute
 questionHow can I contribute?/question
 answer
  
  
  
  1.9   +10 -6 xml-fop/src/documentation/content/xdocs/gethelp.xml
  
  Index: gethelp.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/gethelp.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- gethelp.xml   15 May 2003 16:28:01 -  1.8
  +++ gethelp.xml   18 Jul 2003 16:39:18 -  1.9
  @@ -18,14 +18,18 @@
   We have included several useful links on our link 
href=resources.htmlResources/link page that may help you get started.
   /p
   /section
  -section id=compliance
  -  titleReview FOP's Standards Compliance/title
  -  pFOP is a work in progress, and does not yet fully comply with the W3C 
XSL-FO standard.
  +section id=limitations
  +  titleUnderstand FOP's Limitations/title
  +  pFOP is a work in progress, and has some limitations./p
  +  pFOP does not yet fully comply with the W3C XSL-FO standard.
   The developers track which standard requirements have been implemented, and have 
documented these capabilities on the link href=compliance.htmlCompliance/link 
page.
  -If this document appears to be in error, continue down this checklist so that 
either the document or the software can be corrected.
  -Otherwise, please do not submit mailing list questions or bug reports regarding 
features documented in the standard.
  -Please especially do not submit questions asking when a particular feature will be 
implemented.
  +FOP has other limitations regarding specific output formats, graphic formats, etc.
  +These limitations are noted in appropriate places in the documentation.
  +If these documents appear to be in error, continue down this checklist so that 
either the document or the software can be corrected.
  +Otherwise, please do not submit mailing list questions or bug reports regarding 
features documented in the standard, or documented as limitations in other parts of 
the documentation./p
  +  pPlease especially do not submit questions asking when a particular feature 
will be implemented.
   There are too many unknowns to make even a reasonable estimate.
  +Every time a developer stops to answer such a question, the answer will inevitably 
be I don't know, but the time taken to respond is time spent away from development.
   The only sure way to get a feature implemented is to link 
href=#how-to-helppitch in and help/link./p
   /section
   section id=doc
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]