DOCSLIB.ORG

Extensible Stylesheet Language (XSL) - 2 - Abstract

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Extensible Stylesheet Language (XSL) - 2 - Abstract Extensible Stylesheet Language (XSL) - 2 - Abstract XSL is a language for expressing stylesheets. It consists of two parts: • a language for transforming XML documents, and • an XML vocabulary for specifying formatting semantics. An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary. - 3 - Contents 1 Processing a Stylesheet . 1 1.1 Introduction to stylesheet processing . 1 1.2 Tree Transformations . 1 1.3 Formatting . 2 1.4 Some test lists . 3 2 Benefits of XSL . 5 2.1 Paging and Scrolling . 5 2.2 Selectors and Tree Construction . 6 2.3 An Extended Page Layout Model . 6 2.4 A Comprehensive Area Model . 7 2.5 Internationalization and Writing-Modes . 7 2.6 Linking . 7 - 4 - More Complex XSL FO Test Document Introduction to stylesheet processing 1 Processing a Stylesheet 1.1 Introduction to stylesheet processing mandated to provide these as separate pro- An XSL stylesheet processor accepts a docu- cesses. Furthermore, implementations are free ment or data in XML and an XSL stylesheet and to process the source document in any way that produces the presentation of that XML source produces the same result as if it were processed content that was intended by the designer of that using the conceptual XSL processing model. stylesheet. There are two aspects of this presen- A diagram depicting the detailed conceptual tation process: first, constructing a result tree model is shown below. from the XML source tree andsecond, interpret- ing the result tree to produce formatted results suitable for presentation on a display, on paper, in speech, or onto other media. The first aspect is called tree transformation and the second is called formatting. The process of formatting is performed by the formatter. This format- ter may simply be a rendering engine inside a browser. Tree transformation allows the structure of the result tree to be significantly different from the structure of the source tree. For example, one 1.2 Tree Transformations could add a table-of-contents as a filtered se- lection of an original source document, or one Tree transformation constructs the result tree. could rearrange source data into a sorted tabular In XSL, this tree is called the element and at- presentation. In constructing the result tree, the tribute tree, with objects primarily in the "for- tree transformation process also adds the infor- matting object" namespace. In this tree, a for- mation necessary to format that result tree. matting object is represented as an XML ele- ment, with the properties represented by a set Formatting is enabled by including formatting of XML attribute-value pairs. The content of semantics in the result tree. Formatting se- the formatting object is the content of the XML mantics are expressed in terms of a catalog of element. Tree transformation is defined in the classes of formatting objects. The nodes of the XSLT Recommendation. A diagram depicting result tree are formatting objects. The classes this conceptual process is shown below. of formatting objects denote typographic ab- stractions such as page, paragraph, table, and so forth. Finer control over the presentation of these abstractions is provided by a set of formatting properties, such as those controlling indents, word- and letter-spacing, and widow, orphan, and hyphenation control. In XSL, the classes of formatting objects and formatting properties provide the vocabulary for express- ing presentation intent. The XSL processing model is intended to be conceptual only. An implementation is not 1 More Complex XSL FO Test Document Formatting The XSL stylesheet is used in tree transforma- that will be applied to the content of that format- tion. A stylesheet contains a set of tree con- ting object as a result of formatting the whole struction rules. The tree construction rules have result tree. Each formatting object class repre- two parts: a pattern that is matched against ele- sents a particular kind of formatting behavior. ments in the source tree and a template that con- For example, the block formatting object class structs a portion of the result tree. This allows represents the breaking of the content of a para- a stylesheet to be applicable to a wide class of graph into lines. Other parts of the specification documents that have similar source tree struc- may come from other formatting objects; for ex- tures. ample, the formatting of a paragraph (block for- matting object) depends on both the specifica- In some implementations of XSL/XSLT, the tion of properties on the block formatting object result of tree construction can be output as an and the specification of the layout structure into XML document. This would allow an XML which the block is placed by the formatter. document which contains formatting objects and formatting properties to be output. This The properties associated with an instance of capability is neither necessary for an XSL pro- a formatting object control the formatting of cessor nor is it encouraged. There are, however, that object. Some of the properties, for exam- cases where this is important, such as a server ple "color", directly specify the formatted re- preparing input for a known client; for example, sult. Other properties, for example "space-be- the way that a WAP (h tt p: / /w w w. wa p fo - fore", only constrain the set of possible format- ru m .o rg / fa q s/ in d ex . ht m ) server prepares ted results without specifying any particular for- specialized input for a WAP capable hand held matted result. The formatter may make choices device. To preserve accessibility, designers among other possible considerations such as es- of Web systems should not develop architec- thetics. tures that require (or use) the transmission of Formatting consists of the generation of a tree of documents containing formatting objects and geometric areas, called the area tree. The geo- properties unless either the transmitter knows metric areas are positioned on a sequence of one that the client can accept formatting objects and or more pages (a browser typically uses a single properties or the transmitted document contains page). Each geometric area has a position on the a reference to the source document(s) used page, a specification of what to display in that in the construction of the document with the area and may have a background, padding, and formatting objects and properties. borders. For example, formatting a single char- 1.3 Formatting acter generates an area sufficiently large enough to hold the glyph that is used to present the char- Formatting interprets the result tree in its for- acter visually and the glyph is what is displayed matting object tree form to produce the presen- in this area. These areas may be nested. For tation intended by the designer of the stylesheet example, the glyph may be positioned within a from which the XML element and attribute tree line, within a block, within a page. in the "fo" namespace was constructed. Rendering takes the area tree, the abstract model The vocabulary of formatting objects supported of the presentation (in terms of pages and their by XSL--the set of f o: element types--repre- collections of areas), and causes a presentation sents the set of typographic abstractions avail- to appear on the relevant medium, such as a able to the designer. Semantically, each format- browser window on a computer display screen tingobject represents a specificationfor a part of or sheets of paper. The semantics of rendering the pagination, layout, and styling information are not described in detail in this specification. 2 More Complex XSL FO Test Document Some test lists The first step in formatting is to "objectify" the The third step in formatting is the construction element and attribute tree obtained via an XSLT of the area tree. The area tree is generated transformation. Objectifying the tree basically as described in the semantics of each format- consists of turning the elements in the tree into ting object. The traits applicable to each for- formatting object nodes and the attributes into matting object class control how the areas are property specifications. The result of this step generated. Although every formatting property is the formatting object tree. may be specified on every formatting object, for each formatting object class, only a subset of the As part of the step of objectifying, the char- formatting properties are used to determine the acters that occur in the result tree are replaced traits for objects of that class. by f o: c ha ra c te r nodes. Characters in text nodes which consist solely of whitespace char- 1.4 Some test lists acters and which are children of elements whose An Ordered List: corresponding formatting objects do not per- 1. The 1st item in this 1st level list. mit f o :c h ar ac t er nodes as children are ig- 2. The 2nd item in this 1st level list. nored. Other characters within elements whose corresponding formatting objects do not permit a. The 1st item in this 2nd level list. fo : ch ar a ct e r nodes as children are errors. b. The 2nd item in this 2nd level list. The first phase of the Unicode Bidirectional Al- i. The 1st item inthis 3rd level list. gorithm is used to convert implicit Bidirectional ii. The 2nd item in this 3rd level markup to explicit nodes with the appropriate list. directional properties. Care is taken to insure 1. The 1st item in this 4th level that the explicit nodes so introduced are prop- list. erly nested in the formatting object tree.
Load more

