<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="docbook.css.source"> <refmeta> <refentrytitle>docbook.css.source</refentrytitle> <refmiscinfo class="other" otherclass="datatype">string</refmiscinfo> </refmeta> <refnamediv> <refname>docbook.css.source</refname> <refpurpose>Name of the default CSS input file</refpurpose> </refnamediv> <refsynopsisdiv> <src:fragment xml:id="docbook.css.source.frag"><xsl:param name="docbook.css.source">docbook.css.xml</xsl:param></src:fragment> </refsynopsisdiv> <refsection><info><title>Description</title></info> <para>The <parameter>docbook.css.source</parameter> parameter specifies the name of the file containing the default DocBook CSS styles. Those styles are necessary when the <parameter>make.clean.html</parameter> parameter is nonzero.</para> <para>The file is a well-formed XML file that must consist of a single <tag>style</tag> root element that contains CSS styles as its text content. The default value of the parameter (and filename) is <literal>docbook.css.xml</literal>. The stylesheets ship with the default file. You can substitute your own and specify its path in this parameter.</para> <para>If <parameter>docbook.css.source</parameter> is not blank, and <parameter>make.clean.html</parameter> is nonzero, then the stylesheet takes the following actions:</para> <orderedlist> <listitem> <para>The stylesheet uses the XSLT <literal>document()</literal> function to open the file specified by the parameter and load it into a variable.</para> </listitem> <listitem> <para>The stylesheet forms an output pathname consisting of the value of the <parameter>base.dir</parameter> parameter (if it is set) and the value of <parameter>docbook.css.source</parameter>, with the <literal>.xml</literal> suffix stripped off. </para> </listitem> <listitem> <para>The stylesheet removes the <tag>style</tag> wrapper element and writes just the CSS text content to the output file.</para> </listitem> <listitem> <para>The stylesheet adds a <tag>link</tag> element to the HTML <tag>HEAD</tag> element to reference the external CSS stylesheet. For example:</para> <programlisting><link rel="stylesheet" href="docbook.css" type="text/css"> </programlisting> <para>However, if the <parameter>docbook.css.link</parameter> parameter is set to zero, then no <tag>link</tag> is written for the default CSS file. That is useful if a custom CSS file will import the default CSS stylesheet to ensure proper cascading of styles.</para> </listitem> </orderedlist> <para>If the <parameter>docbook.css.source</parameter> parameter is changed from its default <literal>docbook.css.xml</literal> to blank, then no default CSS is generated. Likewise if the <parameter>make.clean.html</parameter> parameter is set to zero, then no default CSS is generated. The <parameter>custom.css.source</parameter> parameter can be used instead to generate a complete custom CSS file.</para> <para>You can use the <parameter>generate.css.header</parameter> parameter to instead write the CSS to each HTML <tag>HEAD</tag> element in a <tag>style</tag> tag instead of an external CSS file.</para> </refsection> </refentry>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#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. |