xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1421838 [2/3] - in /xmlgraphics/site/trunk/content/fop: ./ 0.95/ 1.0/ 1.1/ dev/ dev/design/ trunk/
Date Fri, 14 Dec 2012 13:06:18 GMT
Modified: xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext Fri Dec 14 13:06:02 2012
@@ -10,7 +10,8 @@ Title: Apache(tm) FOP: Hyphenation
 Apache™ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.
 
 Because of [licensing issues](#license-issues) (and for convenience), all hyphenation patterns for FOP are made available through the [Objects For Formatting Objects](http://offo.sourceforge.net/hyphenation/index.html) project.
-If you have made improvements to an existing Apache™ FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user).
+
+<note>If you have made improvements to an existing Apache&trade; FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user).</note>
 
 ### License Issues {#license-issues}
 
@@ -36,6 +37,7 @@ To install a custom hyphenation pattern 
 -  `en_US.xml` would be the file name for American English hyphenation patterns.
 
 -  `it.xml` would be the file name for Italian hyphenation patterns.
+
 The language and country codes must match the XSL-FO input, which follows [ISO 639](http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt) (languages) and [ISO 3166](http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt) (countries). NOTE: The ISO 639/ISO 3166 convention is that language names are written in lower case, while country codes are written in upper case. FOP does not check whether the language and country specified in the FO source are actually from the current standard, but it relies on it being two letter strings in a few places. So you can make up your own codes for custom hyphenation patterns, but they should be two letter strings too (patches for proper handling extensions are welcome)
 
 1. There are basically three ways to make the FOP-compatible hyphenation pattern file(s) accessible to FOP:

Modified: xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext Fri Dec 14 13:06:02 2012
@@ -2,7 +2,8 @@ Title: Apache(tm) FOP: Intermediate Form
 
 #Apache&trade; FOP: Intermediate Format
 
-Please note that the intermediate formats described here are **advanced features** and can be ignored by most users of Apache&trade; FOP.
+<note>Please note that the intermediate formats described here are **advanced features** and can be ignored by most users of Apache&trade; FOP.</note>
+
 ## Introduction {#introduction}
 
 Apache&trade; FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as generated by the layout engine. The area tree is conceptually defined in the [XSL-FO specification in chapter 1.1.2](http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting). Even though the area tree is mentioned in the XSL-FO specification, this part is not standardized. Therefore, the area tree XML format is a FOP-proprietary XML file format. The area tree XML can be generated through the area tree XML Renderer (the XMLRenderer).
@@ -90,7 +91,9 @@ This initial example is obviously not ve
 ### Modifying Documents {#modifying}
 
 One of the most important use cases for this format is obviously modifying the area tree XML before finally rendering it to the target format. You can easily use XSLT to process the AT XML file according to your needs. Please note, that we will currently not formally describe the area tree XML format. You need to have a good understanding its structure so you don't create any non-parseable files. We may add an XML Schema and more detailed documentation at a later time. You're invited to help us with that.
