NEW - bug 238018: DocBook Authoring With Eclipse
https://bugs.eclipse.org/bugs/show_bug.cgi?id=238018
NEW - bug 225714: Updated version of the DocBook template for authoring Eclipse Corner articles
https://bugs.eclipse.org/bugs/show_bug.cgi?id=225714
diff --git a/Article-Authoring-With-Eclipse/AuthoringWithEclipse.fo b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.fo
new file mode 100644
index 0000000..8dfdf3e
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.fo
@@ -0,0 +1,2033 @@
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" font-family="serif,Symbol,ZapfDingbats"
+   font-size="10pt" text-align="justify" line-height="normal" font-selection-strategy="character-by-character"
+   line-height-shift-adjustment="disregard-shifts" language="en">
+   <fo:layout-master-set>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="blank">
+         <fo:region-body margin-top="0.5in" margin-bottom="0.5in" display-align="center"
+            region-name="blank-body" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-blank" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-blank" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="titlepage-first">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="titlepage-odd">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="titlepage-even">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="lot-first">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="lot-odd">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="lot-even">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="front-first">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="front-odd">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="front-even">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="body-first">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="body-odd">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="body-even">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="back-first">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="back-odd">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="back-even">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="index-first">
+         <fo:region-body column-count="2" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="index-odd">
+         <fo:region-body column-count="2" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="index-even">
+         <fo:region-body column-count="2" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="blank-draft">
+         <fo:region-body margin-top="0.5in" margin-bottom="0.5in"
+            background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-blank" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-blank" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in"
+         master-name="titlepage-first-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in"
+         master-name="titlepage-odd-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in"
+         master-name="titlepage-even-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="lot-first-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="lot-odd-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="lot-even-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="front-first-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="front-odd-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="front-even-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="body-first-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="body-odd-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="body-even-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="back-first-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="back-odd-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in - 0pt"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="back-even-draft">
+         <fo:region-body column-count="1" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="index-first-draft">
+         <fo:region-body column-count="2" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-first" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-first" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-right="1in" margin-left="1in"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="index-odd-draft">
+         <fo:region-body column-count="2" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-odd" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-odd" />
+      </fo:simple-page-master>
+      <fo:simple-page-master margin-left="1in" margin-right="1in"
+         margin-bottom="0.5in" margin-top="0.5in" page-height="11in" page-width="8.5in" master-name="index-even-draft">
+         <fo:region-body column-count="2" column-gap="12pt" margin-top="0.5in"
+            margin-bottom="0.5in" background-image="url(http://docbook.sourceforge.net/release/images/draft.png)"
+            background-attachment="fixed" background-repeat="no-repeat"
+            background-position-horizontal="center" background-position-vertical="center" />
+         <fo:region-before display-align="before" extent="0.4in" region-name="xsl-region-before-even" />
+         <fo:region-after display-align="after" extent="0.4in" region-name="xsl-region-after-even" />
+      </fo:simple-page-master>
+      <fo:page-sequence-master master-name="titlepage">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="titlepage-first" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="titlepage-odd" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="titlepage-odd" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="lot">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="lot-first" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="lot-odd" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="lot-odd" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="front">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="front-first" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="front-odd" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="front-odd" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="body">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="body-first" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="body-odd" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="body-odd" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="back">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="back-first" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="back-odd" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="back-odd" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="index">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="index-first" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="index-odd" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="index-odd" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="titlepage-draft">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank-draft" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="titlepage-first-draft" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="titlepage-odd-draft" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="titlepage-odd-draft" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="lot-draft">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank-draft" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="lot-first-draft" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="lot-odd-draft" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="lot-odd-draft" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="front-draft">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank-draft" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="front-first-draft" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="front-odd-draft" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="front-odd-draft" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="body-draft">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank-draft" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="body-first-draft" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="body-odd-draft" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="body-odd-draft" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="back-draft">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank-draft" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="back-first-draft" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="back-odd-draft" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="back-odd-draft" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+      <fo:page-sequence-master master-name="index-draft">
+         <fo:repeatable-page-master-alternatives>
+            <fo:conditional-page-master-reference
+               blank-or-not-blank="blank" master-reference="blank-draft" />
+            <fo:conditional-page-master-reference
+               page-position="first" master-reference="index-first-draft" />
+            <fo:conditional-page-master-reference odd-or-even="odd"
+               master-reference="index-odd-draft" />
+            <fo:conditional-page-master-reference odd-or-even="even"
+               master-reference="index-odd-draft" />
+         </fo:repeatable-page-master-alternatives>
+      </fo:page-sequence-master>
+   </fo:layout-master-set>
+   <fo:page-sequence xmlns:axf="http://www.antennahouse.com/names/XSL/Extensions"
+      master-reference="body" hyphenate="true" language="en" format="1" initial-page-number="1"
+      force-page-count="no-force" hyphenation-character="-" hyphenation-push-character-count="2"
+      hyphenation-remain-character-count="2">
+      <fo:static-content flow-name="xsl-region-before-first">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-bottom-width="0.5pt"
+               border-bottom-style="solid" border-bottom-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="before" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-before-odd">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-bottom-width="0.5pt"
+               border-bottom-style="solid" border-bottom-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="before" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block>DocBook Authoring with Eclipse</fo:block>
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-before-even">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-bottom-width="0.5pt"
+               border-bottom-style="solid" border-bottom-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="before" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block>DocBook Authoring with Eclipse</fo:block>
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-before-blank">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-bottom-width="0.5pt"
+               border-bottom-style="solid" border-bottom-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="before" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="before" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-footnote-separator">
+         <fo:block>
+            <fo:leader color="black" leader-pattern="rule" leader-length="1in" />
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="blank-body">
+         <fo:block text-align="center" />
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-after-first">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-top-width="0.5pt"
+               border-top-style="solid" border-top-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="after" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block>
+                              <fo:page-number />
+                           </fo:block>
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-after-odd">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-top-width="0.5pt"
+               border-top-style="solid" border-top-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="after" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block>
+                              <fo:page-number />
+                           </fo:block>
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-after-even">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-top-width="0.5pt"
+               border-top-style="solid" border-top-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="after" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block>
+                              <fo:page-number />
+                           </fo:block>
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:static-content flow-name="xsl-region-after-blank">
+         <fo:block font-family="serif,Symbol,ZapfDingbats" margin-left="0pt">
+            <fo:table table-layout="fixed" width="100%" border-top-width="0.5pt"
+               border-top-style="solid" border-top-color="black">
+               <fo:table-column column-number="1" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="2" column-width="proportional-column-width(1)" />
+               <fo:table-column column-number="3" column-width="proportional-column-width(1)" />
+               <fo:table-body>
+                  <fo:table-row block-progression-dimension.minimum="14pt">
+                     <fo:table-cell display-align="after" text-align="left"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="center"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block>
+                              <fo:page-number />
+                           </fo:block>
+                        </fo:block>
+                     </fo:table-cell>
+                     <fo:table-cell display-align="after" text-align="right"
+                        relative-align="baseline">
+                        <fo:block>
+                           <fo:block />
+                        </fo:block>
+                     </fo:table-cell>
+                  </fo:table-row>
+               </fo:table-body>
+            </fo:table>
+         </fo:block>
+      </fo:static-content>
+      <fo:flow flow-name="xsl-region-body" start-indent="4pc" end-indent="0pt">
+         <fo:block id="article">
+            <fo:block font-family="sans-serif,Symbol,ZapfDingbats">
+               <fo:block text-align="center" start-indent="0pt">
+                  <fo:block font-weight="bold" font-size="24.8832pt"
+                     keep-with-next.within-column="always">
+                     <fo:block keep-with-next.within-column="always" space-before.optimum="10pt"
+                        space-before.minimum="10pt * 0.8" space-before.maximum="10pt * 1.2"
+                        hyphenate="false" text-align="center" start-indent="0pt"
+                        hyphenation-character="-" hyphenation-push-character-count="2"
+                        hyphenation-remain-character-count="2">DocBook Authoring with Eclipse
+                     </fo:block>
+                  </fo:block>
+                  <fo:block font-size="14.4pt" space-before="0.5em">
+                     <fo:wrapper>
+                        <fo:block>
+                           David Carver, Standards for Technology in Automotive Retail
+                           <fo:inline font-family="monospace">
+                              <fo:inline hyphenate="false" keep-together.within-line="always">
+                                 dcarver@starstandard.org</fo:inline>
+                           </fo:inline>
+                        </fo:block>
+                     </fo:wrapper>
+                  </fo:block>
+                  <fo:block space-before="0.5em">
+                     Copyright
+                     <fo:inline font-family="serif">©</fo:inline>
+                     2008 Standards for Technology in Automotive Retail. All rights reserved.
+                  </fo:block>
+                  <fo:block font-family="serif,Symbol,ZapfDingbats" margin-right="0.5in"
+                     margin-left="0.5in" text-align="start">
+                     <fo:block id="N10033">
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em"> Java and all Java-based trademarks are trademarks
+                           of Sun Microsystems, Inc. in the United States, other countries, or both.
+                        </fo:block>
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em"> Linux is a trademark of Linus Torvalds in the
+                           United States, other countries, or both.</fo:block>
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em"> Microsoft is a trademark of Microsoft Corporation
+                           in the United States, other countries, or both.</fo:block>
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em"> UNIX is a registered trademark of The Open Group in
+                           the United States and other countries.</fo:block>
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em"> Other company, product, or service names may be
+                           trademarks or service marks of others.</fo:block>
+                     </fo:block>
+                  </fo:block>
+                  <fo:block space-before="0.5em">
+                     <fo:table width="100%" table-layout="fixed">
+                        <fo:table-column column-width="proportional-column-width(1)"
+                           column-number="1" />
+                        <fo:table-column column-width="proportional-column-width(1)"
+                           column-number="2" />
+                        <fo:table-column column-width="proportional-column-width(1)"
+                           column-number="3" />
+                        <fo:table-body end-indent="0pt" start-indent="0pt">
+                           <fo:table-row>
+                              <fo:table-cell number-columns-spanned="3">
+                                 <fo:block>Revision History</fo:block>
+                              </fo:table-cell>
+                           </fo:table-row>
+                           <fo:table-row>
+                              <fo:table-cell>
+                                 <fo:block>Revision 1.0</fo:block>
+                              </fo:table-cell>
+                              <fo:table-cell>
+                                 <fo:block>June 20, 2008</fo:block>
+                              </fo:table-cell>
+                              <fo:table-cell>
+                                 <fo:block>DAC</fo:block>
+                              </fo:table-cell>
+                           </fo:table-row>
+                           <fo:table-row>
+                              <fo:table-cell number-columns-spanned="3">
+                                 <fo:block>Updated to DocBook 4.5, Web Standard Tools 3.0,
+                                    and XSL Tooling 0.5M8</fo:block>
+                              </fo:table-cell>
+                           </fo:table-row>
+                        </fo:table-body>
+                     </fo:table>
+                  </fo:block>
+                  <fo:block font-family="serif,Symbol,ZapfDingbats" margin-right="0.5in"
+                     margin-left="0.5in" text-align="start" space-before="0.5em">
+                     <fo:block>
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" font-weight="bold" font-size="12pt"
+                           hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em"
+                           space-after.maximum="0.8em" keep-with-next.within-column="always">Abstract
+                        </fo:block>
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em">
+                           Eclipse is not know for it's ability to write documentation, but it is
+                           something that every programmer eventually has to do. In today's world it
+                           is not uncommon to have to support not only print media, but also online
+                           content as well. This article will take a look at the advances of eclipse
+                           as an authoring environment. It will revisit concepts original discussed
+                           in the
+                           <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                              external-destination="url(http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html)">"Authoring with Eclipse"
+                           </fo:basic-link>
+                           <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink"
+                              hyphenate="false">
+                              [
+                              <fo:basic-link
+                                 external-destination="url(http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html)">
+                                 http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html
+                              </fo:basic-link>
+                              ]
+                           </fo:inline>
+                           article, published in December 2005.
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+         </fo:block>
+         <fo:block space-before.minimum="0.5em" space-before.optimum="1em"
+            space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em"
+            space-after.maximum="2em" id="toc...article">
+            <fo:block>
+               <fo:block>
+                  <fo:block font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
+                     font-size="17.28pt" start-indent="0pt" margin-left="0pt" space-after="0.5em"
+                     space-before.maximum="2em" space-before.optimum="1.5em" space-before.minimum="1em">
+                     Table of Contents</fo:block>
+               </fo:block>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N1003F">Environment
+                  </fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N1003F">
+                     <fo:page-number-citation ref-id="N1003F" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N1006A">Preface</fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N1006A">
+                     <fo:page-number-citation ref-id="N1006A" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N10073">Introduction
+                  </fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N10073">
+                     <fo:page-number-citation ref-id="N10073" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N10078">Technical Documentation
+                  </fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N10078">
+                     <fo:page-number-citation ref-id="N10078" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block id="toc.article.N10078" margin-left="24pt">
+               <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+                  last-line-end-indent="-24pt">
+                  <fo:inline keep-with-next.within-line="always">
+                     <fo:basic-link internal-destination="N10092">Advantages of an
+                        XML format</fo:basic-link>
+                  </fo:inline>
+                  <fo:inline keep-together.within-line="always">
+                     <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                        leader-pattern-width="3pt" leader-pattern="dots" />
+                     <fo:basic-link internal-destination="N10092">
+                        <fo:page-number-citation ref-id="N10092" />
+                     </fo:basic-link>
+                  </fo:inline>
+               </fo:block>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N100B9">Examples</fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N100B9">
+                     <fo:page-number-citation ref-id="N100B9" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block id="toc.article.N100B9" margin-left="24pt">
+               <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+                  last-line-end-indent="-24pt">
+                  <fo:inline keep-with-next.within-line="always">
+                     <fo:basic-link internal-destination="N100C6">The Right Tool for the
+                        Right Job.</fo:basic-link>
+                  </fo:inline>
+                  <fo:inline keep-together.within-line="always">
+                     <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                        leader-pattern-width="3pt" leader-pattern="dots" />
+                     <fo:basic-link internal-destination="N100C6">
+                        <fo:page-number-citation ref-id="N100C6" />
+                     </fo:basic-link>
+                  </fo:inline>
+               </fo:block>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N101AB">Summary</fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N101AB">
+                     <fo:page-number-citation ref-id="N101AB" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N101B0">Acknowledgments
+                  </fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N101B0">
+                     <fo:page-number-citation ref-id="N101B0" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N101B7">About the Author
+                  </fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N101B7">
+                     <fo:page-number-citation ref-id="N101B7" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+            <fo:block text-align-last="justify" text-align="start" end-indent="24pt"
+               last-line-end-indent="-24pt">
+               <fo:inline keep-with-next.within-line="always">
+                  <fo:basic-link internal-destination="N101C0">Resources
+                  </fo:basic-link>
+               </fo:inline>
+               <fo:inline keep-together.within-line="always">
+                  <fo:leader keep-with-next.within-line="always" leader-alignment="reference-area"
+                     leader-pattern-width="3pt" leader-pattern="dots" />
+                  <fo:basic-link internal-destination="N101C0">
+                     <fo:page-number-citation ref-id="N101C0" />
+                  </fo:basic-link>
+               </fo:inline>
+            </fo:block>
+         </fo:block>
+         <fo:block id="N1003F">
+            <fo:block>
+               <fo:block>
+                  <fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats"
+                     margin-left="0pt">
+                     <fo:block keep-with-next.within-column="always">
+                        <fo:block font-family="sans-serif" font-weight="bold"
+                           keep-with-next.within-column="always" space-before.minimum="0.8em"
+                           space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left"
+                           start-indent="0pt">
+                           <fo:marker marker-class-name="section.head.marker">Environment</fo:marker>
+                           <fo:block font-size="20.735999999999997pt">Environment</fo:block>
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+            <fo:block space-before.minimum="0.8em" space-before.optimum="1em"
+               space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N10042">
+               <fo:block font-size="14pt" font-weight="bold" hyphenate="false"
+                  keep-with-next.within-column="always">Note</fo:block>
+               <fo:block>
+                  <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                     space-before.maximum="1.2em">
+                     The examples in this article were built and tested with:
+                     <fo:list-block space-before.optimum="1em" space-before.minimum="0.8em"
+                        space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em"
+                        space-after.maximum="1.2em" provisional-label-separation="0.2em"
+                        provisional-distance-between-starts="1.0em" id="N10045">
+                        <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" id="N10046">
+                           <fo:list-item-label end-indent="label-end()">
+                              <fo:block>•</fo:block>
+                           </fo:list-item-label>
+                           <fo:list-item-body start-indent="body-start()">
+                              <fo:block>
+                                 <fo:block>
+                                    <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       external-destination="url(http://www.eclipse.org/download)">Eclipse 3.4</fo:basic-link>
+                                    <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       hyphenate="false">
+                                       [
+                                       <fo:basic-link external-destination="url(http://www.eclipse.org/download)">
+                                          http://www.eclipse.org/download</fo:basic-link>
+                                       ]
+                                    </fo:inline>
+                                 </fo:block>
+                              </fo:block>
+                           </fo:list-item-body>
+                        </fo:list-item>
+                        <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" id="N1004D">
+                           <fo:list-item-label end-indent="label-end()">
+                              <fo:block>•</fo:block>
+                           </fo:list-item-label>
+                           <fo:list-item-body start-indent="body-start()">
+                              <fo:block>
+                                 <fo:block>
+                                    <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       external-destination="url(http://www.eclipse.org/webtools)"> Eclipse Web Tools Platform (WTP) 3.0
+                                    </fo:basic-link>
+                                    <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       hyphenate="false">
+                                       [
+                                       <fo:basic-link external-destination="url(http://www.eclipse.org/webtools)">
+                                          http://www.eclipse.org/webtools</fo:basic-link>
+                                       ]
+                                    </fo:inline>
+                                 </fo:block>
+                              </fo:block>
+                           </fo:list-item-body>
+                        </fo:list-item>
+                        <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" id="N10054">
+                           <fo:list-item-label end-indent="label-end()">
+                              <fo:block>•</fo:block>
+                           </fo:list-item-label>
+                           <fo:list-item-body start-indent="body-start()">
+                              <fo:block>
+                                 <fo:block>
+                                    <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       external-destination="url(http://www.eclipse.org/webtools/incubator)"> XSL Tooling 0.5M8 - Incubator
+                                    </fo:basic-link>
+                                    <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       hyphenate="false">
+                                       [
+                                       <fo:basic-link
+                                          external-destination="url(http://www.eclipse.org/webtools/incubator)">
+                                          http://www.eclipse.org/webtools/incubator</fo:basic-link>
+                                       ]
+                                    </fo:inline>
+                                 </fo:block>
+                              </fo:block>
+                           </fo:list-item-body>
+                        </fo:list-item>
+                        <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" id="N1005B">
+                           <fo:list-item-label end-indent="label-end()">
+                              <fo:block>•</fo:block>
+                           </fo:list-item-label>
+                           <fo:list-item-body start-indent="body-start()">
+                              <fo:block>
+                                 <fo:block>
+                                    <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       external-destination="url(http://www.docbook.org)">Docbook 4.5</fo:basic-link>
+                                    <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       hyphenate="false">
+                                       [
+                                       <fo:basic-link external-destination="url(http://www.docbook.org)">
+                                          http://www.docbook.org</fo:basic-link>
+                                       ]
+                                    </fo:inline>
+                                 </fo:block>
+                              </fo:block>
+                           </fo:list-item-body>
+                        </fo:list-item>
+                        <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" id="N10062">
+                           <fo:list-item-label end-indent="label-end()">
+                              <fo:block>•</fo:block>
+                           </fo:list-item-label>
+                           <fo:list-item-body start-indent="body-start()">
+                              <fo:block>
+                                 <fo:block>
+                                    <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       external-destination="url(http://docbook.sourceforge.net/)">The DocBook XSL stylesheets from the
+                                       DocBook Project</fo:basic-link>
+                                    <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink"
+                                       hyphenate="false">
+                                       [
+                                       <fo:basic-link external-destination="url(http://docbook.sourceforge.net/)">
+                                          http://docbook.sourceforge.net/</fo:basic-link>
+                                       ]
+                                    </fo:inline>
+                                 </fo:block>
+                              </fo:block>
+                           </fo:list-item-body>
+                        </fo:list-item>
+                     </fo:list-block>
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+         </fo:block>
+         <fo:block id="N1006A">
+            <fo:block>
+               <fo:block>
+                  <fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats"
+                     margin-left="0pt">
+                     <fo:block keep-with-next.within-column="always">
+                        <fo:block font-family="sans-serif" font-weight="bold"
+                           keep-with-next.within-column="always" space-before.minimum="0.8em"
+                           space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left"
+                           start-indent="0pt">
+                           <fo:marker marker-class-name="section.head.marker">Preface</fo:marker>
+                           <fo:block font-size="20.735999999999997pt">Preface</fo:block>
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+            <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+               space-before.maximum="1.2em">
+               This article is a revisiting of the original
+               <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                  external-destination="url(http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html)">"Authoring With Eclipse"</fo:basic-link>
+               <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false">
+                  [
+                  <fo:basic-link
+                     external-destination="url(http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html)">
+                     http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html
+                  </fo:basic-link>
+                  ]
+               </fo:inline>
+               article by Chris Aniszczyk and Lawrence Mandel. The article revisits many of the
+               concepts discussed in the original article, and expands on them where it is
+               necessary. Much has changed since the original article, but much of the information
+               is still relevant to authoring with eclipse today.
+            </fo:block>
+         </fo:block>
+         <fo:block id="N10073">
+            <fo:block>
+               <fo:block>
+                  <fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats"
+                     margin-left="0pt">
+                     <fo:block keep-with-next.within-column="always">
+                        <fo:block font-family="sans-serif" font-weight="bold"
+                           keep-with-next.within-column="always" space-before.minimum="0.8em"
+                           space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left"
+                           start-indent="0pt">
+                           <fo:marker marker-class-name="section.head.marker">Introduction
+                           </fo:marker>
+                           <fo:block font-size="20.735999999999997pt">Introduction</fo:block>
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+            <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+               space-before.maximum="1.2em"> Writing documentation is something that almost any programmer
+               or architect is eventually going to have to do. It's not a job that most enjoy, and
+               the fact that the documentation usually has to be available in multiple formats at
+               the same time, makes the job of creating the documentation that much less enjoyable.
+               However, all is not lost. There are many ways to produce content that can be written
+               once and documented in many formats. In the sections that follow we will discuss one
+               of these options, DocBook, and how you can use existing eclipse projects and open
+               source plugins to create and authoring system. This article in fact is entirely
+               written in DocBook and leverages the tools discussed.</fo:block>
+         </fo:block>
+         <fo:block id="N10078">
+            <fo:block>
+               <fo:block>
+                  <fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats"
+                     margin-left="0pt">
+                     <fo:block keep-with-next.within-column="always">
+                        <fo:block font-family="sans-serif" font-weight="bold"
+                           keep-with-next.within-column="always" space-before.minimum="0.8em"
+                           space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left"
+                           start-indent="0pt">
+                           <fo:marker marker-class-name="section.head.marker">Technical Documentation
+                           </fo:marker>
+                           <fo:block font-size="20.735999999999997pt">Technical Documentation</fo:block>
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+            <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+               space-before.maximum="1.2em">According to Chris and Lawrence, "In the open source
+               world, technical documentation is primarily accomplished using two popular formats:
+               DocBook and the Darwin Information Typing Architecture (DITA)." Both of these formats
+               leverage XML. They separate the content from the presentation. Unlike HTML which
+               mixes the two together, and you don't have an easy time of separating them. The
+               advantage to DocBook and DITA formats is that it frees the author to concentrate on
+               the content they are entering and not how it will necessarily look. This is necessary
+               because the same content can be targeted to multiple formats, each with its own
+               unique presentation and requirements. It is not uncommon to have DocBook content
+               appear in PDF, Presentation Slides, HTML, RTF, Man, and many more formats.</fo:block>
+            <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+               space-before.maximum="1.2em"> DocBook itself has it's beginnings with SGML, the precursor to
+               XML. It is widely used in the publishing industry, and the O'Reily publishing house
+               use DocBook for all it's books.</fo:block>
+            <fo:block space-before.minimum="0.8em" space-before.optimum="1em"
+               space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N1007F">
+               <fo:block font-size="14pt" font-weight="bold" hyphenate="false"
+                  keep-with-next.within-column="always">Tip</fo:block>
+               <fo:block>
+                  <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                     space-before.maximum="1.2em">
+                     Norman Walsh, has written a book called
+                     <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink"
+                        external-destination="url(http://www.docbook.org/tdg/en/html/docbook.html)">DocBook: The Definitive Guide</fo:basic-link>
+                     <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false">
+                        [
+                        <fo:basic-link external-destination="url(http://www.docbook.org/tdg/en/html/docbook.html)">
+                           http://www.docbook.org/tdg/en/html/docbook.html</fo:basic-link>
+                        ]
+                     </fo:inline>
+                     . The book is available on line as well as at many book resellers. Anything and
+                     everything about the DocBook markup can be found in the book.
+                  </fo:block>
+               </fo:block>
+            </fo:block>
+            <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+               space-before.maximum="1.2em"> Writing an article or a book in XML is no different than
+               writing most any other application. You can break the process down into several
+               stages. Chris and Lawrence original had these in the following steps:</fo:block>
+            <fo:list-block space-before.optimum="1em" space-before.minimum="0.8em"
+               space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em"
+               space-after.maximum="1.2em" provisional-label-separation="0.2em"
+               provisional-distance-between-starts="1.0em" id="N10088">
+               <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                  space-before.maximum="1.2em" id="N10089">
+                  <fo:list-item-label end-indent="label-end()">
+                     <fo:block>•</fo:block>
+                  </fo:list-item-label>
+                  <fo:list-item-body start-indent="body-start()">
+                     <fo:block>
+                        <fo:block> Creation - The process of adding your content to the file. This
+                           includes such meta data as authors, editors, revision history, chapters,
+                           sections, figures, tables, etc.</fo:block>
+                     </fo:block>
+                  </fo:list-item-body>
+               </fo:list-item>
+               <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                  space-before.maximum="1.2em" id="N1008C">
+                  <fo:list-item-label end-indent="label-end()">
+                     <fo:block>•</fo:block>
+                  </fo:list-item-label>
+                  <fo:list-item-body start-indent="body-start()">
+                     <fo:block>
+                        <fo:block> Review - The process of fixing the inevitable grammar and content
+                           mistakes that tend to creep into the document. Regardless of how well the
+                           author tries, some no excuse error is going to creep into the document.
+                           The nice thing about writing is that during this process one is not
+                           concerned as much about how it looks, just that the content is correct.
+                        </fo:block>
+                     </fo:block>
+                  </fo:list-item-body>
+               </fo:list-item>
+               <fo:list-item space-before.optimum="1em" space-before.minimum="0.8em"
+                  space-before.maximum="1.2em" id="N1008F">
+                  <fo:list-item-label end-indent="label-end()">
+                     <fo:block>•</fo:block>
+                  </fo:list-item-label>
+                  <fo:list-item-body start-indent="body-start()">
+                     <fo:block>
+                        <fo:block> Publication - The final step is actually publish the document.
+                           This is either creating the PDF, the HTML, or the eclipse Help format
+                           files. This is where the formatting is reviewed, and for the most part
+                           with the help of the DocBook Project's XSL Stylesheets very little has to
+                           be done to get a professional looking publication. If errors are found,
+                           then repeat the Review process, and republish.</fo:block>
+                     </fo:block>
+                  </fo:list-item-body>
+               </fo:list-item>
+            </fo:list-block>
+            <fo:block id="N10092">
+               <fo:block>
+                  <fo:block>
+                     <fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats"
+                        margin-left="0pt">
+                        <fo:block keep-with-next.within-column="always">
+                           <fo:block font-family="sans-serif" font-weight="bold"
+                              keep-with-next.within-column="always" space-before.minimum="0.8em"
+                              space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left"
+                              start-indent="0pt">
+                              <fo:marker marker-class-name="section.head.marker">Advantages of an XML
+                                 format</fo:marker>
+                              <fo:block font-size="17.28pt">Advantages of an XML format
+                              </fo:block>
+                           </fo:block>
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+               </fo:block>
+               <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                  space-before.maximum="1.2em"> Microsoft Word has the ability to create a master document
+                  from multiple word documents. However, anybody that has tried to do this, knows
+                  that the process is more brittle than it needs to be. It should be a simple as
+                  saying include these three files, and generate me out one complete book that
+                  contains everything. With DocBook and XML it is that simple if you leverage a
+                  little known specification called XInclude.</fo:block>
+               <fo:block id="N10097">
+                  <fo:block>
+                     <fo:block>
+                        <fo:block keep-together.within-column="always"
+                           font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+                           <fo:block keep-with-next.within-column="always">
+                              <fo:block font-family="sans-serif" font-weight="bold"
+                                 keep-with-next.within-column="always" space-before.minimum="0.8em"
+                                 space-before.optimum="1.0em" space-before.maximum="1.2em"
+                                 text-align="left" start-indent="0pt">
+                                 <fo:block font-size="14.399999999999999pt">XInclude</fo:block>
+                              </fo:block>
+                           </fo:block>
+                        </fo:block>
+                     </fo:block>
+                  </fo:block>
+                  <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                     space-before.maximum="1.2em">
+                     XInlcude allows you create the Modularity that Chris and Lawrence original
+                     talked about. An example of an XInclude is shown in
+                     <fo:basic-link internal-destination="Xinclude_Example">
+                        <fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">Example 1, “XInclude”</fo:inline>
+                     </fo:basic-link>
+                  </fo:block>
+                  <fo:block>
+                     <fo:block space-before.minimum="0.5em" space-before.optimum="1em"
+                        space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em"
+                        space-after.maximum="2em" keep-together.within-column="auto" id="Xinclude_Example">
+                        <fo:block space-before.optimum="1em" space-before.minimum="0.8em"
+                           space-before.maximum="1.2em" font-weight="bold" font-size="12pt"
+                           hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em"
+                           space-after.maximum="0.8em" keep-with-next.within-column="always">
+                           Example 1. XInclude</fo:block>
+                        <fo:block space-before.minimum="0.8em" space-before.optimum="1em"
+                           space-before.maximum="1.2em" space-after.minimum="0.8em"
+                           space-after.optimum="1em" space-after.maximum="1.2em" hyphenate="false"
+                           wrap-option="no-wrap" white-space-collapse="false" white-space-treatment="preserve"
+                           linefeed-treatment="preserve" text-align="start" font-family="monospace"
+                           id="N100A3"> &amp;lt;book id='Book1' xmlns:xi="http://www.w3.org/2001/XInclude"&gt;
+  &amp;lt;xi:include href="Introduction.xml"/&gt;
+  &amp;lt;xi:include href="WorkbenchLayout.xml"/&gt;
+&amp;lt;book&gt;
+
+               </fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.minimum="0.8em" space-before.optimum="1em" space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N100A5">
+<fo:block font-size="14pt" font-weight="bold" hyphenate="false" keep-with-next.within-column="always">Note</fo:block>
+<fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                    more
+                </fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+            
+            </fo:block>
+</fo:block>
+<fo:block id="N100AA">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="14.399999999999999pt">Version Control</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> Leveraging Eclipse's built-in version control support with CVS or adding a open
+               source or third party plugin for another version control system, makes maintaining
+               and working on the documentation as convenient as working on any source code for a
+               program. The same comparison and merging abilities that are used with source code for
+               programs can be leveraged for the authoring process as well. Compare this to trying
+               to work with formats that are stored in a binary format and the speed advantage
+               becomes clear pretty quickly. When dealing with a binary formatted file, typically a
+               locking mechanism has to be implemented. Working with DocBook since it is a text
+               format, allows one to take advantage of agile development practices as Continuous
+               Integration and automated builds. Documentation doesn't have to become a thing that
+               is put to the end. It should become a part of the standard build process.</fo:block>
+</fo:block>
+<fo:block id="N100AF">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="14.399999999999999pt">Formatting</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> As stated earlier. The advantage that an XML format has is that it allows
+               presentation and content to be separated. The formatting of the document is
+               independent of the content. One of the most time consuming parts of creating
+               documentation is making sure the formatting is the same. Traditionally if you move
+               sections or cut and paste content from another source, it messes up the formatting of
+               the document. With DocBook you don't run into this issue, as the formatting is
+               controlled during the publication phase. Thus freeing up time that the author would
+               have to spend trying to make the document legible, to make sure that they have the
+               necessary content correct.</fo:block>
+</fo:block>
+<fo:block id="N100B4">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="14.399999999999999pt">One Source, Multiple Targets</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> DocBook, allows for one source content to be generated into multiple formats.
+               Typically DocBook is published in PDF, but it is also widely used for web pages,
+               multi-sectioned HTML pages, Tex, and RTF formats as well. The author doesn't need to
+               worry about any of these formats or how it will necessarily look as that is taken
+               care of by the publishing process. Typically with an XSL stylesheet that already
+               contains the necessary formatting information.</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block id="N100B9">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:marker marker-class-name="section.head.marker">Examples</fo:marker>
+<fo:block font-size="20.735999999999997pt">Examples</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+         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
+         <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(files/book.xml)">here</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(files/book.xml)">files/book.xml</fo:basic-link>]</fo:inline>
+         . This DocBook source for this article is also available and can be seen
+         <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(AuthoringWithEclipse.xml)">here</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(AuthoringWithEclipse.xml)">AuthoringWithEclipse.xml</fo:basic-link>]</fo:inline>
+         .
+      </fo:block>
+<fo:block id="N100C6">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:marker marker-class-name="section.head.marker">The Right Tool for the Right Job.</fo:marker>
+<fo:block font-size="17.28pt">The Right Tool for the Right Job.</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> In order to write an article or a book with DocBook, one needs an editor. Preferably
+            one that understands the XML dialect and it's support tools. The eclipse Web Standard
+            Tools project comes with the necessary tools that are needed. The XML editing support
+            provides the following functionality:</fo:block>
+<fo:list-block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em" space-after.maximum="1.2em" provisional-label-separation="0.2em" provisional-distance-between-starts="1.0em" id="N100CB">
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N100CC">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block> Validation - the ability to check for syntax errors against a specified
+                  grammar. A grammar in this case can be either a DTD or XML Schema for the XML that
+                  is being edited. The XML editor also contains as you type validation to always
+                  keep your XML well formed and valid according the grammar provided.</fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N100CF">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block> Syntax Coloring - Working with XML is much easier of the tags can be easily
+                  separated from the content.</fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N100D2">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block> Content Assistance - If a grammar is detected for the XML file that has been
+                  loaded, then content assistance is available for the tags and attributes. This is
+                  activated using CTRL+SPACE. Also any templates that may be available from the XML
+                  templates preference page will be displayed as well.</fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> The XML editor provided by Web Standard Tools is just the first tool that you will
+            need, but it will be the one that is used the most. The next will be the DocBook XSL
+            stylesheets provided by the DocBook Project. This is is a set of XSL stylesheets that
+            can transform the DocBook files into something that is actually readable. Output formats
+            include HTML, Tex, RTF, and even PDF via XSL-FO.</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> The examples that are shown here are all built using tools that are available at
+            eclipse. Only when we get to the PDF publication do we need to leverage a plugin that
+            isn't available from eclipse directly, but is available as free software. More when PDF
+            generation is covered later in the article.</fo:block>
+<fo:block id="N100D9">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="14.399999999999999pt">Creation and Review</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.minimum="0.8em" space-before.optimum="1em" space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N100DC">
+<fo:block font-size="14pt" font-weight="bold" hyphenate="false" keep-with-next.within-column="always">Note</fo:block>
+<fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> The following section is taken primarily from the original article. Some
+                  updating has been done to update the content.</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> Although creation and review are two separate parts of the technical
+               documentation process, the same tools are required and therefore will be discussed
+               together.</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+               As you may already know, the Eclipse project is composed of several top-level
+               projects including Eclipse itself (known as the Eclipse base) and the WTP project.
+               WTP adds many tools to the Eclipse base including an XML editor with graphical and
+               source representations of the content. Although the graphical editor is useful for
+               viewing the document, the source editor, shown in
+               <fo:basic-link internal-destination="xml-source-editor">
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">Figure 1, “The XML Source Editor”</fo:inline>
+</fo:basic-link>
+               , is more useful when authoring in XML.
+            </fo:block>
+<fo:block space-before.minimum="0.5em" space-before.optimum="1em" space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em" space-after.maximum="2em" keep-together.within-column="auto" id="xml-source-editor">
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" font-weight="bold" font-size="12pt" hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em" space-after.maximum="0.8em" keep-with-next.within-column="always">Figure 1. The XML Source Editor</fo:block>
+<fo:block id="N100EA" text-align="center">
+<fo:external-graphic src="url(images/xmlsourceeditor.gif)" width="auto" height="auto" content-width="auto" content-height="auto" content-type="content-type:image/gif" text-align="center"/>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> In addition to the features discussed previously, Web Standard Tools provides
+               additional XML functionality.</fo:block>
+<fo:list-block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em" space-after.maximum="1.2em" provisional-label-separation="0.2em" provisional-distance-between-starts="1.0em" id="N100F2">
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N100F3">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block>
+                     <fo:inline font-style="italic">Outline View</fo:inline>
+                     - Assists you in editing and viewing the content of your document.
+                  </fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N100F9">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block>
+                     <fo:inline font-style="italic">XML Catalog</fo:inline>
+                     - Allows you to register Document Type Definitions (DTD) and XML Schema
+                     grammars associated with your document with your workspace so you can work with
+                     the benefits of validation while disconnected from the Internet.
+                  </fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> Aside from the benefits of the XML editor, working in Eclipse provides other
+               benefits. Eclipse includes integrated version control for CVS. There also exists
+               freely available plugins for Subversion as well. Integrated version control allows
+               you to check your changes into, and view others' changes in, your version control
+               system from within Eclipse. These tools are also useful for your reviewers, who, if
+               you give them permission, can add comments and suggestions to your document and check
+               their changes in. Giving your reviewers permission to make these changes allows you
+               to avoid the need to use e-mail or some other communication mechanism.</fo:block>
+</fo:block>
+<fo:block id="N10101">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="14.399999999999999pt">Publication</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+               The DocBook XSL
+               <fo:basic-link internal-destination="docbookxsl">
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">[docbookxsl]</fo:inline>
+</fo:basic-link>
+               project offers numerous transformations, including HTML and PDF formats. The most
+               common transformation technique is to use an Ant file with the appropriate tasks for
+               the various transformations. In this article we use the XSL Tooling set of plugins to
+               simplify this task. XSL Tooling integrates into the familiar Eclipse launcher
+               framework. This integration allows you to select the style sheet and pass in
+               necessary parameters for the transformation.
+            </fo:block>
+<fo:block id="N10109">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="12pt">HTML</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> Of all the available transformations, transforming your document into HTML is
+                  the easiest to use. All that you need to do is create a proper transformation
+                  launch configuration and run the transformation. Specifically, you need to specify
+                  the correct style sheet:</fo:block>
+<fo:list-block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em" space-after.maximum="1.2em" provisional-label-separation="0.2em" provisional-distance-between-starts="1.0em" id="N1010E">
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N1010F">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block>DocBook</fo:block>
+<fo:list-block provisional-label-separation="0.2em" provisional-distance-between-starts="1.0em" id="N10112">
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N10113">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block>html/docbook.xsl</fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                  <fo:basic-link internal-destination="html-transformation">
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">Figure 2, “Sample HTML Transformation Configuration for book.xml”</fo:inline>
+</fo:basic-link>
+                  shows a sample transformation configuration that will transform our DocBook sample
+                  <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(files/book.xml)">document</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(files/book.xml)">files/book.xml</fo:basic-link>]</fo:inline>
+                  into HTML.
+               </fo:block>
+<fo:block space-before.minimum="0.5em" space-before.optimum="1em" space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em" space-after.maximum="2em" keep-together.within-column="auto" id="html-transformation">
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" font-weight="bold" font-size="12pt" hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em" space-after.maximum="0.8em" keep-with-next.within-column="always">Figure 2. Sample HTML Transformation Configuration for book.xml</fo:block>
+<fo:block id="N10123" text-align="center">
+<fo:external-graphic src="url(images/html.jpg)" width="741px" height="592px" content-width="scale-to-fit" content-height="scale-to-fit" content-type="content-type:image/jpeg" text-align="center"/>
+</fo:block>
+</fo:block>
+<fo:block space-before.minimum="0.8em" space-before.optimum="1em" space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N1012B">
+<fo:block font-size="14pt" font-weight="bold" hyphenate="false" keep-with-next.within-column="always">Tip</fo:block>
+<fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                     You can augment the transformation by passing parameters to the style sheet.
+                     There's a full listing of DocBook XSL parameters that can be used to configure
+                     the transformation located
+                     <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://docbook.sourceforge.net/release/xsl/current/doc/html/)"> here</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://docbook.sourceforge.net/release/xsl/current/doc/html/)">http://docbook.sourceforge.net/release/xsl/current/doc/html/</fo:basic-link>]</fo:inline>
+                     .
+                  </fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                     Bob Stayton has also written
+                     <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://www.sagehill.net/docbookxsl/)">Docbook XSL: The Complete Guide</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://www.sagehill.net/docbookxsl/)">http://www.sagehill.net/docbookxsl/</fo:basic-link>]</fo:inline>
+                     which is available on line and in print format. This book describes how to
+                     customize the DocBook stylesheets beyond those that you can do with the
+                     parameters. The XSL Tooling provides an XSL aware XML editor that can be used
+                     to help create and debug the stylesheets.
+                  </fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block id="N10138">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="12pt">PDF</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> Transforming a DocBook XML file to PDF format is more involved than the
+                  transformation to HTML but it is still possible using a style sheet. The
+                  difference lies in a task that must be performed before the actual transformation.
+                  So, the transformation from XML to PDF is a two-step process.</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                  Step one is to generate an XSL formatting objects (XSL-FO) document. This document
+                  will then be transformed into a PDF. In order to generate an XSL-FO document, you
+                  need to use the following stylesheet:
+                  <fo:inline font-style="italic">fo/docbook.xsl</fo:inline>
+                  .
+                  <fo:basic-link internal-destination="xslfo-transformation">
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">Figure 3, “Sample XSL-FO Transformation Configuration for book.xml”</fo:inline>
+</fo:basic-link>
+                  shows a sample transformation configuration used to generate an XSL-FO document
+                  from book.xml.
+               </fo:block>
+<fo:block space-before.minimum="0.5em" space-before.optimum="1em" space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em" space-after.maximum="2em" keep-together.within-column="auto" id="xslfo-transformation">
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" font-weight="bold" font-size="12pt" hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em" space-after.maximum="0.8em" keep-with-next.within-column="always">Figure 3. Sample XSL-FO Transformation Configuration for book.xml</fo:block>
+<fo:block id="N10149" text-align="center">
+<fo:external-graphic src="url(images/xsl-fo.png)" width="692px" height="517px" content-width="scale-to-fit" content-height="scale-to-fit" content-type="content-type:image/png" text-align="center"/>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                  Step two is to use a Formatting Objects Processor (FOP) to transform your XSL-FO
+                  document into a PDF. One of the more popular open source FOPs is the
+                  <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://xmlgraphics.apache.org/fop/)"> Apache FOP</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://xmlgraphics.apache.org/fop/)">http://xmlgraphics.apache.org/fop/</fo:basic-link>]</fo:inline>
+                  . We'll use a third-party
+                  <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://www.ahmadsoft.org/fopbridge.html)"> plug-in from Ahmadsoft</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://www.ahmadsoft.org/fopbridge.html)">http://www.ahmadsoft.org/fopbridge.html</fo:basic-link>]</fo:inline>
+                  that integrates Apache FOP into Eclipse. After installing this plug-in, all that
+                  you need to do to render the XSL-FO document is run the FOP transformation.
+                  <fo:basic-link internal-destination="pdf-transformation">
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">Figure 4, “Sample FOP Transformation”</fo:inline>
+</fo:basic-link>
+                  shows an example of running the FOP transformation.
+               </fo:block>
+<fo:block space-before.minimum="0.5em" space-before.optimum="1em" space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em" space-after.maximum="2em" keep-together.within-column="auto" id="pdf-transformation">
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" font-weight="bold" font-size="12pt" hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em" space-after.maximum="0.8em" keep-with-next.within-column="always">Figure 4. Sample FOP Transformation</fo:block>
+<fo:block id="N10162">
+<fo:external-graphic src="url(images/fop.png)" width="430px" height="447px" content-width="scale-to-fit" content-height="scale-to-fit" content-type="content-type:image/png"/>
+</fo:block>
+</fo:block>
+<fo:block space-before.minimum="0.8em" space-before.optimum="1em" space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N10169">
+<fo:block font-size="14pt" font-weight="bold" hyphenate="false" keep-with-next.within-column="always">Note</fo:block>
+<fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                     The example includes a sample Ant
+                     <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(files/pdf/build.xml)"> file</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(files/pdf/build.xml)">files/pdf/build.xml</fo:basic-link>]</fo:inline>
+                     that performs the same transformation as running the FOP transformation using
+                     the
+                     <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://www.ahmadsoft.org/fopbridge.html)"> plug-in from Ahmadsoft</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://www.ahmadsoft.org/fopbridge.html)">http://www.ahmadsoft.org/fopbridge.html</fo:basic-link>]</fo:inline>
+                     . An Ant script is a popular method of performing the publishing stage, and
+                     this example should give you a good starting point if you'd prefer to go this
+                     route. The 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.
+                  </fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                  As before, a Flash movie that shows the transformation is available
+                  <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(files/DocBook-PDF.htm)">here</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(files/DocBook-PDF.htm)">files/DocBook-PDF.htm</fo:basic-link>]</fo:inline>
+                  .
+               </fo:block>
+</fo:block>
+<fo:block id="N1017A">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="12pt">Eclipse Help</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                  The DocBook Project includes a XSL stylesheet that can be used to create the 
+                  necessary files for the eclipse help system. In order to perform this transformation
+                  in DocBook, you need to specify a few parameters and use the following style sheet:
+                  <fo:inline font-style="italic">eclipse/eclipse.xsl</fo:inline>
+                  .
+                  <fo:basic-link internal-destination="eclipse-transformation">
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink">Figure 5, “Sample Eclipse Infocenter Transformation Configuration”</fo:inline>
+</fo:basic-link>
+                  shows a sample transformation configuration along with the correct parameters. To
+                  perform this transformation using a DITA source file, use the
+                  <fo:inline font-style="italic">ant/sample_eclipsehelp.xml</fo:inline>
+                  Ant file.
+               </fo:block>
+<fo:block space-before.minimum="0.5em" space-before.optimum="1em" space-before.maximum="2em" space-after.minimum="0.5em" space-after.optimum="1em" space-after.maximum="2em" keep-together.within-column="auto" id="eclipse-transformation">
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" font-weight="bold" font-size="12pt" hyphenate="false" space-after.minimum="0.4em" space-after.optimum="0.6em" space-after.maximum="0.8em" keep-with-next.within-column="always">Figure 5. Sample Eclipse Infocenter Transformation Configuration</fo:block>
+<fo:block id="N1018C" text-align="center">
+<fo:external-graphic src="url(images/eclipse.png)" width="803px" height="388px" content-width="scale-to-fit" content-height="scale-to-fit" content-type="content-type:image/png" text-align="center"/>
+</fo:block>
+</fo:block>
+<fo:block space-before.minimum="0.8em" space-before.optimum="1em" space-before.maximum="1.2em" margin-left="0.25in" margin-right="0.25in" id="N10194">
+<fo:block font-size="14pt" font-weight="bold" hyphenate="false" keep-with-next.within-column="always">Tip</fo:block>
+<fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                     The complete list of DocBook XSL parameters for the Eclipse Infocenter
+                     transformation is located
+                     <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html)"> here</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html)">http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html</fo:basic-link>]</fo:inline>
+                     .
+                  </fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block id="N1019B">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:block font-size="14.399999999999999pt">Prior Limitations</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> Chris and Lawrence's original article outline two short comings with eclipse as an authoring
+            environment.
+            </fo:block>
+<fo:list-block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em" space-after.maximum="1.2em" provisional-label-separation="0.2em" provisional-distance-between-starts="1.0em" id="N101A0">
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N101A1">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block>
+                        No Grammar and Spell Checking.
+                    </fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N101A4">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block>
+                        No preview screen or WSYIWG editor for documentation.
+                    </fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                The first limitation has been addressed since eclipse 3.3.  Eclipse includes a spell checker and 
+                the Web Standard Tools XML editor leverages this support.   Users may add their own custom dictionary or
+                add any of the freely available dictionaries available on the Internet. 
+            </fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+                The second item may or may not be a limitation depending on the point of view.  The advantage of DocBook is
+                that it separates the content from the presentation.   Worrying about the presentation while creating the
+                content may not be the best thing to do.  The main reason is that how it is formatted is going to greatly
+                depend on the target platforms the documentation is intended.   DocBook authoring is not the same as
+                using a traditional word processor.  A different way of thinking of documentation needs to be approached.  The
+                formatting is not the critical piece, but it is the content of the document that matters the most.
+            </fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block id="N101AB">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:marker marker-class-name="section.head.marker">Summary</fo:marker>
+<fo:block font-size="20.735999999999997pt">Summary</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em"> 
+        Since the original article was published, many advancements have been made with the XML support for eclipse.  The
+        editors are faster, their is better tooling support, and the docbook grammar it self has advanced.  However, the 
+        overall process that Chris and Lawrence had described is fundamentally unchanged three years later.  Eclipse is a
+        perfectly suitable authoring system for technical documentation.  
+      </fo:block>
+</fo:block>
+<fo:block id="N101B0">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:marker marker-class-name="section.head.marker">Acknowledgments</fo:marker>
+<fo:block font-size="20.735999999999997pt">Acknowledgments</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:list-block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" space-after.optimum="1em" space-after.minimum="0.8em" space-after.maximum="1.2em" provisional-label-separation="0.2em" provisional-distance-between-starts="1.0em" id="N101B3">
+<fo:list-item space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" id="N101B4">
+<fo:list-item-label end-indent="label-end()">
+<fo:block>•</fo:block>
+</fo:list-item-label>
+<fo:list-item-body start-indent="body-start()">
+<fo:block>
+<fo:block> Chris Aniszczyk and Lawrence Mandel for their original article title,
+                  "Authoring With Eclipse".</fo:block>
+</fo:block>
+</fo:list-item-body>
+</fo:list-item>
+</fo:list-block>
+</fo:block>
+<fo:block id="N101B7">
+<fo:block>
+<fo:block>
+<fo:block keep-together.within-column="always" font-family="sans-serif,Symbol,ZapfDingbats" margin-left="0pt">
+<fo:block keep-with-next.within-column="always">
+<fo:block font-family="sans-serif" font-weight="bold" keep-with-next.within-column="always" space-before.minimum="0.8em" space-before.optimum="1.0em" space-before.maximum="1.2em" text-align="left" start-indent="0pt">
+<fo:marker marker-class-name="section.head.marker">About the Author</fo:marker>
+<fo:block font-size="20.735999999999997pt">About the Author</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em">
+         David Carver is an XML Data Architect for Standards for Technology in Automotive Retail. He
+         is also a committer on the
+         <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://www.eclipse.org/webtools/incubator)">XSL Tooling</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://www.eclipse.org/webtools/incubator)">http://www.eclipse.org/webtools/incubator</fo:basic-link>]</fo:inline>
+         project.
+      </fo:block>
+</fo:block>
+<fo:block space-before.maximum="2em" space-before.optimum="1.5em" space-before.minimum="1em" id="N101C0">
+<fo:block>
+<fo:block>
+<fo:block font-weight="bold" font-family="sans-serif,Symbol,ZapfDingbats" font-size="24.8832pt" margin-left="0pt">
+<fo:block keep-with-next.within-column="always" space-before.optimum="10pt" space-before.minimum="10pt * 0.8" space-before.maximum="10pt * 1.2" hyphenate="false" text-align="left" start-indent="0pt" hyphenation-character="-" hyphenation-push-character-count="2" hyphenation-remain-character-count="2">Resources</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" start-indent="0.5in" text-indent="-0.5in" id="docbook">[docbook] <fo:inline>
+            <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://www.docbook.org)">Docbook.org - The Source for Documentation.</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://www.docbook.org)">http://www.docbook.org</fo:basic-link>]</fo:inline>
+         . </fo:inline>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" start-indent="0.5in" text-indent="-0.5in" id="docbookxsl">[docbookxsl] <fo:inline>
+            <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://docbook.sourceforge.net/projects/xsl/)"> DocBook XSL Style Sheets</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://docbook.sourceforge.net/projects/xsl/)">http://docbook.sourceforge.net/projects/xsl/</fo:basic-link>]</fo:inline>
+         . </fo:inline>
+</fo:block>
+<fo:block space-before.optimum="1em" space-before.minimum="0.8em" space-before.maximum="1.2em" start-indent="0.5in" text-indent="-0.5in" id="subversion">[subversion] <fo:inline>
+            <fo:basic-link xmlns:xlink="http://www.w3.org/1999/xlink" external-destination="url(http://subversion.tigris.org/)"> Subversion</fo:basic-link>
+<fo:inline xmlns:xlink="http://www.w3.org/1999/xlink" hyphenate="false"> [<fo:basic-link external-destination="url(http://subversion.tigris.org/)">http://subversion.tigris.org/</fo:basic-link>]</fo:inline>
+         . </fo:inline>
+</fo:block>
+</fo:flow>
+</fo:page-sequence>
+</fo:root>
diff --git a/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html
new file mode 100644
index 0000000..0aa6990
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.html
@@ -0,0 +1,596 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Authoring with Eclipse</title><link href="../article.css" rel="stylesheet" type="text/css"><meta content="DocBook XSL Stylesheets V1.73.2" 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"><h1>Authoring with Eclipse</h1><div class="summary"><h2>Summary</h2><p>
+				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.
+			</p><div class="author">
+				By
+				Chris&nbsp;Aniszczyk,
+					IBM Corporation<br>Lawrence&nbsp;Mandel,
+					IBM Corporation<br></div><div class="copyright">
+				Copyright &copy;
+				2005&nbsp;International Business Machines Corporation. All rights reserved.</div><div class="date"><span class="date">December 14, 2005<br></span></div></div><div class="content"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10049"></a>Environment</h2></div></div></div><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><p>
+				The examples in this article were built and tested with:
+				<div class="itemizedlist"><ul type="disc"><li>
+							<a class="ulink" 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 class="ulink" href="http://download.eclipse.org/webtools/downloads/drops/R-1.0-/" target="_new">
+								Eclipse Web Tools Platform (WTP) 1.0
+							</a>
+						</li><li>
+							<a class="ulink" href="http://eclipsexslt.sourceforge.net/" target="_new">
+								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="N10066"></a>Introduction</h2></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
+			publishing, you have writers, editors, typesetters, QA
+			reviewers, and so on. Technical publishing is a collaborative
+			process that currently lacks the tools to facilitate
+			collaboration. The goal of this article is two-fold: give an
+			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="N1006B"></a>Technical Documentation</h2></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
+			formats share two important characteristics: they are both
+			systems for creating structured documents using XML and both focus on content that is written
+			in plain text (or in an editor such as OpenOffice). In this
+			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="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><p>
+				If you're unfamiliar with DocBook, there's an
+				<a class="ulink" href="http://www-128.ibm.com/developerworks/library/l-docbk.html" target="_new">
+					article
+				</a>
+				on the <span class="trademark">IBM</span>&reg; <span class="trademark">developerWorks</span>&reg; site by Joe Brockmeier that can serve as a
+				gentle introduction. There is also an
+				<a class="ulink" 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>
+			The technical documentation process can be broken down into
+			three broad stages: creation, review, and publication.
+		</p><p>
+			Creation simply refers to populating a document with
+			content that adheres to whatever format you choose to write
+			against. This document is usually edited using an XML editor
+			of choice, although it can be edited with any text editor as
+			well. In this article we will use WTP's XML editor to edit
+			documents.
+		</p><p>
+			Once an initial version of the content has been written, it
+			is typically handed off to one or more trusted colleagues
+			for review. The role of these reviewers is to ensure
+			technical accuracy and improve the quality of the writing.
+			The comments and suggestions gathered from the review stage
+			are then used by the document's authors to create a final
+			revision of the document.
+		</p><p>
+			The final revision of a document involves making it is ready for
+			publication. When authoring in an XML format, you must eventually transform the document
+			must be transformed from XML to a human-readable format
+			(that is, one that has both style and formatting applied)
+			such as HTML or PDF. Once in a human-readable format, the
+			document is ready to be published by a selected publisher.
+		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1008B"></a>Advantages of an XML format</h3></div></div></div><p>
+				Before diving into an actual example of the technical
+				documentation process using Eclipse, let's take a look
+				at some of the benefits of authoring in an XML format.
+			</p><p>
+				There are four advantages to authoring in XML that
+				really show the benefit of this format: modularity,
+				version control, consistent formatting, and publishing
+				to multiple formats.
+			</p><p>
+				<span class="emphasis"><em>Modularity</em></span>
+				<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
+							be automatically combined into one document
+							using transformation during the publication
+							stage. Modularizing your documents can be
+							very beneficial when working on large
+							documents, such as a book, or when working
+							with multiple authors. As an example, the 
+							book <span class="emphasis"><em>Java Web
+							Application Development with Eclipse</em></span> (set to
+							be published in time for EclipseCon 2006),
+							was written in DocBook. The book
+							was structured with one table of
+							contents XML file and a separate file for
+							each chapter. Of course, it's up to you to
+							determine the structure that works best for
+							your project. The key is that by using an
+							XML format, you have the freedom to configure
+							your document's structure.
+						</li></ul></div>
+
+				<span class="emphasis"><em>Version Control</em></span>
+				<div class="itemizedlist"><ul type="disc"><li>
+							Version control is very useful and has
+							become a staple in most development
+							processes. Why is it, then, that a system that
+							allows you to maintain the complete history
+							of your files, allowing you to revert to a
+							previous version at any time, is not part of
+							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>&reg; Word or Corel
+							WordPerfect. This mix results in files
+							containing many changes between revisions,
+							reducing the usefulness of version control
+							because it is difficult to view the relevant
+							changes between versions of the document.
+							XML formats do not suffer from this problem
+							as they are content-specific. Authoring in
+							an XML format allows you to use a version
+							control system and reap the benefits that
+							go with it.
+						</li></ul></div>
+
+				<span class="emphasis"><em>Consistent Formatting</em></span>
+				<div class="itemizedlist"><ul type="disc"><li>
+							Ensuring that your document is consistently
+							formatted is a time-consuming aspect of the
+							authoring process. This task can be further
+							aggravated when the authoring format
+							mixes content and formatting in one document
+							or when working with multiple authors or
+							files. One of the typical final steps in the
+							authoring process is ensuring that your
+							document uses consistent formatting. Using
+							an XML format solves the consistent
+							formatting problem by separating your
+							document's content from its formatting. In
+							the XML case, formatting can be applied
+							uniformly to your entire document using a
+							style sheet. An XML format saves you time and
+							guarantees consistent formatting.
+						</li></ul></div>
+
+				<span class="emphasis"><em>Publishing to Multiple Formats</em></span>
+				<div class="itemizedlist"><ul type="disc"><li>
+							By separating your document's
+							formatting from its content, you gain
+							 an enormous freedom. Documents authored
+							in the XML format are not bound by one set
+							of formatting rules. This means that you can
+							author an article, such as this one, and
+							create an HTML version, a PDF version, and
+							even an Eclipse help system version simply
+							by transforming your document with different
+							style sheets. In fact, DocBook includes all
+							three of these stylesheets allowing you to
+							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="N100BB"></a>Examples</h2></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 class="ulink" href="files/book.xml" target="_new">here</a>. This DocBook source for this
+			article is also available and can be seen <a class="ulink" href="AuthoringWithEclipse.xml" target="_new">here</a>.
+		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N100C8"></a>Tool Chain</h3></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
+				chain, so the output of each tool becomes the input of
+				the next
+				<a class="xref" href="#toolchain" title="???TITLE???">[3]</a>
+				. This concept should be very familiar to those who work
+				on the <span class="trademark">UNIX</span>&reg;, 
+				<span class="trademark">Linux</span>&reg;, and 
+				<span class="trademark">AIX</span>&reg; 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
+				tools.
+			</p><p>
+				The beginning of our technical publishing tool chain is
+				the WTP XML editor, which we use to edit our content.
+				After we have finished editing the content, we will feed the
+				output of what we edited into OrangeVolt, an XSLT
+				transformation engine, which will use style sheets to
+				publish the content into a human-readable format.
+			</p><p>
+				The limitation we put on these examples is that our
+				tool chain, including all three stages, creation, review,
+				and publication, will be built with tools available within
+				Eclipse. From our experience, Eclipse has enormous
+				potential as an integrated documentation
+				development environment. In the following sections, we'll
+				discuss how you can make this a reality with current
+				Eclipse tooling and where the tooling falls short.
+			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N100E0"></a>Creation and Review</h4></div></div></div><p>
+					Although creation and review are two separate parts
+					of the technical documentation process, the same
+					tools are required and therefore will be discussed
+					together.
+				</p><p>
+					As you may already know, the Eclipse project
+					is composed of serveral top-level projects including
+					Eclipse itself (known as the Eclipse base) and the
+					WTP project. WTP adds many tools to the Eclipse base
+					including an XML editor with graphical and source
+					representations of the content. Although the
+					graphical editor is useful for viewing your document,
+					we've found that the source editor, shown in
+					<a class="xref" href="#xml-source-editor" title="Figure&nbsp;1.&nbsp;The XML Source Editor">Figure&nbsp;1, &ldquo;The XML Source Editor&rdquo;</a>
+					, is more useful when authoring in XML.
+				</p><div class="figure"><a name="xml-source-editor"></a><p class="title"><b>Figure&nbsp;1.&nbsp;The XML Source Editor</b></p><div class="figure-contents"><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></div><br class="figure-break"><p>
+					The XML editor provides many of the Eclipse
+					franchise functions that <span class="trademark">Java</span>&trade; developers have become
+					accustomed to with the Java editor.
+				</p><p>
+					<span class="emphasis"><em>Content Assistance</em></span>
+				</p><div class="itemizedlist"><ul type="disc"><li>
+							Gives you a list of valid XML elements
+							constrained by an associated grammar.
+						</li></ul></div><p>
+					<span class="emphasis"><em>Syntax Highlighting</em></span>
+				</p><div class="itemizedlist"><ul type="disc"><li>
+							Gives you improved code readability by
+							making certain errors instantly visible.
+						</li></ul></div><p>
+					<span class="emphasis"><em>Validation</em></span>
+				</p><div class="itemizedlist"><ul type="disc"><li>
+							Ensures validity of an XML document based
+							on an associated grammar.
+						</li></ul></div><p>
+					<span class="emphasis"><em>Outline View</em></span>
+				</p><div class="itemizedlist"><ul type="disc"><li>
+							Assists you in editing and viewing the
+							content of your document.
+						</li></ul></div><p>
+					<span class="emphasis"><em>XML Catalog</em></span>
+				</p><div class="itemizedlist"><ul type="disc"><li>
+							Allows you to register Document Type
+							Definitions (DTD) and XML Schema grammars
+							associated with your document with your
+							workspace so you can work with the benefits
+							of validation while disconnected from the
+							Internet.
+						</li></ul></div><p>
+					Aside from the benefits of the XML editor, working
+					in Eclipse provides other benefits. Eclipse includes
+					integrated version control for CVS. (There is also a
+					freely available plug-in for subversion
+					<a class="xref" href="#subversion" title="???TITLE???">[6]</a>, another version control 
+					system.) Integrated
+					version control allows you to check your changes
+					into, and view others' changes in, your version
+					control system from within Eclipse. These tools are
+					also useful for your reviewers, who, if you give them
+					permission, can add comments and suggestions to your
+					document and check their changes in. Giving your reviewers
+					permission to make these changes allows you to avoid
+					the need to use e-mail or some other communication
+					mechanism.
+				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1012E"></a>Publication</h4></div></div></div><p>
+					The DocBook XSL
+					<a class="xref" href="#docbookxsl" title="???TITLE???">[1]</a>
+					and DITA
+					<a class="xref" href="#dita" title="???TITLE???">[2]</a>
+					projects offer numerous transformations, including
+					HTML and PDF formats. The most common
+					transformation technique is to use an Ant file with
+					the appropriate tasks for the various
+					transformations. In this article we use the
+					Orangevolt XSLT tool to simplify this task.
+					Orangevolt XSLT integrates into the familiar Eclipse
+					launcher framework. This integration allows you to
+					select the style sheet and pass in necessary
+					parameters for the transformation.
+				</p><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><p>
+					The DITA Open Toolkit (DITA-OT) includes a DITA to DocBook
+					<a class="ulink" href="http://dita-ot.sourceforge.net/doc/DITA-antscript.html" target="_new">
+						transformation
+					</a>.
+				</p></td></tr></table></div><p>
+					Along with the description in this article, we have
+					provided Flash movies that demonstrate how to
+					perform each transformation. Transformations for
+					both DocBook and DITA will be provided where
+					appropriate.
+				</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N10142"></a>HTML</h5></div></div></div><p>
+						Of all the available transformations,
+						transforming your document into HTML is the
+						easiest to use. All that you need to do is
+						create a proper transformation launch
+						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 class="xref" href="#html-transformation" title="Figure&nbsp;2.&nbsp;Sample HTML Transformation Configuration for book.xml">Figure&nbsp;2, &ldquo;Sample HTML Transformation Configuration for book.xml&rdquo;</a>
+						shows a sample transformation configuration that
+						will transform our DocBook sample
+						<a class="ulink" href="files/book.xml" target="_new">document</a>
+						into HTML.
+					</p><div class="figure"><a name="html-transformation"></a><p class="title"><b>Figure&nbsp;2.&nbsp;Sample HTML Transformation Configuration for book.xml</b></p><div class="figure-contents"><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><br class="figure-break"><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><p>
+							You can augment the transformation by
+							passing parameters to the style sheet.
+							There's a full listing of DocBook XSL
+							parameters that can be used to configure the
+							transformation located
+							<a class="ulink" href="http://docbook.sourceforge.net/release/xsl/current/doc/html/" target="_new">
+								here
+							</a>.
+						</p></td></tr></table></div><p>
+						A Flash movie that
+						shows how to run the transformation can be seen
+						<a class="ulink" href="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="N10177"></a>PDF</h5></div></div></div><p>
+						Transforming a DocBook XML file to PDF format is
+						more involved than the transformation to HTML
+						but it is still possible using a style sheet. The
+						difference lies in a task that must be performed
+						before the actual transformation. So, the
+						transformation from XML to PDF is a two-step
+						process.
+					</p><p>
+						Step one is to generate an XSL formatting objects
+						(XSL-FO) document. This document will then be
+						transformed into a PDF. In order to generate an
+						XSL-FO document, you need to use the following
+						stylesheet:
+						<span class="emphasis"><em>fo/docbook.xsl</em></span>.
+						<a class="xref" href="#xslfo-transformation" title="Figure&nbsp;3.&nbsp;Sample XSL-FO Transformation Configuration for book.xml">Figure&nbsp;3, &ldquo;Sample XSL-FO Transformation Configuration for book.xml&rdquo;</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&nbsp;3.&nbsp;Sample XSL-FO Transformation Configuration for book.xml</b></p><div class="figure-contents"><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></div><br class="figure-break"><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
+						open source FOPs is the
+						<a class="ulink" href="http://xmlgraphics.apache.org/fop/" target="_new">
+							Apache FOP
+						</a>
+						. We'll use a third-party
+						<a class="ulink" href="http://www.ahmadsoft.org/fopbridge.html" target="_new">
+							plug-in from Ahmadsoft
+						</a>
+						that integrates Apache FOP into Eclipse. After
+						installing this plug-in, all that you need to do
+						to render the XSL-FO document is run the FOP
+						transformation.
+						<a class="xref" href="#pdf-transformation" title="Figure&nbsp;4.&nbsp;Sample FOP Transformation">Figure&nbsp;4, &ldquo;Sample FOP Transformation&rdquo;</a>
+						shows an example of running the FOP
+						transformation.
+					</p><div class="figure"><a name="pdf-transformation"></a><p class="title"><b>Figure&nbsp;4.&nbsp;Sample FOP Transformation</b></p><div class="figure-contents"><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><br class="figure-break"><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><p>
+							The example includes a sample Ant
+							<a class="ulink" href="files/pdf/build.xml" target="_new">
+								file
+							</a>
+							that performs the same transformation as
+							running the FOP transformation using the
+							<a class="ulink" href="http://www.ahmadsoft.org/fopbridge.html" target="_new">
+								plug-in from Ahmadsoft
+							</a>. An Ant script is a popular method of
+							performing the publishing stage, and this
+							example should give you a good starting
+							point if you'd prefer to go this route. The
+							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>
+						As before, a Flash movie that shows the
+						transformation is available
+						<a class="ulink" href="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="N101BA"></a>Eclipse Infocenter</h5></div></div></div><p>
+						In our opinion, one of the coolest features of
+						the DocBook and DITA projects is the generation
+						of an Eclipse help plug-in (information center) from
+						your source XML file. In order to perform this
+						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 class="xref" href="#eclipse-transformation" title="Figure&nbsp;5.&nbsp;Sample Eclipse Infocenter Transformation Configuration">Figure&nbsp;5, &ldquo;Sample Eclipse Infocenter Transformation Configuration&rdquo;</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&nbsp;5.&nbsp;Sample Eclipse Infocenter Transformation Configuration</b></p><div class="figure-contents"><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><br class="figure-break"><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><p>
+							The complete list of DocBook XSL parameters
+							for the Eclipse Infocenter transformation
+							is located
+							<a class="ulink" href="http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html" target="_new">
+								here
+
+							</a>
+							.
+						</p></td></tr></table></div><p>
+						The Flash movie that shows the Eclipse
+						Infocenter DocBook transformation can be found
+						<a class="ulink" href="files/DocBook-InfoCenter.htm" target="_new">
+							here
+						</a>
+						.
+					</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N101E1"></a>Current Limitations</h4></div></div></div><p>
+					Although we have shown that Eclipse's current XML
+					authoring support is pretty good, there are a two
+					noteworthy limitations.
+				</p><p>
+					The first is grammar and spell-checking. While these
+					tools are commonplace in word-processing software,
+					they do not yet exist for WTP's XML editor.
+				</p><p>
+					The second is a WYSIWYG editor for XML documentation
+					formats such as DITA and DocBook (or a preview
+					window). The lack of a sophisticated editor or a way
+					to preview what you've written requires that you
+					stop authoring and transform your document in order
+					to view the results of your changes.
+				</p><p>
+					While neither of these limitations has been a show-stopper 
+					in our authoring process, our hope is that as
+					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="N101EC"></a>Summary</h2></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
+			how to use Eclipse to aid the different phases of the
+			technical documentation process. Although there is still a
+			lot of room for improvement in this area we hope we've
+			convinced you that technical documentation in Eclipse is
+			both possible and already viable. It's now up to you in
+			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="N101F1"></a>Acknowledgements</h2></div></div></div><p>
+			We'd like to thank:
+			<div class="itemizedlist"><ul type="disc"><li>
+						Sushma Patel and Anne James for correcting our horrible
+						grammar.
+					</li></ul></div>
+			<div class="itemizedlist"><ul type="disc"><li>
+						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="N10200"></a>About the Authors</h2></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 class="ulink" href="http://www.gentoo.org" target="_new">Gentoo Linux</a>
+			distribution and also a committer on the
+			<a class="ulink" href="http://www.eclipse.org/emft" target="_new">
+				Eclipse Modeling Framework Technology (EMFT)
+			</a>
+			project.
+		</p><p>
+			Lawrence Mandel, a software developer at the IBM Toronto
+			Laboratory, is the documentation lead and a
+			committer for the Eclipse
+			<a class="ulink" href="http://www.eclipse.org/webtools" target="_new">
+				Web Tools Platform (WTP)
+			</a>
+			project. He is also authoring a book with Arthur Ryman and
+			Naci Dai about Java Web application development with
+			Eclipse.
+		</p></div><div class="appendix" lang="en"><h2 class="title" style="clear: both"><a name="N10246"></a>A.&nbsp;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
+			reviews a couple of other editors out there for technical
+			documentation in case WTP's XML editor doesn't suit your fancy.
+		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1024B"></a>The Article</h3></div></div></div><p>
+				This article was written in DocBook using WTP's XML
+				editor. To transform the article into the correct format
+				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 class="ulink" href="files/article.xsl" target="_new">here</a>.
+				<div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><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 class="ulink" 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="N1025C"></a>Editors</h3></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
+				content creator (think EMACS versus VI). We decided to
+				use the WTP XML editor as the editor for this article
+				because of our familiarity with it and because both of us like working
+				within Eclipse. However, we realize that there are other
+				options for creating and editing content so we'll
+				discuss of a couple of those options in the following
+				sections.
+			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10261"></a>Vex</h4></div></div></div><p>
+					Vex
+					<a class="xref" href="#vex" title="???TITLE???">[4]</a>
+					is an open source project that lets you edit XML
+					files visually. Vex uses standard Document Type
+					Definition (DTD) files to define document types and
+					Cascading Style Sheets (CSS) to define document
+					layout. In essence, Vex only requires that you have
+					knowledge of CSS and DTDs in order to contribute a
+					visual editor for XML files. The Vex editor can be
+					seen in
+					<a class="xref" href="#vex-editor" title="Figure&nbsp;A.1.&nbsp;Vex DocBook editor screenshot">Figure&nbsp;A.1, &ldquo;Vex DocBook editor screenshot&rdquo;</a>
+					.
+					<div class="figure"><a name="vex-editor"></a><p class="title"><b>Figure&nbsp;A.1.&nbsp;Vex DocBook editor screenshot</b></p><div class="figure-contents"><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></div><br class="figure-break">
+
+				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10279"></a>OpenOffice</h4></div></div></div><p>
+					OpenOffice
+					<a class="xref" href="#openoffice" title="???TITLE???">[5]</a>
+					is a multi-platform open source office suite that is
+					capable of visually editing DocBook and various
+					other formats. OpenOffice is a popular editing
+					choice because of its ability to open multiple
+					document formats, including Microsoft Word, and then
+					export the documents to DocBook.
+				</p><p>
+					OpenOffice doesn't fully support DocBook. An
+					updated list of what portions of DocBook OpenOffice
+					supports can be found on the OpenOffice site
+					<a class="ulink" href="http://xml.openoffice.org/xmerge/docbook/DocBookTags.html" target="_new">
+						here
+					</a>
+					. The site also contains a getting started
+					<a class="ulink" href="http://xml.openoffice.org/xmerge/docbook/UserGuide.html" target="_new">
+						guide
+					</a>
+					that will get you started with DocBook in
+					OpenOffice.
+				</p></div></div></div><div class="bibliography"><div class="titlepage"><div><div><h2 class="title"><a name="N10213"></a>Resources</h2></div></div></div><div class="biblioentry"><a name="docbookxsl"></a><p>[1] <span class="bibliosource">
+				<a class="ulink" href="http://docbook.sourceforge.net/projects/xsl/" target="_new">
+					DocBook XSL Style Sheets
+				</a>
+			. </span></p></div><div class="biblioentry"><a name="dita"></a><p>[2] <span class="bibliosource">
+				<a class="ulink" href="http://dita-ot.sourceforge.net/" target="_new">
+					DITA Open Toolkit
+				</a>
+			. </span></p></div><div class="biblioentry"><a name="toolchain"></a><p>[3] <span class="bibliosource">
+				<a class="ulink" href="http://en.wikipedia.org/wiki/Toolchain" target="_new">
+					Wikipedia: Toolchain
+				</a>
+			. </span></p></div><div class="biblioentry"><a name="vex"></a><p>[4] <span class="bibliosource">
+				<a class="ulink" 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 class="ulink" 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 class="ulink" href="http://subversion.tigris.org/" target="_new">
+					Subversion
+				</a>
+			. </span></p></div></div><div class="notices"><h3>Legal Notices</h3><p>
+				IBM, AIX, and developerWorks are registered trademarks of International Business Machines 
+				Corporation in the United States, other countries, or both.
+			</p><p>
+				Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United 
+				States, other countries, or both.
+			</p><p>
+				Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
+			</p><p>
+				Microsoft is a trademark of Microsoft Corporation in the United States, other countries, or both.
+			</p><p>
+				UNIX is a registered trademark of The Open Group in the United States and other countries.
+			</p><p>
+				Other company, product, or service names may be trademarks or service marks of others.
+			</p></div></div><div class="content"></div></body></html>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/AuthoringWithEclipse.xml b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.xml
new file mode 100644
index 0000000..1cae679
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.xml
@@ -0,0 +1,970 @@
+<?xml version="1.0" encoding="utf-8"?>

+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"

+          "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">

+<article id="article">

+	<articleinfo>

+		<title>Authoring with Eclipse</title>

+		<releaseinfo>

+			<remark>Updated May 2008 by Peter Friese, itemis AG (see <ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=225714">Bug 225714)</ulink>.</remark>

+		</releaseinfo>

+		<date>December 14, 2005</date>

+		<authorgroup>

+			<author>

+				<firstname>Chris</firstname>

+				<surname>Aniszczyk</surname>

+				<affiliation>

+					<orgname>IBM Corporation</orgname>

+					<address>

+						<email>zx@us.ibm.com</email>

+					</address>

+				</affiliation>

+			</author>

+			<author>

+				<firstname>Lawrence</firstname>

+				<surname>Mandel</surname>

+				<affiliation>

+					<orgname>IBM Corporation</orgname>

+					<address>

+						<email>lmandel@ca.ibm.com</email>

+					</address>

+				</affiliation>

+			</author>

+		</authorgroup>

+		<copyright>

+			<year>2005</year>

+			<holder>International Business Machines Corporation. All rights reserved.</holder>

+		</copyright>

+		<abstract>

+			<para>

+				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.

+			</para>

+		</abstract>

+		<legalnotice>

+			<para>

+				IBM, AIX, and developerWorks are registered trademarks of International Business Machines 

+				Corporation in the United States, other countries, or both.

+			</para>

+			<para>

+				Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United 

+				States, other countries, or both.

+			</para>

+			<para>

+				Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

+			</para>

+			<para>

+				Microsoft is a trademark of Microsoft Corporation in the United States, other countries, or both.

+			</para>

+			<para>

+				UNIX is a registered trademark of The Open Group in the United States and other countries.

+			</para>

+			<para>

+				Other company, product, or service names may be trademarks or service marks of others.

+			</para>

+		</legalnotice>

+	</articleinfo>

+	<section>

+		<title>Environment</title>

+		<note>

+			<para>

+				The examples in this article were built and tested with:

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							<ulink 

+								url="http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.1-200506271435/eclipse-SDK-3.1-win32.zip">

+								Eclipse 3.1

+							</ulink>

+						</simpara>

+					</listitem>

+					<listitem>

+						<simpara>

+							<ulink 

+								url="http://download.eclipse.org/webtools/downloads/drops/R-1.0-/">

+								Eclipse Web Tools Platform (WTP) 1.0

+							</ulink>

+						</simpara>

+					</listitem>

+					<listitem>

+						<simpara>

+							<ulink 

+								url="http://eclipsexslt.sourceforge.net/">

+								Orangevolt XSLT 1.0.4

+							</ulink>

+						</simpara>

+					</listitem>

+				</itemizedlist>

+			</para>

+		</note>

+	</section>

+	<section>

+		<title>Introduction</title>

+

+		<para>

+			The authors of this document view technical documentation as

+			another development process that shares the same

+			characteristics as a software process. In technical

+			publishing, you have writers, editors, typesetters, QA

+			reviewers, and so on. Technical publishing is a collaborative

+			process that currently lacks the tools to facilitate

+			collaboration. The goal of this article is two-fold: give an

+			introduction to technical documentation and show, through an

+			example, how Eclipse can help make technical documentation a

+			collaborative process.

+		</para>

+

+	</section>

+

+	<section>

+		<title>Technical Documentation</title>

+

+		<para>

+			In the open source world, technical documentation is

+			primarily accomplished using two popular formats: DocBook

+			and the Darwin Information Typing Architecture (DITA). These two

+			formats share two important characteristics: they are both

+			systems for creating structured documents using XML and both focus on content that is written

+			in plain text (or in an editor such as OpenOffice). In this

+			article we focus on DocBook because of our familiarity with the

+			format. However, we will also provide complementary DITA

+			information where appropriate.

+		</para>

+

+		<tip>

+			<para>

+				If you're unfamiliar with DocBook, there's an

+				<ulink 

+					url="http://www-128.ibm.com/developerworks/library/l-docbk.html">

+					article

+				</ulink>

+				on the <trademark class="registered">IBM</trademark> <trademark class="registered">developerWorks</trademark> site by Joe Brockmeier that can serve as a

+				gentle introduction. There is also an

+				<ulink 

+					url="http://www-128.ibm.com/developerworks/xml/library/x-dita1/index.html">

+					introduction

+				</ulink>

+				to DITA on developerWorks.

+			</para>

+		</tip>

+

+		<para>

+			The technical documentation process can be broken down into

+			three broad stages: creation, review, and publication.

+		</para>

+		<para>

+			Creation simply refers to populating a document with

+			content that adheres to whatever format you choose to write

+			against. This document is usually edited using an XML editor

+			of choice, although it can be edited with any text editor as

+			well. In this article we will use WTP's XML editor to edit

+			documents.

+		</para>

+		<para>

+			Once an initial version of the content has been written, it

+			is typically handed off to one or more trusted colleagues

+			for review. The role of these reviewers is to ensure

+			technical accuracy and improve the quality of the writing.

+			The comments and suggestions gathered from the review stage

+			are then used by the document's authors to create a final

+			revision of the document.

+		</para>

+		<para>

+			The final revision of a document involves making it is ready for

+			publication. When authoring in an XML format, you must eventually transform the document

+			must be transformed from XML to a human-readable format

+			(that is, one that has both style and formatting applied)

+			such as HTML or PDF. Once in a human-readable format, the

+			document is ready to be published by a selected publisher.

+		</para>

+

+		<section>

+			<title>Advantages of an XML format</title>

+

+			<para>

+				Before diving into an actual example of the technical

+				documentation process using Eclipse, let's take a look

+				at some of the benefits of authoring in an XML format.

+			</para>

+			<para>

+				There are four advantages to authoring in XML that

+				really show the benefit of this format: modularity,

+				version control, consistent formatting, and publishing

+				to multiple formats.

+			</para>

+			<para>

+				<emphasis>Modularity</emphasis>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							XML formats such as DocBook and DITA are

+							modular. This allows you to break up your

+							documents into multiple sections, which can

+							be automatically combined into one document

+							using transformation during the publication

+							stage. Modularizing your documents can be

+							very beneficial when working on large

+							documents, such as a book, or when working

+							with multiple authors. As an example, the 

+							book <emphasis>Java Web

+							Application Development with Eclipse</emphasis> (set to

+							be published in time for EclipseCon 2006),

+							was written in DocBook. The book

+							was structured with one table of

+							contents XML file and a separate file for

+							each chapter. Of course, it's up to you to

+							determine the structure that works best for

+							your project. The key is that by using an

+							XML format, you have the freedom to configure

+							your document's structure.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+

+				<emphasis>Version Control</emphasis>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Version control is very useful and has

+							become a staple in most development

+							processes. Why is it, then, that a system that

+							allows you to maintain the complete history

+							of your files, allowing you to revert to a

+							previous version at any time, is not part of

+							the authoring process? One reason is that many

+							documents are authored using word-processing

+							tools that mix formatting information and

+							content, such as <trademark class="registered">Microsoft</trademark> Word or Corel

+							WordPerfect. This mix results in files

+							containing many changes between revisions,

+							reducing the usefulness of version control

+							because it is difficult to view the relevant

+							changes between versions of the document.

+							XML formats do not suffer from this problem

+							as they are content-specific. Authoring in

+							an XML format allows you to use a version

+							control system and reap the benefits that

+							go with it.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+

+				<emphasis>Consistent Formatting</emphasis>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Ensuring that your document is consistently

+							formatted is a time-consuming aspect of the

+							authoring process. This task can be further

+							aggravated when the authoring format

+							mixes content and formatting in one document

+							or when working with multiple authors or

+							files. One of the typical final steps in the

+							authoring process is ensuring that your

+							document uses consistent formatting. Using

+							an XML format solves the consistent

+							formatting problem by separating your

+							document's content from its formatting. In

+							the XML case, formatting can be applied

+							uniformly to your entire document using a

+							style sheet. An XML format saves you time and

+							guarantees consistent formatting.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+

+				<emphasis>Publishing to Multiple Formats</emphasis>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							By separating your document's

+							formatting from its content, you gain

+							 an enormous freedom. Documents authored

+							in the XML format are not bound by one set

+							of formatting rules. This means that you can

+							author an article, such as this one, and

+							create an HTML version, a PDF version, and

+							even an Eclipse help system version simply

+							by transforming your document with different

+							style sheets. In fact, DocBook includes all

+							three of these stylesheets allowing you to

+							easily publish to any of the formats listed

+							above.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+			</para>

+		</section>

+	</section>

+

+	<section>

+		<title>Examples</title>

+		<para>

+			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

+			<ulink url="files/book.xml">here</ulink>. This DocBook source for this

+			article is also available and can be seen <ulink url="AuthoringWithEclipse.xml">here</ulink>.

+		</para>

+

+		<section>

+			<title>Tool Chain</title>

+

+			<para>

+				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

+				chain, so the output of each tool becomes the input of

+				the next

+				<xref linkend="toolchain" />

+				. This concept should be very familiar to those who work

+				on the <trademark class="registered">UNIX</trademark>, 

+				<trademark class="registered">Linux</trademark>, and 

+				<trademark class="registered">AIX</trademark> 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

+				tools.

+			</para>

+			<para>

+				The beginning of our technical publishing tool chain is

+				the WTP XML editor, which we use to edit our content.

+				After we have finished editing the content, we will feed the

+				output of what we edited into OrangeVolt, an XSLT

+				transformation engine, which will use style sheets to

+				publish the content into a human-readable format.

+			</para>

+			<para>

+				The limitation we put on these examples is that our

+				tool chain, including all three stages, creation, review,

+				and publication, will be built with tools available within

+				Eclipse. From our experience, Eclipse has enormous

+				potential as an integrated documentation

+				development environment. In the following sections, we'll

+				discuss how you can make this a reality with current

+				Eclipse tooling and where the tooling falls short.

+			</para>

+

+			<section>

+				<title>Creation and Review</title>

+				<para>

+					Although creation and review are two separate parts

+					of the technical documentation process, the same

+					tools are required and therefore will be discussed

+					together.

+				</para>

+				<para>

+					As you may already know, the Eclipse project

+					is composed of serveral top-level projects including

+					Eclipse itself (known as the Eclipse base) and the

+					WTP project. WTP adds many tools to the Eclipse base

+					including an XML editor with graphical and source

+					representations of the content. Although the

+					graphical editor is useful for viewing your document,

+					we've found that the source editor, shown in

+					<xref linkend="xml-source-editor" />

+					, is more useful when authoring in XML.

+				</para>

+				<figure id="xml-source-editor">

+					<title>The XML Source Editor</title>

+					<mediaobject>

+						<imageobject>

+							<imagedata width="807" depth="598" fileref="images/xmlsourceeditor.gif"

+								format="GIF" />

+						</imageobject>

+					</mediaobject>

+				</figure>

+

+				<para>

+					The XML editor provides many of the Eclipse

+					franchise functions that <trademark>Java</trademark> developers have become

+					accustomed to with the Java editor.

+				</para>

+				<simpara>

+					<emphasis>Content Assistance</emphasis>

+				</simpara>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Gives you a list of valid XML elements

+							constrained by an associated grammar.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+				<simpara>

+					<emphasis>Syntax Highlighting</emphasis>

+				</simpara>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Gives you improved code readability by

+							making certain errors instantly visible.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+				<simpara>

+					<emphasis>Validation</emphasis>

+				</simpara>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Ensures validity of an XML document based

+							on an associated grammar.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+				<simpara>

+					<emphasis>Outline View</emphasis>

+				</simpara>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Assists you in editing and viewing the

+							content of your document.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+				<simpara>

+					<emphasis>XML Catalog</emphasis>

+				</simpara>

+				<itemizedlist>

+					<listitem>

+						<simpara>

+							Allows you to register Document Type

+							Definitions (DTD) and XML Schema grammars

+							associated with your document with your

+							workspace so you can work with the benefits

+							of validation while disconnected from the

+							Internet.

+						</simpara>

+					</listitem>

+				</itemizedlist>

+				<para>

+					Aside from the benefits of the XML editor, working

+					in Eclipse provides other benefits. Eclipse includes

+					integrated version control for CVS. (There is also a

+					freely available plug-in for subversion

+					<xref linkend="subversion" />, another version control 

+					system.) Integrated

+					version control allows you to check your changes

+					into, and view others' changes in, your version

+					control system from within Eclipse. These tools are

+					also useful for your reviewers, who, if you give them

+					permission, can add comments and suggestions to your

+					document and check their changes in. Giving your reviewers

+					permission to make these changes allows you to avoid

+					the need to use e-mail or some other communication

+					mechanism.

+				</para>

+			</section>

+			<section>

+				<title>Publication</title>

+

+				<para>

+					The DocBook XSL

+					<xref linkend="docbookxsl" />

+					and DITA

+					<xref linkend="dita" />

+					projects offer numerous transformations, including

+					HTML and PDF formats. The most common

+					transformation technique is to use an Ant file with

+					the appropriate tasks for the various

+					transformations. In this article we use the

+					Orangevolt XSLT tool to simplify this task.

+					Orangevolt XSLT integrates into the familiar Eclipse

+					launcher framework. This integration allows you to

+					select the style sheet and pass in necessary

+					parameters for the transformation.

+				</para>

+				<tip>

+				<simpara>

+					The DITA Open Toolkit (DITA-OT) includes a DITA to DocBook

+					<ulink 

+						url="http://dita-ot.sourceforge.net/doc/DITA-antscript.html">

+						transformation

+					</ulink>.

+				</simpara>

+				</tip>

+				<para>

+					Along with the description in this article, we have

+					provided Flash movies that demonstrate how to

+					perform each transformation. Transformations for

+					both DocBook and DITA will be provided where

+					appropriate.

+				</para>

+

+				<section>

+					<title>HTML</title>

+

+					<para>

+						Of all the available transformations,

+						transforming your document into HTML is the

+						easiest to use. All that you need to do is

+						create a proper transformation launch

+						configuration and run the transformation.

+						Specifically, you need to specify the correct

+						style sheet:

+						<itemizedlist>

+							<listitem>

+								<simpara>DocBook</simpara>

+								<itemizedlist>

+									<listitem>

+										<simpara>html/docbook.xsl</simpara>

+									</listitem>

+								</itemizedlist>

+							</listitem>

+							<listitem>

+								<simpara>DITA</simpara>

+								<itemizedlist>

+									<listitem>

+										<simpara>xsl/dita2html.xsl</simpara>

+									</listitem>

+								</itemizedlist>

+							</listitem>

+						</itemizedlist>

+						<xref linkend="html-transformation" />

+						shows a sample transformation configuration that

+						will transform our DocBook sample

+						<ulink url="files/book.xml">document</ulink>

+						into HTML.

+					</para>

+					<figure id="html-transformation">

+						<title>Sample HTML Transformation Configuration for book.xml</title>

+						<mediaobject>

+							<imageobject>

+								<imagedata width="692" depth="517" fileref="images/html.png"

+									format="PNG" />

+							</imageobject>

+						</mediaobject>

+					</figure>

+					<tip>

+						<para>

+							You can augment the transformation by

+							passing parameters to the style sheet.

+							There's a full listing of DocBook XSL

+							parameters that can be used to configure the

+							transformation located

+							<ulink 

+								url="http://docbook.sourceforge.net/release/xsl/current/doc/html/">

+								here

+							</ulink>.

+						</para>

+					</tip>

+					<para>

+						A Flash movie that

+						shows how to run the transformation can be seen

+						<ulink  url="files/DocBook-HTML.htm">here</ulink>

+						.

+					</para>

+

+				</section>

+

+				<section>

+					<title>PDF</title>

+

+					<para>

+						Transforming a DocBook XML file to PDF format is

+						more involved than the transformation to HTML

+						but it is still possible using a style sheet. The

+						difference lies in a task that must be performed

+						before the actual transformation. So, the

+						transformation from XML to PDF is a two-step

+						process.

+					</para>

+					<para>

+						Step one is to generate an XSL formatting objects

+						(XSL-FO) document. This document will then be

+						transformed into a PDF. In order to generate an

+						XSL-FO document, you need to use the following

+						stylesheet:

+						<emphasis>fo/docbook.xsl</emphasis>.

+						<xref linkend="xslfo-transformation" />

+						shows a sample transformation configuration used

+						to generate an XSL-FO document from book.xml.

+					</para>

+					<figure id="xslfo-transformation">

+						<title>Sample XSL-FO Transformation Configuration for book.xml</title>

+						<mediaobject>

+							<imageobject>

+								<imagedata width="692" depth="517" fileref="images/xsl-fo.png"

+									format="PNG" />

+							</imageobject>

+						</mediaobject>

+					</figure>

+					<para>

+						Step two is to use a Formatting Objects

+						Processor (FOP) to transform your XSL-FO

+						document into a PDF. One of the more popular

+						open source FOPs is the

+						<ulink 

+							url="http://xmlgraphics.apache.org/fop/">

+							Apache FOP

+						</ulink>

+						. We'll use a third-party

+						<ulink 

+							url="http://www.ahmadsoft.org/fopbridge.html">

+							plug-in from Ahmadsoft

+						</ulink>

+						that integrates Apache FOP into Eclipse. After

+						installing this plug-in, all that you need to do

+						to render the XSL-FO document is run the FOP

+						transformation.

+						<xref linkend="pdf-transformation" />

+						shows an example of running the FOP

+						transformation.

+					</para>

+					<figure id="pdf-transformation">

+						<title>Sample FOP Transformation</title>

+						<mediaobject>

+							<imageobject>

+								<imagedata width="430" depth="447" fileref="images/fop.png"

+									format="PNG" />

+							</imageobject>

+						</mediaobject>

+					</figure>

+					<note>

+						<para>

+							The example includes a sample Ant

+							<ulink url="files/pdf/build.xml">

+								file

+							</ulink>

+							that performs the same transformation as

+							running the FOP transformation using the

+							<ulink 

+								url="http://www.ahmadsoft.org/fopbridge.html">

+								plug-in from Ahmadsoft

+							</ulink>. An Ant script is a popular method of

+							performing the publishing stage, and this

+							example should give you a good starting

+							point if you'd prefer to go this route. The

+							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.

+						</para>

+					</note>

+					<para>

+						As before, a Flash movie that shows the

+						transformation is available

+						<ulink  url="files/DocBook-PDF.htm">here</ulink>

+						.

+					</para>

+

+				</section>

+

+				<section>

+					<title>Eclipse Infocenter</title>

+

+					<para>

+						In our opinion, one of the coolest features of

+						the DocBook and DITA projects is the generation

+						of an Eclipse help plug-in (information center) from

+						your source XML file. In order to perform this

+						transformation in DocBook, you need to specify a

+						few parameters and use the following style sheet:

+						<emphasis>eclipse/eclipse.xsl</emphasis>.

+						<xref linkend="eclipse-transformation" />

+						shows a sample transformation configuration

+						along with the correct parameters. To perform

+						this transformation using a DITA source file, use

+						the

+						<emphasis>ant/sample_eclipsehelp.xml</emphasis>

+						Ant file.

+					</para>

+					<figure id="eclipse-transformation">

+						<title>Sample Eclipse Infocenter Transformation Configuration</title>

+						<mediaobject>

+							<imageobject>

+								<imagedata width="803" depth="388" fileref="images/eclipse.png"

+									format="PNG" />

+							</imageobject>

+						</mediaobject>

+					</figure>

+					<tip>

+						<para>

+							The complete list of DocBook XSL parameters

+							for the Eclipse Infocenter transformation

+							is located

+							<ulink 

+								url="http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html">

+								here

+							</ulink>

+							.

+						</para>

+					</tip>

+					<para>

+						The Flash movie that shows the Eclipse

+						Infocenter DocBook transformation can be found

+						<ulink  url="files/DocBook-InfoCenter.htm">

+							here

+						</ulink>

+						.

+					</para>

+				</section>

+			</section>

+			

+			

+			

+			<section>

+				<title>Current Limitations</title>

+				<para>

+					Although we have shown that Eclipse's current XML

+					authoring support is pretty good, there are a two

+					noteworthy limitations.

+				</para>

+				<para>

+					The first is grammar and spell-checking. While these

+					tools are commonplace in word-processing software,

+					they do not yet exist for WTP's XML editor.

+				</para>

+				<para>

+					The second is a WYSIWYG editor for XML documentation

+					formats such as DITA and DocBook (or a preview

+					window). The lack of a sophisticated editor or a way

+					to preview what you've written requires that you

+					stop authoring and transform your document in order

+					to view the results of your changes.

+				</para>

+				<para>

+					While neither of these limitations has been a show-stopper 

+					in our authoring process, our hope is that as

+					Eclipse is recognized as an integrated documentation

+					development environment, these limitations will be

+					addressed.

+				</para>

+			</section>

+		</section>

+	</section>

+

+	<section>

+		<title>Summary</title>

+

+		<para>

+			In this article, we introduced the technical documentation

+			process and showed that technical documentation development

+			is possible in Eclipse. We worked through examples showing

+			how to use Eclipse to aid the different phases of the

+			technical documentation process. Although there is still a

+			lot of room for improvement in this area we hope we've

+			convinced you that technical documentation in Eclipse is

+			both possible and already viable. It's now up to you in

+			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.

+		</para>

+

+	</section>

+

+	<section>

+		<title>Acknowledgements</title>

+		<para>

+			We'd like to thank:

+			<itemizedlist>

+				<listitem>

+					<simpara>

+						Sushma Patel and Anne James for correcting our horrible

+						grammar.

+					</simpara>

+				</listitem>

+			</itemizedlist>

+			<itemizedlist>

+				<listitem>

+					<simpara>

+						Don Day and Michael Priestly for their DITA

+						expertise.

+					</simpara>

+				</listitem>

+			</itemizedlist>

+		</para>

+	</section>

+

+	<section>

+		<title>About the Authors</title>

+

+		<para>

+			Chris Aniszczyk is a software developer at the IBM Austin

+			Labs and works in Tivoli Security. He's a developer on the

+			<ulink url="http://www.gentoo.org">Gentoo Linux</ulink>

+			distribution and also a committer on the

+			<ulink url="http://www.eclipse.org/emft">

+				Eclipse Modeling Framework Technology (EMFT)

+			</ulink>

+			project.

+		</para>

+		<para>

+			Lawrence Mandel, a software developer at the IBM Toronto

+			Laboratory, is the documentation lead and a

+			committer for the Eclipse

+			<ulink url="http://www.eclipse.org/webtools">

+				Web Tools Platform (WTP)

+			</ulink>

+			project. He is also authoring a book with Arthur Ryman and

+			Naci Dai about Java Web application development with

+			Eclipse.

+		</para>

+	</section>

+

+	<bibliography>

+		<title>Resources</title>

+		<biblioentry id="docbookxsl">

+			<bibliosource>

+				<ulink  url="http://docbook.sourceforge.net/projects/xsl/">

+					DocBook XSL Style Sheets

+				</ulink>

+			</bibliosource>

+		</biblioentry>

+		<biblioentry id="dita">

+			<bibliosource>

+				<ulink  url="http://dita-ot.sourceforge.net/">

+					DITA Open Toolkit

+				</ulink>

+			</bibliosource>

+		</biblioentry>

+		<biblioentry id="toolchain">

+			<bibliosource>

+				<ulink  url="http://en.wikipedia.org/wiki/Toolchain">

+					Wikipedia: Toolchain

+				</ulink>

+			</bibliosource>

+		</biblioentry>

+		<biblioentry id="vex">

+			<bibliosource>

+				<ulink  url="http://vex.sf.net">

+					Vex

+				</ulink>

+			</bibliosource>

+		</biblioentry>

+		<biblioentry id="openoffice">

+			<bibliosource>

+				<ulink  url="http://www.openoffice.org">

+					OpenOffice

+				</ulink>

+			</bibliosource>

+		</biblioentry>

+		<biblioentry id="subversion">

+			<bibliosource>

+				<ulink  url="http://subversion.tigris.org/">

+					Subversion

+				</ulink>

+			</bibliosource>

+		</biblioentry>

+	</bibliography>

+

+	<appendix>

+		<title>Appendix</title>

+

+		<para>

+			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

+			reviews a couple of other editors out there for technical

+			documentation in case WTP's XML editor doesn't suit your fancy.

+		</para>

+

+		<section>

+			<title>The Article</title>

+

+			<para>

+				This article was written in DocBook using WTP's XML

+				editor. To transform the article into the correct format

+				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

+				<ulink url="files/article.xsl">here</ulink>.

+				<note>

+					<para>

+						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 <ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=115473">

+						#115473</ulink>. We will be contributing our stylesheets for DocBook and

+						DITA to this bug.

+					</para>

+				</note>

+			</para>

+		</section>

+		<section>

+			<title>Editors</title>

+

+			<para>

+				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

+				content creator (think EMACS versus VI). We decided to

+				use the WTP XML editor as the editor for this article

+				because of our familiarity with it and because both of us like working

+				within Eclipse. However, we realize that there are other

+				options for creating and editing content so we'll

+				discuss of a couple of those options in the following

+				sections.

+			</para>

+			<section>

+				<title>Vex</title>

+

+				<para>

+					Vex

+					<xref linkend="vex" />

+					is an open source project that lets you edit XML

+					files visually. Vex uses standard Document Type

+					Definition (DTD) files to define document types and

+					Cascading Style Sheets (CSS) to define document

+					layout. In essence, Vex only requires that you have

+					knowledge of CSS and DTDs in order to contribute a

+					visual editor for XML files. The Vex editor can be

+					seen in

+					<xref linkend="vex-editor" />

+					.

+					<figure id="vex-editor">

+						<title>Vex DocBook editor screenshot</title>

+						<mediaobject>

+							<imageobject>

+								<imagedata width="652" depth="498" fileref="images/vex.png"

+									format="PNG" />

+							</imageobject>

+						</mediaobject>

+					</figure>

+

+				</para>

+

+			</section>

+

+			<section>

+				<title>OpenOffice</title>

+

+				<para>

+					OpenOffice

+					<xref linkend="openoffice" />

+					is a multi-platform open source office suite that is

+					capable of visually editing DocBook and various

+					other formats. OpenOffice is a popular editing

+					choice because of its ability to open multiple

+					document formats, including Microsoft Word, and then

+					export the documents to DocBook.

+				</para>

+				<para>

+					OpenOffice doesn't fully support DocBook. An

+					updated list of what portions of DocBook OpenOffice

+					supports can be found on the OpenOffice site

+					<ulink 

+						url="http://xml.openoffice.org/xmerge/docbook/DocBookTags.html">

+						here

+					</ulink>

+					. The site also contains a getting started

+					<ulink 

+						url="http://xml.openoffice.org/xmerge/docbook/UserGuide.html">

+						guide

+					</ulink>

+					that will get you started with DocBook in

+					OpenOffice.

+				</para>

+

+			</section>

+

+

+		</section>

+	</appendix>

+	

+</article>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/AuthoringWithEclipse.zip b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.zip
new file mode 100644
index 0000000..628f503
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/AuthoringWithEclipse.zip
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/AuthoringWithEclipse_Appendix.xml b/Article-Authoring-With-Eclipse/AuthoringWithEclipse_Appendix.xml
new file mode 100644
index 0000000..f3e23e3
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/AuthoringWithEclipse_Appendix.xml
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<appendix xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.docbook.org/xsd/4.5/docbook.xsd">
+   <title>Appendix</title>
+   <para> 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
+      reviews a couple of other editors out there for technical documentation in case WTP's XML
+      editor doesn't suit your fancy.</para>
+   <section>
+      <title>The Article</title>
+      <para>
+         This article was written in DocBook using Web Standard Tools XML editor. To transform the article into
+         the correct format 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
+         <ulink url="files/article.xsl">here</ulink>
+         .
+         <note>
+            <para>
+               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
+               <ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=115473"> #115473</ulink>
+               . We will be contributing our stylesheets for DocBook and DITA to this bug.
+            </para>
+         </note>
+      </para>
+   </section>
+   <section>
+      <title>Editors</title>
+      <para> 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 content creator
+         (think EMACS versus VI). We decided to use the WTP XML editor as the editor for this
+         article because of our familiarity with it and because both of us like working within
+         Eclipse. However, we realize that there are other options for creating and editing content
+         so we'll discuss of a couple of those options in the following sections.</para>
+      <section>
+         <title>Vex</title>
+         <para>
+            Vex
+            <xref linkend="vex" />
+            is an open source project that lets you edit XML files visually. Vex uses standard
+            Document Type Definition (DTD) files to define document types and Cascading Style Sheets
+            (CSS) to define document layout. In essence, Vex only requires that you have knowledge
+            of CSS and DTDs in order to contribute a visual editor for XML files. The Vex editor can
+            be seen in
+            <xref linkend="vex-editor" />
+            .
+            <figure id="vex-editor">
+               <title>Vex DocBook editor screenshot</title>
+               <mediaobject>
+                  <imageobject>
+                     <imagedata width="652" depth="498" fileref="images/vex.png" format="PNG" />
+                  </imageobject>
+               </mediaobject>
+            </figure>
+         </para>
+      </section>
+      <section>
+         <title>OpenOffice</title>
+         <para>
+            OpenOffice
+            <xref linkend="openoffice" />
+            is a multi-platform open source office suite that is capable of visually editing DocBook
+            and various other formats. OpenOffice is a popular editing choice because of its ability
+            to open multiple document formats, including Microsoft Word, and then export the
+            documents to DocBook.
+         </para>
+         <para>
+            OpenOffice doesn't fully support DocBook. An updated list of what portions of DocBook
+            OpenOffice supports can be found on the OpenOffice site
+            <ulink url="http://xml.openoffice.org/xmerge/docbook/DocBookTags.html"> here</ulink>
+            . The site also contains a getting started
+            <ulink url="http://xml.openoffice.org/xmerge/docbook/UserGuide.html"> guide</ulink>
+            that will get you started with DocBook in OpenOffice.
+         </para>
+      </section>
+   </section>
+</appendix>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/about.xml b/Article-Authoring-With-Eclipse/about.xml
index 03ee834..47ec6aa 100644
--- a/Article-Authoring-With-Eclipse/about.xml
+++ b/Article-Authoring-With-Eclipse/about.xml
@@ -1,23 +1,23 @@
-<article link="AuthoringWithEclipse.html">
-	<title>Authoring with Eclipse</title>
-	<date>December 14, 2005</date>
-	
-	<author>
-		<name>Chris Aniszczyk</name>
-		<company>IBM</company>
-	</author>
-	<author>
-		<name>Lawrence Mandel</name>
-		<company>IBM</company>
-	</author>
-	<description>
-		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.
-	</description>
+<article link="AuthoringWithEclipse.html">

+	<title>Authoring with Eclipse</title>

+	<date>December 14, 2005</date>

+	<category>general</category>

+	<author>

+		<name>Chris Aniszczyk</name>

+		<company>IBM</company>

+	</author>

+	<author>

+		<name>Lawrence Mandel</name>

+		<company>IBM</company>

+	</author>

+	<description>

+		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.

+	</description>

 </article>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/build.xml b/Article-Authoring-With-Eclipse/build.xml
index 04d8318..bcb8d70 100644
--- a/Article-Authoring-With-Eclipse/build.xml
+++ b/Article-Authoring-With-Eclipse/build.xml
@@ -1,64 +1,164 @@
-<!--
-        Build script for Eclipse.org Articles
-        $Id: build.xml,v 1.2 2007/05/01 18:03:46 wbeaton Exp $
-        author: Chris Aniszczyk <zx@us.ibm.com>
-        author: Lawrence Mandel <lmandel@ca.ibm.com>
--->
-
-<project name="eclipse.org article (docbook)" default="build-doc" basedir=".">
-	
-	<!-- ========== Properties: User Defined Options ========================= -->	
-	
-	<property name="article.source.name" value="article"/>
-	<property name="article.dest.name" value="index"/>
-	<property name="article.stylesheet" value="../article.xsl"/>
-	
-	<property name="dest.dir" value="."/>
-	<property name="download.dir" value="${user.home}${file.separator}downloads"/>
-	
-	<property name="docbook.dir" value="${download.dir}${file.separator}docbook-xsl-1.71.1"/>
-	<property name="docbookxsl.url" value="http://downloads.sourceforge.net/docbook/docbook-xsl-1.71.1.zip"/>
-	
-	<property name="build.home" value="build"/>
-		
-	<!-- ========== Targets =================================================== -->	
-		
-	<target name="init">
-		<mkdir dir="${download.dir}"/>
-	</target>
-		
-	<target name="build-doc" depends="init, get-docbook-xsl">
-		<echo>Building Article...</echo>
-		<antcall target="docbook2html"/>
-		<antcall target="docbook2pdf"/>
-		<antcall target="dist"/>
-	</target>
-		
-	<target name="check-docbook">
-		<available file="${download.dir}${file.separator}docbook.zip" property="hasDocbook"/>
-	</target>
-			
-	<target name="get-docbook-xsl" description="Downloads docbook xsl" depends="init, check-docbook" unless="hasDocbook">
-		<echo>Downloading DocBook XSL...</echo>
-		<get dest="${download.dir}${file.separator}docbook.zip" src="${docbookxsl.url}"/>
-		<unzip src="${download.dir}${file.separator}docbook.zip" dest="${download.dir}"/>
-	</target>
-	
-	<target name="docbook2html" depends="get-docbook-xsl">
-		<echo>Converting article to HTML...</echo>
-		<delete file="${dest.dir}${file.separator}${article.name}.html"/>
-		<xslt in="${article.source.name}.xml" extension="xml" out="${dest.dir}${file.separator}${article.dest.name}.html" style="${article.stylesheet}">
-			<xmlcatalog>
-				<entity 
-					publicId="docbook.xsl"
-				    location="${docbook.dir}${file.separator}html${file.separator}docbook.xsl"/>
-			</xmlcatalog>
-			<param name="header.rule" expression="1" />
-			<param name="admon.graphics.extension" expression=".gif"/>
-			<param name="admon.textlabel" expression="0"/>
-			<param name="ulink.target" expression="_new"/>
-		</xslt>
-	</target>
-	
-
+<!--

+        Build script for Eclipse.org Articles

+        $Id: build.xml,v 1.3 2008/09/09 02:24:03 wbeaton Exp $

+        author: Chris Aniszczyk <zx@us.ibm.com>

+        author: Lawrence Mandel <lmandel@ca.ibm.com>

+-->

+

+<project name="eclipse.org article (docbook)" default="build-doc" basedir=".">

+	

+	<!-- ========== Properties: User Defined Options ========================= -->	

+	

+	<property name="article.name" value="AuthoringWithEclipse"/>

+	<property name="article.stylesheet" value="../article.xsl"/>

+	

+	<property name="dest.dir" value="."/>

+	<property name="dest.name" value="index"/>

+	<property name="download.dir" value="${java.io.tmpdir}${file.separator}downloads"/>

+	

+	<property name="docbook.version" value="1.73.2" />

+	<property name="docbook.dir" value="${download.dir}${file.separator}docbook-xsl-${docbook.version}"/>

+	<property name="docbookxsl.url" value="http://internap.dl.sourceforge.net/sourceforge/docbook/docbook-xsl-${docbook.version}.zip"/>

+	<property name="fop.dir" value="${download.dir}${file.separator}fop-0.20.5"/>

+	<property name="fop.url" value="http://archive.apache.org/dist/xmlgraphics/fop/binaries/fop-0.20.5-bin.zip"/>

+	<property name="jai.dir" value="ENTER_JAI_DIRECTORY"/>

+	

+	<property name="build.home" value="build"/>

+		

+	<!-- ========== Macro Definition =================================================== -->	

+	

+    <macrodef name="docbook2pdf">

+        <attribute name="source"/>

+    	<attribute name="target"/>

+        <sequential>

+        	<taskdef name="fop" classname="org.apache.fop.tools.anttasks.Fop">

+        		<classpath>

+        			<pathelement location="${fop.dir}${file.separator}build${file.separator}fop.jar" />

+        			<pathelement location="${fop.dir}${file.separator}lib${file.separator}avalon-framework-cvs-20020806.jar" />

+        			<pathelement location="${fop.dir}${file.separator}lib${file.separator}batik.jar" />

+        			<pathelement location="${jai.dir}${file.separator}lib${file.separator}jai_core.jar" />

+        			<pathelement location="${jai.dir}${file.separator}lib${file.separator}jai_codec.jar" />

+        		</classpath>

+        	</taskdef>

+        	<fop 

+        		format="application/pdf" 

+        		fofile="@{source}" 

+        		outfile="@{target}"

+        		messagelevel="info"/>

+        </sequential>

+    </macrodef>

+	

+	<!-- ========== Targets =================================================== -->	

+		

+	<target name="init">

+		<mkdir dir="${download.dir}"/>

+		

+		<available file="${jai.dir}" property="jai.exists"/>

+		<antcall target="notifyJAI"/>

+	</target>

+	

+	<target name="initpdf" depends="init">

+			<available file="${jai.dir}" property="jai.exists"/>

+			<antcall target="notifyJAI"/>

+		</target>

+	

+	<target name="notifyJAI" unless="jai.exists">

+		<echo message="The Java Advanced Imaging (JAI) library is not available."/>

+		<echo message="JAI is required if you want to use PNG images in your article."/>

+		<echo message="You can download JAI from http://java.sun.com/products/java-media/jai/downloads/download-1_1_2_01.html."/>

+		<echo message="Specify the JAI installation directory to the article build by providing the parameter jai.dir to this build script."/>

+	</target>

+	

+	<target name="build-doc" depends="init, get-docbook-xsl">

+			<echo>Building Article...</echo>

+			<antcall target="docbook2html"/>

+			<antcall target="dist"/>

+		</target>

+	

+	<target name="build-doc-pdf" depends="initpdf, get-docbook-xsl, get-fop">

+		<echo>Building Article...</echo>

+		<antcall target="docbook2html"/>

+		<antcall target="docbook2pdf"/>

+		<antcall target="dist"/>

+	</target>

+		

+	<target name="check-docbook">

+		<available file="${download.dir}${file.separator}docbook.zip" property="hasDocbook"/>

+	</target>

+	

+	<target name="check-fop">

+		<available file="${download.dir}${file.separator}fop.zip" property="hasFOP"/>

+	</target>

+		

+	<target name="get-docbook-xsl" description="Downloads docbook xsl" depends="check-docbook" unless="hasDocbook">

+		<echo>Downloading DocBook XSL...</echo>

+		<get dest="${download.dir}${file.separator}docbook.zip" src="${docbookxsl.url}"/>

+		<unzip src="${download.dir}${file.separator}docbook.zip" dest="${download.dir}"/>

+	</target>

+	

+	<target name="get-fop" description="Downloads FOP" depends="check-fop" unless="hasFOP">

+		<echo>Downloading FOP...</echo>

+		<get dest="${download.dir}${file.separator}fop.zip" src="${fop.url}"/>

+		<unzip src="${download.dir}${file.separator}fop.zip" dest="${download.dir}"/>

+	</target>

+	

+	<target name="docbook2html">

+		<echo>Converting article to HTML...</echo>

+		<delete file="${dest.dir}${file.separator}${dest.name}.html"/>

+		<xslt in="${article.name}.xml" extension="xml" out="${dest.dir}${file.separator}${dest.name}.html" style="${article.stylesheet}">

+			<factory name="org.apache.xalan.processor.TransformerFactoryImpl">

+				<attribute name="http://xml.apache.org/xalan/features/optimize" value="true"/>

+			</factory>

+			<xmlcatalog>

+				<entity 

+					publicId="docbook.xsl"

+					location="${docbook.dir}${file.separator}html${file.separator}docbook.xsl"/>

+			</xmlcatalog>

+			<param name="header.rule" expression="1" />

+			<param name="admon.graphics.extension" expression=".gif"/>

+			<param name="admon.textlabel" expression="0"/>

+			<param name="ulink.target" expression="_new"/>

+		</xslt>

+	</target>

+	

+	<target name="docbook2pdf">

+		<echo>Converting article to PDF...</echo>

+

+		<delete file="${dest.dir}${file.separator}${article.name}.pdf"/>

+		<delete file="${dest.dir}${file.separator}${article.name}.fo"/>

+		<xslt in="${article.name}.xml" extension="xml" out="${dest.dir}${file.separator}${article.name}.fo" style="${docbook.dir}${file.separator}fo${file.separator}docbook.xsl">

+			<factory name="org.apache.xalan.processor.TransformerFactoryImpl">

+				<attribute name="http://xml.apache.org/xalan/features/optimize" value="true"/>

+			</factory>

+			<xmlcatalog>

+				<entity 

+					publicId="docbook.xsl"

+					location="${docbook.dir}${file.separator}fo${file.separator}docbook.xsl"/>

+			</xmlcatalog>

+			<param name="generate.toc" expression="book toc" />

+			<param name="show.comments" expression="0" />

+			<param name="header.rule" expression="1" />

+			<param name="admon.graphics.extension" expression=".gif"/>

+			<param name="admon.textlabel" expression="0"/>

+			<param name="admon.graphics" expression="1"/>

+		</xslt>

+		

+		<docbook2pdf 

+			source="${dest.dir}${file.separator}${article.name}.fo"

+			target="${dest.dir}${file.separator}${article.name}.pdf"/>

+		

+		<!-- Remove the resulting formatting object. This object isn't necessary in the

+		     result of this build. -->

+		<delete file="${dest.dir}${file.separator}${article.name}.fo"/>

+	</target>

+	

+	<target name="dist">

+		<echo>Building article zip file...</echo>

+		<delete file="${dest.dir}${file.separator}${article.name}.zip"/>

+		<zip basedir="${dest.dir}" destfile="${dest.dir}${file.separator}${article.name}.zip"

+			 excludes="article.xsl, build.xml, ${article.name}.fo, ${article.name}.zip, .project">

+		</zip>

+		<echo>If you're done with your article, please post the zip file on the related bugzilla entry.</echo>

+	</target>

+

 </project>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/default_style.css b/Article-Authoring-With-Eclipse/default_style.css
index 5c03945..44fa78e 100644
--- a/Article-Authoring-With-Eclipse/default_style.css
+++ b/Article-Authoring-With-Eclipse/default_style.css
@@ -1,12 +1,12 @@
-p, table, td, th {  font-family: arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: arial,helvetica,geneva; font-size: 10px}
-h3 {  font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}
-body {  font-family: arial, helvetica, geneva; font-size: 10pt; clip:   rect(   ); margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}
+p, table, td, th {  font-family: arial, helvetica, geneva; font-size: 10pt}

+pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}

+h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}

