The DocBook XSL stylesheets are a set of XSLT stylesheets for the XML -based DocBook language.
9-406: DocBook is a semantic markup language. That is, it specifies the meaning of the elements in a document, not how they are intended to be presented to the end user. It provides separation between the content of the document and the visual representation . While DocBook is a readable markup language, it is not intended to be read by end-users in its DocBook form. The purpose of DocBook XSL is to provide
18-647: A standard set of transformations from DocBook to several presentational formats. DocBook XSL provides for transforms into the following formats: Webhelp is a chunked HTML output format in the DocBook xslt stylesheets that was introduced in version 1.76.1. The documentation for web help also provides an example of web help and is part of the DocBook xsl distribution. Its major features include CSS-based page layout without frameset, multilingual full content search, Table of contents (TOC) pane with collapsible TOC tree, Auto-synchronization of content pane and TOC. This web help format
27-476: Is a stub . You can help Misplaced Pages by expanding it . This digital typography article is a stub . You can help Misplaced Pages by expanding it . Separation of presentation and content Separation of content and presentation (or separation of content and style ) is the separation of concerns design principle as applied to the authoring and presentation of content. Under this principle, visual and design aspects (presentation and style) are separated from
36-447: Is not a rigid guideline, but serves more as best practice for keeping appearance and structure separate. In many cases, the design and development aspects of a project are performed by different people, so keeping both aspects separated ensures both initial production accountability and later maintenance simplification, as in the don't repeat yourself (DRY) principle. LaTeX is a document markup language that focuses primarily on
45-468: The CSS portion of a HTML document, where the formatting, document specifications and other visual attributes are specified. Under this methodology, academic writings and publications can be structured, styled and typeset with minimal effort by its creators. In fact, it also prevents the end-users — who are usually not trained as designers themselves — from alternating between tweaking the formatting and working on
54-558: The XSL-FO transforms allow the user to define the size of the pages. Additionally, the XSLT documents themselves are modular; it is possible for the user to add, change, or replace particular levels of functionality. This can allow DocBook XSL to process new documentation tags added to the standard DocBook, or to simply change how the XSLTs generate the resulting format. This markup language article
63-456: The content and structure of a document. When a document is prepared using the LaTeX system, the source code of the document can be divided into two parts: the document body and the preamble (and the style sheets). The document body can be likened to the body of a HTML document, where one specifies the content and the structure of the document, whereas the preamble (and the style sheets) can be likened to
72-484: The core material and structure (content) of a document. A typical analogy used to explain this principle is the distinction between the human skeleton (as the structural component) and human flesh (as the visual component) which makes up the body's appearance. Common applications of this principle are seen in Web design ( HTML vs. CSS ) and document typesetting ( Lambert's document body vs. its preamble). This principle
81-458: Was originally implemented by Kasun Gajasinghe and David Cramer as part of the Google Summer of Code 2010 program. DocBook XSL also has transformations to slide-like formats for HTML and XSL-FO. EPUB support is currently experimental. DocBook XSL's stylesheets are highly configurable. Each of the different formats has a number of XSLT parameters available for simple customization. For example,
#349650