-The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.
+
+<note>The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.</note>
+
 ### Advanced Use {#advanced}
 
 The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()`).

Modified: xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext Fri Dec 14 13:06:02 2012
@@ -7,12 +7,13 @@ Title: Apache(tm) FOP: Known Issues
 
 This page lists currently known issues in the current release.
 
+<note>
 For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:
 
-
 -  [the bug list in Bugzilla](../bugs.html)
 
 -  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks)
+</note>
 
 Apache&trade; FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext Fri Dec 14 13:06:02 2012
@@ -39,7 +39,7 @@ Document-level metadata can be specified
     <fo:page-sequence ...
     [..]
 
-`fo:declarations`  **must** be declared after `fo:layout-master-set` and before the first `page-sequence`.
+<note>`fo:declarations` **must** be declared after `fo:layout-master-set` and before the first `page-sequence`.</note>
 
 ## Implementation in Apache FOP {#xmp-impl-in-fop}
 
@@ -61,7 +61,10 @@ The mapping between the Info and the Met
 | Producer | text string | pdf:Producer | Text | Internal |
 | CreationDate | date | xmp:CreationDate | Date | Internal |
 | ModDate | date | xmp:ModifyDate | Date | Internal |
-"Internal" in the Category column means that the user should not set this value. It is set by the application.The "Subject" used to be mapped to `dc:subject` in the initial publication of PDF/A-1 (ISO 19005-1). In the [Technical Corrigendum 1](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613) this was changed to map to `dc:description["x-default"]`.
+
+<note>"Internal" in the Category column means that the user should not set this value. It is set by the application.</note>
+
+<note>The "Subject" used to be mapped to `dc:subject` in the initial publication of PDF/A-1 (ISO 19005-1). In the [Technical Corrigendum 1](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613) this was changed to map to `dc:description["x-default"]`.</note>
 
 ### Namespaces {#namespaces}
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/output.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/output.mdtext Fri Dec 14 13:06:02 2012
@@ -386,14 +386,16 @@ An outline font configuration is simpler
     :::xml
     <font>
       <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH200  "
-           base-uri="file:/fonts/ibm" />
+          base-uri="file:/fonts/ibm" />
       <font-triplet name="sans-serif" style="normal" weight="normal"/>
       <font-triplet name="Helvetica" style="normal" weight="normal"/>
       <font-triplet name="any" style="normal" weight="normal"/>
-   </font>
+    </font>
 
 If "base-uri" is missing or a relative URI, the fonts are resolved relative to the font base URI specified in the configuration (or on the FopFactory).
-Previously, the location of the font files was given by the "path" attribute. This is still supported for the time being, but you should move to using the more flexible "base-uri" attribute so you can profit from the power of URI resolvers.
+
+<note>Previously, the location of the font files was given by the "path" attribute. This is still supported for the time being, but you should move to using the more flexible "base-uri" attribute so you can profit from the power of URI resolvers.</note>
+
 A CID-keyed font (Type 0, double-byte outline font) configuration is much the same as an outline font. However, the characterset definition is now required within the afp-font element.
 
     :::xml
@@ -421,21 +423,21 @@ Experimentation has shown that the font 
     </font>
     <font>
       <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH300  "
-        base14-font="HelveticaOblique" />
+          base14-font="HelveticaOblique" />
       <font-triplet name="sans-serif" style="italic" weight="normal"/>
       <font-triplet name="Helvetica" style="italic" weight="normal"/>
       <font-triplet name="any" style="italic" weight="normal"/>
     </font>
     <font>
       <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH400  "
-        base14-font="HelveticaBold" />
+          base14-font="HelveticaBold" />
       <font-triplet name="sans-serif" style="normal" weight="bold"/>
       <font-triplet name="Helvetica" style="normal" weight="bold"/>
       <font-triplet name="any" style="normal" weight="bold"/>
     </font>
     <font>
       <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH500  "
-        base14-font="HelveticaBoldOblique" />
+          base14-font="HelveticaBoldOblique" />
       <font-triplet name="sans-serif" style="italic" weight="bold"/>
       <font-triplet name="Helvetica" style="italic" weight="bold"/>
       <font-triplet name="any" style="italic" weight="bold"/>
@@ -444,7 +446,7 @@ Experimentation has shown that the font 
     <!-- serif fonts based on Times Roman -->
     <font>
       <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZN200  "
-        base14-font="TimesRoman" />
+          base14-font="TimesRoman" />
       <font-triplet name="serif" style="normal" weight="normal"/>
       <font-triplet name="Times" style="normal" weight="normal"/>
       <font-triplet name="Times-Roman" style="normal" weight="normal"/>
@@ -577,7 +579,7 @@ By default the AFP Renderer will place a
     :::xml
     <resource-group-file>external_resources.afp</resource-group-file>
 
-Be careful when using this option not to overwrite existing resource files from previous rendering runs.
+<note>Be careful when using this option not to overwrite existing resource files from previous rendering runs.</note>
 
 #### Resource Level Defaults {#afp-resource-level-defaults}
 
@@ -618,7 +620,7 @@ The include-page-segment extension eleme
 
     :::xml
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+        xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
       <fo:layout-master-set>
         <fo:simple-page-master master-name="simple">
           <afp:include-page-segment name="S1ISLOGO" src="../../resources/images/bgimg300dpi.jpg" />
@@ -638,7 +640,7 @@ The tag-logical-element extension elemen
 
     :::xml
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+        xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
       <fo:layout-master-set>
         <fo:simple-page-master master-name="simple">
           <afp:tag-logical-element name="The TLE Name" value="The TLE Value" />
@@ -659,7 +661,7 @@ The no-operation extension provides the 
 
     :::xml
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+        xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
       <fo:layout-master-set>
         <fo:simple-page-master master-name="simple">
           <afp:no-operation name="My NOP">insert up to 32k of character data here!</afp:no-operation>
@@ -674,7 +676,7 @@ The invoke-medium-map extension allows t
 
     :::xml
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+        xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
       [..]
       <fo:page-sequence master-reference="normal">
         <afp:invoke-medium-map name="MYMAP"/>
@@ -689,14 +691,16 @@ Apache FOP supports embedding an externa
 
     :::xml
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-         xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+        xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
       [..]
       <fo:declarations>
         <afp:include-form-map name="F1SAMP1" src="file:f1samp1.fde"/>
       </fo:declarations>
 
 The `afp:include-form-map` is to be placed as a direct child of `fo:declarations`. The `name` is an AFP resource name (max. 8 characters) and the `src` attribute is the URI identifying the external form map resource. When such a form map is embedded, you can use the `afp:invoke-medium-map` extension (described above) to invoke any medium map included in the form map.
-Apache FOP doesn't support a way to define a form map or medium map using XML means inside an XSL-FO document. You will have to build the form map with some third-party tool.
+
+<note>Apache FOP doesn't support a way to define a form map or medium map using XML means inside an XSL-FO document. You will have to build the form map with some third-party tool.</note>
+
 ### Foreign Attributes {#afp-foreign-attributes}
 
 #### Resource {#afp-foreign-attributes-resource}
@@ -705,7 +709,7 @@ The resource foreign attributes provides
 
     :::xml
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+        xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
      ...
      <fo:block>
       <fo:external-graphic width="2.0cm" content-width="2.0cm" height="1.8cm" content-height="1.8cm"
@@ -734,7 +738,9 @@ The resource-level attribute where the r
 JFOR, an open source XSL-FO to RTF converter has been integrated into Apache FOP. This will create an RTF (rich text format) document that will attempt to contain as much information from the XSL-FO document as possible. It should be noted that is not possible (due to RTF's limitations) to map all XSL-FO features to RTF. For complex documents, the RTF output will never reach the feature level from PDF, for example. Thus, using RTF output is only recommended for simple documents such as letters.
 
 The RTF output follows Microsoft's RTF specifications and produces best results on Microsoft Word.
-RTF output is currently unmaintained and lacks many features compared to other output formats. Using other editable formats like Open Document Format, instead of producing XSL-FO then RTF through FOP, might give better results.
+
+<note>RTF output is currently unmaintained and lacks many features compared to other output formats. Using other editable formats like Open Document Format, instead of producing XSL-FO then RTF through FOP, might give better results.</note>
+
 These are some known restrictions compared to other supported output formats (not a complete list):
 
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext Fri Dec 14 13:06:02 2012
@@ -54,7 +54,7 @@ There are a number of things that must b
 
 - No filter must be specified explicitely for metadata objects. Metadata must be embedded in clear text so non-PDF-aware applications can extract the XMP metadata.
 
-There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is particularly the specification of the natural language and alternative descriptions for images. Please refer to the [Accessibility page](accessibility.html) for details.
+<note>There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is particularly the specification of the natural language and alternative descriptions for images. Please refer to the [Accessibility page](accessibility.html) for details.</note>
 
 ## PDF profile compatibility {#profile-compatibility}
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext Fri Dec 14 13:06:02 2012
@@ -32,7 +32,6 @@ Further restrictions can be imposed by u
 |  `-noassembledoc`  | disable assembling documents |
 |  `-noprinthq`  | disable high quality printing |
 
-
 ## Usage (embedded) {#embedded}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
@@ -50,7 +49,9 @@ When FOP is embedded in another Java app
 | allowAccessContent | Allows/disallows text and graphics extraction for accessibility purposes | "TRUE" or "FALSE" | "TRUE" |
 | allowAssembleDocument | Allows/disallows assembling document | "TRUE" or "FALSE" | "TRUE" |
 | allowPrintHq | Allows/disallows high quality printing | "TRUE" or "FALSE" | "TRUE" |
-Encryption is enabled as soon as one of these options is set.
+
+<note>Encryption is enabled as soon as one of these options is set.</note>
+
 An example to enable PDF encryption in Java code:
 
     :::java
@@ -130,8 +131,8 @@ The pure Java implementation from [Bounc
 
 1. Open the `java.security` file and add
 
-     `security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,
+    `security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,
 
-     preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider).
+    preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider).
 
 If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.

Modified: xmlgraphics/site/trunk/content/fop/1.1/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/running.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/running.mdtext Fri Dec 14 13:06:02 2012
@@ -175,9 +175,13 @@ If the system property `fop.optional.lib
 ## Using Xalan to Check XSL-FO Input {#check-input}
 
 FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the problem. If the problem is in the first process, the user's stylesheet is likely the cause. The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful [Specifications](../resources.html#specs) and [Books/Articles](../resources.html#articles). If the problem is in the second process, FOP may have a bug or an unimplemented feature that does require attention from the FOP development team.
-The user is always responsible to provide correct XSL-FO code to FOP.
+
+<note>The user is always responsible to provide correct XSL-FO code to FOP.</note>
+
 In the case of using -xml and -xsl input, although the user is responsible for the XSL-FO code that is FOP's input, it is not visible to the user. To make the intermediate FO file visible, the FOP distribution includes the "-foout" option which causes FOP to run only the first (transformation) step, and write the results to a file. (See also the Xalan command-line below)