+code {  font-family: "Courier New", Courier, mono; font-size: 10pt}

+sup {  font-family: arial,helvetica,geneva; font-size: 10px}

+h3 {  font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}

+li {  font-family: arial, helvetica, geneva; font-size: 10pt}

+h1 {  font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}

+body {  font-family: arial, helvetica, geneva; font-size: 10pt; clip:   rect(   ); margin-top: 5mm; margin-left: 3mm}

+.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}

+.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}

 .corner { color: #FFFFFF; font-weight: bold; }
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/files/AuthoringWithEclipse.xml b/Article-Authoring-With-Eclipse/files/AuthoringWithEclipse.xml
new file mode 100644
index 0000000..6a16467
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/files/AuthoringWithEclipse.xml
@@ -0,0 +1,637 @@
+<?xml version="1.0" encoding="utf-8"?>

+<article id="article" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

+   xsi:noNamespaceSchemaLocation="http://www.docbook.org/xsd/4.5/docbook.xsd">

+   <articleinfo>

+      <title>DocBook Authoring with Eclipse</title>

+      <revhistory>

+         <revision>

+            <revnumber>1.0</revnumber>

+            <date>June 20, 2008</date>

+            <authorinitials>DAC</authorinitials>

+            <revremark>Updated to DocBook 4.5, Web Standard Tools 3.0, and XSL Tooling 0.5M8

+            </revremark>

+         </revision>

+      </revhistory>

+      <authorgroup>

+         <author>

+            <firstname>David</firstname>

+            <surname>Carver</surname>

+            <affiliation>

+               <jobtitle>XML Data Architect</jobtitle>

+               <orgname>Standards for Technology in Automotive Retail</orgname>

+               <address>

+                  <email>dcarver@starstandard.org</email>

+               </address>

+            </affiliation>

+         </author>

+      </authorgroup>

+      <copyright>

+         <year>2008</year>

+         <holder> Standards for Technology in Automotive Retail. All rights reserved.</holder>

+      </copyright>

+      <abstract>

+         <para>

+            Eclipse is not know for it's ability to write documentation, but it is something that

+            every programmer eventually has to do. In today's world it is not uncommon to have to

+            support not only print media, but also online content as well. This article will take a

+            look at the advances of eclipse as an authoring environment. It will revisit concepts

+            original discussed in the

+            <ulink

+            url="http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html">"Authoring with Eclipse"</ulink>

+            article, published in December 2005.

+         </para>

+      </abstract>

+      <legalnotice>

+         <para> Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the

+            United States, other countries, or both.</para>

+         <para> Linux is a trademark of Linus Torvalds in the United States, other countries, or

+            both.</para>

+         <para> Microsoft is a trademark of Microsoft Corporation in the United States, other

+            countries, or both.</para>

+         <para> UNIX is a registered trademark of The Open Group in the United States and other

+            countries.</para>

+         <para> Other company, product, or service names may be trademarks or service marks of

+            others.</para>

+      </legalnotice>

+   </articleinfo>

+   <section>

+      <title>Environment</title>

+      <note>

+         <para>

+            The examples in this article were built and tested with:

+            <itemizedlist>

+               <listitem>

+                  <para>

+                     <ulink url="http://www.eclipse.org/download">Eclipse 3.4</ulink>

+                  </para>

+               </listitem>

+               <listitem>

+                  <para>

+                     <ulink url="http://www.eclipse.org/webtools"> Eclipse Web Tools Platform (WTP) 3.0</ulink>

+                  </para>

+               </listitem>

+               <listitem>

+                  <para>

+                     <ulink url="http://www.eclipse.org/webtools/incubator"> XSL Tooling 0.5M8 - Incubator</ulink>

+                  </para>

+               </listitem>

+               <listitem>

+                  <para>

+                     <ulink url="http://www.docbook.org">Docbook 4.5</ulink>

+                  </para>

+               </listitem>

+               <listitem>

+                  <para>

+                     <ulink url="http://docbook.sourceforge.net/">The DocBook XSL stylesheets from the DocBook Project

+                     </ulink>

+                  </para>

+               </listitem>

+            </itemizedlist>

+         </para>

+      </note>

+   </section>

+   <section>

+      <title>Preface</title>

+      <para>

+         This article is a revisiting of the original

+         <ulink

+         url="http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html">"Authoring With Eclipse"</ulink>

+         article by Chris Aniszczyk and Lawrence Mandel. The article revisits many of the concepts

+         discussed in the original article, and expands on them where it is necessary. Much has

+         changed since the original article, but much of the information is still relevant to

+         authoring with eclipse today.

+      </para>

+   </section>

+   <section>

+      <title>Introduction</title>

+      <para> Writing documentation is something that almost any programmer or architect is

+         eventually going to have to do. It's not a job that most enjoy, and the fact that the

+         documentation usually has to be available in multiple formats at the same time, makes the

+         job of creating the documentation that much less enjoyable. However, all is not lost. There

+         are many ways to produce content that can be written once and documented in many formats.

+         In the sections that follow we will discuss one of these options, DocBook, and how you can

+         use existing eclipse projects and open source plugins to create and authoring system. This

+         article in fact is entirely written in DocBook and leverages the tools discussed.</para>

+   </section>

+   <section>

+      <title>Technical Documentation</title>

+      <para>According to Chris and Lawrence, "In the open source world, technical

+         documentation is primarily accomplished using two popular formats: DocBook and the Darwin

+         Information Typing Architecture (DITA)." Both of these formats leverage XML. They separate

+         the content from the presentation. Unlike HTML which mixes the two together, and you don't

+         have an easy time of separating them. The advantage to DocBook and DITA formats is that it

+         frees the author to concentrate on the content they are entering and not how it will

+         necessarily look. This is necessary because the same content can be targeted to multiple

+         formats, each with its own unique presentation and requirements. It is not uncommon to have

+         DocBook content appear in PDF, Presentation Slides, HTML, RTF, Man, and many more formats.

+      </para>

+      <para> DocBook itself has it's beginnings with SGML, the precursor to XML. It is widely used

+         in the publishing industry, and the O'Reily publishing house use DocBook for all it's

+         books.</para>

+      <tip>

+         <para>

+            Norman Walsh, has written a book called

+            <ulink url="http://www.docbook.org/tdg/en/html/docbook.html">DocBook: The Definitive Guide</ulink>

+            . The book is available on line as well as at many book resellers. Anything and

+            everything about the DocBook markup can be found in the book.

+         </para>

+      </tip>

+      <para> Writing an article or a book in XML is no different than writing most any other

+         application. You can break the process down into several stages. Chris and Lawrence

+         original had these in the following steps:</para>

+      <itemizedlist>

+         <listitem>

+            <para> Creation - The process of adding your content to the file. This includes such

+               meta data as authors, editors, revision history, chapters, sections, figures, tables,

+               etc.</para>

+         </listitem>

+         <listitem>

+            <para> Review - The process of fixing the inevitable grammar and content mistakes that

+               tend to creep into the document. Regardless of how well the author tries, some no

+               excuse error is going to creep into the document. The nice thing about writing is

+               that during this process one is not concerned as much about how it looks, just that

+               the content is correct.</para>

+         </listitem>

+         <listitem>

+            <para> Publication - The final step is actually publish the document. This is either

+               creating the PDF, the HTML, or the eclipse Help format files. This is where the

+               formatting is reviewed, and for the most part with the help of the DocBook Project's

+               XSL Stylesheets very little has to be done to get a professional looking publication.

+               If errors are found, then repeat the Review process, and republish.</para>

+         </listitem>

+      </itemizedlist>

+      <section>

+         <title>Advantages of an XML format</title>

+         <para> Microsoft Word has the ability to create a master document from multiple word

+            documents. However, anybody that has tried to do this, knows that the process is more

+            brittle than it needs to be. It should be a simple as saying include these three files,

+            and generate me out one complete book that contains everything. With DocBook and XML it

+            is that simple if you leverage a little known specification called XInclude.</para>

+         <section>

+            <title>XInclude</title>

+            <para>

+               XInlcude allows you create the Modularity that Chris and Lawrence original talked

+               about. An example of an XInclude is shown in

+               <xref linkend="Xinclude_Example" />

+            </para>

+            <example id="Xinclude_Example">

+               <title>XInclude</title>

+               <programlisting><![CDATA[

+<book id='Book1' xmlns:xi="http://www.w3.org/2001/XInclude">

+  <xi:include href="Introduction.xml"/>

+  <xi:include href="WorkbenchLayout.xml"/>

+<book>

+]]>

+               </programlisting>

+            </example>

+            <note>

+               <para>

+                    More information about XInclude can be found in <xref linkend="XSL_Tooling"/>.

+                </para>

+            </note>

+            <para>

+            

+            </para>

+         </section>

+         <section>

+            <title>Version Control</title>

+            <para> Leveraging Eclipse's built-in version control support with CVS or adding a open

+               source or third party plugin for another version control system, makes maintaining

+               and working on the documentation as convenient as working on any source code for a

+               program. The same comparison and merging abilities that are used with source code for

+               programs can be leveraged for the authoring process as well. Compare this to trying

+               to work with formats that are stored in a binary format and the speed advantage

+               becomes clear pretty quickly. When dealing with a binary formatted file, typically a

+               locking mechanism has to be implemented. Working with DocBook since it is a text

+               format, allows one to take advantage of agile development practices as Continuous

+               Integration and automated builds. Documentation doesn't have to become a thing that

+               is put to the end. It should become a part of the standard build process.</para>

+         </section>

+         <section>

+            <title>Formatting</title>

+            <para> As stated earlier. The advantage that an XML format has is that it allows

+               presentation and content to be separated. The formatting of the document is

+               independent of the content. One of the most time consuming parts of creating

+               documentation is making sure the formatting is the same. Traditionally if you move

+               sections or cut and paste content from another source, it messes up the formatting of

+               the document. With DocBook you don't run into this issue, as the formatting is

+               controlled during the publication phase. Thus freeing up time that the author would

+               have to spend trying to make the document legible, to make sure that they have the

+               necessary content correct.</para>

+         </section>

+         <section>

+            <title>One Source, Multiple Targets</title>

+            <para> DocBook, allows for one source content to be generated into multiple formats.

+               Typically DocBook is published in PDF, but it is also widely used for web pages,

+               multi-sectioned HTML pages, Tex, and RTF formats as well. The author doesn't need to

+               worry about any of these formats or how it will necessarily look as that is taken

+               care of by the publishing process. Typically with an XSL stylesheet that already

+               contains the necessary formatting information.</para>

+         </section>

+      </section>

+   </section>

+   <section>

+      <title>Examples</title>

+      <para>

+         To show the authoring tool chain in Eclipse, this article will use the DocBook file that

+         was used to write this article. The XML version of the document can be seen

+         <ulink url="AuthoringWithEclipse.xml">here</ulink>

+      </para>

+      <section>

+         <title>The Right Tool for the Right Job.</title>

+         <para> In order to write an article or a book with DocBook, one needs an editor. Preferably

+            one that understands the XML dialect and it's support tools. The eclipse Web Standard

+            Tools project comes with the necessary tools that are needed. The XML editing support

+            provides the following functionality:</para>

+         <itemizedlist>

+            <listitem>

+               <para> Validation - the ability to check for syntax errors against a specified

+                  grammar. A grammar in this case can be either a DTD or XML Schema for the XML that

+                  is being edited. The XML editor also contains as you type validation to always

+                  keep your XML well formed and valid according the grammar provided.</para>

+            </listitem>

+            <listitem>

+               <para> Syntax Coloring - Working with XML is much easier of the tags can be easily

+                  separated from the content.</para>

+            </listitem>

+            <listitem>

+               <para> Content Assistance - If a grammar is detected for the XML file that has been

+                  loaded, then content assistance is available for the tags and attributes. This is

+                  activated using CTRL+SPACE. Also any templates that may be available from the XML

+                  templates preference page will be displayed as well.</para>

+            </listitem>

+         </itemizedlist>

+         <para> The XML editor provided by Web Standard Tools is just the first tool that you will

+            need, but it will be the one that is used the most. The next will be the DocBook XSL

+            stylesheets provided by the DocBook Project. This is is a set of XSL stylesheets that

+            can transform the DocBook files into something that is actually readable. Output formats

+            include HTML, Tex, RTF, and even PDF via XSL-FO.</para>

+         <para> The examples that are shown here are all built using tools that are available at

+            eclipse. Only when we get to the PDF publication do we need to leverage a plugin that

+            isn't available from eclipse directly, but is available as free software. More when PDF

+            generation is covered later in the article.</para>

+         <section>

+            <title>Creation and Review</title>

+            <note>

+               <para> The following section is taken primarily from the original article. Some

+                  updating has been done to update the content.</para>

+            </note>

+            <para> Although creation and review are two separate parts of the technical

+               documentation process, the same tools are required and therefore will be discussed

+               together.</para>

+            <para>

+               As you may already know, the Eclipse project is composed of several top-level

+               projects including Eclipse itself (known as the Eclipse base) and the WTP project.

+               WTP adds many tools to the Eclipse base including an XML editor with graphical and

+               source representations of the content. Although the graphical editor is useful for

+               viewing the document, the source editor, shown in

+               <xref linkend="xml-source-editor" />

+               , is more useful when authoring in XML.

+            </para>

+            <figure id="xml-source-editor">

+               <title>The XML Source Editor</title>

+               <mediaobject>

+                  <imageobject>

+                     <imagedata fileref="images/xmlsourceeditor.gif" format="GIF" align="center" />

+                  </imageobject>

+               </mediaobject>

+            </figure>

+            <para> In addition to the features discussed previously, Web Standard Tools provides

+               additional XML functionality.</para>

+            <itemizedlist>

+               <listitem>

+                  <para>

+                     <emphasis>Outline View</emphasis>

+                     - Assists you in editing and viewing the content of your document.

+                  </para>

+               </listitem>

+               <listitem>

+                  <para>

+                     <emphasis>XML Catalog</emphasis>

+                     - Allows you to register Document Type Definitions (DTD) and XML Schema

+                     grammars associated with your document with your workspace so you can work with

+                     the benefits of validation while disconnected from the Internet.

+                  </para>

+               </listitem>

+            </itemizedlist>

+            <para> Aside from the benefits of the XML editor, working in Eclipse provides other

+               benefits. Eclipse includes integrated version control for CVS. There also exists

+               freely available plugins for Subversion as well. Integrated version control allows

+               you to check your changes into, and view others' changes in, your version control

+               system from within Eclipse. These tools are also useful for your reviewers, who, if

+               you give them permission, can add comments and suggestions to your document and check

+               their changes in. Giving your reviewers permission to make these changes allows you

+               to avoid the need to use e-mail or some other communication mechanism.</para>

+         </section>

+         <section id="XSL_Tooling">

+            <title>XSL Tooling</title>

+            <para>

+            Chris and Lawerence's original article used an open source plugin called Organevolt XSLT, to

+            provide the publication steps that are discussed later in the article.  However, since the

+            publication of the original article, eclipse now has it's own XSL Tooling project.   This is

+            currently incubating under the eclipse Web Tools Project, but it provides the same functionality

+            and more.

+         </para>

+            <para>

+            One such new features is the XML perspective as shown in <xref linkend="XML_Perspective" />

+         </para>

+            <figure id="XML_Perspective">

+               <title>XML Perspective</title>

+               <mediaobject>

+                  <imageobject>

+                     <imagedata align="center" fileref="images/XMLPerspective.png" />

+                  </imageobject>

+               </mediaobject>

+            </figure>

+            <para>

+            The XML perspective provides the basic views that are most important for

+            working with XML related content.   The XPath View allows the user to

+            run XPath Expressions against the data that is in the current XML based editor.

+            It show the xpath expression for the current location with in the editor.

+         </para>

+            <para>

+            In addition to the XML perspective XSL Tooling provides the following additional

+            features and functions.

+         </para>

+            <itemizedlist>

+               <listitem>

+                  <para>

+                    XSL Editor - an XSL 1.0 and XSL 2.0 grammar aware editor.   Providing

+                    content assistance for XSL, as well as XML namespaced content included

+                    within the XSL editor.   Content assistance is also available for XPath

+                    1.0 in select and test attributes.

+                </para>

+                  <para>

+                    XSL Debugging - Developing or working with XSL stylesheets requires the

+                    use of an debugger at times.  The XSL Tooling provides launch configurations

+                    and debugging support for the Xalan 2.7.1 processor.   Extension points

+                    are available for adopters to add additional processors for debugging and

+                    launching.

+                </para>

+                  <para>

+                    XSL File Wizards - Wizards are available for creating new XSL files. Templates

+                    can be provided for a variety of XSL patterns.

+                </para>

+                  <para>

+                    XPath and XSL Preference Settings - Additional configuration is available

+                    through the XSL and XPath prefernce pages.  Templates can be created as well

+                    as choosing the default parser to use during transformations.

+                </para>

+                  <para>

+                    XSL Launch Configurations - The user has the ability to setup launch

+                    configurations for transforming XSL.   ANT launch configurations are

+                    also supported for more complex scenarios.

+                </para>

+                  <para>

+                    XInclude ANT Task - An ant task is available that allows for the use of

+                    XInclude pre-processing of XML files.  XInclude allows for a way to include

+                    XML or text based content into XML file and merge the two files together.

+                    This is one way to provide the Modularity benefit that working with an

+                    XML format provides.

+                </para>

+               </listitem>

+            </itemizedlist>

+         </section>

+         <section>

+            <title>Publication</title>

+            <para>

+               The DocBook XSL

+               <xref linkend="docbookxsl" />

+               project offers numerous transformations, including HTML and PDF formats. The most

+               common transformation technique is to use an Ant file with the appropriate tasks for

+               the various transformations. In this article we use the XSL Tooling set of plugins to

+               simplify this task. XSL Tooling integrates into the familiar Eclipse launcher

+               framework. This integration allows you to select the style sheet and pass in

+               necessary parameters for the transformation.

+            </para>

+            <section>

+               <title>HTML</title>

+               <para> Of all the available transformations, transforming your document into HTML is

+                  the easiest to use. All that you need to do is create a proper transformation

+                  launch configuration and run the transformation. Specifically, you need to specify

+                  the correct style sheet:</para>

+               <itemizedlist>

+                  <listitem>

+                     <para>DocBook</para>

+                     <itemizedlist>

+                        <listitem>

+                           <para>html/docbook.xsl</para>

+                        </listitem>

+                     </itemizedlist>

+                  </listitem>

+               </itemizedlist>

+               <para>

+                  <xref linkend="html-transformation" />

+                  shows a sample transformation configuration that will transform our DocBook sample

+                  <ulink url="files/book.xml">document</ulink>

+                  into HTML.

+               </para>

+               <figure id="html-transformation">

+                  <title>Sample HTML Transformation Configuration for book.xml</title>

+                  <mediaobject>

+                     <imageobject>

+                        <imagedata align="center" width="741" depth="592" fileref="images/html.jpg"

+                           format="JPG" />

+                     </imageobject>

+                  </mediaobject>

+               </figure>

+               <tip>

+                  <para>

+                     You can augment the transformation by passing parameters to the style sheet.

+                     There's a full listing of DocBook XSL parameters that can be used to configure

+                     the transformation located

+                     <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/html/"> here</ulink>

+                     .

+                  </para>

+                  <para>

+                     Bob Stayton has also written

+                     <ulink url="http://www.sagehill.net/docbookxsl/">Docbook XSL: The Complete Guide</ulink>

+                     which is available on line and in print format. This book describes how to

+                     customize the DocBook stylesheets beyond those that you can do with the

+                     parameters. The XSL Tooling provides an XSL aware XML editor that can be used

+                     to help create and debug the stylesheets.

+                  </para>

+               </tip>

+               <para>

+                    In addition to setting up the Main tab for the stylesheet to use.  You may also want

+                    to change the output location and the processor that will be used.  By default the

+                    transformation output will be placed into the same location as the input file, with the

+                    extensions ".out.xml".

+               </para>

+            </section>

+            <section>

+               <title>PDF</title>

+               <para> Transforming a DocBook XML file to PDF format is more involved than the

+                  transformation to HTML but it is still possible using a style sheet. The

+                  difference lies in a task that must be performed before the actual transformation.

+                  So, the transformation from XML to PDF is a two-step process.</para>

+               <para>

+                  Step one is to generate an XSL formatting objects (XSL-FO) document. This document

+                  will then be transformed into a PDF. In order to generate an XSL-FO document, you

+                  need to use the following stylesheet:

+                  <emphasis>fo/docbook.xsl</emphasis>

+                  .

+                  <xref linkend="xslfo-transformation" />

+                  shows a sample transformation configuration used to generate an XSL-FO document

+                  from book.xml.

+               </para>

+               <figure id="xslfo-transformation">

+                  <title>Sample XSL-FO Transformation Configuration for book.xml</title>

+                  <mediaobject>

+                     <imageobject>

+                        <imagedata align="center" fileref="images/xsl-fo.png"

+                           format="PNG" />

+                     </imageobject>

+                  </mediaobject>

+               </figure>

+               <para>

+                  Step two is to use a Formatting Objects Processor (FOP) to transform your XSL-FO

+                  document into a PDF. One of the more popular open source FOPs is the

+                  <ulink url="http://xmlgraphics.apache.org/fop/"> Apache FOP</ulink>

+                  . We'll use a third-party

+                  <ulink url="http://www.ahmadsoft.org/fopbridge.html"> plug-in from Ahmadsoft</ulink>

+                  that integrates Apache FOP into Eclipse. After installing this plug-in, all that

+                  you need to do to render the XSL-FO document is run the FOP transformation.

+                  <xref linkend="pdf-transformation" />

+                  shows an example of running the FOP transformation.

+               </para>

+               <figure id="pdf-transformation">

+                  <title>Sample FOP Transformation</title>

+                  <mediaobject>

+                     <imageobject>

+                        <imagedata align="center" fileref="images/fop.png"

+                           format="PNG" />

+                     </imageobject>

+                  </mediaobject>

+               </figure>

+               <note>

+                  <para>

+                     The example includes a sample Ant

+                     <ulink url="files/pdf/build.xml"> file</ulink>

+                     that performs the same transformation as running the FOP transformation using

+                     the

+                     <ulink url="http://www.ahmadsoft.org/fopbridge.html"> plug-in from Ahmadsoft</ulink>

+                     . An Ant script is a popular method of performing the publishing stage, and

+                     this example should give you a good starting point if you'd prefer to go this

+                     route.

+                  </para>

+               </note>

+            </section>

+            <section>

+               <title>Eclipse Help</title>

+               <para>

+                  The DocBook Project includes a XSL stylesheet that can be used to create the 

+                  necessary files for the eclipse help system. In order to perform this transformation

+                  in DocBook, you need to specify a few parameters and use the following style sheet:

+                  <emphasis>eclipse/eclipse.xsl</emphasis>

+                  .

+                  <xref linkend="eclipse-transformation" />

+                  shows a sample transformation configuration along with the correct parameters.

+               </para>

+               <note>

+                   <para>

+                        The eclipse help stylesheet included with DocBook creates a plugin.xml

+                        and toc.xml file only.  In addition to the configuration information shown

+                        the xalan.jar extension included with DocBook is required as the transformation

+                        leverages the chunk.xsl file from the html stylesheet directory to output multiple

+                        html files, and build to the necessary toc.xml file.

+                   </para>

+               </note>

+               <figure id="eclipse-transformation">

+                  <title>Sample Eclipse Help Transformation Configuration</title>

+                  <mediaobject>

+                     <imageobject>

+                        <imagedata align="center" fileref="images/eclipse.png"

+                           format="PNG" />

+                     </imageobject>

+                  </mediaobject>

+               </figure>

+               <tip>

+                  <para>

+                     The complete list of DocBook XSL parameters for the Eclipse Infocenter

+                     transformation is located

+                     <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html"> here</ulink>

+                     .

+                  </para>

+               </tip>

+            </section>

+         </section>

+         <section>

+            <title>Prior Limitations</title>

+            <para> Chris and Lawrence's original article outline two short comings with eclipse as an authoring

+            environment.

+            </para>

+            <itemizedlist>

+               <listitem>

+                  <para>

+                        No Grammar and Spell Checking.

+                    </para>

+               </listitem>

+               <listitem>

+                  <para>

+                        No preview screen or WSYIWG editor for documentation.

+                    </para>

+               </listitem>

+            </itemizedlist>

+            <para>

+                The first limitation has been addressed since eclipse 3.3.  Eclipse includes a spell checker and 

+                the Web Standard Tools XML editor leverages this support.   Users may add their own custom dictionary or

+                add any of the freely available dictionaries available on the Internet. 

+            </para>

+            <para>

+                The second item may or may not be a limitation depending on the point of view.  The advantage of DocBook is

+                that it separates the content from the presentation.   Worrying about the presentation while creating the

+                content may not be the best thing to do.  The main reason is that how it is formatted is going to greatly

+                depend on the target platforms the documentation is intended.   DocBook authoring is not the same as

+                using a traditional word processor.  A different way of thinking of documentation needs to be approached.  The

+                formatting is not the critical piece, but it is the content of the document that matters the most.

+            </para>

+         </section>

+      </section>

+   </section>

+   <section>

+      <title>Summary</title>

+      <para> 

+        Since the original article was published, many advancements have been made with the XML support for eclipse.  The

+        editors are faster, their is better tooling support, and the docbook grammar it self has advanced.  However, the 

+        overall process that Chris and Lawrence had described is fundamentally unchanged three years later.  Eclipse is a

+        perfectly suitable authoring system for technical documentation.  

+      </para>

+   </section>

+   <section>

+      <title>Acknowledgments</title>

+      <itemizedlist>

+         <listitem>

+            <para> Chris Aniszczyk and Lawrence Mandel for their original article title,

+                  "Authoring With Eclipse".</para>

+         </listitem>

+      </itemizedlist>

+   </section>

+   <section>

+      <title>About the Author</title>

+      <para>

+         David Carver is an XML Data Architect for Standards for Technology in Automotive Retail. He

+         is also a committer on the

+         <ulink url="http://www.eclipse.org/webtools/incubator">XSL Tooling</ulink>

+         project.

+      </para>

+   </section>

+   <bibliography>

+      <title>Resources</title>

+      <biblioentry id="docbook">

+         <bibliosource>

+            <ulink url="http://www.docbook.org">Docbook.org - The Source for Documentation.</ulink>

+         </bibliosource>

+      </biblioentry>

+      <biblioentry id="docbookxsl">

+         <bibliosource>

+            <ulink url="http://docbook.sourceforge.net/projects/xsl/"> DocBook XSL Style Sheets</ulink>

+         </bibliosource>

+      </biblioentry>

+      <biblioentry id="subversion">

+         <bibliosource>

+            <ulink url="http://subversion.tigris.org/"> Subversion</ulink>

+         </bibliosource>

+      </biblioentry>

+   </bibliography>

+</article>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/files/article.xsl b/Article-Authoring-With-Eclipse/files/article.xsl
index f525b57..e67f6da 100644
--- a/Article-Authoring-With-Eclipse/files/article.xsl
+++ b/Article-Authoring-With-Eclipse/files/article.xsl
@@ -1,70 +1,70 @@
-<?xml version='1.0'?>
-<!--
-        $Id: article.xsl,v 1.4 2006/01/18 17:23:40 wbeaton Exp $
-        author: Chris Aniszczyk <zx@us.ibm.com>
-        author: Lawrence Mandel <lmandel@ca.ibm.com>
--->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-	version="1.0">
-	<xsl:import href="docbook.xsl" />
-	
-	<xsl:param name="html.stylesheet"
-		select="'default_style.css'" />
-	<xsl:param name="admon.graphics" select="1" />
-	<xsl:param name="admon.graphics.path">images/</xsl:param>
-	<xsl:param name="admon.graphics.extension">.png</xsl:param>
-	<xsl:param name="suppress.navigation" select="1" />
-	<xsl:param name="bibliography.numbered" select="1" />
-	<xsl:param name="generate.toc">article nop</xsl:param>
-	<xsl:param name="ulink.target" select="'_new'"/>
-	<xsl:param name="admon.style">
-  		<xsl:text>margin-left: 0.38in; margin-right: 0.38in;</xsl:text>
-	</xsl:param>
-
-	<!--  supress the releaseinfo and copyright information -->
-	<xsl:template match="releaseinfo | copyright"
-		mode="titlepage.mode">
-	</xsl:template>
-
-	<xsl:template name="user.header.content">
-		<div align="right">
-			&#160;
-			<span class="copy">
-				Copyright &#x00A9;<xsl:value-of select="//copyright/year[1]" />&#160;<xsl:value-of select="//copyright/holder[1]" />
-			</span>
-		</div>
-	</xsl:template>
-	
-	<xsl:template name="article.titlepage.recto">
-		<h1 align="center"><xsl:value-of select="articleinfo/title"/></h1>
- 
-		<blockquote> 
-			<b>Summary</b><br/>
-			<xsl:value-of select="articleinfo/abstract"/> <br/>
-	
-   			 <p>
-   			 	<b>By 
-    				<xsl:for-each select="articleinfo/authorgroup/author">
-  						<xsl:value-of select="firstname"/>&#160;<xsl:value-of select="surname"/>, <xsl:value-of select="affiliation/orgname"/><br/>
-    				</xsl:for-each>
-   			 	</b>
-    			<xsl:apply-templates mode="article.titlepage.recto.mode" select="articleinfo/date"/>
-    		</p>
- 		</blockquote>
-	</xsl:template>
-
-	<xsl:template match="legalnotice"
-     	mode="article.titlepage.recto.auto.mode.footnote">
-    	<div xsl:use-attribute-sets="article.titlepage.recto.style">
-      		<xsl:apply-templates select="."
-         		mode="titlepage.mode"/>
-    	</div>
-  	</xsl:template>
-  	
-  	<xsl:template name="process.footnotes">
-  		<p></p>
-    	<h3>Trademarks</h3>
-    	<xsl:apply-templates select="articleinfo/legalnotice"
-      		mode="article.titlepage.recto.auto.mode.footnote"/>
-  	</xsl:template>
+<?xml version='1.0'?>

+<!--

+        $Id: article.xsl,v 1.5 2008/09/09 02:24:07 wbeaton Exp $

+        author: Chris Aniszczyk <zx@us.ibm.com>

+        author: Lawrence Mandel <lmandel@ca.ibm.com>

+-->

+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

+	version="1.0">

+	<xsl:import href="docbook.xsl" />

+	

+	<xsl:param name="html.stylesheet"

+		select="'default_style.css'" />

+	<xsl:param name="admon.graphics" select="1" />

+	<xsl:param name="admon.graphics.path">images/</xsl:param>

+	<xsl:param name="admon.graphics.extension">.png</xsl:param>

+	<xsl:param name="suppress.navigation" select="1" />

+	<xsl:param name="bibliography.numbered" select="1" />

+	<xsl:param name="generate.toc">article nop</xsl:param>

+	<xsl:param name="ulink.target" select="'_new'"/>

+	<xsl:param name="admon.style">

+  		<xsl:text>margin-left: 0.38in; margin-right: 0.38in;</xsl:text>

+	</xsl:param>

+

+	<!--  supress the releaseinfo and copyright information -->

+	<xsl:template match="releaseinfo | copyright"

+		mode="titlepage.mode">

+	</xsl:template>

+

+	<xsl:template name="user.header.content">

+		<div align="right">

+			&#160;

+			<span class="copy">

+				Copyright &#x00A9;<xsl:value-of select="//copyright/year[1]" />&#160;<xsl:value-of select="//copyright/holder[1]" />

+			</span>

+		</div>

+	</xsl:template>

+	

+	<xsl:template name="article.titlepage.recto">

+		<h1 align="center"><xsl:value-of select="articleinfo/title"/></h1>

+ 

+		<blockquote> 

+			<b>Summary</b><br/>

+			<xsl:value-of select="articleinfo/abstract"/> <br/>

+	

+   			 <p>

+   			 	<b>By 

+    				<xsl:for-each select="articleinfo/authorgroup/author">

+  						<xsl:value-of select="firstname"/>&#160;<xsl:value-of select="surname"/>, <xsl:value-of select="affiliation/orgname"/><br/>

+    				</xsl:for-each>

+   			 	</b>

+    			<xsl:apply-templates mode="article.titlepage.recto.mode" select="articleinfo/date"/>

+    		</p>

+ 		</blockquote>

+	</xsl:template>

+

+	<xsl:template match="legalnotice"

+     	mode="article.titlepage.recto.auto.mode.footnote">

+    	<div xsl:use-attribute-sets="article.titlepage.recto.style">

+      		<xsl:apply-templates select="."

+         		mode="titlepage.mode"/>

+    	</div>

+  	</xsl:template>

+  	

+  	<xsl:template name="process.footnotes">

+  		<p></p>

+    	<h3>Trademarks</h3>

+    	<xsl:apply-templates select="articleinfo/legalnotice"

+      		mode="article.titlepage.recto.auto.mode.footnote"/>

+  	</xsl:template>

 </xsl:stylesheet>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/files/book.xml b/Article-Authoring-With-Eclipse/files/book.xml
index b1b5682..8a64bd3 100644
--- a/Article-Authoring-With-Eclipse/files/book.xml
+++ b/Article-Authoring-With-Eclipse/files/book.xml
@@ -1,832 +1,832 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-          "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-<!ENTITY blah "<para>Blah blah blah blah. Blah blah blah blah. Blah blah blah blah.
-</para>">
-]>
-<book id="book">
-	<bookinfo>
-		<title>Unit Test: book.001</title>
-		<releaseinfo role="CVS">
-			$Id: book.xml,v 1.3 2006/01/18 17:23:40 wbeaton Exp $
-		</releaseinfo>
-		<authorgroup>
-			<corpauthor>SomeCorp</corpauthor>
-			<author>
-				<firstname>Norman</firstname>
-				<surname>Walsh</surname>
-				<affiliation>
-					<address>
-						<email>ndw@nwalsh.com</email>
-					</address>
-				</affiliation>
-			</author>
-			<editor>
-				<firstname>Jane</firstname>
-				<surname>Doe</surname>
-			</editor>
-		</authorgroup>
-		<legalnotice>
-			<para>
-				Some legal notice. Some legal notice. Some legal notice.
-				Some legal notice. Some legal notice. Some legal notice.
-			</para>
-		</legalnotice>
-		<copyright>
-			<year>1998</year>
-			<year>1999</year>
-			<year>2000</year>
-			<year>2001</year>
-			<year>2002</year>
-			<holder>Norman Walsh</holder>
-		</copyright>
-		<pubdate>18 January 2002</pubdate>
-		<abstract>
-			<para>
-				Some abstract. Some abstract. Some abstract. Some
-				abstract.
-			</para>
-			<para>
-				Some abstract. Some abstract. Some abstract. Some
-				abstract. Some abstract. Some abstract. Some abstract.
-				Some abstract.
-			</para>
-		</abstract>
-		<revhistory>
-			<revision>
-				<revnumber>1.1</revnumber>
-				<date>18 Jan 2002</date>
-				<authorinitials>ndw</authorinitials>
-				<revremark>Reworked.</revremark>
-			</revision>
-			<revision>
-				<revnumber>1.0</revnumber>
-				<date>20 Nov 1998</date>
-				<authorinitials>ndw</authorinitials>
-				<revremark>Some remark about the revision</revremark>
-			</revision>
-			<revision>
-				<revnumber>0.9</revnumber>
-				<date>19 Nov 1998</date>
-				<authorinitials>ndw</authorinitials>
-				<revremark>Some remark about the revision</revremark>
-			</revision>
-			<revision>
-				<revnumber>0.4</revnumber>
-				<date>18 Nov 1998</date>
-				<authorinitials>ndw</authorinitials>
-				<revremark>Some remark about the revision</revremark>
-			</revision>
-		</revhistory>
-	</bookinfo>
-
-	<dedication id="ded1">
-		<title>First Dedication</title>
-
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-
-	</dedication>
-
-	<dedication id="ded2">
-
-		<para>A second dedication without a title.</para>
-
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-
-	</dedication>
-
-	<preface id="forward">
-		<title>Foreword</title>
-
-		<para>A preface.</para>
-
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-
-	</preface>
-
-	<preface id="preface">
-		<title>Preface</title>
-
-		<para>Another preface.</para>
-
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-		&blah;
-
-	</preface>
-
-	<part id="partI">
-		<title>Part One Title</title>
-		<partintro id="pIpintro">
-			<title>PartIntro Title</title>
-
-			<para>
-				Partintro content
-				<footnote>
-					<para>This is a footnote in a partintro.</para>
-				</footnote>
-				.
-			</para>
-
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-
-			<sect1 id="pIpis1">
-				<title>PartIntro Section</title>
-				<para>
-					PartIntros can actually have section content as
-					well.
-				</para>
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-			</sect1>
-		</partintro>
-
-		<chapter id="chap1">
-			<title>First Chapter</title>
-			<titleabbrev>F. Chap</titleabbrev>
-
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-
-			<section id="c1s1">
-				<title>First Section</title>
-				<titleabbrev>F. Sect</titleabbrev>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="c1s2">
-				<title>Second Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="c1s3">
-				<title>Third Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-		</chapter>
-
-		<chapter id="chap2">
-			<title>Second Chapter</title>
-
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-
-			<section id="c2s1">
-				<title>First Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="c2s2">
-				<title>Second Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="c2s3">
-				<title>Third Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-		</chapter>
-
-		<chapter id="chap3">
-			<title>Third Chapter</title>
-
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-
-		</chapter>
-
-	</part>
-	<part id="partII">
-		<title>Appendixes</title>
-
-		<appendix id="app1">
-			<title>First Appendix</title>
-
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-
-			<section id="a1s1">
-				<title>First Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="a1s2">
-				<title>Second Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="a1s3">
-				<title>Third Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-		</appendix>
-
-		<appendix id="app2">
-			<title>Second Appendix</title>
-
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-			&blah;
-
-			<section id="a2s1">
-				<title>First Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="a2s2">
-				<title>Second Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-			<section id="a2s3">
-				<title>Third Section</title>
-
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-				&blah;
-
-			</section>
-		</appendix>
-
-	</part>
+<?xml version="1.0" encoding="utf-8"?>

