Alternative set of rules for text indent calculation (start-indent and end-indent) which tries to mimic many commercial FO implementation that have chosen to break the specification in this aspect. I think I have found the behaviour for most cases. But I'm operating in reverse-engineering mode here and not all FO implementations behave in the same way!

This is an optional feature that has to be explicitely enabled through the user agent. Otherwise, FOP will behave like before.
In the FO tree tests a processing instruction is used to enable the feature/bug ;-) in the user agent so I can test both cases.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@354763 13f79535-47bb-0310-9956-ffa450edef68

2 files changed, 31 insertions, 0 deletions

diff --git a/src/documentation/content/xdocs/trunk/configuration.xml b/src/documentation/content/xdocs/trunk/configuration.xml
index c5e1b8973..16465f54b 100644
--- a/src/documentation/content/xdocs/trunk/configuration.xml
+++ b/src/documentation/content/xdocs/trunk/configuration.xml
@@ -76,6 +76,28 @@
         <td>Resolution in dpi (dots per inch) which is used internally.</td>
       </tr>
       <tr>
+        <td>strict-validation</td>
+        <td>Boolean (true, false)</td>
+        <td>
+          Setting this option to 'false' causes FOP to be more forgiving about XSL-FO validity, 
+          for example, you're allowed to specify a border on a region-body which is supported 
+          by some FO implementations but is non-standard. Note that such a border would 
+          currently have no effect in Apache FOP.</td>
+      </tr>
+      <tr>
+        <td>break-indent-inheritance</td>
+        <td>Boolean (true, false)</td>
+        <td>
+          Setting this option to 'true' causes FOP to use an alternative rule set to determine
+          text indents specified through margins, start-indent and end-indent. Many commercial
+          FO implementations have chosen to break the XSL specification in this aspect. This
+          option tries to mimic their behaviour. Please note that Apache FOP may still not
+          behave exactly like those implementations either because FOP has not fully matched
+          the desired behaviour and because the behaviour among the commercial implementations
+          varies. The default for this option (i.e. false) is to behave exactly like the 
+          specification describes.</td>
+      </tr>
+      <tr>
         <td>default-page-settings</td>
         <td>n/a</td>
         <td>
diff --git a/src/documentation/content/xdocs/trunk/embedding.xml b/src/documentation/content/xdocs/trunk/embedding.xml
index 2e77c11ab..f54af136a 100644
--- a/src/documentation/content/xdocs/trunk/embedding.xml
+++ b/src/documentation/content/xdocs/trunk/embedding.xml
@@ -359,6 +359,15 @@ Fop fop = new Fop(MimeConstants.MIME_POSTSCRIPT, userAgent);]]></source>
         </p>
         <source>userAgent.setPDFEncryptionParams(new PDFEncryptionParams(null, "owner", false, false, true, true));</source>
       </li>
+      <li>
+        <p>
+          Enable an <strong>alternative set of rules for text indents</strong> that tries to mimic the behaviour of many commercial 
+          FO implementations that chose to break the specification in this aspect. The default of this option is 
+          'false' which causes Apache FOP to behave exactly as describes in the specification. To enable the 
+          alternative behaviour, call:
+        </p>
+        <source>userAgent.setBreakIndentInheritanceOnReferenceAreaBoundary(true);</source>
+      </li>
     </ul>
     <note>
       You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially