Hi Joerg, I have had a quick look over the document. Looks very good and comprehensive. I have attached a diff with some changes, mostly typos.
Should this be checked into the cvs trunk so it can be with the current docs. There was no commit email that I could find (not that it always works). On Fri, 2002-05-31 at 23:34, J.Pietschmann wrote: > The faq-big has been checked in, you are invited to proof-read > it. It's not yet integrated into the build process, and many links are > dead. I intend to write a few more documents the links will point to, > some are already in progress. Furthermore I have some plans to migrate > the FOP xdocs to the v11 DTDs under development now by forrest. I'd > like to have the old short FAQ kept active until everything else is > ready. > > Regards > J.Pietschmann
Index: docs/xml-docs/fop/faq-big.xml =================================================================== RCS file: /home/cvspublic/xml-fop/docs/xml-docs/fop/Attic/faq-big.xml,v retrieving revision 18.104.22.168 diff -u -r22.214.171.124 faq-big.xml --- docs/xml-docs/fop/faq-big.xml 29 May 2002 20:14:59 -0000 126.96.36.199 +++ docs/xml-docs/fop/faq-big.xml 6 Jun 2002 10:14:03 -0000 @@ -63,7 +63,7 @@ <answer> <p> XSL is a W3C standard concerned with publishing XML documents. It - consists of wo parts: <jump anchor="XSLT">XSLT</jump> and <jump + consists of two parts: <jump anchor="XSLT">XSLT</jump> and <jump anchor="XSLFO">XSLFO</jump>. The acronym expands to e<strong>X</strong>tensible <strong>S</strong>tylesheet <strong>L</strong>anguage. @@ -184,6 +184,10 @@ old XML tools in the classpath. Check in particular for parser.jar, jaxp.jar, xml4j.jar or lotusxsl.jar. </p> + <p> + Incompatible versions of Batik may also cause this problem. Use + the version of Batik that comes with FOP. + </p> </answer> </faq> <faq> @@ -202,7 +206,7 @@ <ul> <li> Avoid forward <link>references</link>. Forward references cause all - pages from the page with the reference on to be hold in memory until + 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 <link>"page N of TOTAL"</link> in footers. Forward @@ -304,6 +308,10 @@ separately to check for this, usually you'll get a detailed error message from the XSLT processor. </p> + <p> + If you turn on debugging with the "-d" option you may be able to + see more detailed information. + </p> </answer> </faq> <faq id=""> @@ -372,7 +380,7 @@ <question>FOP does not find my fonts.</question> <answer> <p> - Did you got: «Failed to read font metrics file C:\foo\arial.xml + Did you get: «Failed to read font metrics file C:\foo\arial.xml : File "C:\foo\arial.xml" not found»? The value for the metrics-file attribute in the user config file is actually an URL, not a file name. Use "file:///C:/foo/arial.xml" instead. @@ -699,13 +707,14 @@ <p> Even though the relevant methods of the Driver object are synchronized, there are still problems because FOP uses static - variables for configuration data. Be sure not to change the - configuration data while there is a Driver object rendering. It is - recommended to setup the configuration only once while initialising - the servlet. If you have to change the configuration data more often, - or if you have several servlets within the same webapp using FOP, - consider implementing a singleton class encapsulating both the - configuration settings and running FOP in synchronized methods. + variables for configuration data and loading images. Be sure not + to change the configuration data while there is a Driver object + rendering. It is recommended to setup the configuration only + once while initialising the servlet. If you have to change the + configuration data more often, or if you have several servlets + within the same webapp using FOP, consider implementing a + singleton class encapsulating both the configuration settings + and running FOP in synchronized methods. </p> </answer> </faq> @@ -788,8 +797,10 @@ <p> This is really a "resolving relative URI" problem with some twists. The problem is that the <code>#stuff</code> URL fragment - identifier is resolved against the FOP baseDir property, which is a - directory and not a good source for SVG snippets. Some options to try: + identifier is resolved within the current SVG document. So the + reference must be valid within the XML subset and it cannot + reference other SVG documents in the same XML file. Some options + to try: </p> <ul> <li> @@ -808,6 +819,10 @@ to deploy. </li> <li> + Make sure that the reference is valid in the current SVG document. + </li> + <li> + **DOES THIS WORK** Let the URL refer to some location where the gradient could be retrieved, for example if the SVG code is embedded in your XSL, try <code>fill="url(my.xsl#PurpleToWhite)"</code>. @@ -822,7 +837,7 @@ <p> Ultimately, both FOP and especially Batik should be fixed to make your code work as expected, but this will not only take some time - but also some efford by a standard committee in order to make the + but also some effort by a standard committee in order to make the semantics of this kind of references in embedded SVG clearer. </p> <p>See also <link>MalformedURLException</link></p> @@ -915,14 +930,14 @@ </li> <li> Give IEx the opportunity to cache. In particular, ensure the server - does not set any headers causing IEx not to cache the content. THis + does not set any headers causing IEx not to cache the content. This may be a real problem if the document is sent over HTTPS. Consult your server manual. </li> <li> Cache in the server. Including a parameter in the URL which has a timestamp as the value may help you to decide whether a request is - repeated. IEx is reported to retrieve a document up to trhee times, + repeated. IEx is reported to retrieve a document up to three times, but never more often. </li> </ul> @@ -932,7 +947,7 @@ <question>How do I print PDF directly from the browser?</question> <answer> <p> - It depends whether you men "printing to a printer under control of the + It depends whether you mean "printing to a printer under control of the server" or "printing on the client's printer". </p> <p> @@ -942,7 +957,7 @@ </p> <p> For the second task, you can use some client side script to start - Acrobat Reader in print mode, or use a or Java applet based on the FOP + Acrobat Reader in print mode, or use a Java applet based on the FOP print servlet. This depends heavily on the client installation and should not relied on except in tightly controlled environments. </p> @@ -1060,9 +1075,9 @@ section http://www.dpawson.co.uk/xsl/sect3/index.html </p> <p> - Define a page master mit alternating pages masters for odd and even + Define a page master with alternating pages masters for odd and even pages, specify appropriate regions in these page masters, and be sure - to give them different names. You use this names to put different + to give them different names. You use these names to put different static content in these regions. A self contained document demonstrating this: </p> @@ -1180,7 +1195,7 @@ XML, XSLT or FO. </p> <p> - Watch out for font traps, see #, change font teporarily using + Watch out for font traps, see #, change font temporarily using fo:inline if necessary. </p> <p> @@ -1289,7 +1304,7 @@ </p> <p> If you have a header region with an extent of 20mm, you should define - a to margin for the body region of at least 20mm too, otherwise the + a margin for the body region of at least 20mm too, otherwise the header content may overwrite some stuff in the body region. This applies similarly to the extent of the after region and the bottom margin of the body region. @@ -1443,4 +1458,4 @@ </answer> </faq> </faqsection> -</faqs> \ No newline at end of file +</faqs>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]