-When asking for help on the FOP mailing lists, *never* attach XML and XSL to illustrate the issue. Always run the XSLT step (-foout) and send the resulting XSL-FO file instead. Of course, be sure that the XSL-FO file is correct before sending it.
+
+<note>When asking for help on the FOP mailing lists, *never* attach XML and XSL to illustrate the issue. Always run the XSLT step (-foout) and send the resulting XSL-FO file instead. Of course, be sure that the XSL-FO file is correct before sending it.</note>
+
 The -foout option works the same way as if you would call the [Xalan command-line](http://xml.apache.org/xalan-j/commandline.html):
 
  `java org.apache.xalan.xslt.Process -IN xmlfile -XSL file -OUT outfile`

Modified: xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext Fri Dec 14 13:06:02 2012
@@ -21,9 +21,13 @@ The servlet is automatically built when 
 
 
 The source code for the servlet can be found under {fop-dir}/src/java/org/apache/fop/servlet/FopServlet.java.
-This example servlet should not be used on a public web server connected to the Internet as it does not contain any measures to prevent Denial-of-Service-Attacks. It is provided as an example and as a starting point for your own servlet.
+
+<note>This example servlet should not be used on a public web server connected to the Internet as it does not contain any measures to prevent Denial-of-Service-Attacks. It is provided as an example and as a starting point for your own servlet.</note>
+
 ## Create your own Servlet {#servlet}
-This section assumes you are familiar with [embedding FOP](embedding.html).
+
+<note>This section assumes you are familiar with [embedding FOP](embedding.html).</note>
+
 ### A minimal Servlet {#minimal-servlet}
 
 Here is a minimal code snippet to demonstrate the basics:
@@ -46,7 +50,7 @@ Here is a minimal code snippet to demons
         }
     }
 
-There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.
+<note>There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.</note>
 
 ### Adding XSL tranformation (XSLT) {#xslt}
 
@@ -89,7 +93,8 @@ A common requirement is to transform an 
     response.getOutputStream().write(out.toByteArray());
     response.getOutputStream().flush();
 
-Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet Explorer.
+<note>Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet Explorer.</note>
+
 The `Source` instance used above is simply an example. If you have to read the XML from a string, supply a `new StreamSource(new
           StringReader(xmlstring))`. Constructing and reparsing an XML string is generally less desirable than using a SAXSource if you generate your XML. You can alternatively supply a DOMSource as well. You may also use dynamically generated XSL if you like.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext Fri Dec 14 13:06:02 2012
@@ -40,7 +40,7 @@ If you're planning to upgrade to the lat
 
 - The new code is much more strict about the interpretation of the XSL-FO specification. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
 