+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"

+          "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [

+<!ENTITY blah "<para>Blah blah blah blah. Blah blah blah blah. Blah blah blah blah.

+</para>">

+]>

+<book id="book">

+	<bookinfo>

+		<title>Unit Test: book.001</title>

+		<releaseinfo role="CVS">

+			$Id: book.xml,v 1.4 2008/09/09 02:24:07 wbeaton Exp $

+		</releaseinfo>

+		<authorgroup>

+			<corpauthor>SomeCorp</corpauthor>

+			<author>

+				<firstname>Norman</firstname>

+				<surname>Walsh</surname>

+				<affiliation>

+					<address>

+						<email>ndw@nwalsh.com</email>

+					</address>

+				</affiliation>

+			</author>

+			<editor>

+				<firstname>Jane</firstname>

+				<surname>Doe</surname>

+			</editor>

+		</authorgroup>

+		<legalnotice>

+			<para>

+				Some legal notice. Some legal notice. Some legal notice.

+				Some legal notice. Some legal notice. Some legal notice.

+			</para>

+		</legalnotice>

+		<copyright>

+			<year>1998</year>

+			<year>1999</year>

+			<year>2000</year>

+			<year>2001</year>

+			<year>2002</year>

+			<holder>Norman Walsh</holder>

+		</copyright>

