You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

faq.xml 50KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!--
  3. Licensed to the Apache Software Foundation (ASF) under one or more
  4. contributor license agreements. See the NOTICE file distributed with
  5. this work for additional information regarding copyright ownership.
  6. The ASF licenses this file to You under the Apache License, Version 2.0
  7. (the "License"); you may not use this file except in compliance with
  8. the License. You may obtain a copy of the License at
  9. http://www.apache.org/licenses/LICENSE-2.0
  10. Unless required by applicable law or agreed to in writing, software
  11. distributed under the License is distributed on an "AS IS" BASIS,
  12. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  13. See the License for the specific language governing permissions and
  14. limitations under the License.
  15. -->
  16. <!-- $Id$ -->
  17. <!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.1//EN" "http://forrest.apache.org/dtd/faq-v12.dtd">
  18. <faqs title="FOP FAQ">
  19. <part id="part-general">
  20. <title>General questions</title>
  21. <faq id="fop-general">
  22. <question>What is FOP?</question>
  23. <answer>
  24. <p>
  25. FOP is a print formatter for <link href="#XSLFO">XSL formatting
  26. objects</link>.
  27. </p>
  28. <p>
  29. It can be used to render an XML file containing XSL formatting objects
  30. into a page layout. The main target is PDF but other rendering targets
  31. are supported, such as AWT, PCL, text and direct printing.
  32. </p>
  33. </answer>
  34. </faq>
  35. <faq id="fop-functions">
  36. <question>What can I do with FOP?</question>
  37. <answer>
  38. <p>
  39. FOP provides both an application and a library that converts an XSL FO
  40. document into paginated output.
  41. </p>
  42. <p>
  43. The FOP command line application can be directly used to transform XML
  44. into PDF, PostScript, PCL and other formats, there is also an AWT
  45. based viewer integrated.
  46. </p>
  47. <p>
  48. The library can be used in servlets and other Java applications.
  49. </p>
  50. </answer>
  51. </faq>
  52. <faq id="fop-acronym">
  53. <question>What does "FOP" stand for?</question>
  54. <answer>
  55. <p>
  56. FOP is an acronym for <strong>F</strong>ormatting
  57. <strong>O</strong>bject <strong>P</strong>rocessor
  58. </p>
  59. </answer>
  60. </faq>
  61. <faq id="fop-other-apache">
  62. <question>How does FOP interact with other Apache Projects?</question>
  63. <answer>
  64. <p>
  65. FOP is distributed with <link
  66. href="http://xml.apache.org/cocoon">Cocoon</link> as a PDF serializer
  67. for XSL (FO) documents.
  68. </p>
  69. <p>
  70. <link href="http://xml.apache.org/batik">Batik</link> can be used with
  71. FOP to <link
  72. href="http://xml.apache.org/batik/svgrasterizer.html">transcode an SVG
  73. image</link> into a PDF document.
  74. </p>
  75. </answer>
  76. </faq>
  77. <faq id="xsl-def">
  78. <question>What is XSL?</question>
  79. <answer>
  80. <p>
  81. XSL is a W3C standard concerned with publishing XML documents. It
  82. consists of two parts: <link href="#XSLT">XSLT</link> and <link
  83. href="#XSLFO">XSLFO</link>. The acronym expands to
  84. e<strong>X</strong>tensible <strong>S</strong>tylesheet
  85. <strong>L</strong>anguage.
  86. </p>
  87. </answer>
  88. </faq>
  89. <faq id="xslfo">
  90. <question>What is XSL-FO?</question>
  91. <answer>
  92. <p>
  93. XSLFO (aka XSL-FO) is an XML vocabulary that is used to specify a pagination and
  94. other styling for page layout output. The acronym &#8220;FO&#8221;
  95. stands for
  96. <strong>F</strong>ormatting <strong>O</strong>bjects. XSLFO can be
  97. used in conjunction with <link href="#XSLT">XSLT</link> to convert
  98. from any XML format into a paginated layout ready for printing or
  99. displaying.
  100. </p>
  101. <p>
  102. XSLFO defines a set of elements in XML that describes the way pages
  103. are set up. The contents of the pages are filled from flows. There can
  104. be static flows that appear on every page (for headers and footers)
  105. and the main flow which fills the body of the page.
  106. </p>
  107. <p>
  108. Synonyms: XSL FO, XSL (FO), XSL:FO, XSL-FO, Formatting Objects
  109. </p>
  110. </answer>
  111. </faq>
  112. <faq id="XSLT">
  113. <question>What is XSLT?</question>
  114. <answer>
  115. <p>
  116. XSLT describes the transformation of arbitrary XML input into other
  117. XML (like XSLFO), HTML or plain text. The &#8220;T&#8221; comes from
  118. <strong>T</strong>ransformation. For historical reasons, a
  119. transformation is often also called a &#8220;style sheet&#8221;.
  120. </p>
  121. <p>
  122. Synonyms: XSL transformation, XSL:T, XSL style sheet.
  123. </p>
  124. </answer>
  125. </faq>
  126. <faq id="when">
  127. <question>When will feature X be implemented?</question>
  128. <answer>
  129. <p>The short answer is "Don't ask." For more details, see <link href="gethelp.html#limitations">Understand FOP's Limitations</link>.</p>
  130. </answer>
  131. </faq>
  132. <faq id="next-release">
  133. <question>When is the next released planned?</question>
  134. <answer>
  135. <p>
  136. When it's ready and the committers have enough time to go through
  137. the time-consuming process of creating a release. We
  138. released version 0.93 on 9 January 2007, and intend to
  139. release version 1.0 later in 2007. If you
  140. want to speed up the process, consider to
  141. <link href="dev/index.html#involved">contribute</link> to FOP.</p>
  142. </answer>
  143. </faq>
  144. <faq id="redesign">
  145. <question>Why did you redesign FOP?</question>
  146. <answer>
  147. <p>The code redesign of FOP was necessary in order to be able to adress following issues:</p>
  148. <ul>
  149. <li>Keeps and Breaks</li>
  150. <li>XSL-FO Compliance in general</li>
  151. <li>Process Files of Arbitrary Size</li>
  152. <li>Minimize Memory Use</li>
  153. <li>Table Layout</li>
  154. </ul>
  155. </answer>
  156. </faq>
  157. <faq id="contribute">
  158. <question>How can I contribute?</question>
  159. <answer>
  160. <p>
  161. There are numerous ways that you can help. They are outlined in the <link href="dev/index.html">Developer's Introduction</link> page.
  162. </p>
  163. </answer>
  164. </faq>
  165. </part>
  166. <part id="part-running">
  167. <title>Problems running FOP</title>
  168. <faq id="no-page-master">
  169. <question>I get the error: [ERROR]: 'master-reference' for
  170. 'fo:page-sequence'matches no 'simple-page-master' or
  171. 'page-sequence-master'</question>
  172. <answer>
  173. <p>
  174. FOP was changed to be in accordance with the latest standard (see
  175. <link href="resources.html#w3-xsl">XSL standard</link>).The page
  176. master for a fo:page-sequence is now refereced by the
  177. master-reference attribute. Replace the master-name attributes of
  178. your fo:page-sequence elements by master-reference attributes. You
  179. have to do this also for fo:single-page-master-reference,
  180. fo:repeatable-page-master-reference and
  181. fo:conditional-page-master-reference elements in you page master
  182. definitions.
  183. </p>
  184. <p>
  185. Update your FO documents and style sheets.
  186. </p>
  187. </answer>
  188. </faq>
  189. <faq id="NoClassDefFound">
  190. <question>I get a NoClassDefFound exception.</question>
  191. <answer>
  192. <p>This is typically a problem with your classpath.</p>
  193. <p>If you are running FOP from the command line:</p>
  194. <ul>
  195. <li>
  196. Use the <code>fop.bat</code>, <code>fop</code> or <code>fop.sh</code> command file from the FOP
  197. distribution. If you have a FOP version older than 0.20.5,
  198. ensure the directory where FOP and these files have been
  199. installed is the current working directory.
  200. </li>
  201. <li>
  202. If this doesn't help, check whether still all the jar files
  203. mentioned in the classpath in the <code>fop.bat</code> file are in their
  204. respective places.
  205. </li>
  206. </ul>
  207. <p>
  208. If you run FOP embedded in your servlet, web application or
  209. other Java application, check the classpath of the
  210. application. Check the also the information pertaining to <link
  211. href="0.93/servlets.html#servlet-engine">servlet engines</link>
  212. for further hints.
  213. </p>
  214. <p>
  215. If you downloaded the source distribution, or a snapshop
  216. from the repository, remember you have to build the FOP jars
  217. first.
  218. </p>
  219. </answer>
  220. </faq>
  221. <faq id="NoSuchMethodException">
  222. <question>I get a NoSuchMethodException or a NoSuchFieldException
  223. exception.</question>
  224. <answer>
  225. <p>
  226. This is usually caused by an older version of one of the FOP jars or
  227. old XML tools in the classpath. Check in particular for parser.jar,
  228. jaxp.jar, xml4j.jar or lotusxsl.jar.
  229. </p>
  230. <p>
  231. Incompatible versions of Batik may also cause this problem. Use the
  232. version of Batik that comes with FOP. It is not always possible to
  233. use a more recent version of Batik.
  234. </p>
  235. </answer>
  236. </faq>
  237. <faq id="OutOfMemoryException">
  238. <question>I get an OutOfMemoryException.</question>
  239. <answer>
  240. <p>
  241. See <link href="0.93/running.html#memory">FOP Memory</link>.
  242. </p>
  243. </answer>
  244. </faq>
  245. <faq id="MalformedURLException">
  246. <question>I get a MalformedURLException.</question>
  247. <answer>
  248. <anchor id="MalformedURL"/>
  249. <p>
  250. What you probably think of as "file names" are usually URLs, in
  251. particular the <code>src</code> attribute of fo:external-graphic.
  252. </p>
  253. <p>
  254. Because usage of URLs is growing, you should make yourself familiar
  255. with it. The relevant specification is <link
  256. href="http://www.rfc-editor.org/rfc/rfc2396.txt">RFC 2396</link>.
  257. </p>
  258. <p>
  259. In a nutshell, the correct syntax for an absolute file URL is
  260. <code>file:///some/path/file.ext</code> on Unix and
  261. <code>file:///z:/some/path/file.ext</code> on Windows systems. Note
  262. the triple slash, and also that only forward slashes are used, even on
  263. windows.
  264. </p>
  265. <p>
  266. A relative file URL starts with anything but a slash, and doesn't have
  267. the <code>file:</code> prefix, for example <code>file.ext</code>,
  268. <code>path/file.ext</code> or <code>../file.ext</code>. The string
  269. <code>file:path/file.ext</code> is <em>not</em> a relative URL,
  270. in fact, it isn't a valid URL at all. A relative URL is subject to a
  271. resolving process, which transforms it into an absolute
  272. URL.
  273. </p>
  274. <!--p>
  275. See Understanding URIs and URLs and Understanding
  276. URL resolving.
  277. </p-->
  278. </answer>
  279. </faq>
  280. <faq id="NullPointerException">
  281. <question>I get an "[ERROR]: null", or a NullPointerException.</question>
  282. <answer>
  283. <p>
  284. This is often caused by an invalid FO document. Currently only very
  285. common errors are intercepted and produce a comprehensible error
  286. message. If you forgot container elements like <code>fo:page-sequence</code> or
  287. <code>fo:flow</code> and put blocks and inline elements directly as children of
  288. <code>fo:root</code> or <code>fo:page-sequence</code>, you'll only get a
  289. NullPointerException. Check whether your FO file has a proper
  290. structure. In some cases there are mandatory properties, like the
  291. master-reference in <code>fo:conditional-page-master-reference</code>, check also
  292. whether you got them right.
  293. </p>
  294. <p>
  295. You may find it helpful to use the <link href="#FO-validate">validation tools</link> to validate your
  296. FO document. This will catch most problems, but should not be
  297. relied upon to catch all.
  298. </p>
  299. <p>
  300. If you use XSLT, problems in your style sheet and in your
  301. source XML also can produce a NullPointerException. <link
  302. href="0.93/running.html#check-input">Run the transformation
  303. separately</link> to check for this, usually you'll get a
  304. detailed error message from the XSLT processor.
  305. </p>
  306. <p>
  307. If you turn on debugging with the "<code>-d</code>" option you may be able to
  308. see more detailed information.
  309. </p>
  310. </answer>
  311. </faq>
  312. <faq id="not-implemented">
  313. <question>FOP returns the message "[ERROR] <em>object|property - 'x'</em> is not implemented yet." When will it be implemented?</question>
  314. <answer>
  315. <p>See FOP's Standards <link href="compliance.html">Compliance</link> page.</p>
  316. </answer>
  317. </faq>
  318. <faq id="fop-hangs">
  319. <question>FOP hangs. FOP does not exit.</question>
  320. <answer>
  321. <p>
  322. The most likely reason is a known problem with the Java run time
  323. environment which is triggered by rendering SVGs. Suns JDK 1.4 does
  324. not have this problem. See also <link href="#svghangs">FOP does not
  325. exit if a SVG is included</link>.
  326. </p>
  327. <p>
  328. Another possibility is that FOP went into a non terminating
  329. loop. Usually this is indicated by lots of log messages of the form
  330. "[INFO]: [NNNN]" which indicate a new page has been started or <link
  331. href="#boxoverflow">box overflows</link>. After some time, FOP will
  332. crash with an OutOfMemoryException.
  333. </p>
  334. <p>
  335. If you called the FOP command line application from some other
  336. programm, for example from Java using Runtime.exec(), it may hang
  337. while trying to write log entries to the output pipe. You have to read
  338. the FOP output regularly to empty the pipe buffer. It is best to avoid
  339. exec'ing FOP, use the library interface instead.
  340. </p>
  341. </answer>
  342. </faq>
  343. <faq id="boxoverflow">
  344. <question>FOP runs forever, writing lots of "&gt;" to the log.</question>
  345. <answer>
  346. <p>
  347. There is something too large to fit into the intended place, usually a
  348. large image, a table whose rows are kept together or a block with a
  349. space-before or space-after larger than the page size. Catch the first
  350. page showing this phenomenon and check it. If it is not obvious which
  351. element causes the trouble, remove stuff until the problem goes
  352. away. Decrease the dimensions of the offending element or property, or
  353. increase the dimension of the enclosing element or container, or
  354. remove keep-with-* properties.
  355. </p>
  356. </answer>
  357. </faq>
  358. <faq id="cannot-find-external-graphics">
  359. <question>FOP cannot find a file for fo:external-graphics.</question>
  360. <answer>
  361. <p>The src attribute of the <code>fo:external-graphics</code> element requires a URI, not a file name. See <link href="fo.html#external-resources">External Resources</link> for more information about specifying URIs.</p>
  362. </answer>
  363. </faq>
  364. <faq id="fonts-not-found">
  365. <question>FOP does not find my fonts.</question>
  366. <answer>
  367. <p>
  368. Did you get: &#171;Failed to read font metrics file C:\foo\arial.xml
  369. : File "C:\foo\arial.xml" not found&#187;? The value for the
  370. metrics-file attribute in the user config file is actually an URL, not
  371. a file name. Use "file:///C:/foo/arial.xml" instead.
  372. </p>
  373. <p>
  374. If you used a relative URL, make sure your application has the working
  375. directory you expect. Currently FOP does not use the baseDir for
  376. resolving relative URLs pointing to font metric files.
  377. </p>
  378. <p>
  379. Try also setting the <link
  380. href="0.93/configuration.html#general-elements">font-base
  381. configuration</link>.
  382. </p>
  383. </answer>
  384. </faq>
  385. </part>
  386. <part id="part-output">
  387. <title>Problems with FOP output</title>
  388. <faq id="leader-expansion">
  389. <question>Leaders don't work anymore in 0.93. Instead of
  390. filling the line, only three dots or a short ruler is
  391. output.</question>
  392. <answer>
  393. <p>
  394. Leaders still work, in fact they work better than ever
  395. before. You'll just have to add <code>text-align="justify"</code> and/or
  396. <code>text-align-last="justify"</code> to the block with the leader. Be
  397. sure you haven't accidentally overridden the
  398. <code>leader-length.maximum="100%"</code> default value.
  399. </p>
  400. <p>
  401. Earlier versions of FOP used to expand a leader to fill the
  402. rest of the line unconditionally, anything following it,
  403. like page numbers in a TOC, was actually shifted beyong the
  404. right margin.
  405. </p>
  406. <p>
  407. The new implementation uses leader-length.optimum to
  408. determine where to break the line, and expands the leader
  409. only further if the line should be filled, as indicated by
  410. the text-aling and text-align-last properties.
  411. </p>
  412. <p>
  413. Actually due to the fuzzyness of the specification both the
  414. old and the new method are conformant (although adding text
  415. after the expanded leader in the old variant never was).
  416. </p>
  417. <p>
  418. If you want to have a longer ruler or space in a
  419. non-justified line, you have to increase the
  420. leader-length.optimum property.
  421. </p>
  422. </answer>
  423. </faq>
  424. <faq id="blank-page-between-page-sequences">
  425. <question>Why does FOP insert a blank page between my page sequences?</question>
  426. <answer>
  427. <p>
  428. This is because spec conformance has been improved.
  429. </p>
  430. <p>
  431. The <link
  432. href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#force-page-count">force-page-count
  433. property</link> controls how a FO processor pads page sequences in
  434. order to get certain page counts or last page numbers. The default is
  435. "<code>auto</code>". With this setting, if the next page sequence
  436. begins with an odd page number because you set the
  437. initial-page-number, and the current page sequence also ends with an
  438. odd page number, the processor inserts a blank page to keep odd and
  439. even page numbers alternating (similar for the case the current page
  440. sequence ends with an even page number and the next page sequence
  441. starts with an even page number.
  442. </p>
  443. <p>
  444. If you don't want to have this blank page, use
  445. <code>force-page-count="no-force"</code>.
  446. </p>
  447. </answer>
  448. </faq>
  449. <faq id="graphic-not-displayed">
  450. <question>Why is my graphic not rendered?</question>
  451. <answer>
  452. <p>Most commonly, the external file is not being found by FOP.
  453. Check the following:</p>
  454. <ul>
  455. <li>Empty or wrong baseDir setting.</li>
  456. <li>Spelling errors in the file name (including using the wrong case).</li>
  457. <li>Security Problems (i.e. the image could not be accessed
  458. because FOP is not allowed to read the file). This is
  459. especially a problem if the external file is retrieved over
  460. HTTP. Possible issues include security settings on the
  461. server, server configuration, and missing cookies or other
  462. authorization information. Any easy way to check this is to
  463. cut&amp;paste the source URL from the fo:external-graphic
  464. into the Location field of a browser <strong>on the machine
  465. where the FOP process will be running</strong>.</li>
  466. </ul>
  467. <p>Other possibilities:</p>
  468. <ul>
  469. <li>The image format is not supported or not supported completely.
  470. See <link href="0.93/graphics.html">FOP Graphics Formats</link> for a
  471. list of supported formats and related issues.</li>
  472. <li>The graphic may be too large to fit into the intended space.</li>
  473. <li>There may be something (static content) that is obscuring the
  474. graphic. (This is very rare).
  475. </li>
  476. </ul>
  477. </answer>
  478. </faq>
  479. <faq id="png-fails">
  480. <question>My graphical images do not work properly.</question>
  481. <answer>
  482. <p>See <link href="0.93/graphics.html">FOP Graphics Formats</link> for a
  483. list of supported graphics formats and related issues.</p>
  484. </answer>
  485. </faq>
  486. <faq id="graphic-resolution">
  487. <question>Why is my graphic rendered at a different resolution than it was created?</question>
  488. <answer>
  489. <p>See <link href="0.93/graphics.html#resolution">Graphics Resolution</link>.</p>
  490. </answer>
  491. </faq>
  492. <faq id="keep-with">
  493. <question>Keep-with-next, keep-with-previous, keep-together
  494. don't work.</question>
  495. <answer>
  496. <p>
  497. These properties are not implemented on version 0.20.5 and earlier, except on table rows. In
  498. order to take advantage of them, you have to nest stuff to be
  499. kept together in a table.
  500. </p>
  501. <p>
  502. The concept is called &#8220;blind table&#8221;. The table is used for
  503. pure layout reasons and is not obvious in the output.
  504. </p>
  505. <p>
  506. An example of an image and the image caption to be kept together:
  507. </p>
  508. <source><![CDATA[<fo:table table-layout="fixed" width="100%">
  509. <fo:table-column column-width="proportional-column-width(1)"/>
  510. <fo:table-body>
  511. <fo:table-row keep-with-next="always">
  512. <fo:table-cell>
  513. <fo:block>
  514. <fo:external-graphic src="foo.jpg"/>
  515. </fo:block>
  516. </fo:table-cell>
  517. </fo:table-row>
  518. <fo:table-row>
  519. <fo:table-cell>
  520. <fo:block>Image Caption</fo:block>
  521. </fo:table-cell>
  522. </fo:table-row>
  523. </fo:table-body>
  524. </fo:table>]]></source>
  525. <p>
  526. Consider upgrading to the latest version which supports keeps.
  527. </p>
  528. </answer>
  529. </faq>
  530. <faq id="table-missing">
  531. <question>My tables are missing, or missing their content.</question>
  532. <answer>
  533. <p>
  534. Check for <code>fo:table-body</code> around the rows. FOP up to 0.20.4 doesn't
  535. raise an error if it is omitted, it just drops the content. More
  536. recent releases will catch this problem.
  537. </p>
  538. <p>
  539. Also, the <code>fo:table-with-caption</code> element is not implemented, tables
  540. within such an element are dropped too. FOP generates an error
  541. message for this problem. Older DocBook style sheets generate
  542. <code>fo:table-with-caption</code> elements, so watch out.
  543. </p>
  544. </answer>
  545. </faq>
  546. <faq id="cells-overflow">
  547. <question>Text overflowing table cells and the like is not clipped. Long
  548. text flows into adjacent cells/block, obscuring stuff there.</question>
  549. <answer>
  550. <p>
  551. Clipping as specified by the <code>overflow="hidden"</code> is not yet
  552. implemented. If you have long words overflowing table cells, try to
  553. get them hyphenated. Artificial names like product identifications or
  554. long numbers usually aren't hyphenated. You can try special processing
  555. at XSLT level, like
  556. </p>
  557. <ul>
  558. <li>
  559. clip long text,
  560. </li>
  561. <li>
  562. explicit wrapping+clipping,
  563. </li>
  564. <li>
  565. insert zero width spaces (U+200B or &amp;#x200B;) to allow FOP to
  566. wrap.
  567. </li>
  568. </ul>
  569. <p>
  570. Check the <link href="http://dpawson.co.uk/xsl">XSL FAQ</link> and the
  571. <link href="http://www.mulberrytech.com/xsl/xsl-list/">XSL list
  572. archive</link> for how to perform these tasks.
  573. </p>
  574. </answer>
  575. </faq>
  576. <faq id="page-number-align">
  577. <question>Page numbers are not properly right aligned.</question>
  578. <answer>
  579. <p>
  580. This happens for <code>fo:page-number-citation</code> elements if the
  581. citation occurs before FOP formatted the requested page,
  582. usually in TOC or index pages. It is caused by the problem
  583. that FOP has to guess how much space the yet unknown page
  584. number will occupy, and usually the guesses are somewhat
  585. off.
  586. </p>
  587. <p>
  588. The most recent FOP releases should have this problem
  589. fixed. Check whether you can upgrade.
  590. </p>
  591. </answer>
  592. </faq>
  593. <faq id="hyphenation-fails">
  594. <question>Hyphenation does not work.</question>
  595. <answer>
  596. <p>Make sure you have set the language and optionally the country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):</p>
  597. <source><![CDATA[<fo:page-sequence language="fi">]]></source>
  598. <p>See <link href="0.93/hyphenation.html#support">Hyphenation Support</link> for details and instructions on using hyphenation with FOP.</p>
  599. <p>Explicitly enable hyphenation for an appropriate XSL-FO element (fo:block, fo:character):</p>
  600. <source><![CDATA[<fo:block hyphenate="true">]]></source>
  601. </answer>
  602. </faq>
  603. <faq id="indent-inheritance">
  604. <question>When I use margins, my content in a nested table or block-containers gets indented twice. Is this a bug?</question>
  605. <answer>
  606. <p>
  607. (Applies to version 0.90 and later)
  608. No, although you might easily think so. The problem has to do
  609. with property inheritance of the start-indent and end-indent
  610. properties to which the margin properties are mapped. Apache
  611. FOP strictly adheres to the XSL-FO specification here which many
  612. other commercial FO implementations don't do to better meet end-user
  613. expectations. You can make FOP behave like these if you set
  614. <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code>
  615. on the FOUserAgent. The better way is to reset <code>start-indent</code>
  616. and <code>end-indent</code> to "0pt" on table-body or block-container.
  617. For further details, please consult the
  618. <link href="http://wiki.apache.org/xmlgraphics-fop/IndentInheritance">Wiki page on Indent Inheritance</link>.
  619. </p>
  620. </answer>
  621. </faq>
  622. </part>
  623. <part id="part-embedding">
  624. <title>Embedding FOP. Using FOP in a servlet.</title>
  625. <faq id="servlet">
  626. <question>How do I use FOP in a servlet?</question>
  627. <answer>
  628. <p>
  629. See <link href="0.93/servlets.html">Using FOP in a Servlet</link>.
  630. </p>
  631. </answer>
  632. </faq>
  633. <faq id="servlet-with-xslt">
  634. <question>How do I use FOP in a servlet with an XSLT
  635. transformation?</question>
  636. <answer>
  637. <p>
  638. See <link href="0.93/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
  639. </p>
  640. </answer>
  641. </faq>
  642. <faq id="servlet-xslt-params">
  643. <question>How do I pass parameters to the XSLT transformation?</question>
  644. <answer>
  645. <p>
  646. See <link href="0.93/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
  647. </p>
  648. </answer>
  649. </faq>
  650. <faq id="servlet-nonstd-fonts">
  651. <question>How do I use my own fonts when running FOP from a servlet?</question>
  652. <answer>
  653. <p>
  654. Declare the fonts in the <code>userconfig.xml</code> file as usual.
  655. See <link href="#usercfg">loading the user configuration file</link>
  656. for further details.
  657. </p>
  658. </answer>
  659. </faq>
  660. <faq id="servlet-baseDir">
  661. <question>How do I set the baseDir property in a servlet environment?</question>
  662. <answer>
  663. <p>
  664. See <link href="0.93/embedding.html#config-internal">Setting the Configuration Programmatically</link>.
  665. </p>
  666. </answer>
  667. </faq>
  668. <faq id="usercfg">
  669. <question>How do I use a user configuration file from a servlet?</question>
  670. <answer>
  671. <p>
  672. See <link href="0.93/embedding.html#config-external">Using a Configuration File in an Embedded App</link>.
  673. </p>
  674. </answer>
  675. </faq>
  676. <faq id="servlet-NoClassDefFound">
  677. <question>I keep getting NoClassDefFound and other exceptions. How do I
  678. get FOP working for various servlet engines?</question>
  679. <answer>
  680. <p>
  681. See <link href="0.93/servlets.html#servlet-engine">Servlet Engines</link>.
  682. </p>
  683. </answer>
  684. </faq>
  685. <faq id="multithreaded">
  686. <question>Can FOP be used in multithreaded environments?</question>
  687. <answer>
  688. <p>
  689. See <link href="0.93/embedding.html#multithreading">Multithreading FOP</link>.
  690. </p>
  691. </answer>
  692. </faq>
  693. </part>
  694. <part id="part-svg">
  695. <title>SVG specific questions</title>
  696. <faq id="svg-text">
  697. <question>The rendering of SVG text in my PDF is of poor quality.
  698. Can I control this?</question>
  699. <answer>
  700. <p>See <link href="0.93/graphics.html#svg-pdf-text">Placing SVG Text into PDF</link>.</p>
  701. </answer>
  702. </faq>
  703. <faq id="svg-headless">
  704. <question>How do I use FOP with SVG on headless servers?</question>
  705. <answer>
  706. <p>See <link href="0.93/graphics.html#batik">FOP: Graphics (Batik)</link>.</p>
  707. </answer>
  708. </faq>
  709. <faq id="svghangs">
  710. <question>FOP does not exit if a SVG is included.</question>
  711. <answer>
  712. <p>
  713. Applies to older FOP versions and JDK 1.3 and older. That's because
  714. there is an AWT thread hanging around. The solution is to put a
  715. System.exit(0) somewhere.
  716. </p>
  717. </answer>
  718. </faq>
  719. <faq id="svg-url">
  720. <question>I have problems with SVG referring to gradients etc. using
  721. "uri(#stuff)". I get a MalformedURLException.</question>
  722. <answer>
  723. <p>
  724. This is really a "resolving relative URI" problem with some
  725. twists. The problem is that the <code>#stuff</code> URL fragment
  726. identifier is resolved within the current SVG document. So the
  727. reference must be valid within the XML subset and it cannot
  728. reference other SVG documents in the same XML file. Some options
  729. to try:
  730. </p>
  731. <ul>
  732. <li>
  733. Put the SVG into a separate file and use it with
  734. fo:external-graphics.
  735. </li>
  736. <li>
  737. Use a separate SVG file which contains only the gradient (and
  738. perhaps other SVG stuff you want to reference) and point an absolute
  739. URL to it:
  740. <code>fill="url(file:///c:/refstuff/grad.svg#PurpleToWhite)"</code>.
  741. </li>
  742. <li>
  743. Same as above but use a relative URL:
  744. <code>fill="url(grad.svg#PurpleToWhite)"</code>. This may be easier
  745. to deploy.
  746. </li>
  747. <li>
  748. Make sure that the reference is valid in the current SVG document.
  749. </li>
  750. </ul>
  751. <p>
  752. In any case, the referenced stuff has to be pointed to by an URL. It
  753. doesn't necessarily have to be a file URL, HTTP should also
  754. work. Also, expect a performance hit in all cases, because another XML
  755. file has to be retrieved and parsed.
  756. </p>
  757. <p>
  758. Ultimately, both FOP and especially Batik should be fixed to make
  759. your code work as expected, but this will not only take some time
  760. but also some effort by a standard committee in order to make the
  761. semantics of this kind of references in embedded SVG clearer.
  762. </p>
  763. <p>See also <link href="#MalformedURL">MalformedURLException</link></p>
  764. </answer>
  765. </faq>
  766. <faq id="svg-scaling">
  767. <question>Why is my SVG rendered at a size different from that specified in my fo:external-graphic element?</question>
  768. <answer>
  769. <p>See <link href="0.93/graphics.html#svg-scaling">SVG Scaling</link>.</p>
  770. </answer>
  771. </faq>
  772. <faq id="svg-attribute-required">
  773. <question>FOP fails with something like "The attribute "width" of the element &lt;rect&gt; is required". What's wrong?</question>
  774. <answer>
  775. <p>
  776. This phenomenon occurs since FOP 0.92 beta. It surfaced due to a change in the handling of non-FO namespaces. It's not a
  777. bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be
  778. fixed in the next release. In the latest release of Apache Xalan-J, the bug is already fixed. It only occurs in the Xalan
  779. version bundled with Sun's JVM, because Sun uses a rather old version.
  780. </p>
  781. <p>
  782. Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with
  783. <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate
  784. the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty
  785. string as the namespace URI parameter for <code>org.w3c.dom.Element.setAttributeNS()</code>.
  786. </p>
  787. <p>
  788. Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J
  789. on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the
  790. <link href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</link>, i.e.
  791. you must place Xalan-J in the <code>"lib/endorsed"</code> directory of your JRE.
  792. </p>
  793. </answer>
  794. </faq>
  795. </part>
  796. <part id="part-pdf">
  797. <title>PDF specific (includes Acrobat peculiarities)</title>
  798. <faq id="pdf-embed-font">
  799. <question>How do I embed fonts in PDF?</question>
  800. <answer>
  801. <p>
  802. See the <link href="0.93/fonts.html">Fonts</link> page for information
  803. about embedding fonts.
  804. </p>
  805. </answer>
  806. </faq>
  807. <faq id="pdf-characters">
  808. <question>Some characters are not displayed, or displayed incorrectly, or
  809. displayed as &#8220;#&#8221;.</question>
  810. <answer>
  811. <p>
  812. This usually means the selected font doesn't have a glyph
  813. for the character.
  814. </p>
  815. <p>
  816. The standard text fonts supplied with Acrobat Reader have
  817. mostly glyphs for characters from the ISO Latin 1 character
  818. set. For a variety of reasons, even those are not completely
  819. guaranteed to work, for example you can't use the fi
  820. ligature from the standard serif font. Check the <link
  821. href="0.93/output.html#pdf-fonts">overview</link> for the default
  822. PDF fonts.
  823. </p>
  824. <p>
  825. If you use your own fonts, the font must have a glyph for
  826. the desired character. Furthermore the font must be
  827. available on the machine where the PDF is viewed or it must
  828. have been embedded in the PDF file. See <link
  829. href="0.93/fonts.html">embedding fonts</link>.
  830. </p>
  831. <p>
  832. For most symbols, it is better to select the symbol font
  833. explicitely, for example in order to get the symbol for the
  834. mathematical empty set, write:
  835. </p>
  836. <source><![CDATA[<fo:inline font-family="Symbol">&#x2205;</fo:inline>]]></source>
  837. <p>
  838. The "#" shows up if the selected font does not define a glyph for the
  839. required character, for example if you try:
  840. </p>
  841. <source><![CDATA[<fo:inline font-family="Helvetica">&#x2205;</fo:inline>]]></source>
  842. </answer>
  843. </faq>
  844. <faq id="pdf-postprocess">
  845. <question>What tools are available for post-processing my PDF document?</question>
  846. <answer>
  847. <p>See <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
  848. </answer>
  849. </faq>
  850. <faq id="pdf-security">
  851. <question>How do I add security features (encryption, disable printing)
  852. to my PDF document?</question>
  853. <answer>
  854. <p>
  855. See <link href="0.93/pdfencryption.html">PDF Encryption</link>.
  856. See also <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.
  857. </p>
  858. </answer>
  859. </faq>
  860. <faq id="pdf-doc-properties">
  861. <question>How do I add document properties (title, author, etc.) to my
  862. PDF document?</question>
  863. <answer>
  864. <p>See <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
  865. </answer>
  866. </faq>
  867. <faq id="pdf-watermark">
  868. <question>How do I add watermarks to my PDF document?</question>
  869. <answer>
  870. <p>See <link href="0.93/output.html#pdf-watermark">PDF Watermarks</link>.</p>
  871. </answer>
  872. </faq>
  873. <faq id="pdf-print-contortion">
  874. <question>The PDF is printed contorted!</question>
  875. <answer>
  876. <p>
  877. Check the paper size in Acrobat settings and the "fit to page" print
  878. setting. Contorted printing is often caused by a mismatched paper
  879. format, for example if the setting is "US Letter" but the PDF was
  880. made for A4. Sometimes also the printer driver interferes, check its
  881. settings too.
  882. </p>
  883. </answer>
  884. </faq>
  885. <faq id="pdf-bookmark-display">
  886. <question>How do I control the Acrobat bookmark display?</question>
  887. <answer>
  888. <p>
  889. FOP does not currently support this feature. Possible workarounds
  890. include those mentioned in the <link href="#PDF-postprocess">PDF
  891. Post-Processing FAQ</link>.
  892. </p>
  893. </answer>
  894. </faq>
  895. </part>
  896. <part id="part-iex">
  897. <title>IEx specific stuff</title>
  898. <faq id="iex-servlet-multiple">
  899. <question>The FOP servlet is called multiple times!</question>
  900. <answer>
  901. <p>
  902. This is a problem of Internet Explorer requesting the content several
  903. times. Please see the <link href="0.93/servlets.html#ie">notes on Internet Explorer</link>
  904. for more information.
  905. </p>
  906. </answer>
  907. </faq>
  908. <faq id="iex-pdf-print-from-browser">
  909. <question>How do I print PDF directly from the browser?</question>
  910. <answer>
  911. <p>
  912. It depends whether you mean "printing to a printer under control of
  913. the server" or "printing on the client's printer".
  914. </p>
  915. <p>
  916. For the first problem, look at the print servlet in the FOP
  917. examples. You'll have to gather any printer settings in a HTML form
  918. and send it to the server.
  919. </p>
  920. <p>
  921. For the second task, you can use some client side script to start
  922. Acrobat Reader in print mode, or use a Java applet based on the FOP
  923. print servlet. This depends heavily on the client installation and
  924. should not relied on except in tightly controlled environments.
  925. </p>
  926. <p>
  927. See also <link href="http://marc.theaimsgroup.com/?l=fop-dev&amp;m=101065988325115&amp;w=2">http://marc.theaimsgroup.com/?l=fop-dev&amp;m=101065988325115&amp;w=2</link>
  928. </p>
  929. </answer>
  930. </faq>
  931. </part>
  932. <part id="part-input">
  933. <title>General questions regarding XSLT, XSLFO, and basic XML</title>
  934. <faq id="fo-center">
  935. <question>(FO) How do I vertically center an image or a table (or
  936. whatever)?</question>
  937. <answer>
  938. <p>
  939. See <link href="fo.html#fo-center-vertical">XSL-FO Vertical Centering</link>.
  940. </p>
  941. </answer>
  942. </faq>
  943. <faq id="fo-center-table-horizon">
  944. <question>(FO) How do I center a table horizontally?</question>
  945. <answer>
  946. <p>
  947. See <link href="fo.html#fo-center-table-horizon">XSL-FO Horizontal Centering (Tables)</link>.
  948. </p>
  949. </answer>
  950. </faq>
  951. <faq id="fo-page-outer">
  952. <question>(FO) How to get page numbers printed on the "outer side" of the
  953. page (for books, for example)?</question>
  954. <answer>
  955. <p>
  956. See <link href="fo.html#fo-oddeven">Recto/Verso Static Content Differences</link>.
  957. </p>
  958. </answer>
  959. </faq>
  960. <faq id="oddeven">
  961. <question>(FO) How do I use different static content for odd and even
  962. pages?</question>
  963. <answer>
  964. <p>
  965. See <link href="fo.html#fo-oddeven">Recto/Verso Static Content Differences</link>.
  966. </p>
  967. </answer>
  968. </faq>
  969. <faq id="fo-first-page-header">
  970. <question>(FO) How do I get a special header on the first page?</question>
  971. <answer>
  972. <p>
  973. See <link href="fo.html#fo-first-page">Making the First Page Special</link>.
  974. </p>
  975. </answer>
  976. </faq>
  977. <faq id="fo-omit-headers">
  978. <question>(FO) How do I omit my headers on a blank page? How do I write
  979. "This page is left blank" on an intentionally blank page?</question>
  980. <answer>
  981. <p>
  982. See <link href="fo.html#fo-blank-pages">Blank Pages</link>.
  983. </p>
  984. </answer>
  985. </faq>
  986. <faq id="fo-special-symbols">
  987. <question>(FO) How do I print an Euro sign, a checkbox or other some other
  988. special symbols?</question>
  989. <answer>
  990. <p>
  991. See <link href="fo.html#xml-special-chars">Special Characters</link>.
  992. </p>
  993. </answer>
  994. </faq>
  995. <faq id="fo-preformat">
  996. <question>(FO) How do I keep linebreaks and hard spaces? How do I get
  997. preformatted text displayed as expected?</question>
  998. <answer>
  999. <p>
  1000. See <link href="fo.html#fo-preformat">Preformatting Content</link>.
  1001. </p>
  1002. </answer>
  1003. </faq>
  1004. <faq id="fo-total-pages">
  1005. <question>(FO) How do I print the total number of pages, for example "page 1
  1006. of 12"</question>
  1007. <answer>
  1008. <p>
  1009. See <link href="fo.html#fo-total-pages">Total Document Pages</link>.
  1010. </p>
  1011. </answer>
  1012. </faq>
  1013. <faq id="fo-region-overlap">
  1014. <question>(FO) The header overlaps body content. The body extends into
  1015. the footer.</question>
  1016. <answer>
  1017. <p>
  1018. See <link href="fo.html#fo-region-align">Aligning Regions</link>.
  1019. </p>
  1020. </answer>
  1021. </faq>
  1022. <faq id="fo-lines">
  1023. <question>(FO) How do I get lines in the document, as separators, side
  1024. bars or folding marks?</question>
  1025. <answer>
  1026. <p>
  1027. See <link href="fo.html#fo-lines">Drawing Lines</link>.
  1028. </p>
  1029. </answer>
  1030. </faq>
  1031. <faq id="fo-validate">
  1032. <question>(FO) How do I validate my FO document?</question>
  1033. <answer>
  1034. <p>
  1035. See <link href="fo.html#fo-validate">Validating XSL-FO</link>.
  1036. </p>
  1037. </answer>
  1038. </faq>
  1039. <faq id="xml-non-breaking-space">
  1040. <question>(XML) How do I get a non-breaking space in FO? There are complaints about <code>&amp;nbsp;</code>.</question>
  1041. <answer>
  1042. <p>
  1043. See <link href="fo.html#xml-special-chars">XML Special Characters</link>.
  1044. </p>
  1045. </answer>
  1046. </faq>
  1047. <faq id="xml-undefined-entities">
  1048. <question>(XML) How do I enter special characters in XML? There are complaints about undefined entities, such as <code>&amp;uuml;</code>, which work in HTML. </question>
  1049. <answer>
  1050. <p>
  1051. See <link href="fo.html#xml-special-chars">XML Special Characters</link>.
  1052. </p>
  1053. </answer>
  1054. </faq>
  1055. <faq id="xml-illegal-entities">
  1056. <question>(XML) There are complaints about illegal characters and entities
  1057. in the input.</question>
  1058. <answer>
  1059. <p>
  1060. See <link href="fo.html#xml-entity-chars">Using HTML Character Names</link>.
  1061. </p>
  1062. </answer>
  1063. </faq>
  1064. <faq id="xml-illegal-chars">
  1065. <question>(XML) There are complaints about illegal bytes or characters in
  1066. the input. There are odd characters in the result.</question>
  1067. <answer>
  1068. <p>
  1069. See <link href="fo.html#xml-encoding">XML Encoding Issues</link>.
  1070. </p>
  1071. </answer>
  1072. </faq>
  1073. <faq id="xslt-current-date">
  1074. <question>(XSLT) How can I use the current date and time in my document?</question>
  1075. <answer>
  1076. <p>See <link href="fo.html#xslt-date">Current Date and Time</link>.</p>
  1077. </answer>
  1078. </faq>
  1079. <faq id="xhtml-to-pdf">
  1080. <question>Can I use FOP to convert XHTML or HTML files to PDF?</question>
  1081. <answer>
  1082. <p>
  1083. You will get better results if you transform your source
  1084. XML directly into XSLFO. It is tempting to use the
  1085. XML-&gt;XHTML-&gt;XSLFO approach, because this apparently means
  1086. there's only one transformation to maintain, but XHTML
  1087. and publishing grade PDF are dissimilar enough that an
  1088. "generic" XHTML-&gt;XSLFO(PDF) usually wont cut it, because
  1089. the XHTML already lacks information from the original XML.
  1090. It may be worthwhile to go from the source XML to an
  1091. intermediate custom XML which on one hand is close enough
  1092. to representation to allow simple transformation to either
  1093. XHTML or XSLFO for most of the structure, but on the other
  1094. hand retains enough semantic from the original XML that
  1095. elements which must be handled differently in the two
  1096. representations can be handled differently. Setting this
  1097. up requires experience and most likely extensive prototyping.
  1098. </p>
  1099. </answer>
  1100. </faq>
  1101. <faq id="xhtml-to-pdf2">
  1102. <question>I know it may be a bad idea to use FOP to convert XHTML or HTML files to PDF, but I want to do it anyway. Are there any tools available to help me?</question>
  1103. <answer>
  1104. <p>
  1105. The <link href="resources.html">FOP Resources page</link> has links
  1106. to a tool called <link href="http://html2fo.sourceforge.net/">html2fo</link>
  1107. which can be used to make such a transformation. In addition, there
  1108. are tools on the Antenna House <link href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</link>
  1109. page.
  1110. </p>
  1111. </answer>
  1112. </faq>
  1113. </part>
  1114. <part id="dev-help">
  1115. <title>Development-related Questions.</title>
  1116. <faq id="doc-mgt">
  1117. <question>Where can I learn how the FOP docs and web site are built?</question>
  1118. <answer>
  1119. <p>
  1120. See FOP <link href="dev/doc.html">Doc Management</link>. ;-)
  1121. </p>
  1122. </answer>
  1123. </faq>
  1124. </part>
  1125. <part id="part-help">
  1126. <title>General suggestions. How to solve problems.</title>
  1127. <faq id="bugs">
  1128. <question>I think I have found a bug in FOP. What should I do?</question>
  1129. <answer>
  1130. <p>
  1131. See <link href="bugs.html">the Bugs page</link> for information about
  1132. bugs already reported and how to report new ones.
  1133. </p>
  1134. </answer>
  1135. </faq>
  1136. <faq id="postquestions">
  1137. <question>I have questions that are not addressed in this FAQ. Where
  1138. should I post them?</question>
  1139. <answer>
  1140. <ul>
  1141. <li>If your question is a development-related question, please see the <link href="dev/faq.html">Developer FAQs</link>.</li>
  1142. <li>
  1143. If you have a runtime exception or other runtime problem:
  1144. <ul>
  1145. <li>
  1146. double-check the <link href="#part-running">Runtime FAQs</link>.
  1147. </li>
  1148. <li>
  1149. ClassNotFoundException, NoSuchMethodException and
  1150. NoSuchFieldException problems are almost always a problem with
  1151. the local environment. Try to get local help first.
  1152. </li>
  1153. <li>
  1154. Check <link href="bugs.html#issues_existing">Reported Issues</link>
  1155. to see if this is a known problem.
  1156. </li>
  1157. <li>If none of the above apply, post a question to the fop-dev
  1158. mailing list.
  1159. </li>
  1160. </ul>
  1161. </li>
  1162. <li>
  1163. In the case where something works properly with another formatter,
  1164. (AntennaHouse, PassiveTex, etc.) but doesn't work with FOP, please
  1165. check the <link href="relnotes.html">Release Notes</link>, the
  1166. <link href="compliance.html">FOP Standards Compliance</link> document,
  1167. and the remaining FAQ in this document. If not found there, look at the
  1168. list of <link href="bugs.html#issues_existing">Bugs Already Reported</link>.
  1169. If not found there, please post a question on the fop-user mailing list
  1170. or <link href="bugs.html#issues_new">Open a New Bug</link>.
  1171. </li>
  1172. <li>
  1173. Question about how to use FOP, how to perform certain tasks with FOP
  1174. or how to integrate FOP into another application should be posted to
  1175. fop-user.
  1176. </li>
  1177. <li>
  1178. XSLT specific stuff sould go to the <link
  1179. href="http://www.mulberrytech.com/xsl/xsl-list/">XSL
  1180. list</link>. This includes problems with the language and XSLT
  1181. HOW-TOs.
  1182. </li>
  1183. <li>
  1184. Problems specific to a certain XSLT processor, like Xalan, Saxon or
  1185. MSXML, should be handled by processor specific lists. This includes
  1186. problems with deployment, processor specific extensions, suspected
  1187. bugs and processor specific APIs. Note that JDK 1.4 comes with an
  1188. XML parser and an XSLT processor which are older versions of
  1189. Xerces and Xalan, respectively, and both have a number of annoying
  1190. bugs. See $$$FIXME on how to use more recent versions or other
  1191. packages instead.
  1192. </li>
  1193. <li>
  1194. Problems with servlet containers should be asked on the vendor
  1195. specific lists for these software packages.
  1196. </li>
  1197. <li>
  1198. More general questions regarding Java, including deployment, Java
  1199. APIs, classpath issues and property definitions should be redirected
  1200. to some Java specific list.
  1201. </li>
  1202. </ul>
  1203. </answer>
  1204. </faq>
  1205. </part>
  1206. </faqs>