cvs commit: xml-fop/src/documentation/content/xdocs index.xml
vmote 2003/04/05 12:47:08 Modified:src/documentation/content/xdocs index.xml Log: Minor changes for clarity and conciseness. Revision ChangesPath 1.8 +16 -24xml-fop/src/documentation/content/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/index.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- index.xml 31 Mar 2003 23:10:59 - 1.7 +++ index.xml 5 Apr 2003 20:47:08 - 1.8 @@ -7,35 +7,24 @@ FOP - + Introduction FOP (Formatting Objects Processor) is the world's first print formatter driven by XSL formatting - objects and the world's first output independent formatter. It is a - Java application that reads a formatting object tree and then + objects (XSL-FO) and the world's first output independent formatter. It is a + Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats - currently supported are PDF, PCL, PS, SVG, XML (area tree representation), + currently supported include PDF, PCL, PS, SVG, XML (area tree representation), Print, AWT, MIF and TXT. The primary output target is PDF. - - The PDF files on this site are created using current CVS. - -The latest version of FOP is 0.20.5 and it supports the +The latest version of FOP (0.20.5) is a partial implementation of the http://www.w3.org/TR/2001/REC-xsl-20011015/";>XSL-FO Version 1.0 W3C Recommendation. - You can download - FOP including a precompiled version, the source code and many example files to - get you started. Pointers to introductions into xsl:fo can be found in the - resources section. Please be aware, that - FOP is at the moment not a full implementation of the basic conformance level - of the xsl:fo standard. The FOP Compliance - page lists all objects and properties in the standard, and indicates - FOP's current compliance with those features. + Support for each of the standard's objects and properties is detailed in FOP Compliance. + Download options include a precompiled version, source code, and many example files to get you started. Resources include links to XSL-FO introductions and many other useful references. A checklist for Getting Help will guide you toward maximizing the usefulness of FOP. -FOP is part of Apache's XML project. The homepage of FOP is - http://xml.apache.org/fop";>http://xml.apache.org/fop. - Here you can find information about using and developing with FOP. +FOP is proud to be part of http://xml.apache.org";>Apache's XML project. Users can subscribe to [EMAIL PROTECTED] by sending an email to mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] @@ -43,13 +32,13 @@ - -Formatting + +Demonstration This image is a demonstration of a two page document. The xml data on the left -is formatted into the two pages on the right. The document contains static areasthat appear on every page, an external graphic in this case an svg document. -There is a footnote on the first page and a table that goes across both pages. +is formatted into the two pages on the right. The document contains static areas that appear on every page and an external graphic (an svg document in this example). +It also includes a footnote on the first page and a table that goes across both pages. The advantage of XSL is the ability to take an XML document and to format @@ -64,7 +53,7 @@ along with the xml. - + FOP Objectives The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF formatter that is compliant to at least the Basic conformance level described in the W3C Recommendation from 15 October 2001, and that complies with the 11 March 1999 Portable Document @@ -80,6 +69,9 @@ better handle the formatting of all different types of formatting objects. + +The PDF files on this site are created using the latest development version of FOP. + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compliance.xml gethelp.xml
vmote 2003/04/05 11:51:49 Modified:src/documentation/content/xdocs compliance.xml gethelp.xml Log: minor corrections Revision ChangesPath 1.8 +1 -1 xml-fop/src/documentation/content/xdocs/compliance.xml Index: compliance.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- compliance.xml3 Apr 2003 15:29:33 - 1.7 +++ compliance.xml5 Apr 2003 19:51:49 - 1.8 @@ -263,7 +263,7 @@ - + 1.5 +9 -9 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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- gethelp.xml 5 Apr 2003 19:29:26 - 1.4 +++ gethelp.xml 5 Apr 2003 19:51:49 - 1.5 @@ -11,41 +11,41 @@ However, to make wise use of its limited resources, support must be primarily self-service. Go through the following checklist sequentially to determine what kind of help you need, and where to get it: - + Understand Underlying Technologies If you have a questions about XML, XSLT, or XSL-FO that are not directly related to FOP, please consult resources that are appropriate for those questions. FOP is an implementation of these technologies, and when you use FOP, there is a presumption that you have a working understanding of them. We have included several useful links on our Resources page that may help you get started. - + Review FOP's Standards Compliance FOP is a work in progress, and 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 Compliance 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. - + Read the Documentation Review the documentation pages on this site. There is information about how to run FOP, how to embed it, how to add custom fonts etc. - + Check the FAQs Consult the Frequently Asked Questions (FAQ) to see if your question has already been answered. - + Review FOP User Mailing List Archive It is possible that your question has already been answered but has not yet found its way into the FAQ. Links to the FOP User mailing list archives are on the Resources page. - + Look for an Existing Issue Report See Reported Issues for instructions on how to use the list of open issues. Review these open issues to see if any match your concerns. If so, please do not post a mailing list question or report another issue, as these will only slow the development team down. - + Submit Question to FOP User Mailing List Subscription information is on the Resources page. @@ -61,13 +61,13 @@ Instead of attaching large PDF files or screen shots, include a small B&W GIF, JPG or PNG of the area of interest. - + Enter an Issue Report If, and only if, you have followed all of the above steps, and believe that there is a bug or needed feature that you would like to report, please enter an issue in Bugzilla. Never use Bugzilla to post questions, only to enter issues that have already been asked on the user mailing list. See Reporting New Issues for detailed instructions on how to enter an issue. - + Find Out How You Can Help As stated above, the FOP development team is a limited resource. Most make their livings doing things other than writing and supporting FOP. Perhaps you need a feature from the XSL-FO standard to be implemented right away, or a bug fixed, or a new output format, or If so, there are several ways that you can help: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs bugs.xml gethelp.xml resources.xml
vmote 2003/04/05 11:29:26 Modified:src/documentation/content/xdocs bugs.xml gethelp.xml resources.xml Log: Fix link to "Asking Questions ..." Normalize and clean up content. Revision ChangesPath 1.5 +8 -28 xml-fop/src/documentation/content/xdocs/bugs.xml Index: bugs.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/bugs.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- bugs.xml 15 Mar 2003 19:59:46 - 1.4 +++ bugs.xml 5 Apr 2003 19:29:26 - 1.5 @@ -30,40 +30,20 @@ Unreported Issues (Reporting New Issues) User reports of bugs and requests for enhancements are extremely important parts of FOP development, and we appreciate the time you take to help -us track these issues down. -To help us ensure that the bug database is as useful as it should be, please -use the following checklist if you are considering reporting a new issue: - - Is your issue really a request to comply with some aspect of the -XSL-FO standard? -If so, please do not enter a bug report. -The developers already carefully track which standard requirements have been -implemented. -Other enhancement requests are welcome, but please be sure to mark -the issue as an enhancement. - Is your issue addressed by an http://xml.apache.org/fop/faq.html";>FAQ? If so, please do not -enter a bug report unless the FAQ did not adequately address your issue. - Has this issue already been reported? If so, please do not -report it again, as this will only slow the development team down. -See section above for a list of issues that have already been reported. - Do you know how to write a good bug report? -Please review the -http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug -Writing Guidelines before submitting your report. - If, and only if, you have passed all of the above steps, please -enter a new bug report at -http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The -FOP bug database (Bugzilla). +us track these issues down. + +To help us ensure that the bug database is as useful as it should be, please +use the Getting Help checklist to determine whether a bug report should be entered. +Review the http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug Writing Guidelines before submitting your report. +Enter a new issue report at http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP issue database (Bugzilla). You will be asked to login to an existing Bugzilla account or to create a new one. When entering the bug report, please make your description complete and concise. If appropriate, attach a minimal fo file to your report which demonstrates the problem. - After submission, a copy of your bug report will be automatically +After submission, a copy of your bug report will be automatically sent to the FOP developer discussion list. - + - 1.4 +69 -63xml-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.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- gethelp.xml 14 Mar 2003 00:12:10 - 1.3 +++ gethelp.xml 5 Apr 2003 19:29:26 - 1.4 @@ -3,72 +3,78 @@ "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";> -How to Get Help -Solving problems +Getting Help +Checklist for Finding Appropriate Resources +The FOP developer community is eager to help you maximize the usefulness of FOP. +However, to make wise use of its limited resources, support must be primarily self-service. +Go through the following checklist sequentially to determine what kind of help you need, +and where to get it: - How to get Help - - - Have a look at the documentation pages on this site. You can find - information on how to run FOP, how to embed it, how to add custom - fonts etc. - - - Consult the FAQ to see if your question - has already been answered before. - - - If you have a question concerning XSLFO that is not related to FOP - directly or regarding XSLT, please consult the various resources on - the net. See Resources for some - interesting links. - - - Before you post your questions to one of the mailing lists, please -
Re: A FOP Renderer based on Java Printing System and Grapics2D
At 07:31 AM 4/5/2003, you wrote: My renderer, based on the Java Printing System and Graphics2D: pure Java does a perfect job. I will send sources, classes, documentation on request to my e-mail address. JU hmm. Am I getting blind in my old age - I don't see an email address in your post; for that matter I don't even see a signature ;-) Have you considered folding your work into FOP ? ' Best, -Ralph LaChance In theory, there is no difference between theory and practice, but in practice there is. (Jan L.A. van de Snepsheut (1953-1994), late of CalTech) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: A FOP Renderer based on Java Printing System and Grapics2D
Hey J.U. Sounds very interesting. I'd love to see your implementation of the Java Printing System... Please email it to me at this address. Many thanks! jw On Saturday, April 5, 2003, at 06:31 AM, J.U. Anderegg wrote: The Java Printing System enables applications to: - Print Java 2D™ graphics, text and images. - Control document-composition functions such as soft collating, reverse order printing, and booklet printing. - Invoke printer-specific functions such as duplex (two-sided) printing and stapling. - Print on all platforms, including Windows and Solaris. - Data stream generation by platform printer drivers. My renderer, based on the Java Printing System and Graphics2D: pure Java does a perfect job. I will send sources, classes, documentation on request to my e-mail address. __ Highlights - Operation: silent or page/printer dialog - direct printing or output to file - Supported printers, data streams: PCL, AFP, Postscript, Text, PDF (PDFWriter required) - Precise output control by setting page/printer properties of drivers - Several renderings per run - Image Formats: JPEG, PNG, GIF (with JAI Image I/O Tools 1.0-rc also BMP, TIF) - SVG Support - Controls per print job o Destination file o Media sizes, bins, trays o Page orientation o Sides: simplex/duplex handling o Print quality o Chromaticity: color/monochrom o Copies o Finishings o NumberUp, Imposition __ Test Environment - Win2K - FOP 0.20.5rc2 - Java 1.4.1 - JAI Image I/O Tools 1.0-rc - Batik-1.5 __ Sample Printer Configuration: // double-slash is comment // debug: lists system printer and and fontinfo debug // silent: dont prompt page/printer dialog silent // destination: "print to file" destination=file:///C:/fop-0.20.4rc/AnyExtensions/print2D.txt //copies=1 // printer: select an installed printer printer=hp psc 700 series //printer=HP LaserJet 5M //printer=HP LaserJet 4/4M PS //printer=Generic / Text Only //printer=Acrobat PDFWriter // attributes: specify JPS attributes // PORTRAIT=102 ISO_A4=414 attributes=102 414 // SVGimageResolution: the renderer has SVG rasterized to the available area size at this resolution SVGimageResolution=300 // adjustPrinterResolution: scale at resolutions 72 or 150 or 300 or 600 to fit the available area most closely adjustPrinterResolution // map standard fonts to platform fonts HelveticaMap=Arial TimesMap=Times New Roman CourierMap=Courier New - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
A FOP Renderer based on Java Printing System and Grapics2D
The Java Printing System enables applications to: - Print Java 2D graphics, text and images. - Control document-composition functions such as soft collating, reverse order printing, and booklet printing. - Invoke printer-specific functions such as duplex (two-sided) printing and stapling. - Print on all platforms, including Windows and Solaris. - Data stream generation by platform printer drivers. My renderer, based on the Java Printing System and Graphics2D: pure Java does a perfect job. I will send sources, classes, documentation on request to my e-mail address. __ Highlights - Operation: silent or page/printer dialog - direct printing or output to file - Supported printers, data streams: PCL, AFP, Postscript, Text, PDF (PDFWriter required) - Precise output control by setting page/printer properties of drivers - Several renderings per run - Image Formats: JPEG, PNG, GIF (with JAI Image I/O Tools 1.0-rc also BMP, TIF) - SVG Support - Controls per print job o Destination file o Media sizes, bins, trays o Page orientation o Sides: simplex/duplex handling o Print quality o Chromaticity: color/monochrom o Copies o Finishings o NumberUp, Imposition __ Test Environment - Win2K - FOP 0.20.5rc2 - Java 1.4.1 - JAI Image I/O Tools 1.0-rc - Batik-1.5 __ Sample Printer Configuration: // double-slash is comment // debug: lists system printer and and fontinfo debug // silent: dont prompt page/printer dialog silent // destination: "print to file" destination=file:///C:/fop-0.20.4rc/AnyExtensions/print2D.txt //copies=1 // printer: select an installed printer printer=hp psc 700 series //printer=HP LaserJet 5M //printer=HP LaserJet 4/4M PS //printer=Generic / Text Only //printer=Acrobat PDFWriter // attributes: specify JPS attributes // PORTRAIT=102 ISO_A4=414 attributes=102 414 // SVGimageResolution: the renderer has SVG rasterized to the available area size at this resolution SVGimageResolution=300 // adjustPrinterResolution: scale at resolutions 72 or 150 or 300 or 600 to fit the available area most closely adjustPrinterResolution // map standard fonts to platform fonts HelveticaMap=Arial TimesMap=Times New Roman CourierMap=Courier New - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