+		<pubdate>18 January 2002</pubdate>

+		<abstract>

+			<para>

+				Some abstract. Some abstract. Some abstract. Some

+				abstract.

+			</para>

+			<para>

+				Some abstract. Some abstract. Some abstract. Some

+				abstract. Some abstract. Some abstract. Some abstract.

+				Some abstract.

+			</para>

+		</abstract>

+		<revhistory>

+			<revision>

+				<revnumber>1.1</revnumber>

+				<date>18 Jan 2002</date>

+				<authorinitials>ndw</authorinitials>

+				<revremark>Reworked.</revremark>

+			</revision>

+			<revision>

+				<revnumber>1.0</revnumber>

+				<date>20 Nov 1998</date>

+				<authorinitials>ndw</authorinitials>

+				<revremark>Some remark about the revision</revremark>

+			</revision>

+			<revision>

+				<revnumber>0.9</revnumber>

+				<date>19 Nov 1998</date>

+				<authorinitials>ndw</authorinitials>

+				<revremark>Some remark about the revision</revremark>

+			</revision>

+			<revision>

+				<revnumber>0.4</revnumber>

+				<date>18 Nov 1998</date>

+				<authorinitials>ndw</authorinitials>

+				<revremark>Some remark about the revision</revremark>

+			</revision>

