<refentry xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:src="http://nwalsh.com/xmlns/litprog/fragment" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="5.0" xml:id="textinsert.extension"> <refmeta> <refentrytitle>textinsert.extension</refentrytitle> <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo> </refmeta> <refnamediv> <refname>textinsert.extension</refname> <refpurpose>Enables the textinsert extension element</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="textinsert.extension.frag"> <xsl:param name="textinsert.extension" select="1"/> </src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>The textinsert extension element inserts the contents of a file into the result tree (as text).</para> <note> <para>To use the textinsert extension element, you must use either Saxon or Xalan as your XSLT processor (it doesn’t work with xsltproc), along with either the DocBook Saxon extensions or DocBook Xalan extensions (for more information about those extensions, see <link role="tcg" xlink:href="InstallingAProcessor.html#SaxonExtensions" >DocBook Saxon Extensions</link> and <link role="tcg" xlink:href="InstallingAProcessor.html#XalanExtensions" >DocBook Xalan Extensions</link>), and you must set both the <parameter>use.extensions</parameter> and <parameter>textinsert.extension</parameter> parameters to <literal>1</literal>.</para> <para>As an alternative to using the textinsert element, consider using an Xinclude element with the <literal>parse="text"</literal> attribute and value specified, as detailed in <link role="tcg" xlink:href="ExternalCode.html#XIncludeCode" >Using XInclude for text inclusions</link>.</para> </note> </refsection> <refsection><info><title>See Also</title></info> <para>You can also use the <tag class="xmlpi">dbhtml-include href</tag> processing instruction to insert external files — both files containing plain text and files with markup content (including HTML content).</para> </refsection> <refsection><info><title>More information</title></info> <para>For how-to documentation on inserting contents of external code files and other text files into output, see <link role="tcg" xlink:href="ExternalCode.html" >External code files</link>.</para> <para>For guidelines on inserting contents of HTML files into output, see <link role="tcg" xlink:href="InsertExtHtml.html" >Inserting external HTML code</link>.</para> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 26953 | Paul Allen | Move //guest/perforce_software/p4convert to //guest/perforce_software/p4convert/main | ||
//guest/perforce_software/p4convert/docs/docbook-xsl-ns-1.78.1/params/textinsert.extension.xml | |||||
#2 | 14806 | Paul Allen | Update docs and add +w. | ||
#1 | 13920 | Paul Allen | copy part 2 (no errors) | ||
//guest/paul_allen/p4convert-maven/docs/docbook-xsl-ns-1.78.1/params/textinsert.extension.xml | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/params/textinsert.extension.xml | |||||
#1 | 12728 | eedwards |
Upgrade ANT doc build infrastructure to assemble PDFs: - remove non-namespaced DocBook source and add namespaced DocBook source. - add Apache FOP 1.1 - copy fonts, images, XSL into _build, establishing new asset structure. The original structure remains until all guides using it can be upgraded, and several other issues can be resolved. - updated build.xml to allow for per-target build properties. - upgraded the P4SAG to use the new infrastructure. - tweaked admonition presentation in PDFs to remove admonition graphics, and resemble closely the presentation used in the new HTML layout, including the same colors. With these changes, building PDFs involves using a shell, navigating into the guide's directory (just P4SAG for now), and executing "ant pdf". Issues still to be resolved: - PDF generation encounters several warnings about missing fonts (bold versions of Symbol and ZapfDingbats), and a couple of locations where the page content exceeds the defined content area. - Due to issues within Apache FOP, PDF generation emits a substantial amount of output that is not easily suppressed without losing important warning information. - Apache FOP's interface to ANT does not expose a way to set the font base directory. The current configuration does work under Mac OSX, but further testing on Windows will need to be done to determine if the relative paths defined continue to work. The workaround is for Windows users to customize the fop-config.xml to provide absolute system paths to the required fonts. - HTML generation needs further browser testing, and exhibits broken navigation on iOS browsers within the TOC sidebar. - A number of PDF and HTML presentation tweaks still need to be made, for example: sidebars, gui* DocBook tags, whitespace, section separation, etc. |