-    While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element (`(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell)) inside an `fo:table-cell` element.
+    <note>While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element (`(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell)) inside an `fo:table-cell` element.</note>
 
 - Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP extension for [Barcode4J](http://barcode4j.sourceforge.net) is available since January 2007.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext Fri Dec 14 13:06:02 2012
@@ -30,9 +30,13 @@ The break possibilities are generated fr
 Variable size content is taken into account from the bottom up. Each LM returns a range of sizes in the stacking direction, based on property values. For text, this comes from variable word-space values or letter-space values. For other inline objects, it may include variable space-start and space-end values (after calculation of the entire sequence of space specifiers at a particular break possibility.)
 
 The main constraint for laying out lines is the available inline-progression-dimension (IPD) for the line area to be created. This depends on the IPD of the reference area ancestor, on the indents of the containing fo:block, and on any side-floats which may be intruding on this line.
-See below [Getting the Reference IPD](#getRefIPD) for discussion of how the reference area IPD is transmitted to the Line LM.
+
+<note>See below [Getting the Reference IPD](#getRefIPD) for discussion of how the reference area IPD is transmitted to the Line LM.</note>
+
 For now, let's assume that only the LineLM knows about the IPD available to it. Therefore only it can make a decision about which BP is the best one; the lower level inline layout managers can only return potential break points.
-There are certainly optimizations to this model which can be examined later.
+
+<note>There are certainly optimizations to this model which can be examined later.</note>
+
 So the Line LM will ask its child LM(s) for break possibilities until it gets back a BP whose stacking dimension *could* fill the line. This means that the BP.stackdim.max >= LineIPD.min. It can look for further BP, perhaps one whose stackdim.opt is closer to the LineIPD.opt. If it isn't happy with the choice of break possibilities, it can go past the end of the line to the next one, and then try to find a hyphenation point between the last one which fits and the first one which doesn't. If no possibility is found whose min/max values enclose the available IPD, some constraint will be violated (and reported in the log.) The actual strategy is up to the Line LM and should be able to be easily replaced without changing the architecture (Strategy pattern).
 
 The definition of a good break possibility depends on the properties at the block and inline level which govern things such as wrapping behavior and justification mode. For example, if lines are not to be wrapped, only an explicit linefeed can serve as a BP. If lines are wrapped but not justified then there is no requirement to completely fill the IPD on each line, but a sophisticated layout manager will try to achieve "aesthetic rag".

Modified: xmlgraphics/site/trunk/content/fop/dev/design/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/index.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/index.mdtext Fri Dec 14 13:06:02 2012
@@ -1,8 +1,9 @@
 Title: Apache(tm) FOP Design: Introduction
 
 #Apache&trade; FOP Design: Introduction
-<authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors>
-The articles in this section pertain mainly to the *redesign* or *trunk* line of development. The redesign is mainly focusing on parts of the layout process (converting the FO tree into the Area Tree). Therefore other (non-layout) sections in this document are probably largely accurate for the maintenance branch, but should be used with care in that context.
+
+<note>The articles in this section pertain mainly to the *redesign* or *trunk* line of development. The redesign is mainly focusing on parts of the layout process (converting the FO tree into the Area Tree). Therefore other (non-layout) sections in this document are probably largely accurate for the maintenance branch, but should be used with care in that context.</note>
+
 ## The Black Box View {#black-box}
 
 From a user's standpoint, Apache&trade; FOP is a black box that an xml file as input, performs some magic, then creates the desired output:

Modified: xmlgraphics/site/trunk/content/fop/dev/doc.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/doc.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/doc.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/doc.mdtext Fri Dec 14 13:06:02 2012
@@ -7,7 +7,9 @@ Title: Apache(tm) FOP Development: Manag
 ## General Information {#general}
 
 All raw documentation content is managed in the Apache&trade; FOP SVN repository. Updates should be committed to the repository, then the repository files are used to generate usable output. The remaining discussions on this page assume that the SVN repository is the starting place for processing. The path to the documentation is src/documentation/content/xdocs.
-All documentation is maintained on the trunk.
+
+<note>All documentation is maintained on the trunk.</note>
+
 Basic documents are stored in XML files, and use DTDs provided by Apache Forrest.
 
 ## Design Principles {#design}
@@ -40,12 +42,14 @@ The following table summarizes the flow 
 | Developer commits code to FOP repository. | FOP repository (SVN) | Raw XML and other content |  [in SVN](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/)  |
 | Developer builds and uploads documentation using ForrestBot. | /www/xmlgraphics.apache.org/fop on people.apache.org | sync-ready | n/a |
 | Cron job runs rsync to synchronize the website with the real web server (runs every few hours). | Infrastructure knows. :-) | web-ready |  [FOP Web Site](http://xmlgraphics.apache.org/fop)  |
-Server-side ForrestBot is currently not available for website publishing. We use it locally and with manual invocation.
+
+<note>Server-side ForrestBot is currently not available for website publishing. We use it locally and with manual invocation.</note>
 
 ### ForrestBot "publish" Step-by-Step {#web-forrestbot-publish}
 
 We're using ForrestBot for build and deploy the FOP website. ForrestBot comes with Apache Forrest 0.8. The root directory of your FOP checkout contains the file "publish.xml" which is an Ant build file that manages the build and the deployment of the FOP website. Please look into this file for further instructions to set up ForrestBot on your machine. Basically, we're simply running ForrestBot manually by typing "ant -f publish.xml" once we're happy with our changes to the site. Step-by-step instructions for the deployment process again:
-Please make sure you use Forrest from the Trunk (revision 632959 or later) for the time being. You will need to download it directly from SVN: [http://svn.apache.org/repos/asf/forrest/trunk](http://svn.apache.org/repos/asf/forrest/trunk)
+
+<note>Please make sure you use Forrest from the Trunk (revision 632959 or later) for the time being. You will need to download it directly from SVN: [http://svn.apache.org/repos/asf/forrest/trunk](http://svn.apache.org/repos/asf/forrest/trunk).</note>
 
 - Modify the sources of the website and check locally with Forrest (run "forrest run" or just "forrest").
 
@@ -61,7 +65,6 @@ The reason for putting the generated web
 
 To use a local Forrest (during website development, not for deployment):
 
-
 -  [download](http://forrest.apache.org/mirrors.cgi#closest) latest the Forrest release (currently Forrest 0.8)
 
 - set environment variable FORREST_HOME=~/apache-forrest-0.8 where ~ is the directory where Forrest is installed (see [http://forrest.apache.org/docs/your-project.html](http://forrest.apache.org/docs/your-project.html) for details)
@@ -73,7 +76,8 @@ To use a local Forrest (during website d
 - update your local FOP checkout (svn update)
 
 - run forrest(.bat), which will build the web-site documents in xml-fop/build/site.
-You can use "forrest run" to start a local web server. That improves development speed as you can simply refresh in the browser after a change.
+
+<note>You can use "forrest run" to start a local web server. That improves development speed as you can simply refresh in the browser after a change.</note>
 
 ### Updating Distribution Files {#distribution}
 
@@ -84,4 +88,5 @@ Please be careful when doing stuff like 
 ### Deleting Documentation Files {#delete}
 
 ForrestBot simply uploads the whole generated site. It doesn't delete obsolete files. You can do that manually in the /www/xmlgraphics.apache.org/fop folder on cvs.apache.org. Be careful when doing stuff like that.
-Please make sure you always have **group rw permissions on all files** under the /www directory!
\ No newline at end of file
+
+<note>Please make sure you always have **group rw permissions on all files** under the /www directory!</note>

Modified: xmlgraphics/site/trunk/content/fop/dev/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/index.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/index.mdtext Fri Dec 14 13:06:02 2012
@@ -13,9 +13,11 @@ For basic and user information on FOP, p
 
 The main development happens on "FOP Trunk".
 
+<note>
 The SVN repository URL for the trunk is:
 
 `http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/`
+</note>
 
 ## Getting Involved {#involved}
 
@@ -62,7 +64,8 @@ At the moment FOP is mainly a tool to re
 The design for FOP is specified under the [Design](design/index.html) section. This is where the information on how FOP is developed and designed internally will be kept.
 
 Another place where we write design documentation is the [FOP Wiki](http://wiki.apache.org/xmlgraphics-fop/DeveloperPages).
-Our design documentation may not always be up to date!
+
+<note>Our design documentation may not always be up to date!</note>
 
 ### Subscribe to the fop-dev Mailing List {#mail-fop-dev}
 

Modified: xmlgraphics/site/trunk/content/fop/dev/svg.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/svg.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/svg.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/svg.mdtext Fri Dec 14 13:06:02 2012
@@ -18,7 +18,8 @@ These examples illustrate a number of is
 | transparent objects |  [transparency.svg](svg/transparency.svg)  |  [transparency.png](svg/transparency.png)  |  [transparency.pdf](svg/transparency.pdf)  |
 
 As can be seen most of the specific issues are handled.
-You will need Acrobat 5.0 to see transparency.
+
+<note>You will need Acrobat 5.0 to see transparency.</note>
 
 <caption>XSL:FO to PDF examples</caption>|  | fo file | pdf result |
 |--|---------|------------|

Modified: xmlgraphics/site/trunk/content/fop/gethelp.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/gethelp.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/gethelp.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/gethelp.mdtext Fri Dec 14 13:06:02 2012
@@ -36,7 +36,8 @@ See [Reported Issues](bugs.html#issues_e
 ## Submit Question to FOP User Mailing List {#user-mailing-list}
 
 See [FOP User Mailing List](maillist.html#fop-user) for details.
-Please don't write to any developer directly. Only if you submit questions to the [FOP User Mailing List](maillist.html#fop-user) will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.
+
+<note label="Important">Please don't write to any developer directly. Only if you submit questions to the [FOP User Mailing List](maillist.html#fop-user) will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.</note>
 
 ## Enter an Issue Report {#enter-issue}
 

Modified: xmlgraphics/site/trunk/content/fop/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/index.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/index.mdtext Fri Dec 14 13:06:02 2012
@@ -32,4 +32,5 @@ FOP uses the standard XSL-FO file format
 The goals of the Apache FOP project are to deliver an XSL-FO to PDF formatter that is compliant to at least the Basic conformance level described in the W3C Recommendation from 05 December 2006, and that complies with the November 2001 Portable Document Format Specification (Version 1.4) from Adobe Systems.
 
 Conformance to the XML 1.0 and 1.1 Recommendations, XSLT 1.0 and 2.0 Recommendations and the XML Namespaces Recommendation is understood. Other relevant documents, such as the XPath and XLink Working Drafts, are referenced as necessary. The FOP Project will attempt to use the latest version of evolving specifications.
-The PDF files on this site are created using Apache FOP.
\ No newline at end of file
+
+<note>The PDF files on this site are created using Apache FOP.</note>
\ No newline at end of file

Modified: xmlgraphics/site/trunk/content/fop/maillist.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/maillist.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/maillist.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/maillist.mdtext Fri Dec 14 13:06:02 2012
@@ -4,12 +4,10 @@ Title: Apache(tm) FOP: Mailing List Reso
 
 #Apache&trade; FOP: Mailing List Resources
 
-
 ## General Information {#general}
 
 Before posting questions to any list:
 
-
 - Review the [Jakarta Mailing Lists - Guidelines](http://jakarta.apache.org/site/mail.html) for general principles about mailing lists.
 
 - Review "[How To Ask Questions The Smart Way](http://www.catb.org/~esr/faqs/smart-questions.html)".
@@ -42,11 +40,10 @@ To review the archives, you have several
 
 - The [MarkMail archive](http://fop-users.markmail.org/).
 
-If you don't like mailing lists and prefer a forum-like system, have a look at [GMANE][gmaneLink] or [Nabble][nabbleLink]. They allow you to post to the mailing list without having to subscribe.
+<note>If you don't like mailing lists and prefer a forum-like system, have a look at [GMANE][gmaneLink] or [Nabble][nabbleLink]. They allow you to post to the mailing list without having to subscribe.</note>
 
 ### Subscription Information {#fop-user-subscribe}
 
-
 - See [Apache XML Graphics Mailing Lists](http://xmlgraphics.apache.org/mail.html) for detailed subscription information.
 
 - To subscribe (digest only): Send email to [fop-users-digest-subscribe@xmlgraphics.apache.org](mailto:fop-users-digest-subscribe@xmlgraphics.apache.org).
@@ -56,12 +53,13 @@ If you don't like mailing lists and pref
 - To receive information about the mailing list: Send email to [fop-users-help@xmlgraphics.apache.org](mailto:fop-users-help@xmlgraphics.apache.org).
 
 - To **unsubscribe**: Send email to [fop-users-unsubscribe@xmlgraphics.apache.org](mailto:fop-users-unsubscribe@xmlgraphics.apache.org).
-You can find the developer mailing list on the [Development pages](dev/index.html#mail-fop-dev).
+
+<note>You can find the developer mailing list on the [Development pages](dev/index.html#mail-fop-dev).</note>
+
 ### Submitting a Question {#fop-user-policy}
 
 FOP support is primarily *self-service* . The FOP User Mailing List serves as a backup to the self-service documentation for cases where either the documentation is deficient or where users have unusual circumstances. FOP developers and users are happy to help answer questions that are *appropriate to the forum* (i.e. FOP-specific), and that are *submitted after appropriate preparation*. To ensure that your question is not **abusive** of this policy, please use the following checklist:
 
-
 - Have you followed the [Getting Help](gethelp.html) checklist? If not, please do so before submitting your question.
 
 - Is your question appropriate to the forum? If it is really an XSL-FO question, XSLT question, or PDF question, please see the other resources on this page that are intended to help you get those questions answered.

Modified: xmlgraphics/site/trunk/content/fop/team.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/team.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/team.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/team.mdtext Fri Dec 14 13:06:02 2012
@@ -2,11 +2,11 @@ Title: Apache(tm) FOP: Development Team
 
 #Apache&trade; FOP: Development Team
 
-
 All lists on this page are in alphabetical order. Some of them may be incomplete. If you know of an error or omission, please send a message to the [fop-dev](mailto:fop-dev@xmlgraphics.apache.org) mailing list.
 
 ## Active Committers {#commit-active}
-Please don't write to any developer directly if you need help on using FOP. Only if you submit questions to the [FOP User Mailing List](maillist.html#fop-user) will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.
+
+<note>Please don't write to any developer directly if you need help on using FOP. Only if you submit questions to the [FOP User Mailing List](maillist.html#fop-user) will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.</note>
 
 -  [Glenn Adams](mailto:gadams@apache.org) (GA) is an independent consultant. He is former technical director of the Unicode Consortium, and a co-author of the Unicode Standard. He served on ISO JTC1/SC2 (Coded Character Sets) and JTC1/SC18/WG8 (Document Processing) committees, and was actively involved in the creation of ISO 8879 (SGML), ISO/IEC 9541 (Font Information Interchange), ISO/IEC 10179 (DSSSL), ISO/IEC 10180 (SPDL), ISO/IEC 10646 (Universal Coded Character Set), and, within the W3C, on XSL-FO 1.0.
 
@@ -36,7 +36,6 @@ Please don't write to any developer dire
 
 ## Active Contributors {#contribute-active}
 
-
 - Georg Datterl is a software developer from Austria, currently working for Geneon media solutions gmbh in Nuremberg, Germany. He needs FOP to wrestle gigabytes of electronic data into thousands of printed pages.
 
 - Alexios Giotis holds a Ph.D. in the optimization of turbomachinery cascades using evolutionary algorithms, neural networks and parallel processing. He is one of the founding members of i-docs (software for enterprises) and he has been leading its technical design &amp; implementation based on open source libraries since its inception. He is relying on Apache FOP for generating high volumes of documents on major banks and telecom operators since FOP's 1.0 release. He lives in Athens, Greece.

Modified: xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext Fri Dec 14 13:06:02 2012
@@ -31,7 +31,9 @@ There are 3 ways to enable accessibility
         </fop>
 
 When accessibility is enabled, additional information relating to the logical structure of the document is added to the PDF. That information allows the PDF viewer (or a text-to-speech application) to retrieve the natural reading order of the document.
-The processing of the logical structure is memory-hungry. You may need to adjust the Java heap size in order to process larger files.
+
+<note>The processing of the logical structure is memory-hungry. You may need to adjust the Java heap size in order to process larger files.</note>
+
 ## Changes to your XSL-FO input files {#source}
 
 Apache FOP cannot automatically generate accessible PDFs. Some of the work can only be performed by the content provider. Following are some changes that may be necessary to your XSL-FO content in order to generate really accessible documents:

Modified: xmlgraphics/site/trunk/content/fop/trunk/compiling.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/compiling.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/compiling.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/compiling.mdtext Fri Dec 14 13:06:02 2012
@@ -28,11 +28,14 @@ The build script uses [Apache Ant](http:
 ## Run the Build Script {#build-script}
 
 Change to the FOP root directory and build FOP by executing the build script (build.xml) using the "ant" command.
-The "ant" command is only available on your system if you've properly [installed Apache Ant](http://ant.apache.org/manual/) and added Ant's location to the PATH environment variable.
+
+<note>The "ant" command is only available on your system if you've properly [installed Apache Ant](http://ant.apache.org/manual/) and added Ant's location to the PATH environment variable.</note>
+
 The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. You may benefit from looking through this file to learn more about the various build targets. To obtain a complete list of useful build targets:
-ant -projecthelp
-The most useful targets are:
 
+    ant -projecthelp
+
+The most useful targets are:
 
 -  **package**: Generates the JAR files (default). This is the normal build that produces a jar file usable for running FOP.
 
@@ -41,13 +44,23 @@ The most useful targets are:
 -  **javadocs**: Creates the FOP API documentation.
 
 To run the build:
-ant [target ...]
+
+    ant [target ...]
+
 For example to do a normal build for the "all" target (which is the default):
-ant
+
+    ant
+
 OR
-ant all
+
+    ant all
+
 To clean the build directory first:
-ant clean allIf you want to shorten the build time you can just call the "package" target which doesn't perform any automated tests during the build.
+
+    ant clean all
+
+<note>If you want to shorten the build time you can just call the "package" target which doesn't perform any automated tests during the build.</note>
+
 ## Troubleshooting {#problems}
 
 If you have problems building FOP, please try the following:

Modified: xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext Fri Dec 14 13:06:02 2012
@@ -20,13 +20,29 @@ This page describes the [complex scripts
 
 Complex script features are enabled by default. If some application of FOP does not require this support, then it can be disabled in three ways:
 
+1.  **Command line:**
 
-1.  **Command line:**<br/>The command line option `-nocs` turns off complex script features:<br/>`fop -nocs -fo mydocument.fo -pdf mydocument.pdf`<br/>
-1.  **Embedding:**<br/>`userAgent.setComplexScriptFeaturesEnabled(false);`
-1.  **Optional setting in fop.xconf file:**<br/>`<fop version="1.0">`<br/>`<complex-scripts disabled="true"/>`<br/>`...`<br/>`</fop>`
+    The command line option `-nocs` turns off complex script features:
+
+        fop -nocs -fo mydocument.fo -pdf mydocument.pdf
+
+1.  **Embedding:**
+
+        :::java
+        userAgent.setComplexScriptFeaturesEnabled(false);
+
+1.  **Optional setting in fop.xconf file:**
+
+        :::xml
+        <fop version="1.0">
+          <complex-scripts disabled="true"/>
+          ...
+        </fop>`
 
 When complex scripts features are enabled, additional information related to bidirectional level resolution, the association between characters and glyphs, and glyph position adjustments are added to the internal, parsed representation of the XSL-FO tree and its corresponding formatted area tree. This additional information will somewhat increase the memory requirements for processing documents that use these features.
-A document author need not make explicit use of any complex scripts feature in order for this additional information to be created. For example, if the author makes use of a font that contains OpenType GSUB and/or GPOS tables, then those tables will be automatically used unless complex scripts features are disabled.
+
+<note>A document author need not make explicit use of any complex scripts feature in order for this additional information to be created. For example, if the author makes use of a font that contains OpenType GSUB and/or GPOS tables, then those tables will be automatically used unless complex scripts features are disabled.</note>
+
 ## Changes to your XSL-FO input files {#source}
 
 In most circumstances, XSL-FO content does not need to change in order to make use of complex scripts features; however, in certain contexts, fully automatic processing is not sufficient. In these cases, an author may make use of the following XSL-FO constructs:
@@ -116,7 +132,10 @@ The following table enumerates a number 
 |  `tml2`  | Tamil | OpenType Indic Version 2 (May 2008 and following) behavior. |
 |  `tel2`  | Telugu | OpenType Indic Version 2 (May 2008 and following) behavior. |
 
-<warning>Explicit use of one of the above extended script codes is not portable, and should be limited to use with FOP only.</warning>When performing automatic script determination, FOP selects the OpenType Indic Version 2 script codes by default. If the author requires Version 1 behavior, then an explicit, non-extension script code should be specified in a governing `script` property.
+<warning>Explicit use of one of the above extended script codes is not portable, and should be limited to use with FOP only.</warning>
+
+<note>When performing automatic script determination, FOP selects the OpenType Indic Version 2 script codes by default. If the author requires Version 1 behavior, then an explicit, non-extension script code should be specified in a governing `script` property.</note>
+
 ### Language Property {#language_property}
 
 Certain fonts that support complex script features can make use of language information in order for language specific processing rules to be applied. For example, a font designed for the Arabic script may support typographic variations according to whether the written language is Arabic, Farsi (Persian), Sindhi, Urdu, or another language written with the Arabic script. In order to apply these language specific features, the author may explicitly mark the text with a [http://www.w3.org/TR/2006/REC-xsl11-20061205/#language](http://www.w3.org/TR/2006/REC-xsl11-20061205/#language) property.

Modified: xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext Fri Dec 14 13:06:02 2012
@@ -87,7 +87,9 @@ Let's discuss these 5 steps in detail:
 
 -  **Step 5:** Here you set up the input and output for the XSLT transformation. The Source object is set up to load the "myfile.fo" file. The Result is set up so the output of the XSLT transformation is sent to FOP. The FO file is sent to FOP in the form of SAX events which is the most efficient way. Please always avoid saving intermediate results to a file or a memory buffer because that affects performance negatively.
 
--  **Step 6:** Finally, we start the XSLT transformation by starting the JAXP Transformer. As soon as the JAXP Transformer starts to send its output to FOP, FOP itself starts its processing in the background. When the `transform()` method returns FOP will also have finished converting the FO file to a PDF file and you can close the OutputStream.It's a good idea to enclose the whole conversion in a try..finally statement. If you close the OutputStream in the finally section, this will make sure that the OutputStream is properly closed even if an exception occurs during the conversion.
+-  **Step 6:** Finally, we start the XSLT transformation by starting the JAXP Transformer. As soon as the JAXP Transformer starts to send its output to FOP, FOP itself starts its processing in the background. When the `transform()` method returns FOP will also have finished converting the FO file to a PDF file and you can close the OutputStream.
+
+    <note label="Tip!">It's a good idea to enclose the whole conversion in a try..finally statement. If you close the OutputStream in the finally section, this will make sure that the OutputStream is properly closed even if an exception occurs during the conversion.</note>
 
 If you're not totally familiar with JAXP Transformers, please have a look at the [Embedding examples](#examples) below. The section contains examples for all sorts of use cases. If you look at all of them in turn you should be able to see the patterns in use and the flexibility this approach offers without adding too much complexity.
 
@@ -210,7 +212,7 @@ You can set all sorts of things on the F
         :::java
         fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver
 
-Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.
+    <note>Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.</note>
 
 ### Customizing the User Agent {#user-agent}
 
@@ -280,7 +282,9 @@ You can do all sorts of things on the us
         :::java
         userAgent.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver
 
-Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver from the FopFactory is used. You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.
+    <note>Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver from the FopFactory is used.</note>
+
+<note>You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.</note>
 
 ## Using a Configuration File {#config-external}
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/events.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/events.mdtext Fri Dec 14 13:06:02 2012
@@ -122,7 +122,9 @@ This throws a `RuntimeException` with th
 ## The producer side (for FOP developers) {#producer}
 
 This section is primarily for FOP and FOP plug-in developers. It describes how to use the event subsystem for producing events.
-The event package has been designed in order to be theoretically useful for use cases outside FOP. If you think this is interesting independently from FOP, please talk to [us](mailto:fop-dev@xmlgraphics.apache.org).
+
+<note>The event package has been designed in order to be theoretically useful for use cases outside FOP. If you think this is interesting independently from FOP, please talk to [us](mailto:fop-dev@xmlgraphics.apache.org).</note>
+
 ### Producing and sending an event {#basic-event-production}
 
 The basics are very simple. Just instantiate an `Event` object and fill it with the necessary parameters. Then pass it to the `EventBroadcaster` which distributes the events to the interested listeneners. Here's a code example:

Modified: xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext Fri Dec 14 13:06:02 2012
@@ -6,7 +6,9 @@ Title: Standard Apache&trade; FOP Extens
 By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. By having a mechanism for supporting extensions, Apache&trade; FOP is able to add features that are not covered in the specification.
 
 The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the [Developers' Extension Page](../dev/extensions.html).
-All extensions require the correct use of an appropriate namespace in your input document.
+
+<note>All extensions require the correct use of an appropriate namespace in your input document.</note>
+
 ## SVG {#svg}
 
 Please see the [SVG documentation](graphics.html#svg) for more details.
@@ -52,7 +54,7 @@ The two proprietary extension properties
 
 ### fox:external-document {#external-document}
 
-This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.
+<note>This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.</note>
 
 This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the `fox:external-document` element. Each page of the external document will create one full page in the target format.
 
@@ -108,13 +110,18 @@ The following properties apply to this f
 - width
 
 Datatype "page-set": Value: auto | <integer-range>, Default: "auto" which means all pages/subimages of the document. <integer-range> allows values such as "7" or "1-3"
- `fox:external-document` is not suitable for concatenating FO documents. For this, XInclude is recommended.
+
+<note>`fox:external-document` is not suitable for concatenating FO documents.</note>
+
+For this, XInclude is recommended.
+
 ### Free-form Transformation for fo:block-container {#transform}
 
 For `fo:block-container` elements whose `absolute-position` set to "absolute" or "fixed" you can use the extension attribute `fox:transform` to apply a free-form transformation to the whole block-container. The content of the `fox:transform` attribute is the same as for [SVG's transform attribute](http://www.w3.org/TR/SVG/coords.html#TransformAttribute). The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.
 
 Examples: `fox:transform="rotate(45)"` would rotate the block-container by 45 degrees clock-wise around its upper-left corner. `fox:transform="translate(10000,0)"` would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
-This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.
+
+<note>This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.</note>
 
 ### Color functions {#color-functions}
 
@@ -155,7 +162,8 @@ The example fo `examples/fo/advanced/rou
 ### Prepress Support {#prepress}
 
 This section defines a number of extensions related to [prepress](http://en.wikipedia.org/wiki/Prepress) support. `fox:scale` defines a general scale factor for the generated pages. `fox:bleed` defines the [bleed area](http://en.wikipedia.org/wiki/Bleed_%28printing%29) for a page. `fox:crop-offset` defines the outer edges of the area in which crop marks, registration marks, color bars and page information are placed. For details, please read on below.
-Those extensions have been implemented in the PDF and Java2D renderers only.
+
+<note>Those extensions have been implemented in the PDF and Java2D renderers only.</note>
 
 #### fox:scale {#scale}
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext Fri Dec 14 13:06:02 2012
@@ -82,7 +82,7 @@ If you want FOP to use custom fonts, you
       </renderer>
     </renderers>
 
-Review the documentation for [FOP Configuration](configuration.html) for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.
+<note>Review the documentation for [FOP Configuration](configuration.html) for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.</note>
 
 ### Register Fonts with FOP {#register}
 
@@ -190,7 +190,9 @@ PFMReader [options]:
 
 -  **-fn <fontname>** By default, FOP uses the fontname from the .pfm file when embedding the font. Use the "-fn" option to override this name with one you have chosen. This may be useful in some cases to ensure that applications using the output document (Acrobat Reader for example) use the embedded font instead of a local font with the same name.
 
-The classpath in the above example has been simplified for readability. You will have to adjust the classpath to the names of the actual JAR files in the lib directory. xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.
+<note>The classpath in the above example has been simplified for readability. You will have to adjust the classpath to the names of the actual JAR files in the lib directory. xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.</note>
+
+<note>The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.</note>
 
 ### TrueType Font Metrics {#truetype-metrics}
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/graphics.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/graphics.mdtext Fri Dec 14 13:06:02 2012
@@ -34,11 +34,12 @@ The table below summarizes the *theoreti
 
 Legend:
 
-
 - "(X)" means restricted support. Please see the details below.
 
 - [1]: Requires the presence of [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
- [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality.
+
+<note>[JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality.</note>
+
 ### Map of supported image formats by output format {#format-map}
 
 Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:
@@ -126,7 +127,9 @@ PNG images are supported through an Imag
 #### Introduction {#svg-intro}
 
 FOP uses [Apache Batik](#batik) for SVG support. This format can be handled as an `fo:instream-foreign-object` or in a separate file referenced with `fo:external-graphic`.
-Batik's SVG Rasterizer utility may also be used to convert standalone SVG documents into PDF. For more information please see the [SVG Rasterizer documentation](http://xmlgraphics.apache.org/batik/svgrasterizer.html) on the Batik site.
+
+<note>Batik's SVG Rasterizer utility may also be used to convert standalone SVG documents into PDF. For more information please see the [SVG Rasterizer documentation](http://xmlgraphics.apache.org/batik/svgrasterizer.html) on the Batik site.</note>
+
 #### Placing SVG Graphics into PDF {#svg-pdf-graphics}
 
 The SVG is rendered into PDF by using PDF commands to draw and fill lines and curves. This means that the graphical objects created with this remain as vector graphics. The same applies to PostScript output. For other output formats the SVG graphic may be converted to a bitmap image.

Modified: xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext Fri Dec 14 13:06:02 2012
@@ -10,7 +10,8 @@ Title: Apache(tm) FOP: Hyphenation
 Apache&trade; FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.
 
 Because of [licensing issues](#license-issues) (and for convenience), all hyphenation patterns for FOP are made available through the [Objects For Formatting Objects](http://offo.sourceforge.net/hyphenation/index.html) project.
-If you have made improvements to an existing Apache&trade; FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user).
+
+<note>If you have made improvements to an existing Apache&trade; FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user).</note>
 
 ### License Issues {#license-issues}
 
@@ -36,6 +37,7 @@ To install a custom hyphenation pattern 
 -  `en_US.xml` would be the file name for American English hyphenation patterns.
 
 -  `it.xml` would be the file name for Italian hyphenation patterns.
+
 The language and country codes must match the XSL-FO input, which follows [ISO 639](http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt) (languages) and [ISO 3166](http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt) (countries). NOTE: The ISO 639/ISO 3166 convention is that language names are written in lower case, while country codes are written in upper case. FOP does not check whether the language and country specified in the FO source are actually from the current standard, but it relies on it being two letter strings in a few places. So you can make up your own codes for custom hyphenation patterns, but they should be two letter strings too (patches for proper handling extensions are welcome)
 
 1. There are basically three ways to make the FOP-compatible hyphenation pattern file(s) accessible to FOP:

Modified: xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/intermediate.mdtext Fri Dec 14 13:06:02 2012
@@ -2,7 +2,8 @@ Title: Apache(tm) FOP: Intermediate Form
 
 #Apache&trade; FOP: Intermediate Format
 
-Please note that the intermediate formats described here are **advanced features** and can be ignored by most users of Apache&trade; FOP.
+<note>Please note that the intermediate formats described here are **advanced features** and can be ignored by most users of Apache&trade; FOP.</note>
+
 ## Introduction {#introduction}
 
 Apache&trade; FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as generated by the layout engine. The area tree is conceptually defined in the [XSL-FO specification in chapter 1.1.2](http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting). Even though the area tree is mentioned in the XSL-FO specification, this part is not standardized. Therefore, the area tree XML format is a FOP-proprietary XML file format. The area tree XML can be generated through the area tree XML Renderer (the XMLRenderer).
@@ -90,7 +91,9 @@ This initial example is obviously not ve
 ### Modifying Documents {#modifying}
 
 One of the most important use cases for this format is obviously modifying the area tree XML before finally rendering it to the target format. You can easily use XSLT to process the AT XML file according to your needs. Please note, that we will currently not formally describe the area tree XML format. You need to have a good understanding its structure so you don't create any non-parseable files. We may add an XML Schema and more detailed documentation at a later time. You're invited to help us with that.
-The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.
+
+<note>The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.</note>
+
 ### Advanced Use {#advanced}
 
 The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()`).

Modified: xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/metadata.mdtext Fri Dec 14 13:06:02 2012
@@ -39,7 +39,7 @@ Document-level metadata can be specified
     <fo:page-sequence ...
     [..]
 
-`fo:declarations`  **must** be declared after `fo:layout-master-set` and before the first `page-sequence`.
+<note>`fo:declarations` **must** be declared after `fo:layout-master-set` and before the first `page-sequence`.</note>
 
 ## Implementation in Apache FOP {#xmp-impl-in-fop}
 
@@ -61,7 +61,10 @@ The mapping between the Info and the Met
 | Producer | text string | pdf:Producer | Text | Internal |
 | CreationDate | date | xmp:CreationDate | Date | Internal |
 | ModDate | date | xmp:ModifyDate | Date | Internal |
-"Internal" in the Category column means that the user should not set this value. It is set by the application.The "Subject" used to be mapped to `dc:subject` in the initial publication of PDF/A-1 (ISO 19005-1). In the [Technical Corrigendum 1](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613) this was changed to map to `dc:description["x-default"]`.
+
+<note>"Internal" in the Category column means that the user should not set this value. It is set by the application.</note>
+
+<note>The "Subject" used to be mapped to `dc:subject` in the initial publication of PDF/A-1 (ISO 19005-1). In the [Technical Corrigendum 1](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613) this was changed to map to `dc:description["x-default"]`.</note>
 
 ### Namespaces {#namespaces}
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/output.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/output.mdtext Fri Dec 14 13:06:02 2012
@@ -89,7 +89,7 @@ Here is some sample code that uses iText
             Document document = new Document(reader.getPageSizeWithRotation(1));
             PdfWriter writer = PdfWriter.getInstance(document, outfile);
             writer.setEncryption(PdfWriter.STRENGTH40BITS, "pdf", null,
-              PdfWriter.AllowCopy);
+                PdfWriter.AllowCopy);
             document.open();
             PdfContentByte cb = writer.getDirectContent();
             PdfImportedPage page;
@@ -356,8 +356,8 @@ A typical raster font configuration look
     :::xml
     <!-- This is an example of mapping actual IBM raster fonts / code pages to a FOP font -->
     <font>
-      <!-- The afp-font element defines the IBM code page, the matching Java encoding and the
-           base URI for the font -->
+    <!-- The afp-font element defines the IBM code page, the matching Java encoding and the
+         base URI for the font -->
       <afp-font type="raster" codepage="T1V10500" encoding="Cp500" base-uri="fonts/ibm/">
         <!-- For a raster font a separate element for each font size is required providing
              the font size and the corresponding IBM Character set name -->
@@ -386,22 +386,24 @@ An outline font configuration is simpler
     :::xml
     <font>
       <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH200  "
-          base-uri="file:/fonts/ibm" />
+           base-uri="file:/fonts/ibm" />
       <font-triplet name="sans-serif" style="normal" weight="normal"/>
       <font-triplet name="Helvetica" style="normal" weight="normal"/>
       <font-triplet name="any" style="normal" weight="normal"/>
     </font>
 
 If "base-uri" is missing or a relative URI, the fonts are resolved relative to the font base URI specified in the configuration (or on the FopFactory).
-Previously, the location of the font files was given by the "path" attribute. This is still supported for the time being, but you should move to using the more flexible "base-uri" attribute so you can profit from the power of URI resolvers.
+
+<note>Previously, the location of the font files was given by the "path" attribute. This is still supported for the time being, but you should move to using the more flexible "base-uri" attribute so you can profit from the power of URI resolvers.</note>
+
 A CID-keyed font (Type 0, double-byte outline font) configuration is much the same as an outline font. However, the characterset definition is now required within the afp-font element.
 
     :::xml
     <font>
-        <afp-font type="CIDKeyed" characterset="CZJHMNU"
+      <afp-font type="CIDKeyed" characterset="CZJHMNU"
            codepage="T1120000" encoding="UnicodeBigUnmarked"
            base-uri="file:/fonts/ibm" />
-        <font-triplet name="J-Heisei Mincho" style="normal" weight="normal" />
+      <font-triplet name="J-Heisei Mincho" style="normal" weight="normal" />
     </font>
 
 Note that the value of the encoding attribute in the example is the double-byte encoding 'UnicodeBigUnmarked' (UTF-16BE).
@@ -572,7 +574,7 @@ By default the AFP Renderer will place a
     :::xml
     <resource-group-file>external_resources.afp</resource-group-file>
 
-Be careful when using this option not to overwrite existing resource files from previous rendering runs.
+<note>Be careful when using this option not to overwrite existing resource files from previous rendering runs.</note>
 
 #### Resource Level Defaults {#afp-resource-level-defaults}
 
@@ -692,7 +694,9 @@ Apache FOP supports embedding an externa
       </fo:declarations>
 
 The `afp:include-form-map` is to be placed as a direct child of `fo:declarations`. The `name` is an AFP resource name (max. 8 characters) and the `src` attribute is the URI identifying the external form map resource. When such a form map is embedded, you can use the `afp:invoke-medium-map` extension (described above) to invoke any medium map included in the form map.
-Apache FOP doesn't support a way to define a form map or medium map using XML means inside an XSL-FO document. You will have to build the form map with some third-party tool.
+
+<note>Apache FOP doesn't support a way to define a form map or medium map using XML means inside an XSL-FO document. You will have to build the form map with some third-party tool.</note>
+
 ### Foreign Attributes {#afp-foreign-attributes}
 
 #### Resource {#afp-foreign-attributes-resource}
@@ -730,7 +734,9 @@ The resource-level attribute where the r
 JFOR, an open source XSL-FO to RTF converter has been integrated into Apache FOP. This will create an RTF (rich text format) document that will attempt to contain as much information from the XSL-FO document as possible. It should be noted that is not possible (due to RTF's limitations) to map all XSL-FO features to RTF. For complex documents, the RTF output will never reach the feature level from PDF, for example. Thus, using RTF output is only recommended for simple documents such as letters.
 
 The RTF output follows Microsoft's RTF specifications and produces best results on Microsoft Word.
-RTF output is currently unmaintained and lacks many features compared to other output formats. Using other editable formats like Open Document Format, instead of producing XSL-FO then RTF through FOP, might give better results.
+
+<note>RTF output is currently unmaintained and lacks many features compared to other output formats. Using other editable formats like Open Document Format, instead of producing XSL-FO then RTF through FOP, might give better results.</note>
+
 These are some known restrictions compared to other supported output formats (not a complete list):
 
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/pdfa.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/pdfa.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/pdfa.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/pdfa.mdtext Fri Dec 14 13:06:02 2012
@@ -54,7 +54,7 @@ There are a number of things that must b
 
 - No filter must be specified explicitely for metadata objects. Metadata must be embedded in clear text so non-PDF-aware applications can extract the XMP metadata.
 
-There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is particularly the specification of the natural language and alternative descriptions for images. Please refer to the [Accessibility page](accessibility.html) for details.
+<note>There are additional requirements if you want to enabled PDF/A-1a (Tagged PDF). This is particularly the specification of the natural language and alternative descriptions for images. Please refer to the [Accessibility page](accessibility.html) for details.</note>
 
 ## PDF profile compatibility {#profile-compatibility}
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext?rev=1421838&r1=1421837&r2=1421838&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext Fri Dec 14 13:06:02 2012
@@ -32,7 +32,6 @@ Further restrictions can be imposed by u
 |  `-noassembledoc`  | disable assembling documents |
 |  `-noprinthq`  | disable high quality printing |
 
-
 ## Usage (embedded) {#embedded}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
@@ -50,7 +49,9 @@ When FOP is embedded in another Java app
 | allowAccessContent | Allows/disallows text and graphics extraction for accessibility purposes | "TRUE" or "FALSE" | "TRUE" |
 | allowAssembleDocument | Allows/disallows assembling document | "TRUE" or "FALSE" | "TRUE" |
 | allowPrintHq | Allows/disallows high quality printing | "TRUE" or "FALSE" | "TRUE" |
-Encryption is enabled as soon as one of these options is set.
+
+<note>Encryption is enabled as soon as one of these options is set.</note>
+
 An example to enable PDF encryption in Java code:
 
     :::java



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message