+		</revhistory>

+	</bookinfo>

+

+	<dedication id="ded1">

+		<title>First Dedication</title>

+

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+

+	</dedication>

+

+	<dedication id="ded2">

+

+		<para>A second dedication without a title.</para>

+

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+

+	</dedication>

+

+	<preface id="forward">

+		<title>Foreword</title>

+

+		<para>A preface.</para>

+

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+

+	</preface>

+

+	<preface id="preface">

+		<title>Preface</title>

+

+		<para>Another preface.</para>

+

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+		&blah;

+

+	</preface>

+

+	<part id="partI">

+		<title>Part One Title</title>

+		<partintro id="pIpintro">

+			<title>PartIntro Title</title>

+

+			<para>

+				Partintro content

+				<footnote>

+					<para>This is a footnote in a partintro.</para>

+				</footnote>

+				.

+			</para>

+

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+

+			<sect1 id="pIpis1">

+				<title>PartIntro Section</title>

+				<para>

+					PartIntros can actually have section content as

+					well.

+				</para>

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+			</sect1>

+		</partintro>

+

+		<chapter id="chap1">

+			<title>First Chapter</title>

+			<titleabbrev>F. Chap</titleabbrev>

+

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+

+			<section id="c1s1">

+				<title>First Section</title>

+				<titleabbrev>F. Sect</titleabbrev>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="c1s2">

