diff options
| author | Jeremias Maerki <jeremias@apache.org> | 2005-12-07 15:15:38 +0000 |
|---|---|---|
| committer | Jeremias Maerki <jeremias@apache.org> | 2005-12-07 15:15:38 +0000 |
| commit | 973d676bae6d1253f8675b216704752f5897e2fa (patch) | |
| tree | e4a7d895f45fc91d51ad39344a59a78379a9554e /src/documentation/content/xdocs/trunk/configuration.xml | |
| parent | 60cf5396d817f66e1da6ab8ad1b589457be8c41c (diff) | |
| download | xmlgraphics-fop-973d676bae6d1253f8675b216704752f5897e2fa.tar.gz xmlgraphics-fop-973d676bae6d1253f8675b216704752f5897e2fa.zip | |
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
Diffstat (limited to 'src/documentation/content/xdocs/trunk/configuration.xml')
| -rw-r--r-- | src/documentation/content/xdocs/trunk/configuration.xml | 22 |
1 files changed, 22 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> |