<?xml version="1.0" encoding="US-ASCII"?> <!--This file was created automatically by xsl2profile--> <!--from the DocBook XSL stylesheets.--> <!--This file was created automatically by html2xhtml--> <!--from the HTML stylesheets.--> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:d="http://docbook.org/ns/docbook" xmlns:exsl="http://exslt.org/common" xmlns="http://www.w3.org/1999/xhtml" xmlns:exslt="http://exslt.org/common" xmlns:ng="http://docbook.org/docbook-ng" xmlns:db="http://docbook.org/ns/docbook" exslt:dummy="dummy" ng:dummy="dummy" db:dummy="dummy" extension-element-prefixes="exslt" version="1.0" exclude-result-prefixes="exsl exslt d"> <!-- ******************************************************************** $Id: chunk.xsl 6910 2007-06-28 23:23:30Z xmldoc $ ******************************************************************** This file is part of the XSL DocBook Stylesheet distribution. See ../README or http://docbook.sf.net/release/xsl/current/ for copyright and other information. ******************************************************************** --> <!-- ==================================================================== --> <!-- First import the non-chunking templates that format elements within each chunk file. In a customization, you should create a separate non-chunking customization layer such as mydocbook.xsl that imports the original docbook.xsl and customizes any presentation templates. Then your chunking customization should import mydocbook.xsl instead of docbook.xsl. --> <xsl:import href="docbook-no-doctype.xsl"/> <!-- chunk-common.xsl contains all the named templates for chunking. In a customization file, you import chunk-common.xsl, then add any customized chunking templates of the same name. They will have import precedence over the original chunking templates in chunk-common.xsl. --> <xsl:import href="chunk-common.xsl"/> <!-- The manifest.xsl module is no longer imported because its templates were moved into chunk-common and chunk-code --> <!-- chunk-code.xsl contains all the chunking templates that use a match attribute. In a customization it should be referenced using <xsl:include> instead of <xsl:import>, and then add any customized chunking templates with match attributes. But be sure to add a priority="1" to such customized templates to resolve its conflict with the original, since they have the same import precedence. Using xsl:include prevents adding another layer of import precedence, which would cause any customizations that use xsl:apply-imports to wrongly apply the chunking version instead of the original non-chunking version to format an element. --> <xsl:include href="chunk-code.xsl"/> </xsl:stylesheet>
# | 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/xhtml/profile-chunk.xsl | |||||
#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/xhtml/profile-chunk.xsl | |||||
#1 | 13895 | Paul Allen | Copying using p4convert-docbook | ||
//guest/perforce_software/doc_build/main/docbook-xsl-ns-1.78.1/xhtml/profile-chunk.xsl | |||||
#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. |