+				<title>Second Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="c1s3">

+				<title>Third Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+		</chapter>

+

+		<chapter id="chap2">

+			<title>Second Chapter</title>

+

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+

+			<section id="c2s1">

+				<title>First Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="c2s2">

+				<title>Second Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="c2s3">

+				<title>Third Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+		</chapter>

+

+		<chapter id="chap3">

+			<title>Third Chapter</title>

+

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+

+		</chapter>

+

+	</part>

+	<part id="partII">

+		<title>Appendixes</title>

+

+		<appendix id="app1">

+			<title>First Appendix</title>

+

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+

+			<section id="a1s1">

+				<title>First Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="a1s2">

+				<title>Second Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="a1s3">

+				<title>Third Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+		</appendix>

+

+		<appendix id="app2">

+			<title>Second Appendix</title>

+

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+			&blah;

+

+			<section id="a2s1">

+				<title>First Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="a2s2">

+				<title>Second Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+			<section id="a2s3">

+				<title>Third Section</title>

+

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+				&blah;

+

+			</section>

+		</appendix>

+

+	</part>

 </book>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/files/docbook-article-template.zip b/Article-Authoring-With-Eclipse/files/docbook-article-template.zip
index 7f879d3..43a30b3 100644
--- a/Article-Authoring-With-Eclipse/files/docbook-article-template.zip
+++ b/Article-Authoring-With-Eclipse/files/docbook-article-template.zip
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/files/pdf/build.xml b/Article-Authoring-With-Eclipse/files/pdf/build.xml
index b1c0897..f1bef75 100644
--- a/Article-Authoring-With-Eclipse/files/pdf/build.xml
+++ b/Article-Authoring-With-Eclipse/files/pdf/build.xml
@@ -1,37 +1,37 @@
-<project basedir="." name="build-pdf" default="main">
-	<property name="pdfdir" value="pdfs" />
-
-	<!-- 
-		first declare the fop task and where to 
-		find the jar-libraries
-		
-		the libraries are expected in 
-		sub-folder "lib" of the working directory
-	-->
-	<taskdef name="fop" classname="org.apache.fop.tools.anttasks.Fop">
-		<classpath>
-			<pathelement location="lib\fop.jar" />
-			<pathelement location="lib\avalon.jar" />
-			<pathelement location="lib\batik.jar" />
-		</classpath>
-	</taskdef>
-
-	<mkdir dir="${pdfdir}" />
-
-	<target name="main">
-		<!-- 
-			create output of type pdf and generate output in 
-			directory ${pdfdir}
-		-->
-		<fop format="application/pdf" outdir="${pdfdir}"
-			messagelevel="debug">
-			<!-- 
-				convert all fo files in 
-				working directory into pdf
-			-->
-			<fileset dir=".">
-				<include name="*.fo" />
-			</fileset>
-		</fop>
-	</target>
+<project basedir="." name="build-pdf" default="main">

+	<property name="pdfdir" value="pdfs" />

+

+	<!-- 

+		first declare the fop task and where to 

+		find the jar-libraries

+		

+		the libraries are expected in 

+		sub-folder "lib" of the working directory

+	-->

+	<taskdef name="fop" classname="org.apache.fop.tools.anttasks.Fop">

+		<classpath>

+			<pathelement location="lib\fop.jar" />

+			<pathelement location="lib\avalon.jar" />

+			<pathelement location="lib\batik.jar" />

+		</classpath>

+	</taskdef>

+

+	<mkdir dir="${pdfdir}" />

+

+	<target name="main">

+		<!-- 

+			create output of type pdf and generate output in 

+			directory ${pdfdir}

+		-->

+		<fop format="application/pdf" outdir="${pdfdir}"

+			messagelevel="debug">

+			<!-- 

+				convert all fo files in 

+				working directory into pdf

+			-->

+			<fileset dir=".">

+				<include name="*.fo" />

+			</fileset>

+		</fop>

+	</target>

 </project>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/images/XMLPerspective.png b/Article-Authoring-With-Eclipse/images/XMLPerspective.png
new file mode 100644
index 0000000..ed7d32d
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/images/XMLPerspective.png
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/images/html.jpg b/Article-Authoring-With-Eclipse/images/html.jpg
new file mode 100644
index 0000000..6e8566a
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/images/html.jpg
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/index.html b/Article-Authoring-With-Eclipse/index.html
index 5abd5af..0d9047c 100644
--- a/Article-Authoring-With-Eclipse/index.html
+++ b/Article-Authoring-With-Eclipse/index.html
@@ -1,5 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Authoring with Eclipse</title><link href="../article.css" rel="stylesheet" type="text/css"><meta content="DocBook XSL Stylesheets V1.71.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"><h1>Authoring with Eclipse</h1><div class="summary"><h2>Summary</h2><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Authoring with Eclipse</title><link href="../article.css" rel="stylesheet" type="text/css"><meta content="DocBook XSL Stylesheets V1.73.2" 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"><h1>Authoring with Eclipse</h1><div class="summary"><h2>Summary</h2><p>
 				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
@@ -10,27 +10,27 @@
 				an article or a book within Eclipse. In fact, this
 				article was written using Eclipse.
 			</p><div class="author">
-				By 
+				By
 				Chris&nbsp;Aniszczyk,
 					IBM Corporation<br>Lawrence&nbsp;Mandel,
 					IBM Corporation<br></div><div class="copyright">
 				Copyright &copy;
