Updated per https://bugs.eclipse.org/bugs/show_bug.cgi?id=159633#c4
diff --git a/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html
index 4f37f97..4385519 100644
--- a/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html
+++ b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html
@@ -1,17 +1,15 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Authoring with Eclipse</title><link href="default_style.css" rel="stylesheet" type="text/css"><meta content="DocBook XSL Stylesheets V1.69.1" name="generator"><meta name="description" content="
- The topic of technical publishing is relatively new to
- the world of Eclipse. One can make the argument that
- technical publishing is just another collaborative
- development process involving several people with
- different backgrounds and skills. This article will show
- that the Eclipse platform is a viable platform for technical
- publishing by discussing how to write documents such as
- an article or a book within Eclipse. In fact, this
- article was written using Eclipse.
- "></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div align="right">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Authoring with Eclipse</title><link href="images/default_style.htm" rel="stylesheet" type="text/css"><meta content="DocBook XSL Stylesheets V1.69.1" name="generator"><meta name="description" content="The topic of technical publishing is relatively new to
+ the world of Eclipse. One can make the argument that
+ technical publishing is just another collaborative
+ development process involving several people with
+ different backgrounds and skills. This article will show
+ that the Eclipse platform is a viable platform for technical
+ publishing by discussing how to write documents such as
+ an article or a book within Eclipse. In fact, this
+ article was written using Eclipse."></head><body alink="#0000ff" bgcolor="white" link="#0000ff" text="black" vlink="#840084"><div align="right">
<span class="copy">
- Copyright ©2005 International Business Machines Corporation. All rights reserved.</span></div><div class="article" lang="en"><div class="titlepage"><div><h1 align="center">Authoring with Eclipse</h1><blockquote><b>Summary</b><br>
+ Copyright ©2005 International Business Machines Corporation. All rights reserved.</span></div><div class="article" lang="en"><div class="titlepage"><div><h1 align="center">Authoring with Eclipse</h1><blockquote><b>Summary</b><br>
The topic of technical publishing is relatively new to
the world of Eclipse. One can make the argument that
technical publishing is just another collaborative
@@ -22,14 +20,14 @@
an article or a book within Eclipse. In fact, this
article was written using Eclipse.
<br><p><b>By
- Chris Aniszczyk, IBM Corporation<br>Lawrence Mandel, IBM Corporation<br></b><span class="date">December 14, 2005<br></span></p></blockquote></div><div></div><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10046"></a>Environment</h2></div></div><div></div></div><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Note"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ Chris Aniszczyk, IBM Corporation<br>Lawrence Mandel, IBM Corporation<br></b><span class="date">December 14, 2005<br></span></p></blockquote></div><div></div><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N10046"></a>Environment</h2></div></div><div></div></div><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Note" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The examples in this article were built and tested with:
- <div class="itemizedlist"><ul type="disc"><li>
+ </p><div class="itemizedlist"><ul type="disc"><li>
<a href="http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.1-200506271435/eclipse-SDK-3.1-win32.zip" target="_new">
Eclipse 3.1
</a>
</li><li>
- <a href="http://download.eclipse.org/webtools/downloads/drops/R-1.0-/" target="_new">
+ <a href="http://archive.eclipse.org/webtools/downloads/drops/R1.0/R-1.0-200512210855/" target="_new">
Eclipse Web Tools Platform (WTP) 1.0
</a>
</li><li>
@@ -37,7 +35,7 @@
Orangevolt XSLT 1.0.4
</a>
</li></ul></div>
- </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10063"></a>Introduction</h2></div></div><div></div></div><p>
+ <p></p></td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N10063"></a>Introduction</h2></div></div><div></div></div><p>
The authors of this document view technical documentation as
another development process that shares the same
characteristics as a software process. In technical
@@ -48,7 +46,7 @@
introduction to technical documentation and show, through an
example, how Eclipse can help make technical documentation a
collaborative process.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10068"></a>Technical Documentation</h2></div></div><div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N10068"></a>Technical Documentation</h2></div></div><div></div></div><p>
In the open source world, technical documentation is
primarily accomplished using two popular formats: DocBook
and the Darwin Information Typing Architecture (DITA). These two
@@ -58,18 +56,18 @@
article we focus on DocBook because of our familiarity with the
format. However, we will also provide complementary DITA
information where appropriate.
- </p><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Tip"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ </p><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Tip" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
If you're unfamiliar with DocBook, there's an
<a href="http://www-128.ibm.com/developerworks/library/l-docbk.html" target="_new">
article
</a>
- on the <span class="trademark">IBM</span>® <span class="trademark">developerWorks</span>® site by Joe Brockmeier that can serve as a
+ on the <span class="trademark">IBM</span>® <span class="trademark">developerWorks</span>® site by Joe Brockmeier that can serve as a
gentle introduction. There is also an
<a href="http://www-128.ibm.com/developerworks/xml/library/x-dita1/index.html" target="_new">
introduction
</a>
to DITA on developerWorks.
- </p></td></tr></table></div><p>
+ </p></td></tr></tbody></table></div><p>
The technical documentation process can be broken down into
three broad stages: creation, review, and publication.
</p><p>
@@ -105,7 +103,7 @@
to multiple formats.
</p><p>
<span class="emphasis"><em>Modularity</em></span>
- <div class="itemizedlist"><ul type="disc"><li>
+ </p><div class="itemizedlist"><ul type="disc"><li>
XML formats such as DocBook and DITA are
modular. This allows you to break up your
documents into multiple sections, which can
@@ -139,7 +137,7 @@
the authoring process? One reason is that many
documents are authored using word-processing
tools that mix formatting information and
- content, such as <span class="trademark">Microsoft</span>® Word or Corel
+ content, such as <span class="trademark">Microsoft</span>® Word or Corel
WordPerfect. This mix results in files
containing many changes between revisions,
reducing the usefulness of version control
@@ -188,12 +186,12 @@
easily publish to any of the formats listed
above.
</li></ul></div>
- </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N100B8"></a>Examples</h2></div></div><div></div></div><p>
+ <p></p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N100B8"></a>Examples</h2></div></div><div></div></div><p>
To show the authoring tool chain in Eclipse, this article
will use a sample book document from the DocBook XSL project. The
XML version of the document can be seen
- <a href="files/book.xml" target="_new">here</a>. This DocBook source for this
- article is also available and can be seen <a href="AuthoringWithEclipse.xml" target="_new">here</a>.
+ <a href="https://bugs.eclipse.org/bugs/files/book.xml" target="_new">here</a>. This DocBook source for this
+ article is also available and can be seen <a href="https://bugs.eclipse.org/bugs/AuthoringWithEclipse.xml" target="_new">here</a>.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N100C5"></a>Tool Chain</h3></div></div><div></div></div><p>
A tool chain is a set of tools that are used to create a
more complex tool or product. The tools may be used in a
@@ -201,9 +199,9 @@
the next
[<a href="#toolchain">3</a>]
. This concept should be very familiar to those who work
- on the <span class="trademark">UNIX</span>®,
- <span class="trademark">Linux</span>®, and
- <span class="trademark">AIX</span>® platforms,
+ on the <span class="trademark">UNIX</span>®,
+ <span class="trademark">Linux</span>®, and
+ <span class="trademark">AIX</span>® platforms,
for example, where the output of one command
line tool is typically piped to the next tool, allowing
complex operations to be performed using several simple
@@ -238,11 +236,11 @@
representations of the content. Although the
graphical editor is useful for viewing your document,
we've found that the source editor, shown in
- <a href="#xml-source-editor" title="Figure 1. The XML Source Editor">Figure 1, “The XML Source Editor”</a>
+ <a href="#xml-source-editor" title="Figure 1. The XML Source Editor">Figure 1, “The XML Source Editor”</a>
, is more useful when authoring in XML.
- </p><div class="figure"><a name="xml-source-editor"></a><p class="title"><b>Figure 1. The XML Source Editor</b></p><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="807"><tr style="height: 598px"><td><img src="images/xmlsourceeditor.gif" width="807" alt="The XML Source Editor"></td></tr></table></div></div><p>
+ </p><div class="figure"><a name="xml-source-editor"></a><p class="title"><b>Figure 1. The XML Source Editor</b></p><div class="mediaobject"><table summary="manufactured viewport for HTML img" border="0" cellpadding="0" cellspacing="0" width="807"><tbody><tr style="height: 598px;"><td><img src="images/xmlsourceeditor.gif" alt="The XML Source Editor" width="807"></td></tr></tbody></table></div></div><p>
The XML editor provides many of the Eclipse
- franchise functions that <span class="trademark">Java</span>™ developers have become
+ franchise functions that <span class="trademark">Java</span>™ developers have become
accustomed to with the Java editor.
</p><p>
<span class="emphasis"><em>Content Assistance</em></span>
@@ -304,12 +302,12 @@
launcher framework. This integration allows you to
select the style sheet and pass in necessary
parameters for the transformation.
- </p><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Tip"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ </p><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Tip" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The DITA Open Toolkit (DITA-OT) includes a DITA to DocBook
<a href="http://dita-ot.sourceforge.net/doc/DITA-antscript.html" target="_new">
transformation
</a>.
- </p></td></tr></table></div><p>
+ </p></td></tr></tbody></table></div><p>
Along with the description in this article, we have
provided Flash movies that demonstrate how to
perform each transformation. Transformations for
@@ -323,13 +321,13 @@
configuration and run the transformation.
Specifically, you need to specify the correct
style sheet:
- <div class="itemizedlist"><ul type="disc"><li><p>DocBook</p><div class="itemizedlist"><ul type="circle"><li>html/docbook.xsl</li></ul></div></li><li><p>DITA</p><div class="itemizedlist"><ul type="circle"><li>xsl/dita2html.xsl</li></ul></div></li></ul></div>
- <a href="#html-transformation" title="Figure 2. Sample HTML Transformation Configuration for book.xml">Figure 2, “Sample HTML Transformation Configuration for book.xml”</a>
+ </p><div class="itemizedlist"><ul type="disc"><li><p>DocBook</p><div class="itemizedlist"><ul type="circle"><li>html/docbook.xsl</li></ul></div></li><li><p>DITA</p><div class="itemizedlist"><ul type="circle"><li>xsl/dita2html.xsl</li></ul></div></li></ul></div>
+ <a href="#html-transformation" title="Figure 2. Sample HTML Transformation Configuration for book.xml">Figure 2, “Sample HTML Transformation Configuration for book.xml”</a>
shows a sample transformation configuration that
will transform our DocBook sample
- <a href="files/book.xml" target="_new">document</a>
+ <a href="https://bugs.eclipse.org/bugs/files/book.xml" target="_new">document</a>
into HTML.
- </p><div class="figure"><a name="html-transformation"></a><p class="title"><b>Figure 2. Sample HTML Transformation Configuration for book.xml</b></p><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="692"><tr style="height: 517px"><td><img src="images/html.png" width="692" alt="Sample HTML Transformation Configuration for book.xml"></td></tr></table></div></div><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Tip"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ <p></p><div class="figure"><a name="html-transformation"></a><p class="title"><b>Figure 2. Sample HTML Transformation Configuration for book.xml</b></p><div class="mediaobject"><table summary="manufactured viewport for HTML img" border="0" cellpadding="0" cellspacing="0" width="692"><tbody><tr style="height: 517px;"><td><img src="images/html.png" alt="Sample HTML Transformation Configuration for book.xml" width="692"></td></tr></tbody></table></div></div><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Tip" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
You can augment the transformation by
passing parameters to the style sheet.
There's a full listing of DocBook XSL
@@ -338,10 +336,10 @@
<a href="http://docbook.sourceforge.net/release/xsl/current/doc/html/" target="_new">
here
</a>.
- </p></td></tr></table></div><p>
+ </p></td></tr></tbody></table></div><p>
A Flash movie that
shows how to run the transformation can be seen
- <a href="files/DocBook-HTML.htm" target="_new">here</a>
+ <a href="https://bugs.eclipse.org/bugs/files/DocBook-HTML.htm" target="_new">here</a>
.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N10174"></a>PDF</h5></div></div><div></div></div><p>
Transforming a DocBook XML file to PDF format is
@@ -358,10 +356,10 @@
XSL-FO document, you need to use the following
stylesheet:
<span class="emphasis"><em>fo/docbook.xsl</em></span>.
- <a href="#xslfo-transformation" title="Figure 3. Sample XSL-FO Transformation Configuration for book.xml">Figure 3, “Sample XSL-FO Transformation Configuration for book.xml”</a>
+ <a href="#xslfo-transformation" title="Figure 3. Sample XSL-FO Transformation Configuration for book.xml">Figure 3, “Sample XSL-FO Transformation Configuration for book.xml”</a>
shows a sample transformation configuration used
to generate an XSL-FO document from book.xml.
- </p><div class="figure"><a name="xslfo-transformation"></a><p class="title"><b>Figure 3. Sample XSL-FO Transformation Configuration for book.xml</b></p><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="692"><tr style="height: 517px"><td><img src="images/xsl-fo.png" width="692" alt="Sample XSL-FO Transformation Configuration for book.xml"></td></tr></table></div></div><p>
+ </p><div class="figure"><a name="xslfo-transformation"></a><p class="title"><b>Figure 3. Sample XSL-FO Transformation Configuration for book.xml</b></p><div class="mediaobject"><table summary="manufactured viewport for HTML img" border="0" cellpadding="0" cellspacing="0" width="692"><tbody><tr style="height: 517px;"><td><img src="images/xsl-fo.png" alt="Sample XSL-FO Transformation Configuration for book.xml" width="692"></td></tr></tbody></table></div></div><p>
Step two is to use a Formatting Objects
Processor (FOP) to transform your XSL-FO
document into a PDF. One of the more popular
@@ -377,12 +375,12 @@
installing this plug-in, all that you need to do
to render the XSL-FO document is run the FOP
transformation.
- <a href="#pdf-transformation" title="Figure 4. Sample FOP Transformation">Figure 4, “Sample FOP Transformation”</a>
+ <a href="#pdf-transformation" title="Figure 4. Sample FOP Transformation">Figure 4, “Sample FOP Transformation”</a>
shows an example of running the FOP
transformation.
- </p><div class="figure"><a name="pdf-transformation"></a><p class="title"><b>Figure 4. Sample FOP Transformation</b></p><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="430"><tr style="height: 447px"><td><img src="images/fop.png" width="430" alt="Sample FOP Transformation"></td></tr></table></div></div><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Note"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ </p><div class="figure"><a name="pdf-transformation"></a><p class="title"><b>Figure 4. Sample FOP Transformation</b></p><div class="mediaobject"><table summary="manufactured viewport for HTML img" border="0" cellpadding="0" cellspacing="0" width="430"><tbody><tr style="height: 447px;"><td><img src="images/fop.png" alt="Sample FOP Transformation" width="430"></td></tr></tbody></table></div></div><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Note" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The example includes a sample Ant
- <a href="files/pdf/build.xml" target="_new">
+ <a href="https://bugs.eclipse.org/bugs/files/pdf/build.xml" target="_new">
file
</a>
that performs the same transformation as
@@ -396,10 +394,10 @@
DITA project already includes an Ant script
(found in ant/sample_pdf.xml in DITA-OT) to perform
this exact task on DITA source files.
- </p></td></tr></table></div><p>
+ </p></td></tr></tbody></table></div><p>
As before, a Flash movie that shows the
transformation is available
- <a href="files/DocBook-PDF.htm" target="_new">here</a>
+ <a href="https://bugs.eclipse.org/bugs/files/DocBook-PDF.htm" target="_new">here</a>
.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N101B7"></a>Eclipse Infocenter</h5></div></div><div></div></div><p>
In our opinion, one of the coolest features of
@@ -409,14 +407,14 @@
transformation in DocBook, you need to specify a
few parameters and use the following style sheet:
<span class="emphasis"><em>eclipse/eclipse.xsl</em></span>.
- <a href="#eclipse-transformation" title="Figure 5. Sample Eclipse Infocenter Transformation Configuration">Figure 5, “Sample Eclipse Infocenter Transformation Configuration”</a>
+ <a href="#eclipse-transformation" title="Figure 5. Sample Eclipse Infocenter Transformation Configuration">Figure 5, “Sample Eclipse Infocenter Transformation Configuration”</a>
shows a sample transformation configuration
along with the correct parameters. To perform
this transformation using a DITA source file, use
the
<span class="emphasis"><em>ant/sample_eclipsehelp.xml</em></span>
Ant file.
- </p><div class="figure"><a name="eclipse-transformation"></a><p class="title"><b>Figure 5. Sample Eclipse Infocenter Transformation Configuration</b></p><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="803"><tr style="height: 388px"><td><img src="images/eclipse.png" height="388" alt="Sample Eclipse Infocenter Transformation Configuration"></td></tr></table></div></div><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Tip"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ </p><div class="figure"><a name="eclipse-transformation"></a><p class="title"><b>Figure 5. Sample Eclipse Infocenter Transformation Configuration</b></p><div class="mediaobject"><table summary="manufactured viewport for HTML img" border="0" cellpadding="0" cellspacing="0" width="803"><tbody><tr style="height: 388px;"><td><img src="images/eclipse.png" alt="Sample Eclipse Infocenter Transformation Configuration" height="388"></td></tr></tbody></table></div></div><div class="tip" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Tip" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
The complete list of DocBook XSL parameters
for the Eclipse Infocenter transformation
is located
@@ -424,10 +422,10 @@
here
</a>
.
- </p></td></tr></table></div><p>
+ </p></td></tr></tbody></table></div><p>
The Flash movie that shows the Eclipse
Infocenter DocBook transformation can be found
- <a href="files/DocBook-InfoCenter.htm" target="_new">
+ <a href="https://bugs.eclipse.org/bugs/files/DocBook-InfoCenter.htm" target="_new">
here
</a>
.
@@ -452,7 +450,7 @@
Eclipse is recognized as an integrated documentation
development environment, these limitations will be
addressed.
- </p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101E9"></a>Summary</h2></div></div><div></div></div><p>
+ </p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N101E9"></a>Summary</h2></div></div><div></div></div><p>
In this article, we introduced the technical documentation
process and showed that technical documentation development
is possible in Eclipse. We worked through examples showing
@@ -464,9 +462,9 @@
the technical documentation community to speak up, make it
clear that Eclipse is being used for the authoring process,
and push to get the current limitations addressed.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101EE"></a>Acknowledgements</h2></div></div><div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N101EE"></a>Acknowledgements</h2></div></div><div></div></div><p>
We'd like to thank:
- <div class="itemizedlist"><ul type="disc"><li>
+ </p><div class="itemizedlist"><ul type="disc"><li>
Sushma Patel and Anne James for correcting our horrible
grammar.
</li></ul></div>
@@ -474,10 +472,10 @@
Don Day and Michael Priestly for their DITA
expertise.
</li></ul></div>
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101FD"></a>About the Authors</h2></div></div><div></div></div><p>
+ <p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="N101FD"></a>About the Authors</h2></div></div><div></div></div><p>
Chris Aniszczyk is a software developer at the IBM Austin
Labs and works in Tivoli Security. He's a developer on the
- <a href="http://www.gentoo.org" target="_new">Gentoo Linux</a>
+ <a href="http://www.gentoo.org/" target="_new">Gentoo Linux</a>
distribution and also a committer on the
<a href="http://www.eclipse.org/emft" target="_new">
Eclipse Modeling Framework Technology (EMFT)
@@ -506,18 +504,18 @@
Wikipedia: Toolchain
</a>
. </span></p></div><div class="biblioentry"><a name="vex"></a><p>[4] <span class="bibliosource">
- <a href="http://vex.sf.net" target="_new">
+ <a href="http://vex.sf.net/" target="_new">
Vex
</a>
. </span></p></div><div class="biblioentry"><a name="openoffice"></a><p>[5] <span class="bibliosource">
- <a href="http://www.openoffice.org" target="_new">
+ <a href="http://www.openoffice.org/" target="_new">
OpenOffice
</a>
. </span></p></div><div class="biblioentry"><a name="subversion"></a><p>[6] <span class="bibliosource">
<a href="http://subversion.tigris.org/" target="_new">
Subversion
</a>
- . </span></p></div></div><div class="appendix" lang="en"><h2 class="title" style="clear: both"><a name="N10243"></a>A. Appendix</h2><p>
+ . </span></p></div></div><div class="appendix" lang="en"><h2 class="title" style="clear: both;"><a name="N10243"></a>A. Appendix</h2><p>
The appendix contains a discussion about how this article
was written (including the HTML style sheet so you can write
your own eclipse.org article in DocBook). The appendix also
@@ -529,15 +527,15 @@
for eclipse.org, a style sheet was developed that extends
the transformation included in the DocBook XSL project.
The eclipse.org article style sheet can be downloaded
- <a href="files/article.xsl" target="_new">here</a>.
- <div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table border="0" summary="Note"><tr><td valign="top" align="center" rowspan="2" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left"></th></tr><tr><td valign="top" align="left"><p>
+ <a href="https://bugs.eclipse.org/bugs/files/article.xsl" target="_new">here</a>.
+ </p><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table summary="Note" border="0"><tbody><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>
Eclipse.org is in the process of moving to a data driven format
for articles. You can find more information about this process
by following bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=115473" target="_new">
#115473</a>. We will be contributing our stylesheets for DocBook and
DITA to this bug.
- </p></td></tr></table></div>
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10259"></a>Editors</h3></div></div><div></div></div><p>
+ </p></td></tr></tbody></table></div>
+ <p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10259"></a>Editors</h3></div></div><div></div></div><p>
Part of the creation process involves editing the
content of your XML document in an editor. The editor
you use is a preference that is usually precious to the
@@ -559,11 +557,11 @@
knowledge of CSS and DTDs in order to contribute a
visual editor for XML files. The Vex editor can be
seen in
- <a href="#vex-editor" title="Figure A.1. Vex DocBook editor screenshot">Figure A.1, “Vex DocBook editor screenshot”</a>
+ <a href="#vex-editor" title="Figure A.1. Vex DocBook editor screenshot">Figure A.1, “Vex DocBook editor screenshot”</a>
.
- <div class="figure"><a name="vex-editor"></a><p class="title"><b>Figure A.1. Vex DocBook editor screenshot</b></p><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="652"><tr style="height: 498px"><td><img src="images/vex.png" width="652" alt="Vex DocBook editor screenshot"></td></tr></table></div></div>
+ </p><div class="figure"><a name="vex-editor"></a><p class="title"><b>Figure A.1. Vex DocBook editor screenshot</b></p><div class="mediaobject"><table summary="manufactured viewport for HTML img" border="0" cellpadding="0" cellspacing="0" width="652"><tbody><tr style="height: 498px;"><td><img src="images/vex.png" alt="Vex DocBook editor screenshot" width="652"></td></tr></tbody></table></div></div>
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10276"></a>OpenOffice</h4></div></div><div></div></div><p>
+ <p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10276"></a>OpenOffice</h4></div></div><div></div></div><p>
OpenOffice
[<a href="#openoffice">5</a>]
is a multi-platform open source office suite that is
