Name
p:xsl-formatter — The standard p:xsl-formatter step.
Synopsis
The p:xsl-formatter
step receives an XSL 1.1 document and renders the content.
Input port | Primary | Sequence | Content types |
---|---|---|---|
source | ✔ | xml |
Output port | Primary | Sequence | Content types |
---|---|---|---|
result | ✔ | any |
Option name | Type | Default value |
---|---|---|
content-type | xs:string? | () |
parameters | map(xs:QName,item()*)? | () |
Declaration
1 |<p:declare-step xmlns:p="http://www.w3.org/ns/xproc">
| <p:input port="source" content-types="xml"/>
| <p:output port="result" content-types="any"/>
| <p:option name="parameters" as="map(xs:QName,item()*)?"/>
5 | <p:option name="content-type" as="xs:string?"/>
|</p:declare-step>
Errors
Code | Description |
---|---|
err:XC0167 | It is a dynamic error (err:XC0167 ) if the requested document
cannot be produced. |
err:XC0204 | It is a dynamic error (err:XC0204 ) if the requested
content-type is not supported. |
err:XD0079 | It is a dynamic error (err:XD0079 ) if a supplied content-type is not
a valid media type of the form
“type/subtype+ext ”
or “type/subtype ”. |
Implementation defined features
- The use of media type
parameters on the
content-type
option is implementation-defined. - If the
content-type
option is not specified, the output type is implementation-defined. - A formatter may take any number of optional rendering
parameters via the step's
parameters
; such parameters are defined by the XSL implementation used and are implementation-defined.
Description
XML Calabash supports several XSL formatter implementations. There is also a service provider interface so that additional implementations can be provided by third parties. Several CSS formatters are also supported.
Processors can be selected in the configuration file
with the cc:paged-media
element as described in the
User Guide.
Configuration URI | Processor selected |
---|---|
https://xmlcalabash.com/paged-media/xsl-formatter/antenna-house | Antenna House |
https://xmlcalabash.com/paged-media/xsl-formatter/fop | Apache FOP |
You must also obtain and install the relevant processor, configure it on your system, and satisfy its licensing requirements. The XML Calabash distribution includes only the open source Apache FOP processor.
Antenna House
In order to use the Antenna House formatter, you must install and configure Antenna House Formatter.
You can configure the formatter with
a
configuration property or via the parameters
option.
The following configuration options are supported:
Property name | Type |
---|---|
EmbedAllFontsEx | string: “part”, “base14”, or “all” |
ExitLevel | integer |
ImageCompression | integer |
NoAccessibility | boolean |
NoAddingOrChangingComments | boolean |
NoAssembleDoc | boolean |
NoChanging | boolean |
NoContentCopying | boolean |
NoFillForm | boolean |
NoPrinting | boolean |
OptionFileURI | string |
OwnersPassword | string |
TwoPassFormatting | boolean |
For more information about these properties, consult the AH Formatter API documentation.
The following content-type
s are supported:
Content type | AH output format |
---|---|
application/pdf | @PDF |
application/postscript | @PS |
application/vnd.inx | @INX |
application/vnd.mif | @MIF |
image/svg+xml | @SVG |
text/plain | @TEXT |
Apache FOP
You can configure the formatter with
a
configuration property or via the parameters
option.
The following configuration options are supported:
Property name | Type |
---|---|
Accessibility | boolean |
Author | string |
Base14KerningEnabled | boolean |
BreakIndentInheritanceOnReferenceAreaBoundary | boolean |
ConserveMemoryPolicy | boolean |
CreationDate | date |
Creator | string |
Keywords | string |
LocatorEnabled | boolean |
PageHeight | string |
PageWidth | string |
Producer | string |
SourceResolution | float |
StrictFOValidation | boolean |
StrictUserConfigValidation | boolean |
StrictValidation | boolean |
Subject | string |
TargetResolution | float |
Title | string |
UseCache | boolean |
UserConfig | string |
For more information about the properties, consult the FOP API documentation.
The following content-type
s are supported:
application/pdf
, application/postscript
,
application/x-afp
, application/rtf
,
and text/plain
.