-				2005&nbsp;International Business Machines Corporation. All rights reserved.</div><div class="date"><span class="date">December 14, 2005<br></span></div></div><div class="content"><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 class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><p>
+				2005&nbsp;International Business Machines Corporation. All rights reserved.</div><div class="date"><span class="date">December 14, 2005<br></span></div><div class="releaseinfo"><em><span class="remark">Updated May 2008 by Peter Friese, itemis AG (see <a class="ulink" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=225714" target="_new">Bug 225714)</a>.</span></em></div></div><div class="content"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1004C"></a>Environment</h2></div></div></div><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><p>
 				The examples in this article were built and tested with:
 				<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">
+							<a class="ulink" 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 class="ulink" href="http://download.eclipse.org/webtools/downloads/drops/R-1.0-/" target="_new">
 								Eclipse Web Tools Platform (WTP) 1.0
 							</a>
 						</li><li>
-							<a href="http://eclipsexslt.sourceforge.net/" target="_new">
+							<a class="ulink" href="http://eclipsexslt.sourceforge.net/" target="_new">
 								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><p>
+			</p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10069"></a>Introduction</h2></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
@@ -41,7 +41,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><p>
+		</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1006E"></a>Technical Documentation</h2></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
@@ -53,12 +53,12 @@
 			information where appropriate.
 		</p><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><p>
 				If you're unfamiliar with DocBook, there's an
-				<a href="http://www-128.ibm.com/developerworks/library/l-docbk.html" target="_new">
+				<a class="ulink" href="http://www-128.ibm.com/developerworks/library/l-docbk.html" target="_new">
 					article
 				</a>
 				on the <span class="trademark">IBM</span>&reg; <span class="trademark">developerWorks</span>&reg; 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">
+				<a class="ulink" href="http://www-128.ibm.com/developerworks/xml/library/x-dita1/index.html" target="_new">
 					introduction
 				</a>
 				to DITA on developerWorks.
@@ -87,7 +87,7 @@
 			(that is, one that has both style and formatting applied)
 			such as HTML or PDF. Once in a human-readable format, the
 			document is ready to be published by a selected publisher.
-		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10088"></a>Advantages of an XML format</h3></div></div></div><p>
+		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1008E"></a>Advantages of an XML format</h3></div></div></div><p>
 				Before diving into an actual example of the technical
 				documentation process using Eclipse, let's take a look
 				at some of the benefits of authoring in an XML format.
@@ -177,22 +177,22 @@
 							even an Eclipse help system version simply
 							by transforming your document with different
 							style sheets. In fact, DocBook includes all
-							three of these style sheets allowing you to
+							three of these stylesheets allowing you to
 							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><p>
+			</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N100BE"></a>Examples</h2></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="article.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><p>
+			<a class="ulink" href="files/book.xml" target="_new">here</a>. This DocBook source for this
+			article is also available and can be seen <a class="ulink" href="AuthoringWithEclipse.xml" target="_new">here</a>.
+		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N100CB"></a>Tool Chain</h3></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
 				chain, so the output of each tool becomes the input of
 				the next
-				[<a href="#toolchain">3</a>]
+				<a class="xref" href="#toolchain" title="???TITLE???">[3]</a>
 				. This concept should be very familiar to those who work
 				on the <span class="trademark">UNIX</span>&reg;, 
 				<span class="trademark">Linux</span>&reg;, and 
@@ -217,7 +217,7 @@
 				development environment. In the following sections, we'll
 				discuss how you can make this a reality with current
 				Eclipse tooling and where the tooling falls short.
-			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N100DD"></a>Creation and Review</h4></div></div></div><p>
+			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N100E3"></a>Creation and Review</h4></div></div></div><p>
 					Although creation and review are two separate parts
 					of the technical documentation process, the same
 					tools are required and therefore will be discussed
@@ -231,7 +231,7 @@
 					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&nbsp;1.&nbsp;The XML Source Editor">Figure&nbsp;1, &ldquo;The XML Source Editor&rdquo;</a>
+					<a class="xref" href="#xml-source-editor" title="Figure&nbsp;1.&nbsp;The XML Source Editor">Figure&nbsp;1, &ldquo;The XML Source Editor&rdquo;</a>
 					, is more useful when authoring in XML.
 				</p><div class="figure"><a name="xml-source-editor"></a><p class="title"><b>Figure&nbsp;1.&nbsp;The XML Source Editor</b></p><div class="figure-contents"><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></div><br class="figure-break"><p>
 					The XML editor provides many of the Eclipse
@@ -271,7 +271,7 @@
 					in Eclipse provides other benefits. Eclipse includes
 					integrated version control for CVS. (There is also a
 					freely available plug-in for subversion
-					[<a href="#subversion">6</a>], another version control 
+					<a class="xref" href="#subversion" title="???TITLE???">[6]</a>, another version control 
 					system.) Integrated
 					version control allows you to check your changes
 					into, and view others' changes in, your version
@@ -282,11 +282,11 @@
 					permission to make these changes allows you to avoid
 					the need to use e-mail or some other communication
 					mechanism.
-				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1012B"></a>Publication</h4></div></div></div><p>
+				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10131"></a>Publication</h4></div></div></div><p>
 					The DocBook XSL
-					[<a href="#docbookxsl">1</a>]
+					<a class="xref" href="#docbookxsl" title="???TITLE???">[1]</a>
 					and DITA
-					[<a href="#dita">2</a>]
+					<a class="xref" href="#dita" title="???TITLE???">[2]</a>
 					projects offer numerous transformations, including
 					HTML and PDF formats. The most common
 					transformation technique is to use an Ant file with
@@ -299,7 +299,7 @@
 					parameters for the transformation.
 				</p><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><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">
+					<a class="ulink" href="http://dita-ot.sourceforge.net/doc/DITA-antscript.html" target="_new">
 						transformation
 					</a>.
 				</p></td></tr></table></div><p>
@@ -308,7 +308,7 @@
 					perform each transformation. Transformations for
 					both DocBook and DITA will be provided where
 					appropriate.
-				</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N1013F"></a>HTML</h5></div></div></div><p>
+				</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N10145"></a>HTML</h5></div></div></div><p>
 						Of all the available transformations,
 						transforming your document into HTML is the
 						easiest to use. All that you need to do is
@@ -317,10 +317,10 @@
 						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&nbsp;2.&nbsp;Sample HTML Transformation Configuration for book.xml">Figure&nbsp;2, &ldquo;Sample HTML Transformation Configuration for book.xml&rdquo;</a>
+						<a class="xref" href="#html-transformation" title="Figure&nbsp;2.&nbsp;Sample HTML Transformation Configuration for book.xml">Figure&nbsp;2, &ldquo;Sample HTML Transformation Configuration for book.xml&rdquo;</a>
 						shows a sample transformation configuration that
 						will transform our DocBook sample
-						<a href="files/book.xml" target="_new">document</a>
+						<a class="ulink" href="files/book.xml" target="_new">document</a>
 						into HTML.
 					</p><div class="figure"><a name="html-transformation"></a><p class="title"><b>Figure&nbsp;2.&nbsp;Sample HTML Transformation Configuration for book.xml</b></p><div class="figure-contents"><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><br class="figure-break"><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Tip]" src="images/tip.gif"></td><td><p>
 							You can augment the transformation by
@@ -328,15 +328,15 @@
 							There's a full listing of DocBook XSL
 							parameters that can be used to configure the
 							transformation located
-							<a href="http://docbook.sourceforge.net/release/xsl/current/doc/html/" target="_new">
+							<a class="ulink" href="http://docbook.sourceforge.net/release/xsl/current/doc/html/" target="_new">
 								here
 							</a>.
 						</p></td></tr></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 class="ulink" href="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><p>
+					</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N1017A"></a>PDF</h5></div></div></div><p>
 						Transforming a DocBook XML file to PDF format is
 						more involved than the transformation to HTML
 						but it is still possible using a style sheet. The
@@ -351,7 +351,7 @@
 						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&nbsp;3.&nbsp;Sample XSL-FO Transformation Configuration for book.xml">Figure&nbsp;3, &ldquo;Sample XSL-FO Transformation Configuration for book.xml&rdquo;</a>
+						<a class="xref" href="#xslfo-transformation" title="Figure&nbsp;3.&nbsp;Sample XSL-FO Transformation Configuration for book.xml">Figure&nbsp;3, &ldquo;Sample XSL-FO Transformation Configuration for book.xml&rdquo;</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&nbsp;3.&nbsp;Sample XSL-FO Transformation Configuration for book.xml</b></p><div class="figure-contents"><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></div><br class="figure-break"><p>
@@ -359,28 +359,28 @@
 						Processor (FOP) to transform your XSL-FO
 						document into a PDF. One of the more popular
 						open source FOPs is the
-						<a href="http://xmlgraphics.apache.org/fop/" target="_new">
+						<a class="ulink" href="http://xmlgraphics.apache.org/fop/" target="_new">
 							Apache FOP
 						</a>
 						. We'll use a third-party
-						<a href="http://www.ahmadsoft.org/fopbridge.html" target="_new">
+						<a class="ulink" href="http://www.ahmadsoft.org/fopbridge.html" target="_new">
 							plug-in from Ahmadsoft
 						</a>
 						that integrates Apache FOP into Eclipse. After
 						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&nbsp;4.&nbsp;Sample FOP Transformation">Figure&nbsp;4, &ldquo;Sample FOP Transformation&rdquo;</a>
+						<a class="xref" href="#pdf-transformation" title="Figure&nbsp;4.&nbsp;Sample FOP Transformation">Figure&nbsp;4, &ldquo;Sample FOP Transformation&rdquo;</a>
 						shows an example of running the FOP
 						transformation.
 					</p><div class="figure"><a name="pdf-transformation"></a><p class="title"><b>Figure&nbsp;4.&nbsp;Sample FOP Transformation</b></p><div class="figure-contents"><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><br class="figure-break"><div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><p>
 							The example includes a sample Ant
-							<a href="files/pdf/build.xml" target="_new">
+							<a class="ulink" href="files/pdf/build.xml" target="_new">
 								file
 							</a>
 							that performs the same transformation as
 							running the FOP transformation using the
-							<a href="http://www.ahmadsoft.org/fopbridge.html" target="_new">
+							<a class="ulink" href="http://www.ahmadsoft.org/fopbridge.html" target="_new">
 								plug-in from Ahmadsoft
 							</a>. An Ant script is a popular method of
 							performing the publishing stage, and this
@@ -392,9 +392,9 @@
 						</p></td></tr></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 class="ulink" href="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><p>
+					</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N101BD"></a>Eclipse Infocenter</h5></div></div></div><p>
 						In our opinion, one of the coolest features of
 						the DocBook and DITA projects is the generation
 						of an Eclipse help plug-in (information center) from
@@ -402,7 +402,7 @@
 						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&nbsp;5.&nbsp;Sample Eclipse Infocenter Transformation Configuration">Figure&nbsp;5, &ldquo;Sample Eclipse Infocenter Transformation Configuration&rdquo;</a>
+						<a class="xref" href="#eclipse-transformation" title="Figure&nbsp;5.&nbsp;Sample Eclipse Infocenter Transformation Configuration">Figure&nbsp;5, &ldquo;Sample Eclipse Infocenter Transformation Configuration&rdquo;</a>
 						shows a sample transformation configuration
 						along with the correct parameters. To perform
 						this transformation using a DITA source file, use
@@ -413,18 +413,18 @@
 							The complete list of DocBook XSL parameters
 							for the Eclipse Infocenter transformation
 							is located
-							<a href="http://docbook.sourceforge.net/release/xsl/current/doc/html/eclipse_help.html" target="_new">
+							<a class="ulink" href="http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html" target="_new">
 								here
 							</a>
 							.
 						</p></td></tr></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 class="ulink" href="files/DocBook-InfoCenter.htm" target="_new">
 							here
 						</a>
 						.
-					</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N101DE"></a>Current Limitations</h4></div></div></div><p>
+					</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N101E4"></a>Current Limitations</h4></div></div></div><p>
 					Although we have shown that Eclipse's current XML
 					authoring support is pretty good, there are a two
 					noteworthy limitations.
@@ -445,7 +445,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><p>
+				</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101EF"></a>Summary</h2></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
@@ -457,7 +457,7 @@
 			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><p>
+		</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101F4"></a>Acknowledgements</h2></div></div></div><p>
 			We'd like to thank:
 			<div class="itemizedlist"><ul type="disc"><li>
 						Sushma Patel and Anne James for correcting our horrible
@@ -467,12 +467,12 @@
 						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><p>
+		</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10203"></a>About the Authors</h2></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 class="ulink" 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">
+			<a class="ulink" href="http://www.eclipse.org/emft" target="_new">
 				Eclipse Modeling Framework Technology (EMFT)
 			</a>
 			project.
@@ -480,33 +480,33 @@
 			Lawrence Mandel, a software developer at the IBM Toronto
 			Laboratory, is the documentation lead and a
 			committer for the Eclipse
-			<a href="http://www.eclipse.org/webtools" target="_new">
+			<a class="ulink" href="http://www.eclipse.org/webtools" target="_new">
 				Web Tools Platform (WTP)
 			</a>
 			project. He is also authoring a book with Arthur Ryman and
 			Naci Dai about Java Web application development with
 			Eclipse.
-		</p></div><div class="appendix" lang="en"><h2 class="title" style="clear: both"><a name="N10243"></a>A.&nbsp;Appendix</h2><p>
+		</p></div><div class="appendix" lang="en"><h2 class="title" style="clear: both"><a name="N10249"></a>A.&nbsp;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
 			reviews a couple of other editors out there for technical
 			documentation in case WTP's XML editor doesn't suit your fancy.
-		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10248"></a>The Article</h3></div></div></div><p>
+		</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1024E"></a>The Article</h3></div></div></div><p>
 				This article was written in DocBook using WTP's XML
 				editor. To transform the article into the correct format
 				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>.
+				<a class="ulink" href="files/article.xsl" target="_new">here</a>.
 				<div class="note" style="margin-left: 0.38in; margin-right: 0.38in;"><table class="note-table"><tr><td><img alt="[Note]" src="images/note.gif"></td><td><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">
+						by following bug <a class="ulink" 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><p>
+			</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1025F"></a>Editors</h3></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
@@ -517,9 +517,9 @@
 				options for creating and editing content so we'll
 				discuss of a couple of those options in the following
 				sections.
-			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1025E"></a>Vex</h4></div></div></div><p>
+			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10264"></a>Vex</h4></div></div></div><p>
 					Vex
-					[<a href="#vex">4</a>]
+					<a class="xref" href="#vex" title="???TITLE???">[4]</a>
 					is an open source project that lets you edit XML
 					files visually. Vex uses standard Document Type
 					Definition (DTD) files to define document types and
@@ -528,13 +528,13 @@
 					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&nbsp;A.1.&nbsp;Vex DocBook editor screenshot">Figure&nbsp;A.1, &ldquo;Vex DocBook editor screenshot&rdquo;</a>
+					<a class="xref" href="#vex-editor" title="Figure&nbsp;A.1.&nbsp;Vex DocBook editor screenshot">Figure&nbsp;A.1, &ldquo;Vex DocBook editor screenshot&rdquo;</a>
 					.
 					<div class="figure"><a name="vex-editor"></a><p class="title"><b>Figure&nbsp;A.1.&nbsp;Vex DocBook editor screenshot</b></p><div class="figure-contents"><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></div><br class="figure-break">
 
-				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10276"></a>OpenOffice</h4></div></div></div><p>
+				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1027C"></a>OpenOffice</h4></div></div></div><p>
 					OpenOffice
-					[<a href="#openoffice">5</a>]
+					<a class="xref" href="#openoffice" title="???TITLE???">[5]</a>
 					is a multi-platform open source office suite that is
 					capable of visually editing DocBook and various
 					other formats. OpenOffice is a popular editing
@@ -545,37 +545,37 @@
 					OpenOffice doesn't fully support DocBook. An
 					updated list of what portions of DocBook OpenOffice
 					supports can be found on the OpenOffice site
-					<a href="http://xml.openoffice.org/xmerge/docbook/DocBookTags.html" target="_new">
+					<a class="ulink" href="http://xml.openoffice.org/xmerge/docbook/DocBookTags.html" target="_new">
 						here
 					</a>
 					. The site also contains a getting started
-					<a href="http://xml.openoffice.org/xmerge/docbook/UserGuide.html" target="_new">
+					<a class="ulink" href="http://xml.openoffice.org/xmerge/docbook/UserGuide.html" target="_new">
 						guide
 					</a>
 					that will get you started with DocBook in
 					OpenOffice.
-				</p></div></div></div><div class="bibliography"><div class="titlepage"><div><div><h2 class="title"><a name="N10210"></a>Resources</h2></div></div></div><div class="biblioentry"><a name="docbookxsl"></a><p>[1] <span class="bibliosource">
-				<a href="http://docbook.sourceforge.net/projects/xsl/" target="_new">
+				</p></div></div></div><div class="bibliography"><div class="titlepage"><div><div><h2 class="title"><a name="N10216"></a>Resources</h2></div></div></div><div class="biblioentry"><a name="docbookxsl"></a><p>[1] <span class="bibliosource">
+				<a class="ulink" href="http://docbook.sourceforge.net/projects/xsl/" target="_new">
 					DocBook XSL Style Sheets
 				</a>
 			. </span></p></div><div class="biblioentry"><a name="dita"></a><p>[2] <span class="bibliosource">
-				<a href="http://dita-ot.sourceforge.net/" target="_new">
+				<a class="ulink" href="http://dita-ot.sourceforge.net/" target="_new">
 					DITA Open Toolkit
 				</a>
 			. </span></p></div><div class="biblioentry"><a name="toolchain"></a><p>[3] <span class="bibliosource">
-				<a href="http://en.wikipedia.org/wiki/Toolchain" target="_new">
+				<a class="ulink" href="http://en.wikipedia.org/wiki/Toolchain" target="_new">
 					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 class="ulink" 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 class="ulink" 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">
+				<a class="ulink" href="http://subversion.tigris.org/" target="_new">
 					Subversion
 				</a>
 			. </span></p></div></div><div class="notices"><h3>Legal Notices</h3><p>
diff --git a/Article-Authoring-With-Eclipse/info.xml b/Article-Authoring-With-Eclipse/info.xml
index 173b911..37a6b3e 100644
--- a/Article-Authoring-With-Eclipse/info.xml
+++ b/Article-Authoring-With-Eclipse/info.xml
@@ -1,6 +1,8 @@
 <article>
 	<bug id="108397"/>
 	<project id="eclipse">
