X-Git-Url: https://git.stg.codes/stg.git/blobdiff_plain/0c9c28efcd43f53ac54aa60b2dfefa69c70dbadf..6b6d9b29e9e9e91f79507a8bf193fb30de311dcc:/doc/help/xslt/params/section.container.element.xml diff --git a/doc/help/xslt/params/section.container.element.xml b/doc/help/xslt/params/section.container.element.xml new file mode 100644 index 00000000..a6c40599 --- /dev/null +++ b/doc/help/xslt/params/section.container.element.xml @@ -0,0 +1,62 @@ + + +section.container.element +list +block +wrapper + + +section.container.element +Select XSL-FO element name to contain sections + + + + +block + + + +Description + +Selects the element name for outer container of +each section. The choices are block (default) +or wrapper. +The fo: namespace prefix is added +by the stylesheet to form the full element name. + + +This element receives the section id +attribute and the appropriate section level attribute-set. + + +Changing this parameter to wrapper +is only necessary when producing multi-column output +that contains page-wide spans. Using fo:wrapper +avoids the nesting of fo:block +elements that prevents spans from working (the standard says +a span must be on a block that is a direct child of +fo:flow). + + +If set to wrapper, the +section attribute-sets only support properties +that are inheritable. That's because there is no +block to apply them to. Properties such as +font-family are inheritable, but properties such as +border are not. + + +Only some XSL-FO processors need to use this parameter. +The Antenna House processor, for example, will handle +spans in nested blocks without changing the element name. +The RenderX XEP product and FOP follow the XSL-FO standard +and need to use wrapper. + + + +