Differences between revisions 20 and 21
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
|
<bookinfo> <title>Cookbook for the DocBook in the SQI microPublishing System</title> <subtitle>Markup Examples for the Layout Specific of the Automated Publishing System</subtitle> <affiliation> <orgname>SQI Inc.</orgname> </affiliation> <copyright> <year>2007</year> <holder>SQI Inc.</holder> </copyright> <author> <firstname>Jeff</firstname> <surname>Elpern</surname> </author> </bookinfo> <preface id="preface"> <title>Prefaces</title> <para>The SQI DocBook System combines the power of our Knowledge Base technology - direct input from <emphasis>content authors</emphasis>, continuous improvement, instants publishing, and extensive search - with the power of DocBook technology - extensive specialized markup for technical publication and multichannel publishing. The result is a on-demand environment where content experts can update material at any time, these enhancements are instantly published, updated material is instantly re-indexed, and html for the Web and PDF for printed output are simultaneously produced. </para> <note> <para>Add a description on the <emphasis>component up</emphasis> strategy of the SQI system. ???</para> </note> <formalpara> <title>SQI Commitment to <emphasis>Instant Publishing</emphasis></title> <para>This book is an statement, and a working example, of the SQI philosophy of <emphasis role="bolditalic"/> instant publishing. This book is a work-in-progress. All of the material is in draft form (some in rough draft form). Some of the How-To sections have example code with little of the description provided. But all of the material fulfills the SQI concept that any insight or new knowledge has value and needs to be quickly shared</para> </formalpara> <bridgehead renderas="sect1">Author Notes</bridgehead> <note> <title>Customization ToDo</title> <para>The <code><subtitle></code> tag needs to get the same <emphasis>right justify</emphasis> as the <code><title></code> in a <code>"style":"howto"</code> document setting.</para> </note> <note> <formalpara> <title>Authors Add</title> <para>The document structure is here: <ulink url="https://sqi.ecosq.com/ic/Univ/CIE/KA/StrucDoc/HowToBookProto/DocumentSettings">Document Settings</ulink> </para> </formalpara> </note> </preface> <!-- Chapters go here --> |
<bookinfo> <title>microPublishing Cookbook</title> <subtitle>Markup Examples for the Layout Specific of the Automated Publishing System</subtitle> <affiliation> <orgname>SQI Inc.</orgname> </affiliation> <copyright> <year>2007</year> <holder>SQI Inc.</holder> </copyright> <author> <firstname>Jeff</firstname> <surname>Elpern</surname> </author> </bookinfo> <preface id="preface"> <title>Prefaces</title> <para>The SQI DocBook System combines the power of our Knowledge Base technology - direct input from <emphasis>content authors</emphasis>, continuous improvement, instants publishing, and extensive search - with the power of DocBook technology - extensive specialized markup for technical publication and multichannel publishing. The result is a on-demand environment where content experts can update material at any time, these enhancements are instantly published, updated material is instantly re-indexed, and html for the Web and PDF for printed output are simultaneously produced. </para> <note> <para>Add a description on the <emphasis>component up</emphasis> strategy of the SQI system. ???</para> </note> <formalpara> <title>SQI Commitment to <emphasis>Instant Publishing</emphasis></title> <para>This book is an statement, and a working example, of the SQI philosophy of <emphasis role="bolditalic"/> instant publishing. This book is a work-in-progress. All of the material is in draft form (some in rough draft form). Some of the How-To sections have example code with little of the description provided. But all of the material fulfills the SQI concept that any insight or new knowledge has value and needs to be quickly shared</para> </formalpara> <bridgehead renderas="sect1">Author Notes</bridgehead> <note> <title>Customization ToDo</title> <para>The <code><subtitle></code> tag needs to get the same <emphasis>right justify</emphasis> as the <code><title></code> in a <code>"style":"howto"</code> document setting.</para> </note> <note> <formalpara> <title>Authors Add</title> <para>The document structure is here: <ulink url="https://sqi.ecosq.com/ic/Univ/CIE/KA/StrucDoc/HowToBookProto/DocumentSettings" >Document Settings</ulink> </para> </formalpara> </note> </preface> <!-- Chapters go here --> |
Markup Examples for the Layout Specific of the Automated Publishing System
Copyright © 2007 SQI Inc.
Table of Contents
The SQI DocBook System combines the power of our Knowledge Base technology - direct input from content authors, continuous improvement, instants publishing, and extensive search - with the power of DocBook technology - extensive specialized markup for technical publication and multichannel publishing. The result is a on-demand environment where content experts can update material at any time, these enhancements are instantly published, updated material is instantly re-indexed, and html for the Web and PDF for printed output are simultaneously produced.
![[Note]](/wiki/docbook/images/note.png) | Note Add a description on the component up strategy of the SQI system. ??? |
SQI Commitment to Instant Publishing. This book is an statement, and a working example, of the SQI philosophy of instant publishing. This book is a work-in-progress. All of the material is in draft form (some in rough draft form). Some of the How-To sections have example code with little of the description provided. But all of the material fulfills the SQI concept that any insight or new knowledge has value and needs to be quickly shared
Author Notes
| Customization ToDo The |
| Note Authors Add. The document structure is here: Document Settings |
Table of Contents
List of Figures
- 3.1. Published output of Example 1, “Markup to Insert a Graphic into a Text Stream”
- 5.1. Example of Simple Image/Graphic with Figure Number and Title
- 5.2. Markup Fragment for Graphic with Figure Number and Title
- 5.3. Graphic Example with both web and print quality
- 5.4. DocBook markup for multi-channel publishing of a Graphic
- 5.5. Markup Fragment for Multi-Channel Publishing of Graphic with Figure Number and Title
- 5.6. Attachments for Multi-channel Publishing
- 5.7. Multi-channel web and print quality graphic
- 6.1. Published output of Example 1, “ for In-Line Code”
- 6.2. Published output of Example 2, “Entity Codes for In-Line Special Characters” and Example 3, “CDATA for In-Line Special Characters”
- 6.3. Published output of Example 1, “Markup for Embedded Callouts”
- 6.4. Published output of Example 2, “Markup for Placement Map”
- 6.5. Published output of Example 1, “ to display Published Markup”
- 7.1. A Chapter Page and the First Section Page
- 7.2. Content Associated with Web Page
- 7.3. Revision History of Page Content
- 7.4. Revision History of Page Content
- 7.5. Revision History of Page Content
- 7.6. Example of First Formating
- 7.7. DocBook Markup for "Free-Floating" Headings
- 7.8. Markup Fragment for Creating Heading without tag
List of Tables
List of Examples
- 2.1. Page Structure for Simple Book
- 2.2. Model File Structure
- 2.3. Document Structure Definition
- 2.4. XML before Restructure
- 2.5. XML after Restructure
- 3.1. Markup to Insert a Graphic into a Text Stream
- 6.1. Listing Markup Code
- 6.2. Program Listing with Line Numbers
- 6.3. for In-Line Code
- 6.4. Entity Codes for In-Line Special Characters
- 6.5. CDATA for In-Line Special Characters
- 6.6. Markup for Program Listing
- 6.7. Markup for Listing DocBook Markup
- 6.8. Program Listing with Line Numbers
- 6.9. Markup for Embedded Callouts
- 6.10. Markup for Placement Map
- 6.11. to display Published Markup