+		<release>3.4</release>
+		<release>3.3</release>
 		<release>3.2</release>
 	</project>
 </article>
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/output/AuthoringWithEclipse.html b/Article-Authoring-With-Eclipse/output/AuthoringWithEclipse.html
new file mode 100644
index 0000000..9de99c4
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/AuthoringWithEclipse.html
@@ -0,0 +1,1005 @@
+<html>
+   <head>
+      <title>DocBook Authoring with Eclipse</title>
+      <link href="default_style.css" rel="stylesheet" type="text/css"/>
+      <meta content="text/html; charset='UTF-8'"/>
+      <meta content="DocBook XSL Stylesheets V1.73.2" name="generator"/>
+      <meta name="description" content="Eclipse is not known for it's ability to write documentation, but it is something that every programmer eventually has to do. In today's world it is not uncommon to have to support not only print media, but also online content as well. This article will take a look at the advances of eclipse as an authoring environment. It will revisit concepts original discussed in the &quot;Authoring with Eclipse&quot; article, published in December 2005."/>
+   </head>
+   <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <div align="right">
+         <span class="copy">Copyright ©2008  Standards for Technology in Automotive Retail. All rights reserved.</span>
+      </div>
+      <div class="article" lang="en">
+         <div class="titlepage">
+            <div>
+               <h1 align="center">DocBook Authoring with Eclipse</h1>
+               <blockquote>
+                  <b>Summary</b>
+                  <br/>
+            Eclipse is not known for it's ability to write documentation, but it is something that
+            every programmer eventually has to do. In today's world it is not uncommon to have to
+            support not only print media, but also online content as well. This article will take a
+            look at the advances of eclipse as an authoring environment. It will revisit concepts
+            original discussed in the
+            "Authoring with Eclipse"
+            article, published in December 2005.
+         <br/>
+                  <p>
+                     <b>By 
+               David Carver, Standards for Technology in Automotive Retail<br/>
+                     </b>
+                  </p>
+               </blockquote>
+            </div>
+            <hr/>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N10041"/>Environment</h2>
+                  </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">Note</th>
+                  </tr>
+                  <tr>
+                     <td valign="top" align="left">
+                        <p>
+            The examples in this article were built and tested with:
+            <div class="itemizedlist">
+                              <ul type="disc">
+                                 <li>
+                                    <p>
+                     <a class="ulink" href="http://www.eclipse.org/download" target="_new">Eclipse 3.4</a>
+                  </p>
+                                 </li>
+                                 <li>
+                                    <p>
+                     <a class="ulink" href="http://www.eclipse.org/webtools" target="_new"> Eclipse Web Tools Platform (WTP) 3.0</a>
+                  </p>
+                                 </li>
+                                 <li>
+                                    <p>
+                     <a class="ulink" href="http://www.eclipse.org/webtools/incubator" target="_new"> XSL Tools 0.5M8 - Incubator</a>
+                  </p>
+                                 </li>
+                                 <li>
+                                    <p>
+                     <a class="ulink" href="http://www.docbook.org" target="_new">Docbook 4.5</a>
+                  </p>
+                                 </li>
+                                 <li>
+                                    <p>
+                     <a class="ulink" href="http://docbook.sourceforge.net/" target="_new">The DocBook XSL stylesheets from the DocBook Project
+                     </a>
+                  </p>
+                                 </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="N1006C"/>Preface</h2>
+                  </div>
+               </div>
+            </div>
+            <p>
+         This article is a revisiting of the original
+         <a class="ulink" href="http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html" target="_new">"Authoring With Eclipse"</a>
+         article by Chris Aniszczyk and Lawrence Mandel. The article revisits many of the concepts
+         discussed in the original article, and expands on them where it is necessary. Much has
+         changed since the original article, but much of the information is still relevant to
+         authoring with eclipse today.
+      </p>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N10075"/>Introduction</h2>
+                  </div>
+               </div>
+            </div>
+            <p> Writing documentation is something that almost any programmer or architect is
+         eventually going to have to do. It's not a job that most enjoy, and the fact that the
+         documentation usually has to be available in multiple formats at the same time, makes the
+         job of creating the documentation that much less enjoyable. However, all is not lost. There
+         are many ways to produce content that can be written once and documented in many formats.
+         The sections that follow discuss one of these options, DocBook, and how existing eclipse projects can be used along
+         with a few open source plugins to create an authoring system. This  article in fact is entirely
+         written in DocBook and leverages the tools discussed.</p>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N1007A"/>Technical Documentation</h2>
+                  </div>
+               </div>
+            </div>
+            <p>According to Chris and Lawrence, "In the open source world, technical
+         documentation is primarily accomplished using two popular formats: DocBook and the Darwin
+         Information Typing Architecture (DITA)." <a class="xref" href="#authoringwitheclipse" title="Authoring with Eclipse">[1]</a>  Projects such as GNOME, PHP,
+         KDE, the Linux Kernel, and PostgreSQL are
+         a few examples of projects using DocBook for their documentation format <a class="xref" href="#whousesdocbook" title="???TITLE???">[5]</a>.
+         </p>
+            <p>
+         Both DocBook and DITA formats leverage XML. DocBook and DITA separate the content from the presentation.
+         Unlike HTML which mixes the two together, making it difficult or impossible to separate content from
+         formatting. The advantage to DocBook and DITA formats is that both of these specification
+         frees the author to concentrate on the content and not how it will
+         necessarily look. This is necessary because the same content can be targeted to multiple
+         formats, each with its own unique presentation and requirements. It is not uncommon to have
+         DocBook content appear in PDF, Presentation Slides, HTML, RTF, Man, and many more formats.
+      </p>
+            <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">Note</th>
+                  </tr>
+                  <tr>
+                     <td valign="top" align="left">
+                        <p>
+                           <a class="ulink" href="http://www.eclipse.org/webtools/incubator" target="_new">XSL Tools'</a> user documentation
+        is entirely written in DocBook and transformed into eclipse help files.
+        </p>
+                     </td>
+                  </tr>
+               </table>
+            </div>
+            <p> DocBook itself has it's beginnings with SGML, the precursor to XML. It is widely used
+         in the publishing industry, and the O'Reily publishing house uses DocBook for it's main archival format for it's books.
+         books.</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">Tip</th>
+                  </tr>
+                  <tr>
+                     <td valign="top" align="left">
+                        <p>
+            Norman Walsh, has written a book called
+            <a class="ulink" href="http://www.docbook.org/tdg/en/html/docbook.html" target="_new">DocBook: The Definitive Guide</a>
+            . The book is available on line as well as at many book resellers. Anything and
+            everything about the DocBook markup can be found in the book.
+         </p>
+                     </td>
+                  </tr>
+               </table>
+            </div>
+            <p> Writing an article or a book in XML is no different than writing most any other
+         application. The author can break the process down into several stages. Chris and Lawrence
+         originally had these in the following steps:</p>
+            <div class="itemizedlist">
+               <ul type="disc">
+                  <li>
+                     <p> Creation - The process of adding content to the file. This includes such
+               meta data as authors, editors, revision history, chapters, sections, figures, tables,
+               etc.</p>
+                  </li>
+                  <li>
+                     <p> Review - The process of fixing the inevitable grammar and content mistakes that
+               tend to creep into the document. Regardless of how well the author tries, some no
+               excuse error is going to creep into the document. The nice thing about writing is
+               that during this process one is not concerned as much about how it looks, just that
+               the content is correct.</p>
+                  </li>
+                  <li>
+                     <p> Publication - The final step is actually publishing the document. This is either
+               creating the PDF, the HTML, or the eclipse Help format files. This is where the
+               formatting is reviewed, and for the most part with the help of the DocBook Project's
+               XSL Stylesheets very little has to be done to get a professional looking publication.
+               If errors are found, then repeat the Review process, and republish.</p>
+                  </li>
+               </ul>
+            </div>
+            <div class="section" lang="en">
+               <div class="titlepage">
+                  <div>
+                     <div>
+                        <h3 class="title">
+                           <a name="N100A2"/>Advantages of an XML format</h3>
+                     </div>
+                  </div>
+               </div>
+               <p> <span class="trademark">Microsoft</span>™ Word has the ability to create a master document from multiple word
+            documents. However, anybody that has tried to do this, knows that the process is more
+            brittle than it needs to be. It should be as simple as saying include these three files,
+            and generate me out one complete book that contains everything. With DocBook and XML it
+            is that simple if you leverage a little known specification called XInclude.</p>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N100AA"/>XInclude</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p>
+               XInlcude allows you create the Modularity that Chris and Lawrence originally talked
+               about. An example of a XInclude is shown in
+               <a class="xref" href="#Xinclude_Example" title="Example 1. XInclude">Example 1, “XInclude”</a>
+            </p>
+                  <div class="example">
+                     <a name="Xinclude_Example"/>
+                     <p class="title">
+                        <b>Example 1. XInclude</b>
+                     </p>
+                     <div class="example-contents">
+                        <pre class="programlisting">
+&lt;book id='Book1' xmlns:xi="http://www.w3.org/2001/XInclude"&gt;
+  &lt;xi:include href="Introduction.xml"/&gt;
+  &lt;xi:include href="WorkbenchLayout.xml"/&gt;
+&lt;book&gt;
+
+               </pre>
+                     </div>
+                  </div>
+                  <br class="example-break"/>
+                  <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">Note</th>
+                        </tr>
+                        <tr>
+                           <td valign="top" align="left">
+                              <p>
+                    More information about XInclude can be found in <a class="xref" href="#XSL_Tooling" title="XSL Tools">the section called “XSL Tools”</a>.  XSL Tools
+                    also contains built in content assistance for the XInclude elements.
+                </p>
+                           </td>
+                        </tr>
+                     </table>
+                  </div>
+               </div>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N100BE"/>Version Control</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p> Leveraging Eclipse's built-in version control support with CVS or adding a open
+               source or third party plugin for another version control system, makes maintaining
+               and working on the documentation as convenient as working on any source code for a
+               program. The same comparison and merging abilities that are used with source code for
+               programs can be leveraged for the authoring process as well. Compare this to trying
+               to work with formats that are stored in a binary format and the speed advantage
+               becomes clear pretty quickly. When dealing with a binary formatted file, typically a
+               locking mechanism has to be implemented. Working with DocBook since it is a text
+               format, allows one to take advantage of agile development practices as Continuous
+               Integration and automated builds. Documentation does not have to become a thing that
+               is put to the end. It should become a part of the standard build process.</p>
+               </div>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N100C3"/>Formatting</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p> As stated earlier. The advantage that an XML format has is that it allows
+               presentation and content to be separated. The formatting of the document is
+               independent of the content. One of the most time consuming parts of creating
+               documentation is making sure the formatting is the same. Traditionally if you move
+               sections or cut and paste content from another source, it messes up the formatting of
+               the document. With DocBook you don't run into this issue, as the formatting is
+               controlled during the publication phase. Thus freeing up time that the author would
+               have to spend trying to make the document legible, to make sure that they have the
+               necessary content correct.</p>
+               </div>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N100C8"/>One Source, Multiple Targets</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p> DocBook, allows for one source content to be generated into multiple formats.
+               Typically DocBook is published in PDF, but it is also widely used for web pages,
+               multi-sectioned HTML pages, Tex, and RTF formats as well. The author does not need to
+               worry about any of these formats or how it will necessarily look as that is taken
+               care of by the publishing process. Typically with an XSL stylesheet that already
+               contains the necessary formatting information.</p>
+               </div>
+            </div>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N100CD"/>Examples</h2>
+                  </div>
+               </div>
+            </div>
+            <p>
+         To show the authoring tool chain in Eclipse, this article will use the DocBook file that
+         was used to write this article. The XML version of the document can be seen
+         <a class="ulink" href="../AuthoringWithEclipse.xml" target="_new">here</a>
+      </p>
+            <div class="section" lang="en">
+               <div class="titlepage">
+                  <div>
+                     <div>
+                        <h3 class="title">
+                           <a name="N100D6"/>The Right Tool for the Right Job.</h3>
+                     </div>
+                  </div>
+               </div>
+               <p> In order to write an article or a book with DocBook, one needs an editor. Preferably
+            one that understands the XML dialect and it's supporting tools. The eclipse Web Standard
+            Tools project comes with the necessary tools that are needed. The XML editing support
+            provides the following functionality:</p>
+               <div class="itemizedlist">
+                  <ul type="disc">
+                     <li>
+                        <p> Validation - the ability to check for syntax errors against a specified
+                  grammar. A grammar in this case can be either a DTD or XML Schema for the XML that
+                  is being edited. The XML editor also contains as you type validation to always
+                  keep your XML well formed and valid according the grammar provided.</p>
+                     </li>
+                     <li>
+                        <p> Syntax Coloring - Working with XML is much easier of the tags can be easily
+                  separated from the content.</p>
+                     </li>
+                     <li>
+                        <p> Content Assistance - If a grammar is detected for the XML file that has been
+                  loaded, then content assistance is available for the tags and attributes. This is
+                  activated using CTRL+SPACE. Also any templates that may be available from the XML
+                  templates preference page will be displayed as well.</p>
+                     </li>
+                  </ul>
+               </div>
+               <p> The XML editor provided by Web Standard Tools is just the first tool that you will
+            need, but it will be the one that is used the most. The next will be the DocBook XSL
+            stylesheets provided by the DocBook Project. This is is a set of XSL stylesheets that
+            can transform the DocBook files into something that is actually readable. Output formats
+            include HTML, Tex, RTF, and even PDF via XSL-FO.</p>
+               <p> The examples that are shown here are all built using tools that are available at
+            eclipse. Only when we get to the PDF publication do we need to leverage a plugin that
+            isn't available from eclipse directly, but is available as free software. More when PDF
+            generation is covered later in the article.</p>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N100E9"/>Creation and Review</h4>
+                        </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">Note</th>
+                        </tr>
+                        <tr>
+                           <td valign="top" align="left">
+                              <p> The following section is taken primarily from the original article. Some
+                  updating has been done to update the content.</p>
+                           </td>
+                        </tr>
+                     </table>
+                  </div>
+                  <p> Although creation and review are two separate parts of the technical
+               documentation process, the same tools are required and therefore will be discussed
+               together.</p>
+                  <p>
+               As you may already know, the Eclipse project is composed of several top-level
+               projects including Eclipse itself (known as the Eclipse base) and the WTP project.
+               WTP adds many tools to the Eclipse base including an XML editor with graphical and
+               source representations of the content. Although the graphical editor is useful for
+               viewing the document, the source editor, shown in
+               <a class="xref" 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"/>
+                     <p class="title">
+                        <b>Figure 1. The XML Source Editor</b>
+                     </p>
+                     <div class="figure-contents">
+                        <div class="mediaobject" align="center">
+                           <img src="images/xmlsourceeditor.gif" align="middle" alt="The XML Source Editor"/>
+                        </div>
+                     </div>
+                  </div>
+                  <br class="figure-break"/>
+                  <p> In addition to the features discussed previously, Web Standard Tools provides
+               additional XML functionality.</p>
+                  <div class="itemizedlist">
+                     <ul type="disc">
+                        <li>
+                           <p>
+                     <span class="emphasis">
+                                 <em>Outline View</em>
+                              </span>
+                     - Assists you in editing and viewing the content of your document.
+                  </p>
+                        </li>
+                        <li>
+                           <p>
+                     <span class="emphasis">
+                                 <em>XML Catalog</em>
+                              </span>
+                     - Allows you to register Document Type Definitions (DTD) and XML Schema
+                     grammars associated with your document with your workspace so you can work with
+                     the benefits of validation while disconnected from the Internet.
+                  </p>
+                        </li>
+                     </ul>
+                  </div>
+                  <p> Aside from the benefits of the XML editor, working in Eclipse provides other
+               benefits. Eclipse includes integrated version control for CVS. There also exists
+               freely available plugins for Subversion as well. Integrated version control allows
+               you to check your changes into, and view others' changes in, your version control
+               system from within Eclipse. These tools are also useful for your reviewers, who, if
+               you give them permission, can add comments and suggestions to your document and check
+               their changes in. Giving your reviewers permission to make these changes allows you
+               to avoid the need to use e-mail or some other communication mechanism.</p>
+               </div>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="XSL_Tooling"/>XSL Tools</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p>
+            Chris and Lawerence's original article used an open source plugin called "Orangevolt XSLT", to
+            provide the publication steps that are discussed later in the article.  However, since the
+            publication of the original article, eclipse now has it's own XSL Tools project.   This is
+            currently incubating under the eclipse Web Tools Project, but it provides the same functionality
+            and more.
+         </p>
+                  <p>
+            
+            One such new feature is the XML perspective as shown in <a class="xref" href="#XML_Perspective" title="Figure 2. XML Perspective">Figure 2, “XML Perspective”</a>
+         </p>
+                  <div class="figure">
+                     <a name="XML_Perspective"/>
+                     <p class="title">
+                        <b>Figure 2. XML Perspective</b>
+                     </p>
+                     <div class="figure-contents">
+                        <div class="mediaobject" align="center">
+                           <img src="images/XMLPerspective.png" align="middle" alt="XML Perspective"/>
+                        </div>
+                     </div>
+                  </div>
+                  <br class="figure-break"/>
+                  <p>
+            The XML perspective provides the basic views that are most important for
+            working with XML related content.   The XPath View allows the user to
+            run XPath Expressions against the data that is in the current XML based editor.
+            It show the xpath expression for the current location with in the editor.
+         </p>
+                  <p>
+            In addition to the XML perspective XSL Tools provides the following additional
+            features and functions.
+         </p>
+                  <div class="itemizedlist">
+                     <ul type="disc">
+                        <li>
+                           <p>
+                    XSL Editor - an XSL 1.0 and XSL 2.0 grammar aware editor.   Providing
+                    content assistance for XSL, as well as XML namespaced content included
+                    within the XSL editor.   Content assistance is also available for XPath
+                    1.0 in select and test attributes.
+                </p>
+                        </li>
+                        <li>
+                           <p>
+                    XSL Debugging - Developing or working with XSL stylesheets requires the
+                    use of an debugger at times.  The XSL Tools provides launch configurations
+                    and debugging support for the Xalan 2.7.1 processor.   Extension points
+                    are available for adopters to add additional processors for debugging and
+                    launching.
+                </p>
+                        </li>
+                        <li>
+                           <p>
+                    XSL File Wizards - Wizards are available for creating new XSL files. Templates
+                    can be provided for a variety of XSL patterns.
+                </p>
+                        </li>
+                        <li>
+                           <p>
+                    XPath and XSL Preference Settings - Additional configuration is available
+                    through the XSL and XPath preference pages.  Templates can be created as well
+                    as choosing the default parser to use during transformations.
+                </p>
+                        </li>
+                        <li>
+                           <p>
+                    XSL Launch Configurations - The user has the ability to setup launch
+                    configurations for transforming XSL.   ANT launch configurations are
+                    also supported for more complex scenarios.
+                </p>
+                        </li>
+                        <li>
+                           <p>
+                    XInclude ANT Task - An ant task is available that allows for the use of
+                    XInclude pre-processing of XML files.  XInclude allows for a way to include
+                    XML or text based content into XML file and merge the two files together.
+                    This is one way to provide the Modularity benefit that working with an
+                    XML format provides.
+                </p>
+                        </li>
+                     </ul>
+                  </div>
+               </div>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N1013C"/>Publication</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p>
+               The DocBook XSL
+               <a class="xref" href="#docbookxsl" title="???TITLE???">[3]</a>
+               project offers numerous transformations, including HTML and PDF formats. The most
+               common transformation technique is to use an Ant file with the appropriate tasks for
+               the various transformations. In this article we use the XSL Tools set of plugins to
+               simplify this task. XSL Tools integrates into the familiar Eclipse launcher
+               framework. This integration allows you to select the style sheet and pass in
+               necessary parameters for the transformation.
+            </p>
+                  <div class="section" lang="en">
+                     <div class="titlepage">
+                        <div>
+                           <div>
+                              <h5 class="title">
+                                 <a name="N10144"/>HTML</h5>
+                           </div>
+                        </div>
+                     </div>
+                     <p> Of all the available transformations, transforming your document into HTML is
+                  the easiest to use. All that you need to do is create a proper transformation
+                  launch configuration and run the transformation. Specifically, you need to specify
+                  the correct style sheet:</p>
+                     <div class="itemizedlist">
+                        <ul type="disc">
+                           <li>
+                              <p>DocBook</p>
+                              <div class="itemizedlist">
+                                 <ul type="circle">
+                                    <li>
+                                       <p>html/docbook.xsl</p>
+                                    </li>
+                                 </ul>
+                              </div>
+                           </li>
+                        </ul>
+                     </div>
+                     <p>
+                  <a class="xref" href="#html-transformation" title="Figure 3. Sample HTML Transformation Configuration for book.xml">Figure 3, “Sample HTML Transformation Configuration for book.xml”</a>
+                  shows a sample transformation configuration that will transform our DocBook sample
+                  <a class="ulink" href="files/book.xml" target="_new">document</a>
+                  into HTML.
+               </p>
+                     <div class="figure">
+                        <a name="html-transformation"/>
+                        <p class="title">
+                           <b>Figure 3. Sample HTML Transformation Configuration for book.xml</b>
+                        </p>
+                        <div class="figure-contents">
+                           <div class="mediaobject" align="center">
+                              <table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="741">
+                                 <tr style="height: 592px">
+                                    <td align="center">
+                                       <img src="images/html.jpg" align="middle" width="741" alt="Sample HTML Transformation Configuration for book.xml"/>
+                                    </td>
+                                 </tr>
+                              </table>
+                           </div>
+                        </div>
+                     </div>
+                     <br class="figure-break"/>
+                     <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">Tip</th>
+                           </tr>
+                           <tr>
+                              <td valign="top" align="left">
+                                 <p>
+                     The transformation can be augment by passing parameters to the style sheet.
+                     There is a full listing of DocBook XSL parameters that can be used to configure
+                     the transformation located at 
+                     <a class="ulink" href="http://docbook.sourceforge.net/release/xsl/current/doc/html/" target="_new">The DocBook Project.</a>
+                     .
+                  </p>
+                                 <p>
+                     Bob Stayton has also written
+                     <a class="ulink" href="http://www.sagehill.net/docbookxsl/" target="_new">Docbook XSL: The Complete Guide</a>
+                     which is available on line and in print format. This book describes how to
+                     customize the DocBook stylesheets beyond those that you can do with the
+                     parameters. XSL Tools provides an XSL aware XML editor that can be used
+                     to help create and debug the stylesheets.
+                  </p>
+                              </td>
+                           </tr>
+                        </table>
+                     </div>
+                     <p>
+                    In addition to setting up the Main tab for the stylesheet to use.  The the output location
+                    and the processor that will be used may need to be changed.  By default the
+                    transformation output will be placed into the same location as the input file, with the
+                    extensions ".out.xml".
+               </p>
+                  </div>
+                  <div class="section" lang="en">
+                     <div class="titlepage">
+                        <div>
+                           <div>
+                              <h5 class="title">
+                                 <a name="N10175"/>PDF</h5>
+                           </div>
+                        </div>
+                     </div>
+                     <p> Transforming a DocBook XML file to PDF format is more involved than the
+                  transformation to HTML but it is still possible using a style sheet. The
+                  difference lies in a task that must be performed before the actual transformation.
+                  So, the transformation from XML to PDF is a two-step process.</p>
+                     <p>
+                  Step one is to generate an XSL formatting objects (XSL-FO) document. This document
+                  will then be transformed into a PDF. In order to generate an XSL-FO document, you
+                  need to use the following stylesheet:
+                  <span class="emphasis">
+                           <em>fo/docbook.xsl</em>
+                        </span>
+                  .
+                  <a class="xref" href="#xslfo-transformation" title="Figure 4. Sample XSL-FO Transformation Configuration for book.xml">Figure 4, “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"/>
+                        <p class="title">
+                           <b>Figure 4. Sample XSL-FO Transformation Configuration for book.xml</b>
+                        </p>
+                        <div class="figure-contents">
+                           <div class="mediaobject" align="center">
+                              <img src="images/xsl-fo.png" align="middle" alt="Sample XSL-FO Transformation Configuration for book.xml"/>
+                           </div>
+                        </div>
+                     </div>
+                     <br class="figure-break"/>
+                     <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 open source FOPs is the
+                  <a class="ulink" href="http://xmlgraphics.apache.org/fop/" target="_new"> Apache FOP</a>
+                  . We'll use a third-party
+                  <a class="ulink" href="http://www.ahmadsoft.org/fopbridge.html" target="_new"> plug-in from Ahmadsoft</a>
+                  that integrates Apache FOP into Eclipse. After installing this plug-in, all that
+                  you need to do to render the XSL-FO document is run the FOP transformation.
+                  <a class="xref" href="#pdf-transformation" title="Figure 5. Sample FOP Transformation">Figure 5, “Sample FOP Transformation”</a>
+                  shows an example of running the FOP transformation.
+               </p>
+                     <div class="figure">
+                        <a name="pdf-transformation"/>
+                        <p class="title">
+                           <b>Figure 5. Sample FOP Transformation</b>
+                        </p>
+                        <div class="figure-contents">
+                           <div class="mediaobject" align="center">
+                              <img src="images/fop.png" align="middle" alt="Sample FOP Transformation"/>
+                           </div>
+                        </div>
+                     </div>
+                     <br class="figure-break"/>
+                     <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">Note</th>
+                           </tr>
+                           <tr>
+                              <td valign="top" align="left">
+                                 <p>
+                     The example includes a sample Ant
+                     <a class="ulink" href="files/pdf/build.xml" target="_new"> file</a>
+                     that performs the same transformation as running the FOP transformation using
+                     the
+                     <a class="ulink" href="http://www.ahmadsoft.org/fopbridge.html" target="_new"> plug-in from Ahmadsoft</a>
+                     . An Ant script is a popular method of performing the publishing stage, and
+                     this example should give you a good starting point if you'd prefer to go this
+                     route.
+                  </p>
+                              </td>
+                           </tr>
+                        </table>
+                     </div>
+                  </div>
+                  <div class="section" lang="en">
+                     <div class="titlepage">
+                        <div>
+                           <div>
+                              <h5 class="title">
+                                 <a name="N101AE"/>Eclipse Help</h5>
+                           </div>
+                        </div>
+                     </div>
+                     <p>
+                  The DocBook Project includes a XSL stylesheet that can be used to create the 
+                  necessary files for the eclipse help system. In order to perform this 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 class="xref" href="#eclipse-transformation" title="Figure 6. Sample Eclipse Help Transformation Configuration">Figure 6, “Sample Eclipse Help Transformation Configuration”</a>
+                  shows a sample transformation configuration along with the correct parameters.
+               </p>
+                     <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">Note</th>
+                           </tr>
+                           <tr>
+                              <td valign="top" align="left">
+                                 <p>
+                        The eclipse help stylesheet included with DocBook creates a plugin.xml
+                        and toc.xml file only.  In addition to the configuration information shown
+                        the xalan.jar extension included with DocBook is required as the transformation
+                        leverages the chunk.xsl file from the html stylesheet directory to output multiple
+                        html files, and build to the necessary toc.xml file.
+                   </p>
+                              </td>
+                           </tr>
+                        </table>
+                     </div>
+                     <div class="figure">
+                        <a name="eclipse-transformation"/>
+                        <p class="title">
+                           <b>Figure 6. Sample Eclipse Help Transformation Configuration</b>
+                        </p>
+                        <div class="figure-contents">
+                           <div class="mediaobject" align="center">
+                              <img src="images/eclipse.png" align="middle" alt="Sample Eclipse Help Transformation Configuration"/>
+                           </div>
+                        </div>
+                     </div>
+                     <br class="figure-break"/>
+                     <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">Tip</th>
+                           </tr>
+                           <tr>
+                              <td valign="top" align="left">
+                                 <p>
+                     The complete list of DocBook XSL parameters for the Eclipse Infocenter
+                     transformation is located
+                     <a class="ulink" href="http://docbook.sourceforge.net/release/xsl/current/doc/html/rn22.html" target="_new"> here</a>
+                     .
+                  </p>
+                              </td>
+                           </tr>
+                        </table>
+                     </div>
+                  </div>
+               </div>
+               <div class="section" lang="en">
+                  <div class="titlepage">
+                     <div>
+                        <div>
+                           <h4 class="title">
+                              <a name="N101CD"/>Prior Limitations</h4>
+                        </div>
+                     </div>
+                  </div>
+                  <p> Chris and Lawrence's original article outline two short comings with eclipse as an authoring
+            environment.
+            </p>
+                  <div class="itemizedlist">
+                     <ul type="disc">
+                        <li>
+                           <p>
+                        No Grammar and Spell Checking.
+                    </p>
+                        </li>
+                        <li>
+                           <p>
+                        No preview screen or WSYIWG editor for documentation.
+                    </p>
+                        </li>
+                     </ul>
+                  </div>
+                  <p>
+                The first limitation has been addressed since eclipse 3.3.  Eclipse includes a spell checker and 
+                the Web Standard Tools XML editor leverages this support.   Users may add their own custom dictionary or
+                add any of the freely available dictionaries available on the Internet. 
+            </p>
+                  <p>
+                The second item may or may not be a limitation depending on the point of view.  The advantage of DocBook is
+                that it separates the content from the presentation.   Worrying about the presentation while creating the
+                content may not be the best thing to do.  The main reason is that how it is formatted is going to greatly
+                depend on the target platforms the documentation is intended.   DocBook authoring is not the same as
+                using a traditional word processor.  A different way of thinking of documentation needs to be approached.  The
+                formatting is not the critical piece, but it is the content of the document that matters the most.
+            </p>
+               </div>
+            </div>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N101DD"/>Summary</h2>
+                  </div>
+               </div>
+            </div>
+            <p> 
+        Since the original article was published, many advancements have been made with the XML support for eclipse.  The
+        editors are faster, there is better tooling support, and the DocBook grammar it self has advanced.  However, the 
+        overall process that Chris and Lawrence had described is fundamentally unchanged three years later.  Eclipse is a
+        perfectly suitable authoring system for technical documentation.  
+      </p>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N101E2"/>Acknowledgments</h2>
+                  </div>
+               </div>
+            </div>
+            <div class="itemizedlist">
+               <ul type="disc">
+                  <li>
+                     <p> Chris Aniszczyk and Lawrence Mandel for their original article title,
+                  "Authoring With Eclipse".</p>
+                  </li>
+               </ul>
+            </div>
+         </div>
+         <div class="section" lang="en">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title" style="clear: both">
+                        <a name="N101E9"/>About the Author</h2>
+                  </div>
+               </div>
+            </div>
+            <p>
+         David Carver is an XML Data Architect for Standards for Technology in Automotive Retail. He
+         is also a committer on the
+         <a class="ulink" href="http://www.eclipse.org/webtools/incubator" target="_new">XSL Tools</a>
+         project.
+      </p>
+         </div>
+         <div class="bibliography">
+            <div class="titlepage">
+               <div>
+                  <div>
+                     <h2 class="title">
+                        <a name="N101F2"/>Resources</h2>
+                  </div>
+               </div>
+            </div>
+            <div class="biblioentry">
+               <a name="authoringwitheclipse"/>
+               <p>[1] <span class="authorgroup">
+                     <span class="firstname">Chris</span> <span class="surname">Aniszczyk</span> and <span class="firstname">Lawrence</span> <span class="surname">Mandel</span>. </span>
+                  <span class="title">
+                     <i>Authoring with Eclipse</i>. </span>
+                  <span class="bibliosource">
+            <a class="ulink" href="http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html" target="_new">http://www.eclipse.org/articles/article.php?file=Article-Authoring-With-Eclipse/index.html</a>
+        . </span>
+                  <span class="date">Dec 2005. </span>
+               </p>
+            </div>
+            <div class="biblioentry">
+               <a name="docbook"/>
+               <p>[2] <span class="author">
+                     <span class="firstname">Norman</span> <span class="surname">Walsh</span>. </span>
+                  <span class="bibliosource">
+            <a class="ulink" href="http://www.docbook.org" target="_new">Docbook.org - The Source for Documentation.</a>
+         . </span>
+                  <span class="date">24 Jun 2008. </span>
+               </p>
+            </div>
+            <div class="biblioentry">
+               <a name="docbookxsl"/>
+               <p>[3] <span class="bibliosource">
+            <a class="ulink" href="http://docbook.sourceforge.net/projects/xsl/" target="_new"> DocBook XSL Style Sheets</a>
+         . </span>
+                  <span class="date">24 Jun 2008. </span>
+               </p>
+            </div>
+            <div class="biblioentry">
+               <a name="subversion"/>
+               <p>[4] <span class="bibliosource">
+            <a class="ulink" href="http://subversion.tigris.org/" target="_new">Subversion</a>
+         . </span>
+                  <span class="date">24 Jun 2008. </span>
+               </p>
+            </div>
+            <div class="biblioentry">
+               <a name="whousesdocbook"/>
+               <p>[5] <span class="bibliosource">
+            <a class="ulink" href="http://wiki.docbook.org/topic/WhoUsesDocBook" target="_new">Who Uses DocBook</a>
+         . </span>
+                  <span class="date">24 Jun 2008. </span>
+               </p>
+            </div>
+         </div>
+         <p/>
+         <h3>Trademarks</h3>
+         <div>
+            <div class="legalnotice">
+               <a name="N10035"/>
+               <p> Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
+            United States, other countries, or both.</p>
+               <p> Linux is a trademark of Linus Torvalds in the United States, other countries, or
+            both.</p>
+               <p> Microsoft is a trademark of Microsoft Corporation in the United States, other
+            countries, or both.</p>
+               <p> UNIX is a registered trademark of The Open Group in the United States and other
+            countries.</p>
+               <p> Other company, product, or service names may be trademarks or service marks of
+            others.</p>
+            </div>
+         </div>
+      </div>
+   </body>
+</html>
diff --git a/Article-Authoring-With-Eclipse/output/default_style.css b/Article-Authoring-With-Eclipse/output/default_style.css
new file mode 100644
index 0000000..44fa78e
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/default_style.css
@@ -0,0 +1,12 @@
+p, table, td, th {  font-family: arial, helvetica, geneva; font-size: 10pt}

+pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}

+h2 { font-family: arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}

+code {  font-family: "Courier New", Courier, mono; font-size: 10pt}

+sup {  font-family: arial,helvetica,geneva; font-size: 10px}

+h3 {  font-family: arial, helvetica, geneva; font-size: 14pt; font-weight: bold}

+li {  font-family: arial, helvetica, geneva; font-size: 10pt}

+h1 {  font-family: arial, helvetica, geneva; font-size: 28px; font-weight: bold}

+body {  font-family: arial, helvetica, geneva; font-size: 10pt; clip:   rect(   ); margin-top: 5mm; margin-left: 3mm}

+.indextop { font-size: x-large;; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold}

+.indexsub { font-size: xx-small;; font-family: Arial, Helvetica, sans-serif; color: #8080FF}

+.corner { color: #FFFFFF; font-weight: bold; }
\ No newline at end of file
diff --git a/Article-Authoring-With-Eclipse/output/images/Idea.jpg b/Article-Authoring-With-Eclipse/output/images/Idea.jpg
new file mode 100644
index 0000000..119ce70
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/Idea.jpg
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/XMLPerspective.png b/Article-Authoring-With-Eclipse/output/images/XMLPerspective.png
new file mode 100644
index 0000000..ed7d32d
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/XMLPerspective.png
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/eclipse.png b/Article-Authoring-With-Eclipse/output/images/eclipse.png
new file mode 100644
index 0000000..8a67f5d
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/eclipse.png
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/fop.png b/Article-Authoring-With-Eclipse/output/images/fop.png
new file mode 100644
index 0000000..abf87a8
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/fop.png
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/html.jpg b/Article-Authoring-With-Eclipse/output/images/html.jpg
new file mode 100644
index 0000000..6e8566a
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/html.jpg
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/linux_only.gif b/Article-Authoring-With-Eclipse/output/images/linux_only.gif
new file mode 100644
index 0000000..7c135cf
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/linux_only.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/note.gif b/Article-Authoring-With-Eclipse/output/images/note.gif
new file mode 100644
index 0000000..e4e81a9
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/note.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_1.gif b/Article-Authoring-With-Eclipse/output/images/tag_1.gif
new file mode 100644
index 0000000..4859d6f
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_1.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_2.gif b/Article-Authoring-With-Eclipse/output/images/tag_2.gif
new file mode 100644
index 0000000..5ea43dc
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_2.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_3.gif b/Article-Authoring-With-Eclipse/output/images/tag_3.gif
new file mode 100644
index 0000000..a69b68e
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_3.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_4.gif b/Article-Authoring-With-Eclipse/output/images/tag_4.gif
new file mode 100644
index 0000000..a1ad63f
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_4.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_5.gif b/Article-Authoring-With-Eclipse/output/images/tag_5.gif
new file mode 100644
index 0000000..d86a748
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_5.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_6.gif b/Article-Authoring-With-Eclipse/output/images/tag_6.gif
new file mode 100644
index 0000000..b9eb4ec
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_6.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tag_7.gif b/Article-Authoring-With-Eclipse/output/images/tag_7.gif
new file mode 100644
index 0000000..5f0e8fa
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tag_7.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tip.gif b/Article-Authoring-With-Eclipse/output/images/tip.gif
new file mode 100644
index 0000000..77b2451
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tip.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/tryit.gif b/Article-Authoring-With-Eclipse/output/images/tryit.gif
new file mode 100644
index 0000000..f4927a4
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/tryit.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/vex.png b/Article-Authoring-With-Eclipse/output/images/vex.png
new file mode 100644
index 0000000..a2b729d
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/vex.png
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/win_only.gif b/Article-Authoring-With-Eclipse/output/images/win_only.gif
new file mode 100644
index 0000000..895f9ca
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/win_only.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/xmlsourceeditor.gif b/Article-Authoring-With-Eclipse/output/images/xmlsourceeditor.gif
new file mode 100644
index 0000000..0b32c22
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/xmlsourceeditor.gif
Binary files differ
diff --git a/Article-Authoring-With-Eclipse/output/images/xsl-fo.png b/Article-Authoring-With-Eclipse/output/images/xsl-fo.png
new file mode 100644
index 0000000..7529d3c
--- /dev/null
+++ b/Article-Authoring-With-Eclipse/output/images/xsl-fo.png
Binary files differ
diff --git a/article.css b/article.css
index 250f843..5389dfb 100644
--- a/article.css
+++ b/article.css
@@ -49,6 +49,14 @@
 	font-size: 80%;
 }
 
+.releaseinfo {
+	font-size: 80%;
+}
+
+.remark {
+	font-size: 80%;
+}
+
 .copyright {
 	font-size: 80%;
 }
@@ -78,6 +86,18 @@
 	font-style: italic;
 }
 
+.content h4 {
+	font-family: sans-serif;
+	font-size: 110%;
+	font-style: italic;
+}
+
+.content h5 {
+	font-family: sans-serif;
+	font-size: 100%;
+	font-style: italic;
+}
+
 .content p {
 	font-family: serif;
 	font-size: 100%;
diff --git a/article.xsl b/article.xsl
index 92e9565..3b985d4 100644
--- a/article.xsl
+++ b/article.xsl
@@ -1,6 +1,6 @@
 <?xml version='1.0'?>
 <!--
-	$Id: article.xsl,v 1.5 2008/01/16 03:29:08 wbeaton Exp $
+	$Id: article.xsl,v 1.6 2008/09/09 02:24:07 wbeaton Exp $
 	author: Chris Aniszczyk <zx@us.ibm.com>
 	author: Lawrence Mandel <lmandel@ca.ibm.com>
 -->
@@ -55,6 +55,11 @@
 				<xsl:apply-templates mode="article.titlepage.recto.mode"
 					select="articleinfo/date" />
 			</div>
+			<div class="releaseinfo">
+				<xsl:for-each select="articleinfo/releaseinfo">
+					<xsl:apply-templates select="*"/>
+				</xsl:for-each>
+			</div>
 		</div>
 
 		<div class="content">
@@ -125,4 +130,8 @@
 		</ul>
 	</xsl:template>
 	
+	
+	<xsl:template name="releaseinfo">
+		<xsl:apply-templates select="remark"/>
+	</xsl:template>
 </xsl:stylesheet>
\ No newline at end of file