cvs commit: xml-fop/src/documentation/content/xdocs faq.xml fo.xml
vmote 2003/11/12 09:28:07 Modified:src/documentation/content/xdocs faq.xml fo.xml Log: add doc for using current date and time, and create an FAQ referencing it Revision ChangesPath 1.40 +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.39 retrieving revision 1.40 diff -u -r1.39 -r1.40 --- faq.xml 12 Nov 2003 15:11:59 - 1.39 +++ faq.xml 12 Nov 2003 17:28:07 - 1.40 @@ -972,6 +972,12 @@ + + (XSLT) How can I use the current date and time in my document? + +See Current Date and Time. + + General suggestions. How to solve problems. 1.9 +22 -1 xml-fop/src/documentation/content/xdocs/fo.xml Index: fo.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- fo.xml12 Nov 2003 15:11:59 - 1.8 +++ fo.xml12 Nov 2003 17:28:07 - 1.9 @@ -82,6 +82,27 @@ + + XSLT Issues + +Current Date and Time +XSL-FO does not currently have a function for retrieving the current date and time. +However, in some cases, XSLT can be used to place the current date and time into the XSL-FO document as it is generated. +One possibility is to use the http://exslt.org/date/index.html";>exslt date and time extension. +Another possibility is to use java or javascript (or perhaps some other language). +Here is an example, using java, that works with Xalan. First, create the appropriate namespace: + +Next, use the java language to retrieve and format the current date and time. +Here is an example template: + + + XSL-FO Issues - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml gethelp.xml
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 @@ + + When will feature X be implemented? + +The short answer is "Don't ask." For more details, see Understand FOP's Limitations. + + How can I contribute? 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 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. + + Understand FOP's Limitations + FOP is a work in progress, and has some limitations. + FOP 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. -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. + Please 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 pitch in and help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml hyphenation.xml
vmote 2003/07/14 18:12:33
Modified:src/documentation/content/xdocs faq.xml hyphenation.xml
Log:
1. add list of supported country/language codes for hyphenation
2. update FAQ to point to the new hyphenation page
Revision ChangesPath
1.37 +3 -14 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.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- faq.xml 11 Jul 2003 19:01:54 - 1.36
+++ faq.xml 15 Jul 2003 01:12:33 - 1.37
@@ -531,21 +531,10 @@
Hyphenation does not work.
-
- Set the language attribute somewhere and explicitly enable hyphenation.
- Check whether you use a language for which hyphenation is supported.
- Supported languages can be deduced from the files in the
{fop-dir}/src/hyph
- directory of the FOP source distribution. If you want to use a language
- FOP currently doesn't hyphenate, please see the
- Configuration page.
-
-
- Set the language (on fo:page-sequence, fo:block or fo:character):
-
+Make sure you have set the language and/or country attributes for an
appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):
-
- Enable hyphenation on a block:
-
+See Standard Hyphenation
Support for a list of supported language and country codes, and Custom Hyphenation Support for instructions on
adding support for other languages and countries.
+Explicitly enable hyphenation for an appropriate XSL-FO element
(fo:block, fo:character):
1.3 +51 -7 xml-fop/src/documentation/content/xdocs/hyphenation.xml
Index: hyphenation.xml
===
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/hyphenation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hyphenation.xml 10 Jul 2003 19:57:20 - 1.2
+++ hyphenation.xml 15 Jul 2003 01:12:33 - 1.3
@@ -6,26 +6,69 @@
FOP: Hyphenation
-
+
+ Standard Hyphenation Support
+ FOP includes hyphenation support for the following languages:
+
+
+ language_COUNTRY code
+ Description
+
+
+ en
+ English
+
+
+ es
+ Spanish
+
+
+ fi
+ Finnish
+
+
+ hu
+ Hungarian
+
+
+ it
+ Italian
+
+
+ pl
+ Polish
+
+
+ pt
+ Portuguese
+
+
+ ru
+ Russian
+
+
+
+
+Custom Hyphenation Support
+
Introduction
FOP uses an XML-based TeX-like hyphenation pattern scheme.
-Hyphenation pattern files for many languages are included in the standard FOP
distribution.
However, because of licensing issues, there are
currently some significant holes in FOP's hyphenation support.
-The information on this page is intended to help you work around these limitations,
if possible, add support for other languages, or enhance FOP's support of current
languages.
+The information in this section is intended to help you work around these
limitations, if possible, add support for other languages, or enhance FOP's support of
current languages.
If you have access to hyphenation patterns that are licensed in an
Apache-compatible way, or if you have made improvements to an existing FOP hyphenation
pattern, or if you have created one from scratch, please consider contributing these
to FOP so that they can benefit other FOP users as well. Please inquire on the FOP User mailing list.
-
+
License Issues
Many of the hyphenation files distributed with TeX and its offspring are
licenced under the http://www.latex-project.org/lppl.html";>LaTeX Project
Public License (LPPL), which prevents them from being distributed with Apache
software.
Although Apache FOP cannot redistribute hyphenation pattern files that do not
conform with its license scheme, that does not necessarily prevent users from using
such hyphenation patterns with FOP.
However, it does place on the user the responsibility for determining whether the
user can rightly use such hyphenation patterns under the hyphenation pattern
license.
The user is responsible to settle license issues for hyphenation
pattern files that are obtained from non-Apache so
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml svg.xml
vmote 2003/03/26 15:34:57
Modified:src/documentation/content/xdocs faq.xml svg.xml
Log:
Pushed more of the svg doc out of the faq and into svg.xml.
Revision ChangesPath
1.15 +3 -28 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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- faq.xml 24 Mar 2003 23:05:10 - 1.14
+++ faq.xml 26 Mar 2003 23:34:55 - 1.15
@@ -791,35 +791,10 @@
Batik/SVG specific questions
- SVG text rendered in bad quality. How do I put SVG text as text
- into PDF?
+ The rendering of SVG text in my PDF is of poor quality.
+Can I control this?
-
- The svg text is rendered as shapes, the Acrobat viewer displays it
- with bad quality unless you turn on smooth line art in the Acrobat
- preferences. The printout is always ok, it's only the screen view
- which is of bad quality by default.
-
-
- You can force Batik not to render SVG text by setting the
- strokeSVGText property to false. You can do this in the user
- configuration file:
-
-
-
- In a servlet environment, you can set it directly:
-
-org.apache.fop.configuration.Configuration.put("strokeSVGText",
Boolean.FALSE);
-
- See also using a user configuration file
- in a servlet.
-
-
- This does not work for other renderers.
-
+See Placing SVG Text into PDF.
1.5 +9 -2 xml-fop/src/documentation/content/xdocs/svg.xml
Index: svg.xml
===
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/svg.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- svg.xml 26 Mar 2003 22:46:16 - 1.4
+++ svg.xml 26 Mar 2003 23:34:55 - 1.5
@@ -94,19 +94,26 @@
It is possible to make sure that all text is drawn into PDF using the
-PDF text commands by adding the following to the user config:
+PDF text commands (instead of the graphical shapes), by adding the following to the
user config:
+In a servlet environment, you can set it directly:
+org.apache.fop.configuration.Configuration.put("strokeSVGText",
Boolean.FALSE);
+For information on using a configuration file in a servlet, see the FAQ on that topic.
+Note that this configuration setting works only for the PDF renderer.
-The drawback from this is that all text will be confined to text that is
+The drawback to forcing text to be rendered as text is that it will be confined to
text that is
possible for PDF fonts (including embedded fonts) and implemented with
this workaround. The fonts available are the standard pdf fonts and any
fonts that you have embedded using FOP. The font sizes will be rounded
to an integer value. In future this will be improved.
+Note that because SVG text can be rendered as either text or a vector
graphic, you may need to consider settings in your viewer for both.
+The Acrobat viewer has both "smooth line art" and "smooth text" settings that may
need to be set for SVG images to be displayed nicely on your screen (see Edit /
Preferences / Display).
+This setting will not affect the printing of your document, which should be OK in
any case, but will only affect the quality of the screen display.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2003/03/24 15:05:10 Modified:src/documentation/content/xdocs faq.xml Log: Move developer FAQs to the Developer FAQ document. Revision ChangesPath 1.14 +2 -12 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.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- faq.xml 18 Mar 2003 16:48:15 - 1.13 +++ faq.xml 24 Mar 2003 23:05:10 - 1.14 @@ -957,7 +957,7 @@ for adding security features, document properties, watermarks, and many other features to PDF files. FOP and iText can be integrated into one Java application, see sample code for encryption. + href="#pdf-security">encryption. The bad news is that iText swallows PDF bookmarks. @@ -1647,17 +1647,6 @@ - -General Developer Questions - - How do I get the javadocs for FOP? - -Currently, the only way to get FOP javadocs is to -Download the source code and then Build -FOP using the ant build task "javadocs". - - - General suggestions. How to solve problems. @@ -1674,6 +1663,7 @@ should I post them? + If your question is a development-related question, please see the Developer FAQs. If you have a runtime exception or other runtime problem: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2003/03/15 11:55:50 Modified:src/documentation/content/xdocs faq.xml Log: normalize & clean up the general help section a bit. Revision ChangesPath 1.12 +23 -14xml-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.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- faq.xml 15 Mar 2003 18:49:56 - 1.11 +++ faq.xml 15 Mar 2003 19:55:49 - 1.12 @@ -1661,29 +1661,38 @@ General suggestions. How to solve problems. - Where to post bugs. + I think I have found a bug in FOP. What should I do? - See documentation. See also - "where to post - questions". + See the Bugs page for information about + bugs already reported and how to report new ones. - Where to post questions. + I have questions that are not addressed in this FAQ. Where + should I post them? - - Decide where to post: - -You get exceptions. First, check the FAQ whether the exception is -mentioned. ClassNotFoundException, NoSuchMethodException and -NoSuchFieldException problems are almost always a problem with the -local environment, try to get local help first. Check http://nagoya.apache.org";>bugzilla. If still not found, -post to fop-dev. +If you have a runtime exception or other runtime problem: + + +double-check the Runtime FAQs. + + +ClassNotFoundException, NoSuchMethodException and +NoSuchFieldException problems are almost always a problem with +the local environment. Try to get local help first. + + +Check Reported Issues +to see if this is a known problem. + + If none of the above apply, post a question to the fop-dev +mailing list. + + Something doesn't work with FOP but works with another formatter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2003/03/15 10:49:56 Modified:src/documentation/content/xdocs faq.xml Log: 1. Break "stumbling blocks" section into two pieces: (a) runtime problems (b) output problems 2. Add ids for each part, hopefully to get consistent cross-references for them as well. Revision ChangesPath 1.11 +57 -54xml-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.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- faq.xml 12 Mar 2003 01:41:22 - 1.10 +++ faq.xml 15 Mar 2003 18:49:56 - 1.11 @@ -3,7 +3,7 @@ "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/faq-v11.dtd";> - + General questions What is FOP? @@ -120,33 +120,8 @@ - -Common stumbling blocks - - Why does FOP insert a blank page between my page sequences? - - - This is because spec conformance has been improved. - - - The http://www.w3.org/TR/xsl/slice7.html#force-page-count";>force-page-count - property controls how a FO processor pads page sequences in - order to get certain page counts or last page numbers. The default is - "auto". With this setting, if the next page sequence - begins with an odd page number because you set the - initial-page-number, and the current page sequence also ends with an - odd page number, the processor inserts a blank page to keep odd and - even page numbers alternating (similar for the case the current page - sequence ends with an even page number and the next page sequence - starts with an even page number. - - - If you don't want to have this blank page, use - force-page-count="no-force". - - - + +Problems running FOP I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master' or @@ -168,25 +143,6 @@ - - My PNG images don't work. - - - The Jimi image library, which is by default used for processing - images in PNG and other formats, was removed from the distribution - for licensing reasons. You have to http://java.sun.com/products/jimi";>download - and install it by yourself. - - - Extract the file "JimiProClasses.zip" from the archive you've downloaded, rename it to "jimi-1.0.jar" and move it to FOP's lib directory. - - - An alternative to Jimi is to use Sun's JAI. It is much faster, but - not available for all platforms. - - - I get a NoClassDefFound exception. @@ -443,6 +399,53 @@ + + +Problems with FOP output + + Why does FOP insert a blank page between my page sequences? + + + This is because spec conformance has been improved. + + + The http://www.w3.org/TR/xsl/slice7.html#force-page-count";>force-page-count + property controls how a FO processor pads page sequences in + order to get certain page counts or last page numbers. The default is + "auto". With this setting, if the next page sequence + begins with an odd page number because you set the + initial-page-number, and the current page sequence also ends with an + odd page number, the processor inserts a blank page to keep odd and + even page numbers alternating (similar for the case the current page + sequence ends with an even page number and the next page sequence + starts with an even page number. + + + If you don't want to have this blank page, use + force-page-count="no-force". + + + + + My PNG images don't work. + + + The Jimi image library, which is by default used for processing + images in PNG and other formats, was removed from the distribution + for licensing reasons. You have to http://java.sun.com/products/jimi";>download + and install it by yourself. + + + Extract the file "JimiProClasses.zip" from the archive you've downloaded, rename it to "jimi-1.0.jar" and move it to FOP's lib directory. + + + An alternative to Jimi is to use Sun's JAI. It is much faster, but + not available for all platforms. + + +
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2003/03/11 17:41:22 Modified:src/documentation/content/xdocs faq.xml Log: Add ID for each faq, so that document links will be permanent. Revision ChangesPath 1.10 +57 -57xml-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.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- faq.xml 12 Mar 2003 01:15:22 - 1.9 +++ faq.xml 12 Mar 2003 01:41:22 - 1.10 @@ -5,7 +5,7 @@ General questions - + What is FOP? @@ -19,7 +19,7 @@ - + What can I do with FOP? @@ -36,7 +36,7 @@ - + What does "FOP" stand for? @@ -45,7 +45,7 @@ - + How does FOP interact with other Apache Projects? @@ -61,7 +61,7 @@ - + What is XSL? @@ -110,7 +110,7 @@ - + How can I contribute? @@ -122,7 +122,7 @@ Common stumbling blocks - + Why does FOP insert a blank page between my page sequences? @@ -147,7 +147,7 @@ - + I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master' or 'page-sequence-master' @@ -168,7 +168,7 @@ - + My PNG images don't work. @@ -187,7 +187,7 @@ - + I get a NoClassDefFound exception. @@ -212,7 +212,7 @@ - + I get a NoSuchMethodException or a NoSuchFieldException exception. @@ -228,7 +228,7 @@ - + I get an OutOfMemoryException. @@ -299,7 +299,7 @@ - + I get a MalformedURLException. @@ -334,7 +334,7 @@ - + I get an "[ERROR]: null", or a NullPointerException. @@ -366,7 +366,7 @@ - + FOP hangs. FOP does not exit. @@ -406,7 +406,7 @@ - + FOP cannot find a file for fo:external-graphics. @@ -427,7 +427,7 @@ - + FOP does not find my fonts. @@ -443,7 +443,7 @@ - + Keep-with-next, keep-with-previous, keep-together don't work. @@ -478,7 +478,7 @@ ]]> - + My tables are missing, or missing their content. @@ -494,7 +494,7 @@ - + Text overflowing table cells and the like is not clipped. Long text flows into adjacent cells/block, obscuring stuff there. @@ -524,7 +524,7 @@ - + Page numbers are not properly right aligned. @@ -541,7 +541,7 @@ - + A graphic is not displayed. @@ -577,7 +577,7 @@ - + Hyphenation does not work. @@ -590,7 +590,7 @@ Embedding FOP. Using FOP in a servlet. - + How do I use FOP in a servlet? Look at the servlet example. @@ -613,7 +613,7 @@ - + How do I use FOP in a servlet with an XSLT transformation? @@ -669,7 +669,7 @@ - + How do I pass parameters to the XSLT transformation? @@ -677,7 +677,7 @@ - + How do I use my own fonts when running FOP from a servlet? @@ -688,7 +688,7 @@ - + How do I set the baseDir property in a servlet environment? @@ -724,7 +724,7 @@ - + I keep getting NoClassDefFound and other exceptions. How do I get FOP working for various servlet engines? @@ -744,7 +744,7 @@ - + FOP in IBM Websphere
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2003/03/11 17:15:22 Modified:src/documentation/content/xdocs faq.xml Log: Add developer section. Add FAQ for obtaining javadocs. Revision ChangesPath 1.9 +11 -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.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- faq.xml 27 Jan 2003 00:49:44 - 1.8 +++ faq.xml 12 Mar 2003 01:15:22 - 1.9 @@ -1645,6 +1645,17 @@ +General Developer Questions + + How do I get the javadocs for FOP? + +Currently, the only way to get FOP javadocs is to +Download the source code and then Build +FOP using the ant build task "javadocs". + + + + General suggestions. How to solve problems. Where to post bugs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2003/03/11 17:08:53 Modified:src/documentation/content/xdocs Tag: fop-0_20_2-maintain faq.xml Log: Add developer section. Add FAQ for obtaining javadocs. Revision ChangesPath No revision No revision 1.3.2.6 +11 -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.3.2.5 retrieving revision 1.3.2.6 diff -u -r1.3.2.5 -r1.3.2.6 --- faq.xml 18 Feb 2003 12:27:34 - 1.3.2.5 +++ faq.xml 12 Mar 2003 01:08:52 - 1.3.2.6 @@ -1644,6 +1644,17 @@ +General Developer Questions + + How do I get the javadocs for FOP? + +Currently, the only way to get FOP javadocs is to +Download the source code and then Build +FOP using the ant build task "javadocs". + + + + General suggestions. How to solve problems. Where to post bugs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
pietsch 2003/01/26 16:49:44 Modified:lib ant.jar src/documentation/content/xdocs faq.xml Log: Actualization and some additions to the FAQ. Revision ChangesPath 1.8 +2361 -2665xml-fop/lib/ant.jar <> 1.8 +245 -154 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.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- faq.xml 5 Jan 2003 19:43:57 - 1.7 +++ faq.xml 27 Jan 2003 00:49:44 - 1.8 @@ -9,8 +9,8 @@ What is FOP? -FOP is a print formatter for XSL formatting -objects. +FOP is a print formatter for XSL formatting +objects. It can be used to render an XML file containing XSL formatting objects @@ -66,8 +66,8 @@ XSL is a W3C standard concerned with publishing XML documents. It - consists of two parts: XSLT and XSLFO. The acronym expands to + consists of two parts: XSLT and XSLFO. The acronym expands to eXtensible Stylesheet Language. @@ -123,21 +123,45 @@ Common stumbling blocks + Why does FOP insert a blank page between my page sequences? + + + This is because spec conformance has been improved. + + + The http://www.w3.org/TR/xsl/slice7.html#force-page-count";>force-page-count + property controls how a FO processor pads page sequences in + order to get certain page counts or last page numbers. The default is + "auto". With this setting, if the next page sequence + begins with an odd page number because you set the + initial-page-number, and the current page sequence also ends with an + odd page number, the processor inserts a blank page to keep odd and + even page numbers alternating (similar for the case the current page + sequence ends with an even page number and the next page sequence + starts with an even page number. + + + If you don't want to have this blank page, use + force-page-count="no-force". + + + + I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master' or 'page-sequence-master' - FOP was changed to be in accordance with the latest standard - (see XSL - standard).The page master for a fo:page-sequence is - now refereced by the master-reference attribute. Replace the - master-name attributes of your fo:page-sequence elements by - master-reference attributes. You have to do this also for - fo:single-page-master-reference, + FOP was changed to be in accordance with the latest standard (see + XSL standard).The page + master for a fo:page-sequence is now refereced by the + master-reference attribute. Replace the master-name attributes of + your fo:page-sequence elements by master-reference attributes. You + have to do this also for fo:single-page-master-reference, fo:repeatable-page-master-reference and - fo:conditional-page-master-reference elements in you page - master definitions. + fo:conditional-page-master-reference elements in you page master + definitions. See also release notes. @@ -151,17 +175,24 @@ The Jimi image library, which is by default used for processing images in PNG and other formats, was removed from the distribution for licensing reasons. You have to http://java.sun.com";>download +href="http://java.sun.com/products/jimi";>download and install it by yourself. + + Extract the file "JimiProClasses.zip" from the archive you've downloaded, rename it to "jimi-1.0.jar" and move it to FOP's lib directory. + + + An alternative to Jimi is to use Sun's JAI. It is much faster, but + not available for all platforms. + I get a NoClassDefFound exception. - This is typically a problem with your classpath. + This is typically a problem with your classpath. If you are running FOP from the command line: @@ -176,8 +207,8 @@ - If you run FOP embedded in your servlet, web application or other Java - application,
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml output.xml
pietsch 2003/01/05 11:43:57 Modified:.build.xml src/documentation/content/xdocs faq.xml output.xml Log: Added Ant target for validating xdocs. Some FAQ enhancments. Minor edits to output.xml. Revision ChangesPath 1.69 +62 -0 xml-fop/build.xml Index: build.xml === RCS file: /home/cvs/xml-fop/build.xml,v retrieving revision 1.68 retrieving revision 1.69 diff -u -r1.68 -r1.69 --- build.xml 30 Nov 2002 08:54:25 - 1.68 +++ build.xml 5 Jan 2003 19:43:56 - 1.69 @@ -148,6 +148,7 @@ + @@ -706,5 +707,66 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1.7 +250 -109 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.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- faq.xml 12 Dec 2002 10:59:33 - 1.6 +++ faq.xml 5 Jan 2003 19:43:57 - 1.7 @@ -78,9 +78,10 @@ XSLFO is an XML vocabulary that is used to specify a pagination and - other styling for page layout output. The acronym “FO” stands for + other styling for page layout output. The acronym “FO” + stands for Formatting Objects. XSLFO can be - used in conjunction with XSLT to convert + used in conjunction with XSLT to convert from any XML format into a paginated layout ready for printing or displaying. @@ -100,9 +101,9 @@ XSLT describes the transformation of arbitrary XML input into other - XML (like XSLFO), HTML or plain text. The “T” comes from + XML (like XSLFO), HTML or plain text. The “T” comes from Transformation. For historical reasons, a - transformation is often also called a “style sheet”. + transformation is often also called a “style sheet”. Synonyms: XSL transformation, XSL:T, XSL style sheet. @@ -147,9 +148,10 @@ My PNG images don't work. - The Jimi image library, which is used for processing images in PNG and - other formats, was removed from the distribution for licensing - reasons. You have to http://java.sun.com";>download + The Jimi image library, which is by default used for processing + images in PNG and other formats, was removed from the distribution + for licensing reasons. You have to http://java.sun.com";>download and install it by yourself. @@ -157,7 +159,9 @@ I get a NoClassDefFound exception. -This is typically a problem with your classpath. + + This is typically a problem with your classpath. If you are running FOP from the command line: @@ -207,16 +211,23 @@ -Avoid forward references. Forward references cause all -pages from the page with the reference on to be held in memory until -the page with the referenced element is encountered. Common forward +Increase memory settings of the JVM, see for example http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/java.html";>the + -Xmx option. Be aware that it is usually unwise to +increase the memory allocated to the JVM beyond the amount of +physical RAM, it will significantly slow down. YMMV. + + +Avoid forward references. Forward references cause all pages from +the page with the reference on to be held in memory until the +page with the referenced element is encountered. Common forward references are table of contents at the beginning of the document -and the "page N of TOTAL" in footers. Forward -references may be required by the task, however, if you are getting -a memory overflow you should at least check whether this is really -as necessary as claimed. A TOC, for example, could often be placed -at the end of the document without dimishing it's value too much, -the paper can be reshuffled af
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2002/12/09 11:37:44 Modified:src/documentation/content/xdocs faq.xml Log: Expanded FAQs related to PDF post-processing. Revision ChangesPath 1.5 +25 -14xml-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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- faq.xml 9 Dec 2002 18:23:13 - 1.4 +++ faq.xml 9 Dec 2002 19:37:44 - 1.5 @@ -873,24 +873,35 @@ (Still applicable in 0.20.3?) + + What tools are available for post-processing my PDF document? + + + The most popular one that we are aware of is http://www.lowagie.com/iText";>iText, which has tools for adding security features, document properties, watermarks, and many other features to PDF files. See also Joerg Pietschmann's http://marc.theaimsgroup.com/?l=fop-dev&m=102002975028427&w=2";>posting on PDF Encryption for an example of Java application using iText. +You can use Adobe Acrobat (the full version, not the Reader) to process the file manually or with scripting that it supports. + + + - PDF encryption, PDF protection (read-only) + How do I add security features (encryption, for example) to my PDF document? - use some other tool to postprocess the PDF (itext, or something?) +FOP does not currently support this feature. Possible workarounds include those mentioned in the PDF Post-Processing FAQ. - Watermarks + How do I add document properties (title, author, etc.) to my PDF document? - Answer: see 3.3, or use a a region overlapping the flowing text and put - an image there: - - > From: [EMAIL PROTECTED] -Use the region-before. Make it large enough to contain your image and then -include a block (and if required an absolutely positioned block-container) -with your image in the static-content for the region-before. - Could use some code here... - +FOP does not currently support this feature. Possible workarounds include those mentioned in the PDF Post-Processing FAQ. + + + + How do I add watermarks to my PDF document? + +FOP does not currently support this feature. Possible workarounds: + + See the PDF Post-Processing FAQ. + (submitted by [EMAIL PROTECTED]) Place an image in a region that overlaps the flowing text. For example, make region-before large enough to contain your image. Then include a block (if necessary, use an absolutely positioned block-container) containing the watermark image in the static-content for the region-before. + @@ -1340,8 +1351,8 @@ - - (FO) How do I validate my FO document? + + (FO) How do I validate my FO document? http://www.renderx.com";>RenderX has provided an http://www.renderx.com/Tests/validator/fo.dtd.html";>Unofficial DTD for FO Documents. This document may be helpful in validating general FO issues. FOP also maintains an http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/docs/foschema/fop.xsd?rev=HEAD&content-type=text/plain";>Unofficial FOP Schema in the FOP CVS Repository. This document can be used either to validate against the FO standard, or against the actual FOP implementation. See the notes near the beginning of the document for instructions on how to use it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml
vmote 2002/12/09 10:23:13 Modified:src/documentation/content/xdocs faq.xml Log: Add FAQ for FO validation, and refer other FAQs to it. Revision ChangesPath 1.4 +9 -2 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.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- faq.xml 29 Nov 2002 22:00:31 - 1.3 +++ faq.xml 9 Dec 2002 18:23:13 - 1.4 @@ -301,8 +301,8 @@ whether you got them right. - You can use the FOP DTD or FOP Schema to - validate your soure. This will catch most, but still not all problems. + You may find it helpful to use the validation tools to validate your +FO document. This will catch most problems, but should not be relied upon to catch all. If you use XSLT, problems in your style sheet and in your source XML @@ -1338,6 +1338,13 @@ Insert a graphic. GIF, PNG SVG, whatever. + + + + (FO) How do I validate my FO document? + +http://www.renderx.com";>RenderX has provided an http://www.renderx.com/Tests/validator/fo.dtd.html";>Unofficial DTD for FO Documents. This document may be helpful in validating general FO issues. +FOP also maintains an http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/docs/foschema/fop.xsd?rev=HEAD&content-type=text/plain";>Unofficial FOP Schema in the FOP CVS Repository. This document can be used either to validate against the FO standard, or against the actual FOP implementation. See the notes near the beginning of the document for instructions on how to use it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
