1 | =========================================
|
---|
2 | DocBook Framework for OS/2, version 1.0.0
|
---|
3 | =========================================
|
---|
4 |
|
---|
5 | DocBook Framework for OS/2 is a bundle of programs and libraries allowing you
|
---|
6 | to manipulate DocBook source files and convert them to various output formats.
|
---|
7 | The framework itself does not bring any new software to you, it just groups
|
---|
8 | free software downloaded from different places and provides Rexx scripts to
|
---|
9 | configure and launch the software in the right way.
|
---|
10 |
|
---|
11 | DocBook is a XML-based platform-independent format for books, articles,
|
---|
12 | technical documentation, FAQ, slides, etc. Once you write your stuff in DocBook,
|
---|
13 | you can convert it to a number of output formats, including:
|
---|
14 |
|
---|
15 | - HTML
|
---|
16 | - XHTML
|
---|
17 | - HTML Help for Windows
|
---|
18 | - Java Help
|
---|
19 | - Eclipse Help
|
---|
20 | - UNIX Manual Pages
|
---|
21 | - Formatting Objects, an intermediate format between DocBook and various
|
---|
22 | paged-media formats
|
---|
23 | - PCL
|
---|
24 | - PDF
|
---|
25 | - PostScript
|
---|
26 | - RTF
|
---|
27 | - SVG
|
---|
28 | - plain text
|
---|
29 | - WML (Wordprocessing Markup Language)
|
---|
30 |
|
---|
31 | The main advantages of using DocBook are the following:
|
---|
32 |
|
---|
33 | - DocBook is a platform-independent format. You can can edit, read and convert
|
---|
34 | the same file on any platform. You can even change the platform right in the
|
---|
35 | middle of editing your file, the first part can be written on Windows, the
|
---|
36 | second one on OS/2.
|
---|
37 | - DocBook is XML. This means that you can use all standard tools that
|
---|
38 | manipulate XML data, such as parsers, checkers, and converters.
|
---|
39 | - DocBook is an open format. This guarantees that you will be able to read and
|
---|
40 | manipulate your today-written article in the future.
|
---|
41 | - Many output formats available. Being a XML format, DocBook itself is not
|
---|
42 | intended to be read directly by humans. Instead, many output formats can be
|
---|
43 | generated from DocBook, including popular formats such as PDF, HTML and RTF.
|
---|
44 |
|
---|
45 |
|
---|
46 | ----------------------
|
---|
47 | 1. System Requirements
|
---|
48 | ----------------------
|
---|
49 |
|
---|
50 | The framework is a bundle of Java software, data files, and Rexx scripts.
|
---|
51 | Therefore, you will need the following stuff installed:
|
---|
52 |
|
---|
53 | - Rexx
|
---|
54 | - Java. Use Golden Code or InnoTek Java 1.4, if you can. However, IBM Java 1.3
|
---|
55 | should also work.
|
---|
56 | - WarpIN for installation/deinstallation. Since you are reading this file, you
|
---|
57 | have probably installed it already.
|
---|
58 |
|
---|
59 |
|
---|
60 | ----------------------------------
|
---|
61 | 2. Installation and Deinstallation
|
---|
62 | ----------------------------------
|
---|
63 |
|
---|
64 | DocBook Framework is installed automatically using WarpIN. During installation,
|
---|
65 | your CONFIG.SYS will be modified. If you don't allow WarpIN to perform the
|
---|
66 | modification, you will have to:
|
---|
67 |
|
---|
68 | - either modify CONFIG.SYS on your own by adding the "...\Scripts" directory to
|
---|
69 | your PATH, or
|
---|
70 | - add the "...\Scripts" directory to your PATH from the command line every time
|
---|
71 | you use the framework.
|
---|
72 |
|
---|
73 | In addition, java.exe must be in your PATH. It is assumed that PATH already
|
---|
74 | contains a Java "...\jre\bin" directory and no checks are performed, neither
|
---|
75 | during installation nor during normal operation.
|
---|
76 |
|
---|
77 | Before you start using the framework, take a little time to configure it. A few
|
---|
78 | configuration files must be set up in order for the tools to operate properly.
|
---|
79 | Please read the file PatchTheseFiles.TXT for more details. These changes can be
|
---|
80 | performed automatically and future versions of the framework will contain
|
---|
81 | a little configuration tool that will be executed during installation.
|
---|
82 |
|
---|
83 | The framework can be uninstalled using WarpIN. You can also delete it manually,
|
---|
84 | but then the WarpIN database will not be consistent with your hard disk's
|
---|
85 | content.
|
---|
86 |
|
---|
87 |
|
---|
88 | ------------------------------
|
---|
89 | 3. Components of the Framework
|
---|
90 | ------------------------------
|
---|
91 |
|
---|
92 | The framework consists of the following components:
|
---|
93 |
|
---|
94 | 1. DocBook DTD and ISO entities.
|
---|
95 | 2. DocBook XSL stylesheets that prescribe how DocBook documents should be
|
---|
96 | converted into other formats.
|
---|
97 | 3. Saxon - XSLT processor that converts a DocBook document into another format
|
---|
98 | using a XSL stylesheet.
|
---|
99 | 4. FOP - FO processor that converts an FO document (generated by Saxon) into
|
---|
100 | a paged-media document.
|
---|
101 | 5. Rexx scripts that set up the environment properly before launching the
|
---|
102 | programs.
|
---|
103 |
|
---|
104 | Other software can be plugged into the framework, e.g. XFC or XEP. Rexx scripts
|
---|
105 | for starting them are present in the distribution, but the programs could not
|
---|
106 | be included because of their strict licenses. However, you can easily download
|
---|
107 | them on your own and install them into the "...\SW\XFC" and "...\SW\XEP"
|
---|
108 | directories. Look into the UsefulLinks.TXT file for links to the software.
|
---|
109 |
|
---|
110 | Some DocBook-related programs were not included in the distribution. An example
|
---|
111 | of such programs is OpenJade, a converter using DSSSL styles. DSSSL styles are
|
---|
112 | older than XSL styles and their importance falls down continuously. In adition,
|
---|
113 | OpenJade is a native program. Programs like OpenJade may be included in a future
|
---|
114 | version if users request it.
|
---|
115 |
|
---|
116 | Editors were not included either. I recommend using either jEdit or XXE. The
|
---|
117 | latter is almost-WYSIWYG so it will probably be preferred by many users. Again,
|
---|
118 | see the file UsefulLinks.TXT for an URL.
|
---|
119 |
|
---|
120 |
|
---|
121 | ----------------------
|
---|
122 | 4. Using the Framework
|
---|
123 | ----------------------
|
---|
124 |
|
---|
125 | The framework offers 19 Rexx scripts that you can call directly and pass them
|
---|
126 | your DocBook file as a parameter. The scripts are as follows:
|
---|
127 |
|
---|
128 | DB2EclipseHelp.CMD
|
---|
129 | - Converts DocBook into Eclipse help.
|
---|
130 |
|
---|
131 | DB2FO.CMD
|
---|
132 | - Converts DocBook into Formatting Objects. Formatting objects are the
|
---|
133 | starting point for paged-media formats, therefore a very important format.
|
---|
134 | Look at FO2* scripts to see what you get out of formatting objects.
|
---|
135 |
|
---|
136 | DB2HTML.CMD
|
---|
137 | - Converts DocBook into a single HTML file.
|
---|
138 |
|
---|
139 | DB2HTMLChunks.CMD
|
---|
140 | - Converts DocBook into a set of HTML files, chained by links.
|
---|
141 |
|
---|
142 | DB2HTMLHelp.CMD
|
---|
143 | - Converts DocBook into a set of HTML files that can be compiled into a CHM
|
---|
144 | file. This can be used on Windows only.
|
---|
145 |
|
---|
146 | DB2JavaHelp.CMD
|
---|
147 | - Converts DocBook into a set of HTML and XML files that can be packed into
|
---|
148 | a JAR archive and read by a Java program.
|
---|
149 |
|
---|
150 | DB2ManPages.CMD
|
---|
151 | - Converts DocBook reference entries into UNIX manual pages. Not much useful
|
---|
152 | on OS/2...
|
---|
153 |
|
---|
154 | DB2XHTML.CMD
|
---|
155 | - Converts DocBook into a single XHTML file.
|
---|
156 |
|
---|
157 | DB2XHTMLChunks.CMD
|
---|
158 | - Converts DocBook into a set XHTML files, chained by links.
|
---|
159 |
|
---|
160 | FO2MIF.CMD
|
---|
161 | - This conversion does not work yet.
|
---|
162 |
|
---|
163 | FO2PCL.CMD
|
---|
164 | - Converts Formatting Objects into a PCL file that can be sent to a printer.
|
---|
165 |
|
---|
166 | FO2PDF.CMD
|
---|
167 | - Converts Formatting Objects into a Portable Document format.
|
---|
168 |
|
---|
169 | FO2Printer.CMD
|
---|
170 | - Renders Formatting Objects directly onto a printer.
|
---|
171 |
|
---|
172 | FO2PS.CMD
|
---|
173 | - Converts Formatting Objects into PostScript.
|
---|
174 |
|
---|
175 | FO2RTF-UsingXFC.CMD
|
---|
176 | - Converts Formatting Objects into Rich Text Format. On OS/2, use OpenOffice
|
---|
177 | to open the resulting RTF. You must install XFC on your own to be able to
|
---|
178 | perform this conversion.
|
---|
179 |
|
---|
180 | FO2Screen.CMD
|
---|
181 | - Renders Formatting Objects on the screen.
|
---|
182 |
|
---|
183 | FO2SVG.CMD
|
---|
184 | - Converts Formatting Objects into Scalable Vector Graphics.
|
---|
185 |
|
---|
186 | FO2TXT.CMD
|
---|
187 | - Converts Formatting Objects into plain text.
|
---|
188 |
|
---|
189 | FO2WML-UsingXFC.CMD
|
---|
190 | - Converts Formatting Objects into Wordprocessing Markup Language. The
|
---|
191 | resulting file can be opened by Microsoft Word XP and 2003 on Windows. You
|
---|
192 | must install XFC on your own to be able to perform this conversion.
|
---|
193 |
|
---|
194 | If a new XSL stylesheet appears, you can directly call the converters and
|
---|
195 | supply them the stylesheet as a parameter. See Saxon.CMD, FOP.CMD, XFC.CMD, and
|
---|
196 | XEP.CMD for details.
|
---|
197 |
|
---|
198 |
|
---|
199 | -------------------
|
---|
200 | 5. More Information
|
---|
201 | -------------------
|
---|
202 |
|
---|
203 | The framework's homepage is at
|
---|
204 | http://www.kacer.biz/os2/docbook-framework
|
---|
205 |
|
---|
206 | To contact the packager, write to:
|
---|
207 | jarda@kacer.biz
|
---|
208 |
|
---|