Recommended publications
  • Presentation of XML Documents
    Presentation of XML Documents Patryk Czarnik Institute of Informatics University of Warsaw XML and Modern Techniques of Content Management – 2012/13 Stylesheets Separation of content and formatting Separating content and formatting According to XML best practices, documents should contain: “pure” content / data markup for structure and meaning (“semantic” or “descriptive” markup) no formatting How to present? “hard-coded” interpretation of known document types, e.g. Libre Office rendering Writer document importing or pasting content into word processor or DTP tool and manual or automatic formatting, e.g. Adobe InDesign approach external style sheets Patryk Czarnik 05 – Presentation XML 2012/13 4 / 1 Idea of stylesheet <person id="102103" position="specialist"><person id="102105" position="assistant"> <first-name>Dawid</first-name> <first-name>Arkadiusz</first-name> <last-name>Paszkiewicz</last-name> <last-name>Gierasimczyk</last-name> <phone type="office">+48223213203</phone> <phone type="office">+48223213213</phone> <phone type="fax">+48223213200</phone> <phone type="mobile">+48501502503</phone> <email>[email protected]</email> <email>[email protected]</email> </person> </person> * font 'Times 10pt' * yellow backgorund * 12pt for name * blue font and border * abbreviation before * italic font for name phone number * typewritter font for email Stylesheets Separation of content and formatting Benefits of content and formatting separation General advantages of descriptive markup better content understanding and easier analysis Ability to present in the same way: the same document after modification another document of the same structure Formatting managed in one place easy to change style of whole class of documents Ability to define many stylesheets for a document class, depending on purpose and expectations: medium (screen / paper / voice) expected number of details (full report / summary) reader preferences (font size, colors, .
    [Show full text]
  • Sigada 2001 Workshop Symbiosis4jun02 Pub.Fm
    SIGAda 2001 Workshop, “Creating a Symbiotic Relationship Between XML and Ada” Robert C. Leif Ada_Med, a Division of Newport Instruments 5648 Toyon Road, San Diego, CA 92115-1022, USA E-mail [email protected] www.newportinstruments.com www.Ada-Med.com +1 (619)582-0437 Abstract: The purpose of the workshop was to organize the Ada community to take advantage of the opportunity to create Ada applications that are operating systems independent because they are based on a web technology, XML, Extensible Markup Language. The commercial use of the Internet is the driving force behind XML. Four elements of XML, which together are sufficient to build a web application, and all employ the same syntax were described. These are XML; its schema; the Extensible Stylesheet Language, XSL; and the XML mechanism for forms, XForms. XML concerns the data objects that are included on the web page and their order of presentation. The schema contains the information on the types and objects for XML. Schemas are roughly equivalent to an Ada specification without the subprograms. Fortunately, the programing language that has the best fit with XML is Ada. XML has visibility and scoping rules, which are similar to Ada. XML has strong typing and has single inheritance similar to Ada. A mutually beneficial symbiosis requires the creation of applications in Ada that use and support XML, as well as, the use of XML to cre- ate Ada environments including XML based tools. These applications include: automated translation of Ada data types and objects in a specification to an XML schema; and conversely, automated translation of the data types and elements in an XML Schema to an Ada specification.
    [Show full text]
  • SDL Contenta S1000D and SDL Livecontent S1000D Cross-Product Graphics and Multimedia Support
    SDL Contenta S1000D and SDL LiveContent S1000D Cross-Product Graphics and Multimedia Support SDL Contenta S1000D and SDL LiveContent S1000D 5.9 December 2020 Legal notice Copyright and trademark information relating to this product release. Copyright © 2009–2020 SDL Group. SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and exclusive rights of SDL Group. All references to SDL or SDL Group shall mean SDL PLC. and its subsidiaries and affiliates details of which can be obtained upon written request. All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL. Contenta S1000D is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trade- marks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred. This product may include open source or similar third-party software, details of which can be found by clicking the following link: “Acknowledgments” on page 7. Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.
    [Show full text]
  • Refactoring XSLT
    XSLT and XQuery September 19, 2019 Refactoring XSLT Priscilla Walmsley, Datypic, Inc. Class Outline Introduction ......................................................................................................................................2 Cleaning Up......................................................................................................................................9 Improving Code Quality..................................................................................................................14 Other Improvements.......................................................................................................................21 Introduction 2 Obligatory Wikipedia Quote 3 Code refactoring is the process of restructuring existing computer code - changing the factoring - without changing its external behavior. Refactoring improves nonfunctional attributes of the software. Advantages include improved code readability and reduced complexity; these can improve source code maintainability and create a more expressive internal architecture or object model to improve extensibility. Typically, refactoring applies a series of standardised basic micro-refactorings, each of which is (usually) a tiny change in a computer program's source code that either preserves the behaviour of the software, or at least does not modify its conformance to functional requirements. Many development environments provide automated support for performing the mechanical aspects of these basic refactorings. If done extremely well, code
    [Show full text]
  • XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département D©Informatique Et De Recherche Opérationnelle Université De Montréal
    XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 XML to PDF by RenderX XEP XSL-FO Formatter, visit us at http://www.renderx.com/ XML: Looking at the Forest Instead of the Trees Guy Lapalme Professor Département d©informatique et de recherche opérationnelle Université de Montréal C.P. 6128, Succ. Centre-Ville Montréal, Québec Canada H3C 3J7 [email protected] http://www.iro.umontreal.ca/~lapalme/ForestInsteadOfTheTrees/ Publication date April 14, 2019 Abstract This tutorial gives a high-level overview of the main principles underlying some XML technologies: DTD, XML Schema, RELAX NG, Schematron, XPath, XSL stylesheets, Formatting Objects, DOM, SAX and StAX models of processing. They are presented from the point of view of the computer scientist, without the hype too often associated with them. We do not give a detailed description but we focus on the relations between the main ideas of XML and other computer language technologies. A single compact pretty-print example is used throughout the text to illustrate the processing of an XML structure with XML technologies or with Java programs. We also show how to create an XML document by programming in Java, in Ruby, in Python, in PHP, in E4X (Ecmascript for XML) and in Swift. The source code of the example XML ®les and the programs are available either at the companion web site of this document or by clicking on the ®le name within brackets at the start of the caption of each example.
    [Show full text]
  • SVG-Based Knowledge Visualization
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS SVG-based Knowledge Visualization DIPLOMA THESIS Miloš Kaláb Brno, spring 2012 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Advisor: RNDr. Tomáš Gregar Ph.D. ii Acknowledgement I would like to thank RNDr. Tomáš Gregar Ph.D. for supervising the thesis. His opinions, comments and advising helped me a lot with accomplishing this work. I would also like to thank to Dr. Daniel Sonntag from DFKI GmbH. Saarbrücken, Germany, for the opportunity to work for him on the Medico project and for his supervising of the thesis during my erasmus exchange in Germany. Big thanks also to Jochen Setz from Dr. Sonntag’s team who worked on the server background used by my visualization. Last but not least, I would like to thank to my family and friends for being extraordinary supportive. iii Abstract The aim of this thesis is to analyze the visualization of semantic data and sug- gest an approach to general visualization into the SVG format. Afterwards, the approach is to be implemented in a visualizer allowing user to customize the visualization according to the nature of the data. The visualizer was integrated as an extension of Fresnel Editor. iv Keywords Semantic knowledge, SVG, Visualization, JavaScript, Java, XML, Fresnel, XSLT v Contents Introduction . .3 1 Brief Introduction to the Related Technologies ..........5 1.1 XML – Extensible Markup Language ..............5 1.1.1 XSLT – Extensible Stylesheet Lang.
    [Show full text]
  • Ditype User Guide
    DiType User Guide DiType User Guide http://mediawiki.renderx.com/index.php/DiType_User_Guide This Book Is Generated By WikiBooks2PDF using RenderX DiType, XML to PDF XSL-FO Formatter 28 August 2008 DiType User Guide Table of Contents 1. Preface.............................................................................7 What's in this Document? . 7 Prerequisites . .................7 Technical Support . ..............8 2. Overview...........................................................................9 Using DiType . ..................9 Individual User Book Creation . 10 Corporate Documentation System . 11 Mass Production of Documents . 12 Small Office/Home Office . 13 3. Installation.......................................................................15 Windows . .....................15 Mac OS X ................................................ ....................20 Unix/Linux . ...................26 4. Standard Applications..........................................................27 DiType Assistant . 27 What is the DiType Assistant? . 27 Opening the DiType Assistant . 28 Rendering an XML File using the DiType Assistant . 28 DiType Command Line . 31 Running DiType . 31 ditype Switches . 31 ditype Arguments . 33 ActiType . .....................33 Opening ActiType . 34 Formatting an XML or FO File using ActiType . 35 Stopping a Hot Folder . 39 - 3 - by , XML to PDF XSL-FO Formatter DiType User Guide Closing the Application . 40 Running ActiType in Console Mode . 40 Sharing ActiType . 41 5. Configuring DiType.............................................................43
    [Show full text]
  • Create an HTML Output from Your Own Project with XSLT
    Create an HTML output from your own project with XSLT Martina Semlak - Georg Vogeler IDE Spring School 2015, Graz Folie 2 IDE Spring School 2015, Graz Minimal stuff provided <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xpath-default-namespace="http://www.tei-c.org/ns/1.0" version="2.0"> <xsl:output method="xml" omit-xml-declaration="yes" encoding="UTF-8" indent="yes" /> </xsl:stylesheet> Folie 3 IDE Spring School 2015, Graz First step Grab file xsl:template with the attribute: match="/" This template can contain the basic HTML structure of the ouput file Folie 4 IDE Spring School 2015, Graz HTML basics – Reminder <html> <head><title></title><link (e.g. for a css)></head> <body></body> </html> We added this into <xsl:template match="/"> </xsl:template> Folie 5 IDE Spring School 2015, Graz Display text We have prepared basic HTML structure for you: header, section, nav > ul = navigation with references to other files We need a heading for the whole text: html: section > h3 xsl: xsl:value-of, attribute select with the appropriate xpath: //body/head div seems to be convenient to retain: do something with all divs: <xsl:apply-templates select="//body/div"/> what to do: <xsl:template match="div"> <div><xsl:apply-templates /></div> </xsl:template> Folie 6 IDE Spring School 2015, Graz XPath conditions Use a condition in the XPath (square brackets) for html: body/header > h1 and h2: find the appropriate title-element with type main or sub <h1> <xsl:value-of select="//title[@type='main']"/> </h1> Folie 7 IDE Spring School 2015, Graz <apply-templates />: individual templates xsl:template match="lg" div class="stanza" xsl:template match="l" <br/>..
    [Show full text]
  • Markup UK 2021 Proceedings
    2021 Proceedings A Conference about XML and Other Markup Technologies Markup UK 2021 Proceedings 2 Markup UK 2021 Proceedings 3 Markup UK 2021 Proceedings Markup UK Sister Conferences A Conference about XML and Other Markup Technologies https://markupuk.org/ Markup UK Conferences Limited is a limited company registered in England and Wales. Company registration number: 11623628 Registered address: 24 Trimworth Road, Folkestone, CT19 4EL, UK VAT Registration Number: 316 5241 25 Organisation Committee Geert Bormans Tomos Hillman Ari Nordström Andrew Sales Rebecca Shoob Markup UK 2021 Proceedings Programme Committee by B. Tommie Usdin, David Maus, Syd Bauman – Northeastern University Alain Couthures, Michael Kay, Erik Digital Scholarship Group Siegel, Debbie Lapeyre, Karin Bredenberg, Achim Berndzen – <xml-project /> Jaime Kaminski, Robin La Fontaine, Abel Braaksma – Abrasoft Nigel Whitaker, Steven Pemberton, Tony Peter Flynn – University College Cork Graham and Liam Quin Tony Graham – Antenna House Michael Kay – Saxonica The organisers of Markup UK would like to Jirka Kosek – University of Economics, thank Antenna House for their expert and Prague unstinting help in preparing and formatting Deborah A. Lapeyre – Mulberry the conference proceedings, and their Technologies generosity in providing licences to do so. David Maus – State and University Library Hamburg Antenna House Formatter is based on the Adam Retter – Evolved Binary W3C Recommendations for XSL-FO and B. Tommie Usdin – Mulberry Technologies CSS and has long been recognized as Norman Walsh – MarkLogic the most powerful and proven standards Lauren Wood – XML.com based formatting software available. It is used worldwide in demanding applications Thank You where the need is to format HTML and XML into PDF and print.
    [Show full text]
  • Release Notes for the Docbook XSL Stylesheets I
    Release Notes for the DocBook XSL Stylesheets i Release Notes for the DocBook XSL Stylesheets Release Notes for the DocBook XSL Stylesheets ii Contents 1 Release Notes: snapshot 1 2 Release Notes: 1.79.2 1 3 Release Notes: 1.79.1 1 3.1 Gentext . .1 3.2 Common . .2 3.3 FO...........................................................4 3.4 HTML.........................................................9 3.5 Manpages . 13 3.6 Epub.......................................................... 14 3.7 HTMLHelp . 16 3.8 Eclipse . 16 3.9 JavaHelp . 16 3.10 Slides . 17 3.11 Website . 17 3.12 Webhelp . 18 3.13 Params . 18 3.14 Profiling . 20 3.15Lib........................................................... 20 3.16 Tools . 20 3.17 Template . 21 3.18 Extensions . 21 4 Release Notes: 1.79.0 21 4.1 Gentext . 22 4.2 Common . 23 4.3 FO........................................................... 24 4.4 HTML......................................................... 29 4.5 Manpages . 34 4.6 Epub.......................................................... 35 4.7 HTMLHelp . 36 4.8 Eclipse . 36 4.9 JavaHelp . 37 4.10 Slides . 37 4.11 Website . 38 4.12 Webhelp . 38 4.13 Params . 39 Release Notes for the DocBook XSL Stylesheets iii 4.14 Profiling . 40 4.15Lib........................................................... 40 4.16 Tools . 40 4.17 Template . 41 4.18 Extensions . 42 5 Release Notes: 1.78.1 42 5.1 Common . 42 5.2 FO........................................................... 43 5.3 HTML......................................................... 43 5.4 Manpages . 44 5.5 Webhelp . 44 5.6 Params . 44 5.7 Highlighting . 44 6 Release Notes: 1.78.0 44 6.1 Gentext . 45 6.2 Common . 45 6.3 FO........................................................... 46 6.4 HTML......................................................... 47 6.5 Manpages .
    [Show full text]
  • XSL Formatting Objects XSL Formatting Objects
    XSL Formatting Objects XSL Formatting Objects http://en.wikipedia.org/wiki/XSL_Formatting_Objects This Book Is Generated By WikiType using RenderX DiType, XML to PDF XSL-FO Formatter Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". 29 September 2008 XSL Formatting Objects Table of Contents 1. XSL Formatting Objects.........................................................4 XSL-FO basics. ...............4 XSL-FO language concepts. 6 XSL-FO document structure. 6 Capabilities of XSL-FO v1.0. 7 Multiple columns. ...........7 Lists.........................................................................8 Pagination controls. 8 Footnotes....................................................................8 Tables................................................ ........................8 Text orientation controls. 9 Miscellaneous...............................................................9 Capabilities of XSL-FO v1.1. 9 Multiple flows and flow mapping. 9 Bookmarks.................................................................10 Indexing....................................................................10 Last page citation. 10 Table markers. 10 Inside/outside floats. 10 Refined graphic sizing. 11 Advantages of XSL-FO. 11 Drawbacks
    [Show full text]
  • XSL-FO by Dave Pawson Publisher
    XSL-FO By Dave Pawson Publisher : O'Reilly Pub Date : August 2002 ISBN : 0-596-00355-2 Pages : 282 Table of • Contents • Index • Reviews Reader • Reviews Extensible Style Language-Formatting Objects, or XSL-FO, is a set of tools developers and web designers use to describe page printouts of their XML (including XHTML) documents. XSL-FO teaches you how to think about the formatting of your documents and guides you through the questions you'll need to ask to ensure that your printed documents meet the same high standards as your computer-generated content. 777 Copyright Preface Who Should Read This Book? What Does This Book Cover? Motivation Organization of This Book What Else Do You Need? Conventions Used in This Book How to Contact Us Acknowledgments Chapter 1. Planning for XSL-FO Section 1.1. XML and Document Processing Section 1.2. Choosing Your Print Production Approach Section 1.3. Choosing Tools Section 1.4. The Future for XSL-FO Chapter 2. A First Look at XSL-FO Section 2.1. An XSL-FO Overview Section 2.2. Related Stylesheet Specifications Section 2.3. Using XSL-FO as Part of XSL Section 2.4. Shorthand, Short Form, and Inheritance Chapter 3. Pagination Section 3.1. Document Classes Section 3.2. The Main Parts of an XSL-FO Document Section 3.3. Simple Page Master Section 3.4. Complex Pagination Section 3.5. Page Sequences Chapter 4. Areas Section 4.1. Informal Definition of an Area Section 4.2. Area Types Section 4.3. Components of an Area Section 4.4.
    [Show full text]