You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by wa...@apache.org on 2020/11/02 20:37:39 UTC

[openoffice-org] 02/02: Migration of xml html content

This is an automated email from the ASF dual-hosted git repository.

wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git

commit 8cb3052ec6e95f8c764af6a24be96e08e6253f52
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Mon Nov 2 12:37:15 2020 -0800

    Migration of xml html content
---
 content/xml/faq.html                               |  295 +++++
 content/xml/filter/index.html                      |  685 ++++++++++++
 content/xml/filters.html                           |   11 +
 content/xml/general.html                           |  151 +++
 content/xml/index.html                             |   94 ++
 content/xml/index2.html                            |   93 ++
 content/xml/modules.html                           |   10 +
 content/xml/oasis/index.html                       |   43 +
 content/xml/odf2xhtml/index.html                   |   41 +
 .../optimization/current_optimization_status.html  |  121 ++
 content/xml/optimization/optimization.html         |  748 +++++++++++++
 content/xml/optimization/optimization2.html        |  115 ++
 content/xml/package.html                           |  804 ++++++++++++++
 content/xml/project_tools.html                     |   46 +
 content/xml/research.html                          |   10 +
 content/xml/saxecho/index.html                     |   63 ++
 content/xml/standardisation/index.html             |   68 ++
 content/xml/sx2ml/index.html                       |  301 +++++
 content/xml/uses.html                              |   11 +
 content/xml/xfilter.html                           |  128 +++
 content/xml/xforms/index.html                      |   10 +
 content/xml/xmerge/background.html                 |  258 +++++
 content/xml/xmerge/docbook/DocBookTags.html        |  951 ++++++++++++++++
 content/xml/xmerge/docbook/UserGuide.html          |    2 +
 content/xml/xmerge/docbook/index.html              |  196 ++++
 .../xml/xmerge/docbook/supported_tag_table.html    | 1156 ++++++++++++++++++++
 content/xml/xmerge/docbook/tag_usage.html          |  319 ++++++
 content/xml/xmerge/docbook/temp_test_only.html     |  252 +++++
 content/xml/xmerge/downloads/gedit.html            |  201 ++++
 content/xml/xmerge/downloads/index.html            |  186 ++++
 content/xml/xmerge/index.html                      |  375 +++++++
 content/xml/xmerge/plugins/aportisdoc.html         |  184 ++++
 content/xml/xmerge/plugins/minicalc.html           |  213 ++++
 content/xml/xmerge/plugins/pexcel_formulas.html    |  330 ++++++
 content/xml/xmerge/plugins/pocketexcel.html        |  204 ++++
 content/xml/xmerge/plugins/pocketword.html         |  373 +++++++
 content/xml/xmerge/starlite.html                   |  248 +++++
 content/xml/xml_advocacy.html                      |  331 ++++++
 38 files changed, 9627 insertions(+)

diff --git a/content/xml/faq.html b/content/xml/faq.html
new file mode 100644
index 0000000..a85efcc
--- /dev/null
+++ b/content/xml/faq.html
@@ -0,0 +1,295 @@
+<!DOCTYPE html>
+<html><head>
+<title>OpenOffice.org XML file format FAQ</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+	<p><strong>Note:</strong>This FAQ is for the OpenOffice.org XML file format only. OASIS OpenDocument/ISO/IEC 26300 FAQs are available at <a href="http://www.oasis-open.org/committees/office/faq.php">OASIS</a> and <a href="http://opendocument.xml.org/faq">opendocument.xml.org</a>.<p>
+<a name="top"></a><p><img alt="" src="http://www.openoffice.org/branding/images/start_blue_bar.gif">&nbsp;&nbsp;<font size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS: QUESTIONS</b></font>&nbsp;&nbsp;<img alt="" src="http://www.openoffice.org/branding/images/end_blue_bar.gif"></p><ol>
+
+ <li><a href="#1">
+    Which OpenOffice.org application uses XML-based file formats?
+  </a></li>
+
+ <li><a href="#2">
+    What are the default file extensions for XML-based documents?
+  </a></li>
+
+ <li><a href="#3">
+    What is all that binary goo I see in your files?
+  </a></li>
+
+ <li><a href="#4">
+    What package format do you use, and what do I find inside?    
+  </a></li>
+
+ <li><a href="#5">
+    How can I put additional information into an XML file?
+  </a></li>
+
+ <li><a href="#6">
+    But I really, really want plain XML. No compression, no binary
+    data, no nothing. Just plain XML. Can I have that, please?
+  </a></li>
+
+ <li><a href="#7">
+    Why are so many styles written out?
+  </a></li>
+
+ <li><a href="#8">
+    How are embedded images and binary data handled?
+  </a></li>
+
+ <li><a href="#9">
+    Why didn't you use XHTML, XSL-FO, SVG, etc. ?
+  </a></li>
+
+ <li><a href="#10">
+    Can I write an XML translation from or into  ...?
+  </a></li>
+
+ <li><a href="#11">
+    I found a bug. What do I do?
+  </a></li>
+
+ <li><a href="#12">
+    Hey, I like your XML format. How can I help?
+  </a></li>
+
+ <li><a href="#13">
+    But what about ...? And why isn't
+    my favorite question in here?
+  </a></li>
+
+ 
+
+</ol><p><img alt="" src="http://www.openoffice.org/branding/images/start_blue_bar.gif">&nbsp;&nbsp;<font size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS: ANSWERS</b></font>&nbsp;&nbsp;<img alt="" src="http://www.openoffice.org/branding/images/end_blue_bar.gif"></p>
+
+ <ol><a name="1"></a><li value="1"><b>
+    Which OpenOffice.org application uses XML-based file formats?
+  </b><p><answer>
+    All OpenOffice.org applications use XML-based file formats. All
+    applications (except Math) use the same format as defined in our <a href="xml_specification.pdf">specification</a>. 
+    The Math component uses our package structure and format (see
+    below), but uses <a href="http://www.w3.org/Math/">MathML</a>
+    inside the package.
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="2"></a><li value="2"><b>
+    What are the default file extensions for XML-based documents?
+  </b><answer>
+    <table summary="OpenOffice.org XML file types">
+     <tr> <th>Writer</th> <td>sxw</td> </tr>
+     <tr> <th>Calc</th> <td>sxc</td> </tr>
+     <tr> <th>Draw</th> <td>sxd</td> </tr>
+     <tr> <th>Impress</th> <td>sxi</td> </tr>
+     <tr> <th>Math</th> <td>sxm</td> </tr>
+     <tr> <th>Writer<br>global document</th> <td>sxg</td> </tr>
+    </table>
+    <p>XML is also used in other OpenOffice.org files
+    (e.g. configuration) which are not covered in the <tt>xmloff</tt> 
+    project.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="3"></a><li value="3"><b>
+    What is all that binary goo I see in your files?
+  </b><answer>
+    <p>Our documents use packages that contain the XML data alongside
+    binary data such as images. The packages use the well known ZIP format. 
+    Just open an sxw/sxc/... file with a ZIP-tool of your choice, and 
+    you get access to the unadulterated XML.</p>
+    <p>The document meta data (in the meta.xml stream) is not
+    compressed. This allows for easy searching and extraction of the
+    meta data.</p>
+    <p> For more information on our packages, see the next question. </p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="4"></a><li value="4"><b>
+    What package format do you use, and what do I find inside?    
+  </b><answer>
+
+    <p>We use the well-known ZIP file format as a package format. In
+    addition, we store an XML-based manifest file that describes the
+    package content and may supply additional information about the
+    included files (e.g. encryption method). Since we use ZIP, most
+    archive programs can already handle our files.</p>
+
+    <p>Inside the package, you generally find several streams that
+    make up the full office document. These are: </p>
+
+    <table>
+     <tr> 
+      <th>meta.xml</th> 
+      <td>information about the document (author, time of last save, ...)</td>
+     </tr>
+     <tr>
+      <th>styles.xml</th>
+      <td>styles that are used in the document</td>
+     </tr>
+     <tr>
+      <th>content.xml</th>
+      <td>main document content (text, tables, graphical elements)</td>
+     </tr>
+     <tr>
+      <th>settings.xml</th>
+      <td>document and view settings (such as magnification level and 
+          selected printer); these are usually application specific </td>
+     </tr>
+     <tr>
+      <th>META-INF/manifest.xml</th>
+      <td>provides additional information about the other files (such
+      as MIME type or encryption method)</td>
+     </tr>
+     <tr>
+      <th>Pictures/</th>
+      <td>directory containing images (in their native, binary formats)</td>
+     </tr>
+     <tr>
+      <th>Dialogs/</th>
+      <td>directory containing dialogs used by document macros</td>
+     </tr>
+     <tr>
+      <th>Basic/</th>
+      <td>directory containing StarBasic macros</td>
+     </tr>
+     <tr>
+      <th>Obj.../</th>
+      <td>directories containing embedded objects, such as charts;
+      each directory contains one such object, stored in its native format.
+      For OpenOffice.org objects that is its XML representation, for other
+      objects it's usually a binary format.</td>
+     </tr>
+    </table>
+
+    <p>For more information on why we chose ZIP, please read <a href="package.html">package.html</a>. For more information on the
+    ZIP format itself, please look <a href="http://www.wotsit.org/">here</a>.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="5"></a><li value="5"><b>
+    How can I put additional information into an XML file?
+  </b><answer>
+    <p><em>Alien</em> attributes, i.e. attributes not defined in the
+    OpenOffice.org DTD, will be preserved if they are attached to
+    <code>&lt;style:properties&gt;</code> elements in style
+    definitions. All other alien content will be discarded by the
+    OpenOffice.org import filters.</p>
+    <p>Since you can attach styles to arbitrary text ranges, you can
+    use this mechanism to attach your information to arbitrary text
+    ranges, too.</p>
+    <p><strong>Note:</strong> The above mechanism seems to only work
+    in Writer. The issue is under investigation.</p>
+    <p>It is planned that you can also put additional files with your
+    own content into the packages. However, this doesn't work yet.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="6"></a><li value="6"><b>
+    But I really, really want plain XML. No compression, no binary
+    data, no nothing. Just plain XML. Can I have that, please?
+  </b><answer>
+    <p>For purposes of import and export, we provide <a href="http://udk.openoffice.org/">UNO</a>-based services that
+    allow you to import or export XML data through the SAX
+    interface. A documentation of this technique is available <a href="filter/">here</a>.</p>
+    <p>Also, it is planned to allow plain XML files (without packages)
+    to be read and written. However, this is not implemented yet.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="7"></a><li value="7"><b>
+    Why are so many styles written out?
+  </b><answer>
+    <p>In general, styles that are used in the document or that have been
+    modified by the user are written to disk. The former is necessary
+    to render the document correctly. The latter is preserved because
+    if a user edited those styles, he/she is likely to use them later
+    on. Therefore, those styles should not be discarded, even though
+    they do not contribute to the document in its current form and
+    shape.</p>
+    <p>If styles that meet neither of these criteria are written, then
+    this is may be considered a bug. The Draw, Impress, and Calc
+    applications currently show this behavior. </p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="8"></a><li value="8"><b>
+    How are embedded images and binary data handled?
+  </b><p><answer>
+    Images and embedded objects are stored in their native formats
+    into the ZIP-based package format.
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="9"></a><li value="9"><b>
+    Why didn't you use XHTML, XSL-FO, SVG, etc. ?
+  </b><answer>
+    <p>Those formats are not used because they do not have a
+    suitable level of presentation for office documents. When we found an
+    established format (like the ones mentioned above) contains
+    concepts that are used in OpenOffice.org as well, then we
+    generally adopted their representation for those concepts in our
+    XML format. We hope this will ease transformation between the
+    formats.</p>
+
+<!--
+    <p>As an example for the unsuitable level of presentation consider
+    text fields: A text field contains a string of text that gets
+    automatically for this consider text fields: Text fields are
+    special regions of text strings that are automatically updated by
+    the application. The text fields must be preserved, of course, so
+    the application can continue to update them. While the above
+    formats easily accomodate the text field output (after all, it's
+    just a string of text), they can only be represented by some sort
+    of extension to the basic format. Since these sort of issues
+    occur quite a lot, it seemed more prudent to create an own format.</p>
+-->
+
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="10"></a><li value="10"><b>
+    Can I write an XML translation from or into  ...?
+  </b><answer>
+    <p>You are absolutely welcome to write transformation from our
+    XML-based file format into and from anything you see fit.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="11"></a><li value="11"><b>
+    I found a bug. What do I do?
+  </b><answer>
+    <p>Report it using <a href="http://www.openoffice.org/issues/enter_bug.cgi">IssueZilla</a>. Try
+    to give a detailed description of what went wrong. Don't forget to
+    include the document in which the error occurred. (After submission
+    of the bug, choose "create attachment".)</p>
+    <p><strong>DON'T BE SHY ABOUT REPORTING BUGS!</strong> All of us
+    are interested in stable and bug-free applications, and bug
+    reports from our users are a very important means towards that
+    end. Bug reports help all of us. If you don't report your
+    findings, we can't fix them, and so they will cause problems for
+    users as well.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="12"></a><li value="12"><b>
+    Hey, I like your XML format. How can I help?
+  </b><p><answer>
+    There are many things you can do to help.
+    <ol>
+     <li>You can spread the word, e.g. by telling your friends and
+     co-workers about OpenOffice.org.</li>
+     <li>You can use the OpenOffice.org applications and report any
+     bugs you find.</li>
+     <li>You can program transformation from our format into others
+     (and vice versa).</li>
+     <li>You can implement one of the suggestions on the todo list on our homepage. </li>
+    </ol>
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="13"></a><li value="13"><b>
+    But what about ...? And why isn't
+    my favorite question in here?
+  </b><p><answer>
+    If your question is not answered here, ask it on our mailing
+    list. You can view the archives <a href="http://xml.openoffice.org/xml-dev/">here</a>. Instructions
+    for joining the list are on our <a href="http://xml.openoffice.org">project homepage</a>.
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ 
+
+<p><small>FAQ maintained by <a href="mailto:dvo@openoffice.org">dvo</a>.</small></p>
+</body>
+</html>
+
diff --git a/content/xml/filter/index.html b/content/xml/filter/index.html
new file mode 100644
index 0000000..e6b0621
--- /dev/null
+++ b/content/xml/filter/index.html
@@ -0,0 +1,685 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>OpenOffice.org filters using the XML based file format</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+	<META NAME="AUTHOR" CONTENT="Daniel Vogelheim">
+	<META NAME="CREATED" CONTENT="20010131;13260648">
+	<META NAME="CHANGEDBY" CONTENT="Daniel Vogelheim">
+	<META NAME="CHANGED" CONTENT="20010212;21041181">
+	<STYLE>
+	<!--
+		@page { margin: 2cm }
+		P { margin-bottom: 0.21cm; text-align: justify; page-break-before: auto }
+		H1 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 16pt }
+		H2 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 14pt; font-style: italic }
+		TD P { margin-bottom: 0.21cm; text-align: justify; page-break-before: auto }
+		TH P { margin-bottom: 0.21cm; font-style: italic; page-break-before: auto }
+	-->
+	</STYLE>
+</head>
+<body>
+<P ALIGN=LEFT STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4>OpenOffice.org
+filters using the XML based file format</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+<P><B>Abstract</B>: This document explains the implementation of
+OpenOffice.org import and export filter components, focusing on
+filter components based on the OpenOffice.org XML file format. It is
+intended as a brief introduction to developers that want to implement
+OpenOffice.org filters for foreign file formats.</P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+<DIV ID="Inhaltsverzeichnis1">
+	<DIV ID="Inhaltsverzeichnis1_Head">
+		<P ALIGN=LEFT STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Table
+		Of Contents</B></FONT></FONT></P>
+	</DIV>
+	<P ALIGN=LEFT STYLE="margin-bottom: 0cm; page-break-before: auto"><A HREF="#1.Preliminaries|outline">1
+	 Preliminaries</A></P>
+	<P ALIGN=LEFT STYLE="margin-bottom: 0cm; page-break-before: auto"><A HREF="#2.TheInnardsofanOpenOffice.orgFilterComponent|outline">2
+	 The Innards of an OpenOffice.org Filter Component</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.1.TheBigPicture|outline">2.1  The Big Picture</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.2.WhereXMLComesIn...|outline">2.2  Where XML Comes In...</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.3.Waiter,theExportPlease!|outline">2.3  Waiter, the
+	Export Please!</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.4.ASecondLookattheFilterWrapper|outline">2.4  A Second
+	Look at the Filter Wrapper</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.5.TheServices|outline">2.5  The Services</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.6.Interfaces|outline">2.6  Interfaces</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.7.Built-inComponents|outline">2.7  Built-in Components</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#2.8.RegisteringaNewFilterWiththeApplication|outline">2.8 
+	Registering a New Filter With the Application</A></P>
+	<P ALIGN=LEFT STYLE="margin-bottom: 0cm; page-break-before: auto"><A HREF="#3.Codeexamples|outline">3
+	 Code examples</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#3.1.TheFilterWrapper:InstantiatingtheXMLFilters|outline">3.1
+	 The Filter Wrapper: Instantiating the XML Filters</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#3.2.ExportingthroughtheXMLfilter|outline">3.2  Exporting
+	through the XML filter</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#3.3.Import:WritingintotheXMLFilter|outline">3.3  Import:
+	Writing into the XML Filter</A></P>
+	<P ALIGN=LEFT STYLE="margin-bottom: 0cm; page-break-before: auto"><A HREF="#4.Appendix|outline">4
+	 Appendix</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#4.1.OthersUses|outline">4.1  Others Uses</A></P>
+	<P ALIGN=LEFT STYLE="margin-left: 0.5cm; margin-bottom: 0cm; page-break-before: auto">
+	<A HREF="#4.2.Resources|outline">4.2  Resources</A></P>
+</DIV>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+<H1><A NAME="1.Preliminaries|outline"></A>1Preliminaries</H1>
+<P>They are several ways to get information into or out of
+OpenOffice.org: You can</P>
+<OL>
+	<LI><P>link against the application core,</P>
+	<LI><P>use the OpenOffice.org API,</P>
+	<LI><P>use the XML file format.</P>
+</OL>
+<P>Each of these ways has unique advantages and disadvantages, that I
+will briefly summarize:</P>
+<P>Using the core data structure and linking against the application
+core is the traditional way to implement filters in OpenOffice.org.
+The advantages this method offers are efficiency and direct access to
+the document. However, the core implementation provides a very
+implementation centric view of the applications. Additionally, there
+are a number of technical disadvantages: Every change in the core
+data structures or objects will have to be followed-up by
+corresponding changes in code that use them. Hence filters need to be
+recompiled to match the binary layout of the application core
+objects. While these things are manageable (albeit cumbersome) for
+closed source applications, this method is expected to create a
+maintenance nightmare if application and filter are developed
+separately, as is customary in open sources applications.
+Simultaneous delivery of a new application build and the
+corresponding filters developed by outside parties looks challenging.</P>
+<P>Using the OpenOffice.org API (based on UNO) is a much better way,
+since it solves the technical problems indicated in the last
+paragraph. The UNO component technology insulates the filter from
+binary layout (and other compiler and version dependent issues).
+Additionally, the API is expected to be more stable than the core
+interfaces, and it even provides a shallow level of abstraction from
+the core applications. In fact, the native XML filter implementations
+largely make use of this strategy and are based on the OpenOffice.org
+API.</P>
+<P>The third (and possibly surprising choice) is to import and export
+documents using the XML based file format. UNO-based XML import and
+export components feature all of the advantages of the previous
+method, but additionally provides the filter implementer with a
+clean, structured, and fully documented view of the document. As a
+significant difficulty in conversion between formats is the
+conceptual mapping from the one format to the other, a clean,
+well-structured view of the document may turn out to be beneficial.</P>
+<H1><A NAME="2.TheInnardsofanOpenOffice.orgFilterComponent|outline"></A>
+2The Innards of an OpenOffice.org Filter Component</H1>
+<P>First, we will try to get an overview of the import and export
+process using UNO components. Let's first attempt to gain a view
+of...</P>
+<H2><A NAME="2.1.TheBigPicture|outline"></A>2.1The Big Picture</H2>
+<P>An in-memory OpenOffice.org document is represented by it's
+document model. On disk, the same document is represented as a file.
+An import component must turn the latter into the former as shown by
+the diagram (Illustration 1).</P>
+<P><SPAN ID="Rahmen1" STYLE="float: left; width: 12.9cm; height: 3.21cm; border: none; padding: 0cm; background: #ffffff">
+	<P ALIGN=LEFT STYLE="margin-top: 0.21cm; page-break-before: auto"><IMG SRC="sveo1eo2.gif" NAME="Objekt1" ALIGN=LEFT WIDTH=488 HEIGHT=121><BR CLEAR=LEFT><FONT SIZE=2><I>Illustration
+	1: a generic import filter</I></FONT></P>
+</SPAN><BR CLEAR=LEFT></P><P>If you make use of UNO, this diagram can be
+turned into programming reality quite easily. The three entities in
+the diagram, (the file, the model, and the filter) all have direct
+counterparts in UNO services. The services themselves may consist of
+several interfaces that finally map into C++ or Java classes. The
+following diagram annotates the entities with their corresponding
+services and interfaces:
+</P>
+<P><SPAN ID="Rahmen2" STYLE="float: left; width: 12.9cm; height: 4.97cm; border: none; padding: 0cm; background: #ffffff">
+	<P ALIGN=LEFT STYLE="margin-top: 0.21cm; page-break-before: auto"><IMG SRC="sveo1eo3.gif" NAME="Objekt2" ALIGN=LEFT WIDTH=488 HEIGHT=188><BR CLEAR=LEFT><FONT SIZE=2><I>Illustration
+	2: services and interfaces used by an import filter</I></FONT></P>
+</SPAN><BR CLEAR=LEFT></P><P>In Illustration 2 (and all following
+illustrations) the gray part marks the part a filter implementer will
+have to program, while the white parts are already built into
+OpenOffice.org.</P>
+<P>If the implementer decides to make use of the OpenOffice.org API
+directly, this diagram is the proper starting point: The filter
+writer must create a class that implements the <CODE>ImportFilter</CODE>
+service. To achieve this, the the <CODE>InputStream</CODE> must be
+obtained from the <CODE>MediaDescriptor</CODE>. The incoming data can
+then be interpreted, and the OpenOffice.org document can be
+constructed by calling the appropriate methods of the document model.
+(The available methods of course depend on the kind of document, as
+described by the document service.)</P>
+<H2><A NAME="2.2.WhereXMLComesIn...|outline"></A>2.2Where XML Comes
+In...</H2>
+<P>If the advantages of an XML based import or export are desired,
+the filter implementer may make use of the existing XML import and
+export components. This way, the import logic does not need to deal
+with the document model itself, but rather generates the document in
+its OpenOffice.org XML file format representation. Done in a naive
+way, such a filter component would generate the XML, write it to
+file, and then call the built-in XML import to read it again. Since
+the XML import is based on the SAX API however, a better way exists:
+The import logic calls the SAX API. Since the XML reader component
+implements the SAX API, the document thus gets translated from the
+foreign format into its XML representation and then into the document
+model without the need to use temporary files, or even to render and
+subsequently parse an XML character stream.</P>
+<P><SPAN ID="Rahmen3" STYLE="float: left; width: 12.9cm; height: 4.1cm; border: none; padding: 0cm; background: #ffffff">
+	<P ALIGN=LEFT STYLE="margin-top: 0.21cm; page-break-before: auto"><IMG SRC="sveo1eo4.gif" NAME="Objekt3" ALIGN=LEFT WIDTH=488 HEIGHT=155><BR CLEAR=LEFT><FONT SIZE=2><I>Illustration
+	3: an XML-based import filter</I></FONT></P>
+</SPAN><BR CLEAR=LEFT></P><P>The link between the XML based import filter
+and the XML reader is the SAX <CODE>XDocumentHandler</CODE>
+interface. Using this model, the filter implementer has to implement
+a class that takes a <CODE>MediaDescriptor</CODE>, reads the
+corresponding file, and calls the <CODE>XDocumentHandler</CODE>
+methods to generate the XML representation. Additionally, a filter
+component (labelled &quot;Filter Wrapper&quot; in the diagram) needs
+to be written that instantiates XML import component and the
+self-written import filter.</P>
+<H2><A NAME="2.3.Waiter,theExportPlease!|outline"></A>2.3Waiter, the
+Export Please!</H2>
+<P>The export into a foreign format may of course be implemented in
+the same fashion. Instead of the <CODE>ImportFilter</CODE>
+service, the component now implements the <CODE>ExportFilter</CODE>
+service. An XML-based export filter would implement the document
+handler interface itself, and write the resulting document in the
+proper format into the location indicated by the <CODE>MediaDescriptor</CODE>.
+For an XML-based export filter, the schematic looks like this:</P>
+<P><SPAN ID="Rahmen4" STYLE="float: left; width: 12.9cm; height: 3.21cm; border: none; padding: 0cm; background: #ffffff">
+	<P ALIGN=LEFT STYLE="margin-top: 0.21cm; page-break-before: auto"><IMG SRC="sveo1eo5.gif" NAME="Objekt4" ALIGN=LEFT WIDTH=488 HEIGHT=121><BR CLEAR=LEFT><FONT SIZE=2><I>Illustration
+	4: an XML-based export filter</I></FONT></P>
+</SPAN><BR CLEAR=LEFT><BR><BR>
+</P>
+<H2><A NAME="2.4.ASecondLookattheFilterWrapper|outline"></A>2.4A
+Second Look at the Filter Wrapper</H2>
+<P>How do the built-in XML export or import components cooperate with
+the self-programmed filter? As was briefly mentioned above, the 
+export filter services consist of two major interfaces: <CODE>XImporter</CODE>
+or <CODE>XExporter</CODE> for import and export, respectively, and
+<CODE>XFilter</CODE> for both filter types. The former interface
+passes in the actual document to be imported to or exported from,
+while the <CODE>XFilter</CODE> interfaces triggers the filtering
+process and passes in the <CODE>MediaDescriptor</CODE> which
+describes the source or target document.</P>
+<P>In the case of an XML-based filter, this functionality gets
+distributed to two components. For the import, the built-in XML
+import component implements the <CODE>XImporter</CODE> interface as
+well as <CODE>XDocumentHandler</CODE>. The XML-based filter
+component should implement the <CODE>XFilter</CODE> interface, and
+additionally provide a way to set an <CODE>XDocumentHandler</CODE>.
+The filter wrapper then needs to instantiate both components and
+connect them by setting the built-in XML import as the document
+handler of the XML-based filter. The wrapper can then delegate the
+<CODE>XImporter</CODE> calls to the XML import and the <CODE>XFilter</CODE>
+calls to the XML-based filter, thereby implementing the filter
+<CODE>ImportFilter</CODE> service.</P>
+<P>The export case is slightly more complicated. The additional
+problem is that the filter(&#133;) call of the <CODE>XFilter</CODE>
+interface provides the <CODE>MediaDescriptor</CODE> and
+simultaneously controls the filter process. However, in the desired
+setup for an XML-based export filter, the built-in XML export
+controls the filtering process, but the XML-based filter handles the
+file output, and hence needs the <CODE>MediaDescriptor</CODE>.
+Therefore the filter wrapper has to operate as follows: First it has
+to instantiate the XML-based export filter. This filter has to
+implement the <CODE>XDocumentHandler</CODE> interface. Then it has to
+instantiate the XML export, which at instantiation time expects the
+document handler as a parameter. The filter wrapper delegates calls
+to both the <CODE>XFilter</CODE> and the <CODE>XExporter</CODE>
+interface to the XML export. For calls to the filter method of
+<CODE>XFilter</CODE>, it additionally has to pass the
+<CODE>MediaDescriptor</CODE> on to the XML-based export filter.
+The means by which this should happen is left to the implementer.</P>
+<H2><A NAME="2.5.TheServices|outline"></A>2.5The Services</H2>
+<P>We should now have a closer look at the involved services:</P>
+<P>The service <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/document/ImportFilter.html">com.sun.star.document.ImportFilter</A></CODE>
+describes a generic import filter. The core of the service is
+provided by the interfaces <CODE>XImporter</CODE> and <CODE>XFilter</CODE>
+(see below). <CODE>XImporter</CODE> supplies the filter object with
+the target document (in form of an <CODE>XComponent</CODE>). The
+<CODE>XFilter</CODE> is used to actually start the filtering process,
+supplying the <CODE>MediaDescriptor</CODE> for the source file as a
+parameter. Additionally, the <CODE>ImportFilter</CODE> service
+supports <CODE>XInitialization</CODE> and <CODE>XPropertySet</CODE>
+interfaces. The <CODE>XInitialization</CODE> interface serves to pass
+parameters to the filter at initialization time, while the
+<CODE>XPropertySet</CODE> can be used to get information from and
+about the filter component. It is generally read-only.</P>
+<P>The twin of the <CODE>ImportFilter</CODE> is the service
+<CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/document/ExportFilter.html">com.sun.star.document.ExportFilter</A></CODE>.
+The main interfaces are <CODE>XExporter</CODE> and <CODE>XFilter</CODE>.
+The <CODE>XExporter</CODE> supplies the filter with the source
+document, whereas the <CODE>XFilter</CODE> starts the filter process.
+The <CODE>MediaDescriptor</CODE> that gets passed into the
+<CODE>XFilter</CODE> describes the output file. The <CODE>ExportFilter</CODE>
+supports the <CODE>XInitialization</CODE> and
+<CODE>XPropertySet</CODE> interfaces, just like the <CODE>ImportFilter</CODE>.</P>
+<P>The <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/document/MediaDescriptor.html">com.sun.star.document.MediaDescriptor</A></CODE>
+finally collects all information about a source or target file to be
+imported from or exported to. It contains meta information (such as
+the file name), as well as an <CODE>InputStream</CODE> which can be
+used to actually manipulate the file. <EM>Caveat</EM>: Objects
+obtained from the <CODE>MediaDescriptor</CODE> may not be referenced
+or otherwise held longer beyond the <CODE>filter(<CODE>&#133;</CODE>)</CODE>
+method call. Doing so (e.g., keeping a reference to the <CODE>InputStream</CODE>
+obtained from the <CODE>MediaDescriptor</CODE> prevents the
+<CODE>InputStream</CODE> from being closed.)</P>
+<P>The document model cannot be described by a single service, as it
+obviously has to vary greatly, depending on the type of document (e.g.,
+text or spreadsheet.) An example for a document model service is the
+<CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/text/AdvancedTextDocument.html">com.sun.star.text.AdvancedTextDocument</A></CODE>
+service. What is important in this context, is that all document model
+services support the <CODE>XComponent</CODE> interface.</P>
+<H2><A NAME="2.6.Interfaces|outline"></A>2.6Interfaces</H2>
+<P>The <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html">com.sun.star.document.X</A><A HREF="http://api.openoffice.org/common/ref/com/sun/star/document/XFilter.html">Filter</A></CODE>
+interface features only two methods: <CODE>filter(&#133;)</CODE> and
+<CODE>cancel()</CODE>. The former starts the filtering process based
+for the given <CODE>MediaDescriptor</CODE>, while the latter cancels
+an ongoing filter process. <CODE>XFilter</CODE> must be implemented
+for both, import and export filters.</P>
+<P>The interface <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html">com.sun.star.document.X</A><A HREF="http://api.openoffice.org/common/ref/com/sun/star/document/XImporter.html">Importer</A></CODE>
+is used for setting up an import before the <CODE>filter(<CODE>&#133;</CODE>)</CODE>
+method from the <CODE>XFilter</CODE> interface is called. The
+<CODE>XImporter</CODE> supplies the document with its (empty) target
+document, i.e., the document whose content is about to be read from
+file.</P>
+<P>The <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html">com.sun.star.document.X</A><A HREF="http://api.openoffice.org/common/ref/com/sun/star/document/XExporter.html">Exporter</A></CODE>
+is structured identically to the <CODE>XImporter</CODE> interface. It
+is used to set the target document, i.e., the document whose content
+should be written to file.</P>
+<P>The <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XDocumentHandler.html">com.sun.star.xml.sax.XDocumentHandler</A></CODE>
+is the core interface for handling XML data in OpenOffice.org. It is
+part of the SAX interface. It has methods for all parts of XML
+documents, like start or end of elements or runs of characters. The
+<CODE>XDocumentHandler</CODE> interface is used for both, incoming
+and outgoing XML data, thus allowing chaining of components handling
+XML. A component that processes XML data should implement the
+<CODE>XDocumentHandler</CODE> interface. A component that will
+generate XML data should call the methods of an <CODE>XDocumentHandler</CODE>
+to output the events. The <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/xml/sax/XExtendedDocumentHandler.html">XExtendedDocumentHandler</A></CODE>,
+being derived from <CODE>XDocumentHandler</CODE>, provides
+an extended version that can also handle comments. If the extended
+functionality is desired, the <CODE>XDocumentHandler</CODE> should be
+queried for the <CODE>XExtendedDocumentHandler</CODE> at
+runtime. However, implementers should make sure their components
+never rely on the presence of extended <CODE>XExtendedDocumentHandler</CODE>,
+but rather make sure they could also work with the plain
+<CODE>XDocumentHandler</CODE>. Since all vital parts of XML can be
+handled through <CODE>XDocumentHandler</CODE>, this should not pose
+much of a problem.</P>
+<P>The interface <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/lang/XComponent.html">com.sun.star.lang.XComponent</A></CODE>
+is the parent interface for all document models. Actual documents
+derive from this model to provide model specific functionality, such
+as <CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/text/XTextDocument.html">XTextDocument</A></CODE>.
+A filter will have to query at runtime whether it can handle the
+supplied <CODE>XModel</CODE>.</P>
+<P>Initialization of components can be supported through the
+<CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/lang/XInitialization.html">com.sun.star.lang.XInitialization</A></CODE>
+interface.</P>
+<P>Properties of the filters can be queried using the
+<CODE><A HREF="http://api.openoffice.org/common/ref/com/sun/star/beans/XPropertySet.html">com.sun.star.beans.XPropertySet</A></CODE>
+interface. The names of the supported properties are part of the
+service description. In general, <CODE>XPropertySet</CODE>
+implementations support both reading and writing, but the intended
+use for filter components is to be read-only.</P>
+<P><BR><BR>
+</P>
+<H2><A NAME="2.7.Built-inComponents|outline"></A>2.7Built-in
+Components</H2>
+<P>All of OpenOffice.org's applications have built-in XML import and
+export components. The component names are summarized in the
+following table:</P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+	<COL WIDTH=30*>
+	<COL WIDTH=112*>
+	<COL WIDTH=114*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=12%>
+				<P>Application</P>
+			</TH>
+			<TH WIDTH=44%>
+				<P>XML import</P>
+			</TH>
+			<TH WIDTH=44%>
+				<P>XML export</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=12%>
+				<P>Writer</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Writer.XMLExporter</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Writer.XMLImporter</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=12%>
+				<P>Calc</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Calc.XMLExporter</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Calc.XMLImporter</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=12%>
+				<P>Chart</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Chart.XMLExporter</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Chart.XMLImporter</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=12%>
+				<P>Impress</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Impress.XMLExporter</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Impress.XMLImporter</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=12%>
+				<P>Draw</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Draw.XMLExporter</P>
+			</TD>
+			<TD WIDTH=44%>
+				<P>com.sun.star.comp.Draw.XMLImporter</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P>Additionally, the XML reader and writer components should be
+mentioned, even though they have not been discussed in the previous
+chapters. These two components implement the XML reader (or parser)
+and writer (or unparser) components used by OpenOffice.org for
+writing all it's XML files. They implement (XML writer) or use (XML
+parser) the <CODE>XDocumentHandler</CODE> interface. In some sense
+they could be considered XML-based filters, since they read or write
+character streams and turn them into SAX function calls. Their names
+are <CODE>com.sun.star.xml.sax.Writer</CODE> and
+<CODE>com.sun.star.xml.sax.Parser</CODE>, respectively.</P>
+<H2><A NAME="2.8.RegisteringaNewFilterWiththeApplication|outline"></A>
+2.8Registering a New Filter With the Application</H2>
+<P>There is a final, crucial step that will not be covered here:
+Registering a filter with the application. The registration process
+will make sure that the application knows the filter, and also knows
+which files the filter can be applied to. The filter registration is
+described <A HREF="http://framework.openoffice.org/documentation/filters/index.html">here</A>.
+</P>
+<H1><A NAME="3.Codeexamples|outline"></A>3Code examples</H1>
+<P>This chapter is intended to give brief code examples for the
+crucial steps in creating XML-based import or export filters. We'll
+start with the filter wrapper, followed by short examples for
+importing into and export from the XML filters.</P>
+<H2><A NAME="3.1.TheFilterWrapper:InstantiatingtheXMLFilters|outline"></A>
+3.1The Filter Wrapper: Instantiating the XML Filters</H2>
+<P>The filter wrapper needs to instantiate the built-in XML import or
+export components. The following code snippet will demonstrate this
+for an XML-based export filter.</P>
+<PRE>
+<CODE>using namespace ::com::sun::star;</CODE>
+
+<CODE>// Instantiate the XML export filter</CODE>
+
+<CODE>// Prerequisites: </CODE>
+<CODE>// 1) a service factory, </CODE>
+<CODE>// 2) a document handler, </CODE>
+<CODE>// 3) a string with the service name.</CODE>
+
+<CODE>// Obtain the service factory</CODE>
+<CODE>uno::Reference&lt; lang::XMultiServiceFactory &gt; xServiceFactory = &#133;;</CODE>
+
+<CODE>// Obtain (or create) the XML-based output filter. It has to implement</CODE>
+<CODE>// the XDocumentHandler interface, so the export component can write to it.</CODE>
+<CODE>uno::Reference&lt; xml::sax::XDocumentHandler &gt; xHandler = &#133; &lt;your filter&gt; <CODE>&#133;</CODE>; </CODE>
+
+<CODE>// Prepare arguments passed to the XML export filter:</CODE>
+<CODE>// The XML-based filter in form of an XdocumentHandler.</CODE>
+<CODE>// Arguments are passed by a sequence of Any. </CODE>
+<CODE>// Our sequence will contain only 1 element.</CODE>
+<CODE>uno::Sequence&lt;uno::Any&gt; aArgs(1);</CODE>
+<CODE>aArgs[0] &lt;&lt;= xHandler;</CODE>
+
+<CODE>// Instantiate the exporter from the factory.</CODE>
+<CODE>::rtl::OUString sService =</CODE>
+<CODE>    ::rtl::OUString::createFromAscii(&quot;com.sun.star.comp.Writer.XMLExporter&quot;);</CODE>
+
+<CODE>uno::Reference&lt; document::XExporter &gt; xExporter(</CODE>
+<CODE>   xServiceFactory-&gt;createInstanceWithArguments(sService),	aArgs ),</CODE>
+<CODE>   uno::UNO_QUERY );</CODE>
+<CODE>ASSERT( xExporter.is(), &quot;can' instantiate XML exporter&quot; );</CODE>
+
+<CODE>// Now we have the two components in xHandler and xExporter and can start </CODE>
+<CODE>// calling the XFilter and XExporter methods. Note that the xHandler needs</CODE>
+<CODE>// to be informed about its MediaDescriptor.</CODE></PRE><H2>
+<A NAME="3.2.ExportingthroughtheXMLfilter|outline"></A>3.2Exporting
+through the XML filter</H2>
+<P>The following code snippet could be located in a filter wrapper
+for an XML-based export filter. The following two methods implement
+the gist of a filter wrapper for an XML-based export. They are really
+simple because the filter wrapper doesn't really do much of its own.
+It only delegates to it's two components.</P>
+<PRE><CODE>using namespace ::com::sun::star;</CODE>
+
+<CODE>void SAL_CALL &lt;filter wrapper&gt;::setSourceDocument( </CODE>
+<CODE>	const uno::Reference&lt;lang::XComponent&gt;&amp; xComponent )</CODE>
+<CODE>{</CODE>
+<CODE>    // delegate to XExporter of the built-in XML export</CODE>
+<CODE>    xExporter-&gt;setSourceDocument( xComponent );</CODE>
+<CODE>}</CODE>
+
+<CODE>sal_Bool SAL_CALL &lt;filter wrapper&gt;::filter( </CODE>
+<CODE>    const uno::Sequence&lt;beans::PropertyValue&gt;&amp; aDescriptor )</CODE>
+<CODE>    throw(uno::RuntimeException)</CODE>
+<CODE>{</CODE>
+<CODE>    // set MediaDescriptor at XML-based export filter</CODE>
+<CODE>    ...</CODE>
+
+<CODE>    // get access to XFilter interface of XML export</CODE>
+<CODE>    uno::Reference&lt;document::XFilter&gt; xFilter(xExporter, uno::UNO_QUERY);</CODE>
+<CODE>    xFilter-&gt;filter(aDescriptor);</CODE>
+<CODE>}</CODE>
+</PRE><H2>
+<A NAME="3.3.Import:WritingintotheXMLFilter|outline"></A>3.3Import:
+Writing into the XML Filter</H2>
+<P>The next example should detail how an import filter would
+communicate with the XML import component. Basically, it only needs
+to call the <CODE>XDocumentHandler</CODE> methods. The following code
+implements the notorious &quot;Hello World!&quot; program as an
+OpenOffice.org import filter.</P>
+<PRE>
+using namespace ::com::sun::star;
+
+// instantiate the XML import component 
+::rtl::OUString sService =
+    ::rtl::OUString::createFromAscii(&quot;com.sun.star.comp.Writer.XMLImporter&quot;)
+uno::Reference&lt;xml::sax::XDocumentHandler&gt; xImport(
+    xServiceFactory-&gt;createInstance(sService), uno::UNO_QUERY );
+ASSERT( xImport.is(), &quot;can't instantiate XML import&quot; );
+
+// OK. Now we have the import. Let's make a real simple document.
+
+// a few comments:
+// 1. We will use string constants from xmloff/xmlkywd.hxx
+// 2. For convenience, we'll use a globally shared attribute list from the 
+//    xmloff project (xmloff/attrlist.hxx)
+// 3. In a real project, we would pre-construct our OUString, rather than use
+//    the slow createFromAscii(&#133;) method every time.
+
+// We will write the following document: (the unavoidable 'Hello World!')
+// &lt;office:document 
+//      office:class=&quot;text&quot; 
+//      xmlns:office=&quot;http://openoffice.org/2000/office&quot; 
+//      xmlns:text=&quot;http://openoffice.org/2000/text&quot; &gt;
+//   &lt;office:body&gt;
+//     &lt;text:p&gt;Hello World!&lt;/text:p&gt;
+//   &lt;/office:body&gt;
+// &lt;/office:document&gt;
+
+SvXMLAttributeList aAttrList;
+
+xHandler-&gt;startDocument();
+
+// our first element: first build up the attribute list, then start the element
+// DON'T FORGET TO ADD THE NAMESPACES!
+aAttrList.AddAttribute(
+    ::rtl::OUString::createFromAscii(&quot;xmlns:office&quot;), 
+    ::rtl::OUString::createFromAscii(&quot;CDATA&quot;), 
+    ::rtl::OUString::createFromAscii(&quot;http://openoffice.org/2000/office&quot;) );
+aAttrList.AddAttribute(
+    ::rtl::OUString::createFromAscii(&quot;xmlns:text&quot;), 
+    ::rtl::OUString::createFromAscii(&quot;CDATA&quot;), 
+    ::rtl::OUString::createFromAscii(&quot;http://openoffice.org/2000/text&quot;) );
+aAttrList.AddAttribute(
+    ::rtl::OUString::createFromAscii(&quot;office:class&quot;), 
+    ::rtl::OUString::createFromAscii(&quot;CDATA&quot;), 
+        ::rtl::OUString::createFromAscii(&quot;text&quot;) );
+xHandler-&gt;startElement(
+    ::rtl::OUString::createFromAscii(&quot;office:document&quot;),
+    aAttrList );
+
+// body element (no attributes)
+aAttrList.clear();
+xHandler-&gt;startElement(
+    ::rtl::OUString::createFromAscii(&quot;office:body&quot;),
+    aAtrList );
+
+// paragraph element (no attributes)
+aAttrList.clear();
+xHandler-&gt;startElement(
+    ::rtl::OUString::createFromAscii(&quot;text:p&quot;),
+    aAtrList );
+
+// write text
+xHandler-&gt;characters(
+    ::rtl::OUString::createFromAscii(&quot;Hello World!&quot;) );
+
+// close paragraph
+xHandler-&gt;startElement(
+    ::rtl::OUString::createFromAscii(&quot;text:p&quot;),
+
+// close body
+xHandler-&gt;endElement(
+    ::rtl::OUString::createFromAscii(&quot;office:body&quot;) );
+
+// close document element
+xHandler-&gt;endElement(
+    ::rtl::OUString::createFromAscii(&quot;office:document&quot;) );
+
+// close document
+xHandler-&gt;endDocument();
+</PRE><H1>
+<A NAME="4.Appendix|outline"></A>4Appendix</H1>
+<H2><A NAME="4.1.OthersUses|outline"></A>4.1 Other Uses</H2>
+<P>This chapter briefly mentions a few other uses of XML-based filter
+components that provide additional value and versatility.</P>
+<P>In some circumstances, it may be desirable to have standalone
+format conversion tools. This would, for example, enable batch
+conversion of legacy documents. The XML-based filter components allow
+us to do that with little extra effort. Let us recall that an
+XML-based import filter uses OpenOffice.org's built-in XML import to
+generate the document. It calls the (generic) <CODE>XDocumentHandler</CODE>
+interface after it has been supplied with the <CODE>XDocumentHandler</CODE>
+implementation by the filter wrapper. Now if the filter wrapper
+instead supplies the XML-based import filter with the XML writer
+component (which implements the <CODE>XDocumentHandler</CODE>
+interface as well), then the XML writer component will output the XML
+as a character stream to disk. Thus we have created the desired
+standalone conversion utility by only implementing a new filter
+wrapper!</P>
+<P><SPAN ID="Rahmen5" STYLE="float: left; width: 12.56cm; height: 3.17cm; border: none; padding: 0cm; background: #ffffff">
+	<P ALIGN=LEFT STYLE="margin-top: 0.21cm; page-break-before: auto"><IMG SRC="sveo1eo6.gif" NAME="Objekt5" ALIGN=LEFT WIDTH=475 HEIGHT=120><BR CLEAR=LEFT><FONT SIZE=2><I>Illustration
+	5: a standalone file format conversion utility</I></FONT></P>
+</SPAN><BR CLEAR=LEFT></P><P>A different possible use is the chaining of
+XML-based filters. Suppose the foreign file format in question is
+also based on XML. Now it doesn't make sense to re-implement the XML
+parser inside that component, so it seems natural to use the existing
+parser (or unparser) component. This way, our import (or export)
+filter would have to implement the <CODE>XDocumentHandler</CODE>
+interface for its input, and also use an <CODE>XDocumentHandler</CODE>
+interface for its output. The resulting implementation is sketched in
+Illustration 6. Note that such XML to XML filters could be chained
+arbitrarily.</P>
+<P><SPAN ID="Rahmen6" STYLE="float: left; width: 14.2cm; height: 3.54cm; border: none; padding: 0cm; background: #ffffff">
+	<P ALIGN=LEFT STYLE="margin-top: 0.21cm; page-break-before: auto"><IMG SRC="sveo1eo7.gif" NAME="Objekt6" ALIGN=LEFT WIDTH=527 HEIGHT=134><BR CLEAR=LEFT><FONT SIZE=2><I>Illustration
+	6: a filter chain with one element</I></FONT></P>
+</SPAN><BR CLEAR=LEFT></P><P>Note that, if the other application is also an
+OpenSource application, it could use UNO component technology as
+well, and thus use the very same filter components for its own import
+and export. A filter converting from the foreign XML into
+OpenOffice.org XML would be an import filter for OpenOffice.org, and
+simultaneously an export filter for the other application.
+</P>
+<P>As OpenOffice.org is being developed further, it becomes likely
+that eventually changes to the file format will have to be made. It
+is mandatory to supply users with the ability to read and write the
+old formats of course. This could indeed be handled by an XML to XML
+transformation, with one format being the old OpenOffice.org XML
+format, and the other being the new format.</P>
+<P>Note that such a filter could also be used by users of the older
+versions to read and write documents in the new format! Additionally,
+it could be chained between other XML-based import or export filters,
+allowing users to utilize import and export filters for versions
+other than their own. Essentially, this would achieve a decoupling of
+application, filter, and file format version. The opportunities this
+opens up are quite amazing: If a new file format is implemented,
+users would not be forced to upgrade their application to make use of
+the new filter. Also, users of newer application versions could still
+use filters developed for the older format. 
+</P>
+<H2><A NAME="4.2.Resources|outline"></A>4.2Resources</H2>
+<P>The following resources may provide additional information:</P>
+<UL>
+	<LI><P ALIGN=LEFT>Tutorial &quot;How to register a component&quot;:
+	<A HREF="http://framework.openoffice.org/documentation/filters/index.html">http://framework.openoffice.org/documentation/filters/index.html</A></P>
+	<LI><P ALIGN=LEFT>XML file format specification:
+	<A HREF="http://xml.openoffice.org/xml_specification.pdf">http://xml.openoffice.org/xml_specification.pdf</A></P>
+	<LI><P ALIGN=LEFT>Tutorial &quot;A Component in C++&quot;:
+	<A HREF="http://udk.openoffice.org/cpp/man/component_tutorial.html">http://udk.openoffice.org/cpp/man/component_tutorial.html</A></P>
+	<LI><P ALIGN=LEFT>OpenOffice.org API Reference:
+	<A HREF="http://api.openoffice.org/common/ref/">http://api.openoffice.org/common/ref/</A></P>
+	<LI><P ALIGN=LEFT>OpenOffice.org XML Homepage:
+	<A HREF="http://xml.openoffice.org/">http://xml.openoffice.org</A></P>
+	<LI><P ALIGN=LEFT>OpenOffice.org Framework Homepage:
+	<A HREF="http://framework.openoffice.org/">http://framework.openoffice.org</A></P>
+	<LI><P ALIGN=LEFT>OpenOffice.org API Homepage:
+	<A HREF="http://api.openoffice.org/">http://api.openoffice.org/</A></P>
+	<LI><P ALIGN=LEFT>OpenOffice.org UNO Homepage:
+	<A HREF="http://udk.openoffice.org/">http://udk.openoffice.org/</A></P>
+</UL>
+<HR>
+<P>The <A HREF="http://xml.openoffice.org/">xmloff</A> development
+team <BR>Summarized by <A HREF="mailto:dvo@openoffice.org">dvo</A></P>
+</body>
+</HTML>
diff --git a/content/xml/filters.html b/content/xml/filters.html
new file mode 100644
index 0000000..18f8035
--- /dev/null
+++ b/content/xml/filters.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html><head>
+<title>OpenOffice.org XML based filters</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Filters">XML based OpenOffice.org filters</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Filters">Wiki</a>.
+</body>
+</html>
+
diff --git a/content/xml/general.html b/content/xml/general.html
new file mode 100644
index 0000000..561d1d8
--- /dev/null
+++ b/content/xml/general.html
@@ -0,0 +1,151 @@
+<!DOCTYPE html>
+<html><head>
+<title>OpenOffice.org XML File Format</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<h1>OpenOffice.org XML File Format</h1>
+<h2>File Format Specification and General Information</h2>
+
+<p><em><b>Note:</b>The information provided on this page is related to the OpenOffice.org XML file format used by OpenOffice.org 1.0 only. Please visit the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS OpenDocument Technical Committee web pages</a> for information regarding the OASIS OpenDocument file format used by OpenOffice.org 2.0.</em></p>
+<h3>Mission</h3>
+    <a name="mission"></a>     
+<p align="justify"> Our mission is to create an open and ubiquitous XML-based 
+ file format for office documents and to provide an open reference implementation 
+ for this format. </p>
+<h4> Core Requirements <small>(these items are absolutely required)</small>
+    </h4>
+        
+<ol>
+     <li> The file format must be capable of being used as an office program's
+  native file format.  The format must be "non-lossy" and must support (at
+ least) the full capability of a StarOffice/OpenOffice document.  The format
+ is likely to be used for document interchange but that use alone is not
+enough.    </li>
+     <li> Structured content should make use of XML's structuring capabilities 
+ and be represented in terms of XML elements and attributes. </li>
+     <li> The file format must be fully documented and have no "secret" features. 
+   </li>
+     <li> OpenOffice must be the reference implementation for this file format. 
+   </li>
+        
+</ol>
+        
+<h4> Core Goals <small>(these items are highly desired)</small> </h4>
+        
+<ol>
+     <li> The file format should be developed in such a way that it will
+be  accepted by the community and can be placed under community control for
+future  development and format evolution. </li>
+     <li> The file formats should be suitable for all office types: text
+processing,   spreadsheet, presentation, drawing, charting, and math. </li>
+     <li> The file formats should reuse portions of each other as much as 
+possible  (so for example a spreadsheet table definition can work also as 
+a text processing  table definition). </li>
+        
+</ol>
+
+<h3>OASIS File Format Standardization</h3>
+
+<p>XML file formats allow users to regain ownership to his/her own
+data, by allowing access and manipulation of office documents by
+arbitrary tools which support the file format. To make such capability
+ubiquitous, we believe it is necessary to standardize file
+formats. Thus, we have contributed the OpenOffice.org XML File
+Format to <a href="http://www.oasis-open.org/">OASIS</a>. The further development of the format now takes place in the <a
+href="http://www.oasis-open.org/committees/office/">OASIS OpenDocument
+Technical Committee</a>.</p>
+        
+
+<h3>General Information on the XML File Format</h3>
+
+<p>The definition of the XML File Format has been developed through
+OpenOffice.org. The resulting reference material, such as the specification and
+DTD may be downloaded here:</p>
+
+<table class="infotable">
+ <thead>
+  <tr>
+   <td colspan="3">OpenOffice.org XML File Format Specification</td>
+  </tr>
+  <tr>
+   <th>Document</th>
+   <th>Summary</th>
+   <th>Format</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td><a href="xml_specification.pdf">XML File Format Specification</a></td>
+   <td>This documents defines the XML file format used OpenOffice.org. It
+   serves as reference for the format.</td>
+   <td>PDF, ca.&nbsp;1.5MB</td>
+  </tr>
+  <tr>
+   <td><a href="/source/browse/xml/xmloff/dtd/">XML File Format DTD</a></td>
+   <td>The document type definition provides a handy reference against which
+   all OpenOffice.org XML files can be validated against.</td>
+   <td>text, ca.&nbsp;200KB</td>
+  </tr>
+ </tbody>
+</table>
+
+<p>Some supplementary information and resources on the OpenOffice.org XML File
+Format are available as well:</p>
+
+<table class="infotable">
+ <thead>
+  <tr>
+   <td colspan="3">General Information on the Format</td>
+  </tr>
+  <tr>
+   <th>Document</th>
+   <th>Summary</th>
+   <th>Format</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td><a href="faq.html">xmloff FAQ</a></td>
+   <td>The FAQ list some frequently asked question, together with answers from
+   the xmloff development team.</td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="xml_advocacy.html">XML Advantages</a></td>
+   <td>This page explains our motivation for using an XML based file
+   format. It lists advantages of our new file format, and discusses how these
+   will benefit different groups of users.</td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="package.html">Package Format Rationale</a></td>
+   <td>This document explains the rationale behind the ZIP-based package
+   format. The decision was made after an elaborate discussion on the XML dev
+   mailing list, whose <a href="http://xml.openoffice.org/xml-dev/">
+   archive</a> can be consulted for additional detail.</td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="filters.html">XML-based filters</a></td>
+   <td><p>Filters and transformations making use of the OpenDocument or OpenOffice.org XML File Formats.</p></td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="uses.html">Uses and Applications</a></td>
+   <td><p>Information on how to make use of the OASIS OpenDocument and OpenOffice.org XML File Format 
+ outside of the OpenOffice.org application.</p></td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="research.html">Resources</a></td>
+   <td><p>Books, articles, reports and research documents covering the OpenDocument and OpenOffice.org XML file formats.</p></td>
+   <td>HTML</td>
+  </tr>
+ </tbody>
+</table>
+</body>
+</html>
+
diff --git a/content/xml/index.html b/content/xml/index.html
new file mode 100644
index 0000000..4b75cab
--- /dev/null
+++ b/content/xml/index.html
@@ -0,0 +1,94 @@
+<html><head>
+<title>XML Project</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<!-- no current top news!
+<h2><strong>Top News</str
+ong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<h1>The OpenOffice.org <strong>XML</strong> Project</h1>               
+<p>Lead: <a href="mailto:Michael.Brauer [AT]sun.com">Michael Brauer</a><br>
+Co-Lead: <a href="mailto:Svante.Schubert [AT]sun.com">Svante Schubert</a><br>
+<small>(Please use the provided <a href="/servlets/ProjectMailingListList">mailing lists</a> for discussion related to this project.</small>
+</p>
+
+<p>The OpenOffice.org <strong>XML project</strong> is the home of of XML related features of <a href="http://download.openoffice.org/">OpenOffice.org</a>, 
+like its <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument</a>/<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300</a> file format implementation. It further provides some XML base implementations,
+like XML parser and printer components.</p>
+
+<p>The following sub-projects are within the scope of the XML project:</p>
+<ul>
+<li><p>The <a href="#ODF">OASIS OpenDocument/ISO/IEC 26300 file format</a> implementation, and the implementation of its predecessor, <a href="#OOo-XML">OpenOffice.org XML</a>.</p>
+<li><p>The <a href="#filter">framework for XML based filters</a>.</p>
+<li><p><a href="#xforms">XForms</a>.</p>
+<li><p><a href="#security">XML Security</a>.</p>
+<li><p><a href="#parser">XML Parser and Writer</a>.</p>
+</ul>
+<p>Please follow above links to get more information about these sub projects.</p>
+The XML project is one of the <a href="http://projects.openoffice.org/accepted.html">accepted projects</a> of <a href="http://www.openoffice.org">OpenOffice.org</a>.</p>
+<p>Please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">XML project's wiki pages</a> for
+more information about the project.</p>
+
+<h2>Contributing to the XML Project</h2>
+<p>If you are interested in contributing to this project, please don't hesitate to contact us at <a href="http://xml.openoffice.org/servlets/ProjectMailingListList">dev@xml.openoffice.org</a>. 
+If you are looking for <a href="http://wiki.services.openoffice.org/wiki/Xml#Contribution_Areas">ideas</a> what you may contribute, please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">project's wiki</a>.
+
+
+<h2 id="ODF">OASIS OpenDocument/ISO/IEC 26300 File Format (ODF)</h2>
+<p>The OpenOffice.org application uses the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument file format</a> (also known as ODF) as 
+native file format. This means, OpenOffice.org stores all documents in 
+OpenDocument file format unless the user requests to store them in a 
+different file format.</p>
+<p><a href="http://opendocument.xml.org""><img align=right border=0 width=315 src="opendocument-cropped_0.jpg" /></a>The OpenDocument file format is developed by a <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">technical committee</a> at <a href="http://www.oasis-open.org">OASIS</a>. 
+It further is an approved and published ISO standard (<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300:2006</a>). The <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument specification</a> is available at the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS OpenDocument TC's web page</a>. See
+<a href="http://opendocument.xml.org">opendocument.xml.org</a> for more information on 
+OpenDocument.</p>
+<p>Several members of the OpenOffice.org XML project and other OpenOffice.org 
+projects are <a href="http://www.oasis-open.org/committees/membership.php?wg_abbrev=office">members</a> of the OASIS OpenDocument technical committee, and 
+collaborate there with members from other projects and vendors on the further 
+development of the OpenDocument file format.</p>
+<p>The XML project maintains the implementation of the OpenDocument file format 
+in OpenOffice.org in very close collaboration and with large support of other 
+OpenOffice.org projects, in particular the 
+<a href="http://framework.openoffice.org/">application framework</a>, 
+<a href="http://graphics.openoffice.org/">graphical application</a>, 
+<a href="http://sc.openoffice.org">spreadsheet</a> and 
+<a href="http://sw.openoffice.org/">word processing</a> 
+projects.</p>
+
+<h2 id="OOo-XML">OpenOffice.org XML File Format</h2>
+<p>The <a href="general.html">OpenOffice.org XML file format</a> is the native 
+file format of OpenOffice.org 1.0. It has been replaced by the 
+<a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument file format</a>
+ in OpenOffice.org 2.0.</p>
+
+<h2 id="filter">XML-Based Filters</h2>
+<p>The XML project contains the framework for the <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">XML based filters</a>. More
+information about the development of XML based filters is available in the <a href="filter">XML Based Filter Tutorial</a>.
+A <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">list of XML based filters</a> available for OpenOffice.org is available <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">in the wiki</a>.
+
+<h2 id="xforms">XForms</h2>
+<p>The XML project maintains the base technology of 
+OpenOffice.org's XForms feature, and cares about specifications in that area 
+in collaboration with the <a href="http://sw.openoffice.org/">word processing</a>
+and <a href="http://dba.openoffice.org/">database</a> projects. The Writer specific parts of the 
+XForms feature is maintained by the <a href="http://sw.openoffice.org/">word processing</a>
+project.</p>
+
+<h2 id="security">XML Security</h2>
+<p>In collaboration with the 
+<a href="http://framework.openoffice.org/">application framework</a> project, the 
+XML projects specifies and implements XML Security features of OpenOffice.org, 
+like digital signatures. 
+
+<h2 id="parser">XML Basis Implementations</h2>
+Being an important client of XML parser and writer implementations, the 
+XML project maintains these components in collaboration with the <a href="http://framework.openoffice.org/">application framwork</a> project project. 
+
+
+</body>
+</html>
+
diff --git a/content/xml/index2.html b/content/xml/index2.html
new file mode 100755
index 0000000..bd1cd00
--- /dev/null
+++ b/content/xml/index2.html
@@ -0,0 +1,93 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<!-- no current top news!
+<h2><strong>Top News</str
+ong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<h1>The OpenOffice.org <strong>XML</strong> Project</h1>               
+<p>Lead: <a href="mailto:Michael.Brauer@sun.com">Michael Brauer</a><br>
+Co-Lead: <a href="mailto:Svante.Schubert@sun.com">Svante Schubert</a><br>
+<small>(Please use the provided <a href="/servlets/ProjectMailingListList">mailing lists</a> for discussion related to this project.</small>
+</p>
+
+<p>The OpenOffice.org <strong>XML project</strong> is the home of of XML related features of <a href="http://download.openoffice.org/">OpenOffice.org</a>, 
+like its <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument</a>/<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300</a> file format implementation. It further provides some XML base implementations,
+like XML parser and printer components.</p>
+
+<p>The following sub-projects are within the scope of the XML project:</p>
+<ul>
+<li><p>The <a href="#ODF">OASIS OpenDocument/ISO/IEC 26300 file format</a> implementation, and the implementation of its predecessor, <a href="#OOo-XML">OpenOffice.org XML</a>.</p>
+<li><p>The <a href="#filter">framework for XML based filters</a>.</p>
+<li><p><a href="#xforms">XForms</a>.</p>
+<li><p><a href="#security">XML Security</a>.</p>
+<li><p><a href="#parser">XML Parser and Writer</a>.</p>
+</ul>
+<p>Please follow above links to get more information about these sub projects.</p>
+The XML project is one of the <a href="http://projects.openoffice.org/accepted.html">accepted projects</a> of <a href="http://www.openoffice.org">OpenOffice.org</a>.</p>
+<p>Please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">XML project's wiki pages</a> for
+more information about the project.</p>
+
+<h2>Contributing to the XML Project</h2>
+<p>If you are interested in contributing to this project, please don't hesitate to contact us at <a href="http://xml.openoffice.org/servlets/ProjectMailingListList">dev@xml.openoffice.org</a>. 
+If you are looking for <a href="http://wiki.services.openoffice.org/wiki/Xml#Contribution_Areas">ideas</a> what you may contribute, please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">project's wiki</a>.
+
+
+<h2 id="ODF">OASIS OpenDocument/ISO/IEC 26300 File Format</h2>
+<p>The OpenOffice.org application uses the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument file format</a> as 
+native file format. This means, OpenOffice.org stores all documents in 
+OpenDocument file format unless the user requests to store them in a 
+different file format.</p>
+<p>The OpenDocument file format is developed by a <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">technical committee</a> at <a href="http://www.oasis-open.org">OASIS</a>. 
+It further is an approved and published ISO standard (<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300:2006</a>). The <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument specification</a> is available at the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS OpenDocument TC's web page</a>. See
+<a href="opendocument.xml.org">opendocument.xml.org</a> for more information on 
+OpenDocument.</p>
+<p>Several members of the OpenOffice.org XML project and other OpenOffice.org 
+projects are <a href="http://www.oasis-open.org/committees/membership.php?wg_abbrev=office">members</a> of the OASIS OpenDocument technical committee, and 
+collaborate there with members from other projects and vendors on the further 
+development of the OpenDocument file format.</p>
+<p>The XML project maintains the implementation of the OpenDocument file format 
+in OpenOffice.org in very close collaboration and with large support of other 
+OpenOffice.org projects, in particular the 
+<a href="http://framework.openoffice.org/">application framework</a>, 
+<a href="http://graphics.openoffice.org/">graphical application</a>, 
+<a href="http://sc.openoffice.org">spreadsheet</a> and 
+<a href="http://sw.openoffice.org/">word processing</a> 
+projects.</p>
+
+<h2 id="OOo-XML">OpenOffice.org XML File Format</h2>
+<p>The <a href="general.html">OpenOffice.org XML file format</a> is the native 
+file format of OpenOffice.org 1.0. It has been replaced by the 
+<a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument file format</a>
+ in OpenOffice.org 2.0.</p>
+
+<h2 id="filter">XML-Based Filters</h2>
+<p>The XML project contains the framework for the <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">XML based filters</a>. More
+information about the development of XML based filters is available in the <a href="filter">XML Based Filter Tutorial</a>.
+A <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">list of XML based filters</a> available for OpenOffice.org is available <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">in the wiki</a>.
+
+<h2 id="xforms">XForms</h2>
+<p>The XML project maintains the base technology of 
+OpenOffice.org's XForms feature, and cares about specifications in that area 
+in collaboration with the <a href="http://sw.openoffice.org/">word processing</a>
+and <a href="http://dba.openoffice.org/">database</a> projects. The Writer specific parts of the 
+XForms feature is maintained by the <a href="http://sw.openoffice.org/">word processing</a>
+project.</p>
+
+<h2 id="security">XML Security</h2>
+<p>In collaboration with the 
+<a href="http://framework.openoffice.org/">application framework</a> project, the 
+XML projects specifies and implements XML Security features of OpenOffice.org, 
+like digital signatures. 
+
+<h2 id="parser">XML Basis Implementations</h2>
+Being an important client of XML parser and writer implementations, the 
+XML project maintains these components in collaboration with the <a href="http://framework.openoffice.org/">application framwork</a> project project. 
+
+
+</body>
+</html>
+
diff --git a/content/xml/modules.html b/content/xml/modules.html
new file mode 100644
index 0000000..63e3dbd
--- /dev/null
+++ b/content/xml/modules.html
@@ -0,0 +1,10 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Modules">Source Code Modules in the OpenOffice.org XML Project</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Modules">Wiki</a>.
+</body>
+</html>
+
diff --git a/content/xml/oasis/index.html b/content/xml/oasis/index.html
new file mode 100644
index 0000000..f846d2d
--- /dev/null
+++ b/content/xml/oasis/index.html
@@ -0,0 +1,43 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+  <h1>Under Construction</h1>
+  <p>This page is under construction. Please visit again later.</p>
+
+  <p>Currently hosted are the following files:</p>
+
+  <dl>
+    <dt><a href="office-spec.sxw">office-spec.sxw</a></dt>
+    <dd>
+      <p>Working document for the OASIS Open Office TC specification. This
+	  draft is only used internally by the TC.</p>
+      <p><b>Note:</b> The current <em>committee draft</em> is available
+      <a
+      href="http://www.oasis-open.org/office/">here</a>.</p>
+    </dd>
+    <dt><a href="extract.xsl">extract.xsl</a></dt>
+    <dd>
+      <p>XSLT to extract the Relax NG from the specification document.</p>
+      <p>May also be used to extract text of a specific format from
+      any OASIS Open Office or OpenOffice.org document.</p>
+    </dd>
+    <dt><a href="oasis2ooo.xsl">oasis2ooo.xsl</a></dt>
+    <dd>
+      <p>XSLT to transform OASIS Open Office into OpenOffice.org documents.</p>
+    </dd>
+    <dt><a href="ooo2oasis.xsl">ooo2oasis.xsl</a></dt>
+    <dd>
+      <p>XSLT to transform OpenOffice.org into OASIS Open Office documents.</p>
+    </dd>
+  </dl>
+
+
+<p>CVS history and past versions of these documents may be accessed
+through <a
+href="http://xml.openoffice.org/servlets/ProjectSource#commandlinecvs"/>anonymous
+CVS</a> or a <a
+href="http://xml.openoffice.org/source/browse/xml/www/oasis/">CVS web
+front end</a>. The CVS path to the documents is <tt>xml/www/oasis</tt>. </p>
+</body>
+</html>
diff --git a/content/xml/odf2xhtml/index.html b/content/xml/odf2xhtml/index.html
new file mode 100644
index 0000000..e0bf570
--- /dev/null
+++ b/content/xml/odf2xhtml/index.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+  PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0//EN" "http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><!--This file was converted to xhtml by OpenOffice.org - see http://xml.openoffice.org/odf2xhtml for more info.--><head profile="http://dublincore.org/documents/dcmi-terms/"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/><title xml:lang="de-DE">XSL transformation from 'OpenOffice.org XML' to 'XHTML 1.0'</title><meta name="DCTERMS.title" content="XSL transformation from 'OpenOffice.org XML' to 'XHTML 1.0'" xml:lang="de-DE"/>< [...]
+	@page { size: 21.59cm 27.94cm; margin-top: 2cm; margin-bottom: 2cm; margin-left: 2cm; margin-right: 2cm }
+	table { border-collapse:collapse; border-spacing:0; empty-cells:show }
+	td, th { vertical-align:top; font-size:12pt;}
+	h1, h2, h3, h4, h5, h6 { clear:both }
+	ol, ul { margin:0; padding:0;}
+	li { margin:0; padding:0;}
+	li span.odfLiEnd { clear: both; line-height:0; width:0; height:0; margin:0; padding:0; }
+	span.footnodeNumber { padding-right:1em; }
+	* { margin:0; }
+	.Contents_20_1 { font-size:12pt; font-family:Thorndale; margin-left:0cm; margin-right:0cm; text-indent:0cm; }
+	.Contents_20_2 { font-size:12pt; font-family:Thorndale; margin-left:0.499cm; margin-right:0cm; text-indent:0cm; }
+	.Contents_20_Heading { font-size:16pt; margin-bottom:0.499cm; margin-top:0.423cm; font-family:Albany; margin-left:0cm; margin-right:0cm; text-indent:0cm; font-weight:bold; }
+	.Heading_20_2 { font-size:18pt; margin-bottom:0.499cm; margin-top:0.423cm; font-family:Thorndale; font-weight:bold; }
+	.P1 { font-size:12pt; margin-left:0.499cm; margin-right:0cm; text-indent:0cm; font-family:Thorndale; }
+	.P3 { background-color:transparent; font-size:12pt; font-weight:bold; margin-bottom:0.499cm; margin-top:0cm; text-align:center ! important; font-family:Thorndale; vertical-align:middle; }
+	.P4 { background-color:transparent; font-size:12pt; margin-bottom:0.499cm; margin-top:0cm; text-align:left ! important; font-family:Thorndale; vertical-align:middle; }
+	.P5 { font-size:12pt; margin-bottom:0.499cm; margin-top:0cm; text-align:justify ! important; font-family:Thorndale; }
+	.P6 { font-size:12pt; margin-bottom:0.499cm; margin-top:0cm; text-align:left ! important; font-family:Thorndale; }
+	.P7 { font-size:12pt; margin-bottom:0cm; margin-top:0cm; text-align:justify ! important; font-family:Thorndale; }
+	.P8 { font-size:12pt; margin-left:0cm; margin-right:0cm; text-indent:0cm; font-family:Thorndale; }
+	.P9 { font-size:24pt; font-weight:bold; margin-bottom:0.499cm; margin-top:0.423cm; font-family:Thorndale; }
+	.Table_20_Contents { font-size:12pt; margin-bottom:0.499cm; margin-top:0cm; text-align:center ! important; font-family:Thorndale; background-color:transparent; vertical-align:middle; }
+	.Table_20_Heading { background-color:transparent; font-size:12pt; margin-bottom:0.499cm; margin-top:0cm; text-align:center ! important; font-family:Thorndale; vertical-align:middle; font-weight:bold; }
+	.Text_20_body { font-size:12pt; font-family:Thorndale; margin-top:0cm; margin-bottom:0.499cm; text-align:justify ! important; }
+	.Sect1 { background-color:transparent; }
+	.Stylesheets { width:32.212cm; margin-left:0cm; margin-right:-0.011cm; float:none; }
+	.Stylesheets_A1 { padding:0.097cm; border-left-width:0.0133cm; border-left-style:solid; border-left-color:#000000; border-right-style:none; border-top-width:0.0133cm; border-top-style:solid; border-top-color:#000000; border-bottom-width:0.0133cm; border-bottom-style:solid; border-bottom-color:#000000; }
+	.Stylesheets_A2 { padding:0.097cm; border-left-width:0.0133cm; border-left-style:solid; border-left-color:#000000; border-right-style:none; border-top-style:none; border-bottom-width:0.0133cm; border-bottom-style:solid; border-bottom-color:#000000; }
+	.Stylesheets_C1 { padding:0.097cm; border-width:0.0133cm; border-style:solid; border-color:#000000; }
+	.Stylesheets_C2 { padding:0.097cm; border-left-width:0.0133cm; border-left-style:solid; border-left-color:#000000; border-right-width:0.0133cm; border-right-style:solid; border-right-color:#000000; border-top-style:none; border-bottom-width:0.0133cm; border-bottom-style:solid; border-bottom-color:#000000; }
+	.Stylesheets_A { width:5.392cm; }
+	.Stylesheets_B { width:8.446cm; }
+	.Stylesheets_C { width:18.374cm; }
+	.Internet_20_link { color:#000080; text-decoration:underline; }
+	<!-- ODF styles with no properties representable as CSS -->
+	.Sect2 .Endnote_20_Symbol .Footnote_20_Symbol { }
+	</style></head><body dir="ltr" style="max-width:21.59cm;margin-top:2cm; margin-bottom:2cm; margin-left:2cm; margin-right:2cm; "><h1 class="P9"><a name="_XSL_Transformation_from_ODF_to_XHTML"><span style="margin-right:0.381cm;"/></a>XSL Transformation from ODF to XHTML<span style="margin-left:;"/></h1><p class="Contents_20_Heading">Contents</p><p class="P8"> </p><p class="P1"><a href="./#1.1.Abstract|outline" class="Internet_20_link">Abstract</a></p><p class="P1"><a href="./#1.2.Use with [...]
\ No newline at end of file
diff --git a/content/xml/optimization/current_optimization_status.html b/content/xml/optimization/current_optimization_status.html
new file mode 100644
index 0000000..c74e3bf
--- /dev/null
+++ b/content/xml/optimization/current_optimization_status.html
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+
+<HTML>
+<head>
+
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20010717;9541500">
+	<META NAME="CHANGED" CONTENT="20010803;19293705">
+
+</head>
+
+<STYLE>
+	<!--
+	BODY { font-family: "Albany", "Arial", "Helvetica", "Lucida", "Geneva", "Helmet", "SansSerif", "Andale Sans UI", "Arial Unicode MS", "Lucida Sans Unicode", "Tahoma"; font-size: 2 }
+	 -->
+</STYLE>
+
+<body TEXT="#000000">
+<TABLE FRAME=VOID CELLSPACING=0 COLS=7 RULES=GROUPS BORDER=1>
+	<COLGROUP><COL WIDTH=127><COL WIDTH=338><COL WIDTH=145><COL WIDTH=334><COL WIDTH=105><COL WIDTH=105><COL WIDTH=86></COLGROUP>
+	<TBODY>
+		<TR>
+			<TD WIDTH=127 HEIGHT=27 ALIGN=CENTER SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Document</FONT></I></B></TD>
+			<TD WIDTH=338 HEIGHT=27 ALIGN=CENTER VALIGN=TOP SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Description</FONT></I></B></TD>
+			<TD WIDTH=145 HEIGHT=27 ALIGN=CENTER SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Action</FONT></I></B></TD>
+			<TD WIDTH=334 HEIGHT=27 ALIGN=CENTER SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Current Problems</FONT></I></B></TD>
+			<TD WIDTH=105 HEIGHT=27 ALIGN=CENTER SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Build 638</FONT></I></B></TD>
+			<TD WIDTH=105 HEIGHT=27 ALIGN=CENTER SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Build 637</FONT></I></B></TD>
+			<TD WIDTH=86 HEIGHT=27 ALIGN=CENTER SDNUM="1031;2057;General"><B><I><FONT SIZE=4>Binary</FONT></I></B></TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="simple_numbercells.sxc">simple number cells</A></TD>
+			<TD ROWSPAN=2 WIDTH=338 HEIGHT=34 ALIGN=LEFT VALIGN=TOP SDNUM="1031;2057;General">This file contains 200.000 cells with numbers. This file contains no style, except for the page style.</TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Load</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_import_simple_numbercells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="40" SDNUM="1031;2057;General">40</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="2,2" SDNUM="1031;2057;General">2.2</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Save</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_export_simple_numbercells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="48" SDNUM="1031;2057;General">48</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="5,5" SDNUM="1031;2057;General">5.5</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="simple_textcells.sxc">simple text cells</A></TD>
+			<TD ROWSPAN=2 WIDTH=338 HEIGHT=34 ALIGN=LEFT VALIGN=TOP SDNUM="1031;2057;General">This file contains 200.000 cells with text. This file contains no style, except for the page style.</TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Load</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_import_simple_textcells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="33" SDNUM="1031;2057;General">33</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="2" SDNUM="1031;2057;General">2</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Save</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_export_simple_textcells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="54" SDNUM="1031;2057;General">54</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="3" SDNUM="1031;2057;General">3</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="simple_formulacells.sxc">simple formula cells</A></TD>
+			<TD ROWSPAN=2 WIDTH=338 HEIGHT=34 ALIGN=LEFT VALIGN=TOP SDNUM="1031;2057;General">This file contains 200.000 cells with simple formulas. This file contains no style, except for the page style.</TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Load</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_import_simple_formulacells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="98" SDNUM="1031;2057;General">98</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="8" SDNUM="1031;2057;General">8</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Save</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_export_simple_formulacells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="69" SDNUM="1031;2057;General">69</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="25" SDNUM="1031;2057;General">25</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="simple_editcells.sxc">simple edit cells</A></TD>
+			<TD ROWSPAN=2 WIDTH=338 HEIGHT=34 ALIGN=LEFT VALIGN=TOP SDNUM="1031;2057;General">This file contains 200 000 cells with text with line breaks. I use this file to test the performance of edit cells. Saving and loading this cells uses a different implementation than simple text cells. This file contains no style, except for the page styles.</TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Load</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_import_simple_editcells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="632" SDNUM="1031;2057;General">632</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="30" SDNUM="1031;2057;General">30</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">Save</TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><A HREF="protocoll_export_simple_editcells.sxc">see here</A></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=RIGHT SDVAL="1380" SDNUM="1031;2057;General">1380</TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=RIGHT SDVAL="36" SDNUM="1031;2057;General">36</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=127 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=338 HEIGHT=17 ALIGN=LEFT VALIGN=TOP SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=145 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=334 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+		</TR>
+		<TR>
+			<TD COLSPAN=4 WIDTH=944 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General">The values for the spreadsheet applications are taken on a Intel Pentium III/550MHz, with 256MB RAM in seconds.</TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=105 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=LEFT SDNUM="1031;2057;General"><BR></TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<!-- ************************************************************************** -->
+</body>
+
+</HTML>
diff --git a/content/xml/optimization/optimization.html b/content/xml/optimization/optimization.html
new file mode 100644
index 0000000..6e83de5
--- /dev/null
+++ b/content/xml/optimization/optimization.html
@@ -0,0 +1,748 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="AUTHOR" CONTENT="Sascha Ballach">
+	<META NAME="CREATED" CONTENT="20010601;9311185">
+	<META NAME="CHANGEDBY" CONTENT="Daniel Vogelheim">
+	<META NAME="CHANGED" CONTENT="20010725;18030177">
+</head>
+<body>
+<H1 ALIGN=CENTER>Loose list of possible optimizations in the xml
+module</H1>
+<P ALIGN=LEFT>This is a loose list of optimizations items, which the
+guys which work on the xml project find out. This list expands if any
+one found more items. The status tells what happens with this items.
+If an item is implemented, then the status change and the build
+version is add.</P>
+<P ALIGN=LEFT>Here are also all items listed which have to do in
+modules like sw, sc, graphics and so to optimize e.g. the save and
+load performance of the new fileformat.</P>
+<P ALIGN=LEFT>If anybody find also some items, where we may change
+the code then he can write a mail to me
+(<A HREF="mailto:sascha.ballach@germany.sun.com">Sascha.Ballach@germany.sun.com</A>)or
+add a task into the <A HREF="http://xml.openoffice.org/project_issues.html">IssueZilla</A>.</P>
+<P ALIGN=LEFT><A HREF="current_optimization_status.html">Here</A> can
+anybody see the current state of our optimizations and the current
+problems.</P>
+<P ALIGN=LEFT><A HREF="current_optimization_status.sxc">Here</A> is
+the complete overview as OpenOffice.org 6.0 file.</P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0 FRAME=VOID RULES=GROUPS>
+	<COLGROUP>
+		<COL WIDTH=13*>
+		<COL WIDTH=20*>
+	</COLGROUP>
+	<COLGROUP>
+		<COL WIDTH=28*>
+	</COLGROUP>
+	<COLGROUP>
+		<COL WIDTH=36*>
+	</COLGROUP>
+	<COLGROUP>
+		<COL WIDTH=159*>
+	</COLGROUP>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH COLSPAN=2 WIDTH=13%>
+				<P>Status</P>
+			</TH>
+			<TH WIDTH=11%>
+				<P>Module</P>
+			</TH>
+			<TH WIDTH=14%>
+				<P>Type</P>
+			</TH>
+			<TH WIDTH=62%>
+				<P>Description</P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>ALL</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>At the moment is the <CODE>getPropertyStates</CODE> method
+				implemented as a loop which calls the <CODE>getPropertyState</CODE>
+				method for every Property. So the Property has to be searched
+				again and again. Therefor this method needs a lot of string
+				compares. We have to use a better implementation which use, that
+				the <CODE>getPropertyStates</CODE> method gets the PropertyNames
+				in alphabetical order.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>P</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>ALL</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>We have to implement a XMultiPropertySet interface and use it
+				instead of the XPropertySet interface to get and set the style
+				properties. (Done in some modules)</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>P</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>ALL</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Code/Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Don�t export XML tokens as character pointer in an own object
+				file. This expand the size of each DLL which use any of these XML
+				tokens. This can change to a <CODE>GetToken(nId)</CODE> and
+				<CODE>IsToken(nId)</CODE>.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Remember the style names of the cells so they have not to get
+				again. (save spreadsheet document)</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Collect all cells and his styles and merge the cells to ranges
+				and set the styles on this ranges. (load spreadsheet document)</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Remember all API objects which are used again and again, so
+				they have not to create so often.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Find a better way to find out whether a cell contains a
+				annotation or not.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>The method <CODE>getFormula()</CODE> change in every document
+				which is not English the language to get the English formula.
+				This is not necessary.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>ALL</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Code</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Some Attributes contains the old virtual <CODE>importXML</CODE>
+				and <CODE>exportXML</CODE> methods. These can remove, because the
+				XML attribute export is changed</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>ALL</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Use MultipropertySet in the API for PageDescriptor�s</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>The package component has two major performance problems:</P>
+				<OL>
+					<LI><P>When saving, all zip file data is written to a buffer in
+					memory which is then passed to the UCB to be written to disk. If
+					there are multiple OLE objects, this could be crippling. Data
+					should be written to disk, buffered.</P>
+					<LI><P>When loading, whole streams are read into memory at once
+					and are then read from memory. They should be uncompressed and
+					written to temporary files and be read from there instead</P>
+				</OL>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>P</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SW</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>The XML load/save creates every time a DrawModel
+				(SwDoc::MakeDrawModel). This must change, so its only created if
+				its needed.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>On save and load of edit cells the method <CODE>GetTextForwarder()</CODE>
+				makes to much to often. This is not necessary. On every creation
+				of a new API Object like XTextRange, XTextCursor and so on on the
+				same cell creates a new object and set all the properties and so
+				on. The method should remember the created object and give this
+				again and again.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>C</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>On save of a document the method <CODE>GetOutputStringImpl</CODE>
+				ask for the numberformat on every cell. On documents with more
+				languages this needs very long, because the language is every
+				time changed. The calling method knows the numberformat, but
+				there is no way to give this to the method with the API.</P>
+				<P>This optimization is changed to a optimization of the
+				<CODE>ChangeIntl</CODE> method and the use of an English
+				NumberFormatter to ask whether a string cell use a NumberFormat.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Extend the API to get all formated ranges with one call. This
+				means to make a possibility to get all formated ranges with the
+				same format as XCellRanges object. So we have to ask for the
+				autostyle only one time.</P>
+				<P>The same should be possible while loading a document. Here we
+				need a possibility to create a XCellRanges object and give them
+				all ranges with the same format and then set the format on all
+				this ranges in one time.</P>
+				<P>Finally we have to use this extensions.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Use a English NumberFormatter to reduce the calls of the
+				<CODE>ChangeIntl<CODE> method.</CODE></CODE></P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>SC</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>We have also to optimize the <CODE>GetTextForwarder</CODE>
+				method for the saving of the PageStyles.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P>&nbsp;</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>The <CODE>GetKeyByAttrName</CODE> method should be optimized
+				so the string will be created only once and then the string
+				should be cached. This increase the performance, because the same
+				strings are used very often.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>P</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>Creating the <CODE>PropertySetMapper</CODE>s takes a long
+				time, mainly due to string creation. This can be sped up by
+				storing the string length in the maps.</P>
+				<P><I>dvo: As it turns out, the string length doesn't help a
+				whole lot. Copying the string from sal_Char* to sal_Unicode* and
+				the corresponding malloc seems to take most of the time. So I'm
+				afraid there's nothing we can do about this.</I></P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P>When loading/saving small documents, reading/setting the
+				document settings takes a long time. In the writer, reading the
+				document settings takes about as long as importing 200
+				paragraphs. This should be investigated.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>The NumberFormatter takes quite long to find the
+				first data style for a particular language. Thus, exporting the
+				first textfield that uses a number format takes about as long as
+				exporting 25 paragraphs.</P>
+				<P ALIGN=LEFT><I>dvo: I can't think of any way to avoid this,
+				though.</I></P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>P</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>The NumberFormatsSupplier is always obtained from
+				the document, even though it is not used. That takes quite some
+				time in small documents that don't use it.</P>
+				<P ALIGN=LEFT><I>dvo: creating the NumberFormatsSupplier
+				on-demand fixes the problem. However, this requires an
+				incompatible build, so it is not checked in yet.</I></P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>Resetting existing styles to default takes a long
+				time during import. (use <CODE>XMultiPropertsStates</CODE>
+				interface). Currently this uses getPropertySet and then sets them
+				to default one-by-one.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>P</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML/Writer</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>All styles for a style family are obtained from the
+				document through an <CODE>XIndexAccess</CODE>, which is then used
+				to iterate over all styles. The current Writer implementation for
+				that is really, really slow (probably true for the other apps as
+				well, but I haven't checked).</P>
+				<P ALIGN=LEFT><I>dvo: I have tried replacing the XIndexAccess
+				with an XNameAccess. This speeds obtaining all styles up from
+				280ms to 10ms, which is almost a factor of 30. However, I'm not
+				sure if other apps have the same performance characteristics.
+				Also, a properly implemented getByIndex should resolve this
+				issues, too. Therefore, I will not commit this 'fix'.</I></P>
+				<P ALIGN=LEFT><I>dvo: I submitted a performance bug about this
+				(#90251#)</I></P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>Writer</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>The conversion between UI names and
+				internationalized names is slow.</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>Writer</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>The IsPhysical property with styles is much slower
+				than most other properties.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML / Writer</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>In exportTextContentEnumeration, determining which
+				(relevant) service is implemented by the current XTextContent is
+				quite slow. For a simple document with 14 text content objects
+				(which run twice through the method) the total time needed to
+				determine the service takes as much time as exporting 80 simple
+				paragraphs.</P>
+				<P ALIGN=LEFT><I>dvo: A more radical approach to this problem
+				would be to give an XTextContent a required property which
+				returns this type as a string or an integer key. However, this
+				would require a modified TextContent service.</I></P>
+				<P ALIGN=LEFT><I>dvo: Most of the time seems to be spent in
+				asking a shape whether it happens to be of some type of service.
+				The way the interfaces are, there aren't too many way to speed up
+				the shape implementation. Simply asking the shape early solves
+				this problem nicely. For the 'einfach' Test-Dokument, checking
+				for shapes early reduces time for the entire
+				exportTextContentEnumeration by 10%.</I></P>
+				<P ALIGN=LEFT><I>dvo: I submitted a performance Bug #90240# about
+				this.</I></P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>I</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>Writer</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>The 'FileLink' property of text sections is
+				implemented fairly slow.</P>
+			</TD>
+		</TR>
+		<TR BGCOLOR="#e6e6e6" VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>D</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>The FilterPropertyInfo_mpl::AddProperty method is
+				quite slow because it used an (albeit hacked-up) version of
+				insertion sort.</P>
+				<P ALIGN=LEFT><I>dvo: Using STL sort during GetApiNames() speeds
+				up the operation by about 30%.</I></P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=5%>
+				<P>C</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P><BR>
+				</P>
+			</TD>
+			<TD WIDTH=11%>
+				<P>XML</P>
+			</TD>
+			<TD WIDTH=14%>
+				<P>Runtime</P>
+			</TD>
+			<TD WIDTH=62%>
+				<P ALIGN=LEFT>Importing a single control is about as slow as
+				importing 150 simple paragraphs.</P>
+				<P ALIGN=LEFT><I>dvo: The time is spent in loading several DLLs
+				required for the controls. This is probably unavoidable. The
+				second control is quite speedy.</I></P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P>Last change: 07/25/2001</P>
+<P><B>Agenda</B>:</P>
+<P STYLE="margin-bottom: 0.01cm">Status Symbols:</P>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0>
+	<COL WIDTH=16*>
+	<COL WIDTH=240*>
+	<TR VALIGN=TOP>
+		<TD WIDTH=6%>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=94%>
+			<P>Idea 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=6%>
+			<P>D</P>
+		</TD>
+		<TD WIDTH=94%>
+			<P>Done</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=6%>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=94%>
+			<P>in Progress</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=6%>
+			<P>C</P>
+		</TD>
+		<TD WIDTH=94%>
+			<P>Cancelled</P>
+		</TD>
+	</TR>
+</TABLE>
+<P STYLE="margin-bottom: 0.01cm"><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/xml/optimization/optimization2.html b/content/xml/optimization/optimization2.html
new file mode 100644
index 0000000..83beb0b
--- /dev/null
+++ b/content/xml/optimization/optimization2.html
@@ -0,0 +1,115 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE>Possible optimizations in the xml module</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 8 PreAlpha (Win32)">
+	<META NAME="AUTHOR" CONTENT="Sascha Ballach">
+	<META NAME="CREATED" CONTENT="20031021;10425905">
+	<META NAME="CHANGEDBY" CONTENT="Sascha Ballach">
+	<META NAME="CHANGED" CONTENT="20031021;12355280">
+	<STYLE>
+	<!--
+		@page { size: 29.7cm 21cm; margin: 2cm }
+		P { margin-bottom: 0.21cm }
+		TD P { margin-bottom: 0.21cm }
+	-->
+	</STYLE>
+</head>
+<body LANG="de-DE" DIR="LTR">
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+	<COL WIDTH=44*>
+	<COL WIDTH=171*>
+	<COL WIDTH=20*>
+	<COL WIDTH=22*>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TD WIDTH=17%>
+				<P LANG="en-US"><B>Optimization</B></P>
+			</TD>
+			<TD WIDTH=67%>
+				<P LANG="en-US"><B>Description</B></P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US"><B>Modules</B></P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US"><B>State</B></P>
+			</TD>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=17%>
+				<P LANG="en-US">Use of ANY and uno::Reference</P>
+			</TD>
+			<TD WIDTH=67%>
+				<P LANG="en-US">Like in the Mail of Daniel B&ouml;lzle in the
+				dev.OpenOffice.org mailing list from 16.10.2003 13:30 described
+				the use of Anys can be optimized. A test in the SC project
+				increased the performance by 10 percent, so every module should
+				do this change in the load and save methods.</P>
+				<P LANG="en-US">The main improvements are to use uno::makeAny()
+				in queryInterface instead of</P>
+				<P LANG="en-US">uno::Any aR; aR &lt;&lt;=
+				uno::Reference&lt;x&gt;(this); return aR;</P>
+				<P LANG="en-US">like this:</P>
+				<P LANG="en-US">return uno::makeAny( uno::Reference&lt;x&gt;(this));</P>
+				<P LANG="en-US">I did also all other in the mail described
+				changes. See also
+				<A HREF="http://api.openoffice.org/TipsAndTricks/cpp_uno_coding_hints.html">http://api.openoffice.org/TipsAndTricks/cpp_uno_coding_hints.html</A></P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US">All</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US">In progress</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=17%>
+				<P LANG="en-US">2 runs to find EditCells</P>
+			</TD>
+			<TD WIDTH=67%>
+				<P LANG="en-US">At the moment we have to go over all text cells
+				to find out whether this cells are simple text cells or EditCells
+				where we have to collect the autostyles for. This could be done
+				by a special Interface in the API. So we can use the much time
+				faster core, which knows where the EditCells are instead of
+				getting all text cells, getting the implementation and test
+				whether it is a EditCell. A fast test showed a possible
+				improvement of 20 percent, while commenting out the complete run.
+				A real possible improvement should be 10 percent, because there
+				is something to do to find the EditCells, but it is much faster
+				to make it directly.</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US">SC</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US">Planned</P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=17%>
+				<P LANG="en-US">Nothing to do in ScDocument::IdleCalcTextWidth()</P>
+			</TD>
+			<TD WIDTH=67%>
+				<P LANG="en-US">At the moment the method IdleCalcTextWidth is
+				called and does a lot of unnecessary things. In a test the method
+				returns directly after calling and the test document is saved 10
+				percent faster. This is a very simple change and we should do it.</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US">SC</P>
+			</TD>
+			<TD WIDTH=8%>
+				<P LANG="en-US">Planned</P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/xml/package.html b/content/xml/package.html
new file mode 100644
index 0000000..bb54a7b
--- /dev/null
+++ b/content/xml/package.html
@@ -0,0 +1,804 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>XML Packages</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20010801;20531125">
+	<META NAME="CHANGEDBY" CONTENT="Daniel Vogelheim">
+	<META NAME="CHANGED" CONTENT="20010801;20534064">
+</head>
+<body>
+<H1>XML Packages</H1>
+<H2>Purpose of this document</H2>
+<P>At the end of September, I (<I>dvo</I>) have asked the
+openoffice.org community for help on the problem of embedding binary
+content in XML documents. This page is intended to summarize the
+discussion and provide a solid foundation that will guide our
+implementation efforts. 
+</P>
+<P>We will first restate the problem. Then follows a summary of the
+requirements that have been stated in the <A HREF="http://www.openoffice.org/www-discuss/">discuss</A>
+and <A HREF="http://xml.openoffice.org/xml-dev/">xml-dev</A> mailing
+lists. The candidate solutions mentioned on the mailing lists are
+then examined in light of these requirements. Finally, a conclusion
+is presented. 
+</P>
+<H3>A few definitions</H3>
+<P>To clarify the following discussion, a definition of a few terms
+for use within this document may be in order: 
+</P>
+<DL>
+	<DT STYLE="margin-bottom: 0.5cm">document 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A document comprises everything a user considers to part of his
+	text, spreadsheet or presentation. In general this will include
+	several images or OLE objects in addition to the main content. 
+	</DD><DD STYLE="margin-bottom: 0.5cm">
+	If images are linked into the document, they are not considered part
+	of it. Whether an image is linked or embedded into the document is
+	determined by the user. Due to limitations in the current OLE
+	handling, OLE objects must always be embedded. 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	file 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A file is a sequence of bytes as stored in the operating system's
+	file system. This fairly obvious definition serves to distinguish
+	between the logical view (the document) and the physical view (the
+	file). 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	<EM>b</EM>inary <EM>l</EM>arge <EM>ob</EM>ject, BLOB 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A BLOB contains binary data that has no structured content that
+	could reasonably be encoded as XML data. Usually, BLOBs will be data
+	in established binary formats such as GIF, JPEG, or OLE data
+	streams. 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	subdocument 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A subdocument refers to an individual component of the document.
+	Each binary large object (BLOB) is one subdocument, as is the main
+	document content encoded as XML. 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	main document content 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	The main document content refers to the subdocument that best
+	represents the document as a whole. For example, if an OpenOffice
+	Writer document consists of an XML subdocument containing the text
+	body, and several image subdocument, then the XML subdocument would
+	form the main document content. 
+	</DD></DL>
+<H2>
+The Problem</H2>
+<P>OpenOffice and the next generation of StarOffice by default use an
+XML based file format (but the user may choose to save in a different
+format). Therefore this project differs from many others, as this is
+an XML based file format intended to be truly a format for the
+masses. The requirements for a native file format are different
+(usually more demanding) than those for an interchange format. 
+</P>
+<P>XML is meant for structured content and has no native support for
+binary objects (BLOBs) such as images, OLE objects or other media
+types. Since embedding of binary objects is needed for office
+documents, a way to handle XML and binary data in the same document
+must be provided. 
+</P>
+<P>One solution may be to simply store the XML data in a file and
+link to image data in separate files, much like in HTML documents.
+While linking files at the user's request should be possible, this is
+in general not considered adequate for office documents. A document
+should be stored in a single file to make external handling of the
+document (e.g. copying the document) possible. Therefore, binary
+content must be stored in the same file as the XML content, requiring
+either a <EM>package</EM> format or a means to encode binary content
+in XML. For the sake of simplicity, we will refer to all solutions
+that store XML and BLOB data in a single file as packages. 
+</P>
+<H2>The Requirements</H2>
+<P>The following requirements have been identified for the package
+format: 
+</P>
+<H3>A. Efficient Operation</H3>
+<P>Users have traditionally required efficient operation, especially
+for basic functionality such as loading or saving of documents. It is
+our experience that independent loading (or saving) of subdocuments
+is the key to efficient handling of large documents. Additionally,
+users require that disk space is used efficiently. This leads us to
+require the document format to support: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">small file sizes 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">on-demand loading (i.e.,
+	independent loading of subdocuments) 
+	</P>
+	<LI><P>independent saving of subdocuments 
+	</P>
+</OL>
+<P>These requirements are strongly supported by ten years of
+experience at StarOffice. Failing to meet these requirements has
+repeatedly resulted in dissatisfaction and significant protests from
+the user base. 
+</P>
+<P><B>Note</B> on independent saving of subdocuments: Previous
+versions of StarOffice have gotten significant benefit from copying
+subdocuments on the file system level rather than reading and then
+writing subdocuments through the <A HREF="http://ucb.openoffice.org/">UCB</A>.
+This should be supported by the package format. Saving modified
+subdocuments into an existing (compound) document may provide further
+benefits. 
+</P>
+<H3>B. Compatibility with Existing Tools</H3>
+<P>A primary motivation for creating an XML based file format is the
+ability to process, create and manipulate StarOffice documents with
+external tools. To deserve the label &quot;open&quot; document
+format, these tools should be standard and widely available. As far
+as possible, this should apply to both, the document and the
+individual subdocuments (if applicable). In particular, the main
+document content (using XML) should be accessible to standard XML
+tools. 
+</P>
+<P>This leads us to state three subrequirements: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">Subdocuments should be usable with
+	standard tools. In particular, XML subdocuments should be usable
+	with standard XML tools, e.g. XSLT transformations. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The document should be accessible
+	with standard tools, making it possible to insert, modify and
+	extract subdocuments, e.g. similar to zip or other popular
+	archivers. 
+	</P>
+	<LI><P>The document should be accessible with ASCII-based tools,
+	e.g. the Windows file find function. 
+	</P>
+</OL>
+<P><B>Note:</B> During discussion on openoffice.org mailing lists
+several people preferred requirement number 1 to be extended to the
+complete document. This would essentially require the document format
+to be XML as well, with subdocuments (including BLOBS) being embedded
+within the XML structure. 
+</P>
+<P><B>Note:</B> Since XML is based on Unicode, ASCII based tools
+cannot generally be assumed to work on XML files. Thus, no solution
+will be able to fully support the third requirement. If UTF-8
+encoding is used, ASCII-based tools will work at least for those
+languages that can be properly represented in ASCII, like English or
+Latin. 
+</P>
+<P><B>Note:</B> Compression interferes with some of the requirements
+above. The discussion on the mailing list has clearly proven that
+those requirements are very important to some users. To support these
+users, 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">compression should be made
+	optional, and 
+	</P>
+	<LI><P>an additional implementation that writes pure XML (and saves
+	binary data into separate files) should be created. 
+	</P>
+</OL>
+<P>Formats supporting compression on a per subdocument basis would
+have an additional advantage in this respect. Also, this would allow
+a subdocument with e.g. meta information (title, keywords, etc.) to
+be stored uncompressed, making it more easily accessible. 
+</P>
+<H3>C. Security</H3>
+<P>An additional advantage that may be gained through the use of a
+package is easy support for document security. We can distinguish
+between two security considerations: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">privacy: be able to encrypt
+	(partial) documents 
+	</P>
+	<LI><P>integrity: be able to verify origin of (partial) documents 
+	</P>
+</OL>
+<P><B>Note:</B> These requirements are of fairly low priority. 
+</P>
+<H3>D. Additional Issues</H3>
+<OL>
+	<LI><P>A package structure supporting documents and subdocuments
+	makes it easy to add additional information to a document, even if
+	the reference implementation does not understand it. For example, in
+	situations where a certain transformation is used very often, the
+	transformation result may be stored in the package as well. 
+	</P>
+	<LI><P>The current implementation is based on the SAX API. XML
+	filters (transformations) also using the SAX API can be pipelined,
+	e.g. they can import (or export) data into (or from) OpenOffice by
+	going directly through the API, rather than going through a file. 
+	</P>
+</OL>
+<H2>The Contenders</H2>
+<P>On the openoffice.org mailing lists, the following possible
+solutions were suggested: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">ZIP or JAR files 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">XML with binary data being
+	ASCII-encoded within special tags (e.g. base64) 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">MIME files 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">.tgz files 
+	</P>
+	<LI><P>BONOBO libefs 
+	</P>
+</OL>
+<P><B>Note:</B> The participants quickly focused on two choices: JAR
+and XML 
+</P>
+<P><B>Note:</B> ZIP and JAR files are identical for most intents and
+purposes. JAR differs from the older ZIP in the file ending, as well
+as in additional meta information stored in a directory called
+META-INF. JAR files can be accessed using unmodified ZIP tools. 
+</P>
+<H2>Examination of the contenders</H2>
+<P>This chapter gives an overview of how well the various contenders
+met the specified requirements. It was my (<I>dvo</I>) impression
+that most people would agree on the suitability of the various
+contenders for the various requirements. The disagreement was mainly
+between the importance of the requirements. 
+</P>
+<P>In particular one group valued accessibility with XML tools (B1)
+very high and consequently would speak for XML with base64 encoding,
+while most others would prefer ZIP/JAR. 
+</P>
+<H3>ZIP / JAR</H3>
+<P>Tools to create and manipulate ZIP files are widely available on
+all platforms. The manifest file used with JAR files is usually
+considered optional and may even be created using a text editor.
+Access to subdocuments requires unzipping the required subdocuments
+first. ASCII based tools will in general not work on the package,
+although (at the user's request) individual subdocuments could be
+stored uncompressed, thus making them available to ASCII based tools.</P>
+<P>Since ZIP files have an index, efficient on-demand loading of
+subdocuments can be achieved. Subdocuments can be copied from one
+package to another without uncompressing and compressing them first.
+With some hackery for on-demand saving, only those files following
+the newly-written subdocuments need to be written. Due to (optional)
+compression, files can be small, although not quite as small as .tgz
+files. 
+</P>
+<P><B>Note:</B> As requested on the mailing list, the JAR manifest
+file should be replaced by an XML-based manifest file. The older JAR
+manifest may be supported for compatibility reasons. This is to be
+determined. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>ZIP / JAR</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>XML + base64</H3>
+<P>This suggestion is to use plain XML documents and embed binary
+content as base64 encoded ASCII in special elements. 
+</P>
+<P>Tools to generate or manipulate subdocuments in this format are
+not commonly available, but could be written with reasonable effort.
+Usability of the main document content with XML tools is, of course,
+excellent. ASCII based tools should work with no problems (except for
+the already mentioned UTF encodings). 
+</P>
+<P>Without an index, on-demand loading is not possible, neither is
+on-demand saving. Files are not compressed and binary subdocuments
+are even expand by 33% due to the base64 encoding. 
+</P>
+<P><B>Note:</B> In the discussion lists, several remedies to allow
+on-demand reading were suggested. Either the inclusion of indices in
+the XML file, or placing the binary data at the end of the file. The
+former was considered to be non-XML (as it relies on the physical
+layout of the XML data) and useless, since any standard XML tool
+would not update the index and thus OpenOffice couldn't rely on it.
+The latter can not be done with standard (e.g. SAX-based) parsers, as
+they are used in the current implementation. The SAX API is necessary
+for the filter pipelining mentioned in the requirements section, so
+forgoing SAX may have significant drawbacks. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>XML + base64</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>MIME</H3>
+<P>MIME is the established packaging format for emails. As is
+required for SMTP compatibility, it is ASCII-based (7bit ASCII).
+Non-Mailer tools to manipulate MIME files are rare. 
+</P>
+<P>Being an ASCII based format, accessibility to ASCII based tools is
+excellent. However, the encoding of non-ASCII characters is solved
+differently than in XML. Tools to manipulate MIME files (outside of
+mail programs) are not readily available, but could be written with
+reasonable effort. Access with XML tools requires unpacking first,
+but as said before the tools to do so are not currently available. 
+</P>
+<P>MIME has no index of subdocuments, making on-demand loading
+difficult. For saving of individual subdocuments, a reasoning similar
+to ZIP files applies. However, copying subdocuments requires
+accessing them, which is slow on MIME due to the lack of an index.
+Since no compression is used, files get fairly large. In addition,
+binary documents are usually encoded in base64, enlarging them by
+33%. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII 
+				</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>MIME</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>.tgz</H3>
+<P>The .tgz format (tar files compressed with gzip) is the most
+popular archiving format on the UNIX platform. Tools to manipulate
+.tgz files exist on most other platforms as well. As participants on
+the mailing lists mentioned, it is used as package format for
+KOffice. 
+</P>
+<P>.tgz operates according to the compress-after-packaging principle.
+in general, this results in very good compression ratios. However,
+the same principle causes on-demand loading of subdocument to be
+severely inefficient: Not only is it impossible to quickly determine
+the start position of subdocuments, it is also impossible to start
+reading subdocuments once the start position is known because the
+state of the uncompression tables cannot easily be reconstructed. For
+the same reason, changing a subdocument or even copying subdocuments
+is inefficient. 
+</P>
+<P>Availability of tools for manipulating .tgz files is good, and
+even very good on UNIX platforms. Accessibility to subdocuments
+requires unpacking the subdocuments first, which is slow because the
+document must be uncompressed from the start. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>.tgz</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>Comparison Table</H3>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII [6]</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>ZIP / JAR</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [1]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+		</TR>
+		<TR>
+			<TH>
+				<P>XML + base64</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>- [3]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [4]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+		<TR>
+			<TH>
+				<P>MIME</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>- [1]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>- [2]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [4]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+		<TR>
+			<TH>
+				<P>.tgz</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+ [5]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<P ALIGN=CENTER>++&nbsp;=&nbsp;very good, +&nbsp;=&nbsp;good,
+0&nbsp;=&nbsp;medium, -&nbsp;=&nbsp;bad, --&nbsp;=&nbsp;very bad</P>
+<P>Remarks:</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">Copying subdocuments is possible.
+	With some hackery, (repeated) partial updates can be supported. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Requires unpackaging (or
+	package-aware tools), so score depends on availability of tools and
+	their efficiency 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">On-demand loading may be
+	implemented at the expense of being unable to use standard XML
+	parser APIs (e.g. SAX). 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Tools can be written with
+	reasonable effort but don't currently exist; at least not on many
+	platforms. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Very good on Unix, good on other
+	platforms. 
+	</P>
+	<LI><P>Due to XML being Unicode-based, ASCII-based tools probably
+	don't work in many circumstances, independent of the document
+	format. 
+	</P>
+</OL>
+<H3>libefs 
+</H3>
+<P>Additionally, the BONOBO libefs was suggested. Since this was not
+much discussed in the mailing lists, I (<I>dvo</I>) tried to find out
+about libefs from the web. This was my impression: 
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">libefs was created to solve a
+	problem very similar to ours. It is designed to be an ambitious
+	file-system-in-a-file solution. If it works out the way its
+	developers imagine, it will be technically superior to the other
+	proposals discussed here. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The page didn't mention any ports,
+	thus making it a UNIX solution only. This prohibits its use in a
+	cross-platform application like OpenOffice. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">No external tools to manipulate
+	libefs files exist. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The page I consulted referred to
+	it as &quot;very much a work-in-progress&quot;, meaning that
+	currently it is not suitable for a consumer product. 
+	</P>
+	<LI><P>The libefs documentation was a bit unclear on the
+	relationship between libefs API and libefs implementation (meaning:
+	file format(s)). If it is mainly an API, it would compete with the
+	current <A HREF="http://ucb.openoffice.org/">UCB</A> architecture. 
+	</P>
+</UL>
+<H3>Security</H3>
+<P>Documents could of course be encrypted for all candidate formats.
+All formats could encrypt subdocuments as well, except for
+XML+base64, which would make it impossible to encrypt the main
+document content without encrypting the binaries as well. In .tgz,
+subdocument encryption could adversely affect compression, since the
+entire file is compressed at once. 
+</P>
+<P>The same applies to file integrity verification. JAR is very
+appealing in this regard, as it has already the full infrastructure
+for subdocument and document integrity verification in place. 
+</P>
+<H2>The Conclusion</H2>
+<P>The JAR file format seems to provide the best balance among the
+stated requirements. Unlike all other formats, it does not have any
+real weakness in regard to any of the requirements, and quite a lot
+of advantages. 
+</P>
+<P>If one values accessibility with standard XML tools very high, XML
++ base64 seems a logical choice. While this is one of the
+requirements for OpenOffice, the xmloff development team does not
+follow the opinion that this single requirement significantly exceeds
+all other requirements in importance. To accommodate this user base,
+an additional pure XML file format with external subdocuments should
+be created. 
+</P>
+<H3>Remaining Issues</H3>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Decide on meta information and
+	manifest file format. 
+	</P>
+	<LI><P>Implement a UCB that allows pure XML documents. 
+	</P>
+</UL>
+<H3>Further Reading</H3>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Most of these topics have been
+	discussed in detail on the openoffice.org <A HREF="http://www.openoffice.org/www-discuss/">discuss</A>
+	and <A HREF="http://xml.openoffice.org/xml-dev/">xml-dev</A> mailing
+	lists. The archives should provide more information. 
+	</P>
+	<LI><P>Details of ZIP and many other file formats are described on
+	<A HREF="http://www.wotsit.org/">www.wotsit.org</A>. 
+	</P>
+</UL>
+<HR>
+<P><FONT SIZE=2>The <A HREF="http://xml.openoffice.org/">xmloff</A>
+development team <BR>Summarized by <A HREF="mailto:dvo@openoffice.org">dvo</A>
+</FONT>
+</P>
+</body>
+</HTML>
diff --git a/content/xml/project_tools.html b/content/xml/project_tools.html
new file mode 100755
index 0000000..6add620
--- /dev/null
+++ b/content/xml/project_tools.html
@@ -0,0 +1,46 @@
+<!-- Note:  You don't have to fill in the name of your project
+with ONE exception:
+you must specify the project name for the Version control link. -->
+
+<div class="label"><strong>Project tools</strong></div>
+<div class="body">
+  <div> <a href="/servlets/ProjectHome">Project home</a> </div>
+  <div> <a href="/servlets/ProjectMemberList">Membership</a> </div>
+</div>
+<div class="body">
+  <div> <a href="/servlets/ProjectNewsList">Announcements</a> </div>
+ <!-- #if ($isLoggedIn && !$loginUser.isAnonymous())
+  <div><a href="/servlets/ProjectForumView">Discussion forums</a></div>
+  #end -->
+  <div> <a href="/servlets/ProjectMailingListList">Mailing lists</a> </div>
+</div>
+<div class="body">
+  <div> <a href="/servlets/ProjectDocumentList">Documents &amp; files</a> </div>
+  <div><a href="/source/browse/xml">Version control</a> </div>
+</div>
+<div class="body">
+  <div> <a href="/servlets/ProjectIssues">Issue tracker</a> </div>
+ <!-- #if ($isLoggedIn && !$loginUser.isAnonymous())
+  <div><a href="http://qa.openoffice.org/issues/buglist.cgi?cmdtype=runuserdefault">My issues</a></div>
+  #end </div> -->
+<!--Other links should just be added using <div>...</div>, with regular expressions, eg., <div>about-downloads.html</div>, to link to http://[projectname].openoffice.org/about-downloads.html, which is in the project/www/ directory.  To link to, say, http://[projectname].openoffice.org/information/index.html, use <div>/information/index.html</div>. 
+
+Thus:
+
+<div>file.html</div>
+<div>/directory/file.html</div>
+
+-->
+
+
+</div>
+<div class="label"><strong><a href="http://wiki.services.openoffice.org/wiki/Xml">Wiki</a></strong></div>
+<div class="body">
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Efforts">Current Efforts</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/ContributionAreas">Contributions</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/ArticlesAndBooks">Articles and Books</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Research">Reports and Research</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Tools">Tools</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Filters">Filters</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Modules">Modules</a> </div>
+</div>
diff --git a/content/xml/research.html b/content/xml/research.html
new file mode 100644
index 0000000..f2edf53
--- /dev/null
+++ b/content/xml/research.html
@@ -0,0 +1,10 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Research">Reports and Research Documents covering the OpenDocument format</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Research">Wiki</a>.
+</body>
+</html>
+
diff --git a/content/xml/saxecho/index.html b/content/xml/saxecho/index.html
new file mode 100644
index 0000000..4fc3baa
--- /dev/null
+++ b/content/xml/saxecho/index.html
@@ -0,0 +1,63 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head><title>SAXEcho</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>SAXEcho</h1>
+<p align="justify"><strong>Project Owners:</strong> <a href="mailto:hao.mi@sun.com">Michael Mi</a>, <a href="mailto:aidan@openoffice.org">Aidan Butler</a><br/>
+<small>(please use the provided <a href="http://xml.openoffice.org/servlets/ProjectMailingListList">mailing lists</a> for discussion of the XML based file format and related issues.)</small>
+</p>
+
+<h2>Overview</h2>
+SAXEcho is an application which runs in parallel to OpenOffice and shows the XML representation of the current document. The application was created by Michael Mi, and has been more recently been expanded by Aidan Butler. The code is Java based, and works by attaching to a OOo process which has been set to listen on a specific port.
+
+<h2>Functionality</h2>
+<p>The SAXEcho program supports the following:</p>
+	<ul>
+	<li>Displaying the XML content of a currently opened OOo document. The result is displayed as plain text and an XML tree structure.</li>
+	<li>Modification of the XML structure by adding, editing and removing nodes.</li>
+	<li>The Assignment of a DTD to the XML representation.</li>
+	<li>The Validation of the displayed XML.</li>
+	<li>The use of an XSLT style-sheet, to display a transformed version of an  OOo document that is currently open.</li>
+	</ul>
+
+<h2>Usage Instructions</h2>
+<p>Before you start, you will need the following:</p>
+	<ul>
+	<li>An OpenOffice.org installation</li>
+	<li>Java 1.3 or greater. If you have an installation that is less than 1.4, you will also need Xalan and an external parser e.g. Xerces or Crimson</li>
+	<li>The SAXEcho source code which is available <a href="http://xml.openoffice.org/source/browse/xml/tools/SAXEcho/source/">here</a></i>
+	</ul>
+
+<h3>To compile the SAXEcho program do the following:</h3>
+	<b>Windows:</b>
+		<ol>
+			<li>Edit the <b>set office =</b> line to point to your OOo installation</li>
+			<li>Execute the <b>SAXEcho.bat</b> file</li>
+		</ol>
+
+	<b>Unix:</b>
+		<ol>
+			<li>Set you CLASSPATH to include all of the jar files in your <b>&lt;OOo-install-dir&gt;/program/classes/</b> directory</li>
+			<li>execute <b>javac SAXEcho.java</b></li>
+			<li>execute <b>java SAXEcho</pre></b>
+		</ol>
+
+<p>Alternatively, the <b>SAXEcho/source</b> directory contains a dmake <b>makefile.mk</b>, which can be used to build the source.</p>
+ 
+<h3>Configuring OpenOffice.org for usage with SAXEcho</h3>
+<p>In order for the SAXEcho program to work with OOo, you must start OpenOffice with the following switches:</p>
+	<pre>	<tt>%soffice -accept=socket,host=localhost,port=2002;urp;</tt></pre>
+	
+
+
+
+<h2>SAXEcho Displaying an OOo Document in Tree form <h2>
+<img src="xmltree.jpg" name="XmlTree Display"/>
+<h2>SAXEcho Displaying an OOo document in Plain Text form<h2>
+<img src="xmlflat.jpg" name="Plain Text Display"/>
+
+</body>
+
+</html> 
diff --git a/content/xml/standardisation/index.html b/content/xml/standardisation/index.html
new file mode 100644
index 0000000..07cc98f
--- /dev/null
+++ b/content/xml/standardisation/index.html
@@ -0,0 +1,68 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<title>
+Inter Office Suite Collaboration
+</title>
+</head>
+<body>
+<h1> Inter Office Suite Collaboration</h1>
+
+<p align="justify"> 
+This site will contain up to date information on the
+ongoing quest for standardisation amongst the various open office suites. It is
+hosted at OpenOffice.org and is meant to be the home for all office developers interested in this
+effort, particularly GnomeOffice, KOffice and OpenOffice.org.
+We hope to
+find many possible areas where we can collaborate, and hopefully share code. 
+</p>
+<p align="justify">
+The
+first issues we want to explore are:
+</p>
+<ul>
+<li> Structured file format - a solution to the problem of XML Packaging</li>
+<li> XML File formats - is it possible to have over-lapping DTDs ?</li>
+<!-- <li> Kill Daniel - for his continuing use of the
+phrase 'To boldly go where no office suite has gone before' </li> --> 
+</ul>
+
+<h2>Mailing List</h2>
+<a name="list_archives"></a>
+<CENTER><TABLE CELLPADDING="4" CELLSPACING="1" BGCOLOR="#ffffff" WIDTH="100%">
+<TBODY>
+	<TR>
+		<TD COLSPAN="4" BGCOLOR="#00315a" ALIGN="middle"><FONT COLOR="#ffffff" FACE="Arial, Helvetica" SIZE="2"><B>Inter-Office Suite Mailing List</B></FONT></TD>
+	</TR>
+	<TR>
+		<TD BGCOLOR="#99ccff" ALIGN="middle"><FONT COLOR="#00315a" FACE="Arial, Helvetica" SIZE="2"><B>List</B></FONT></TD>
+		<TD BGCOLOR="#99ccff" ALIGN="middle"><FONT COLOR="#00315a" FACE="Arial, Helvetica" SIZE="2"><B>Subscribe</B></FONT></TD>
+		<TD BGCOLOR="#99ccff" ALIGN="middle"><FONT COLOR="#00315a" FACE="Arial, Helvetica" SIZE="2"><B>Unsubscribe</B></FONT></TD>
+		<TD BGCOLOR="#99ccff" ALIGN="middle"><FONT COLOR="#00315a" FACE="Arial, Helvetica" SIZE="2"><B>Browse Archives</B></FONT></TD>
+	</TR>
+
+	<TR>
+		<TD BGCOLOR="#f0f0f0"><FONT FACE="Arial, Helvetica" SIZE="2">
+			<B>office_standards@openoffice.org</B><BR>
+			This mailing list is dedicated to collaboration among all
+			office-suites. It covers standardisation of package and 
+            file formats, and hopefully further areas of cooperation
+            can be discovered.
+		</TD>
+		<TD BGCOLOR="#f0f0f0" ALIGN="middle"><FONT FACE="Arial, Helvetica" SIZE="2">
+			<A href="mailto:dev-subscribe@openoffice.apache.org">dev-subscribe@openoffice.apache.org </A></FONT>
+		</TD>
+		<TD BGCOLOR="#f0f0f0" ALIGN="middle"><FONT FACE="Arial, Helvetica" SIZE="2">
+			<A href="mailto:dev-unsubscribe@openoffice.apache.org">dev-subscribe@openoffice.apache.org</A></FONT>
+		</TD>
+		<TD BGCOLOR="#f0f0f0" ALIGN="middle"><FONT FACE="Arial, Helvetica" SIZE="2">
+			<A HREF="http://www.openoffice.org/servlets/SummarizeList?listName=office_standards">Browse archives</A></FONT>
+		</TD>
+	</TR>
+
+
+</TBODY>
+</TABLE>
+</CENTER>
+</body>
+</html>
+
diff --git a/content/xml/sx2ml/index.html b/content/xml/sx2ml/index.html
new file mode 100644
index 0000000..2ffd585
--- /dev/null
+++ b/content/xml/sx2ml/index.html
@@ -0,0 +1,301 @@
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+	<head>
+		<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+		<title>XSL transformation from 'OpenOffice.org XML' to 'XHTML 1.0'</title>
+		<meta name="generator" content="StarOffice/OpenOffice.org XSLT (http://xml.openoffice.org/sx2ml)" />
+		<meta name="created" content="2005-11-17T15:11:55" />
+		<meta name="changedby" content="Svante Schubert" />
+		<meta name="changed" content="2005-12-21T13:41:22" />
+		<meta name="subject" content="XSL transformation from 'OpenOffice.org XML' to 'XHTML 1.0'" />
+		<meta name="keywords" content="xslt xhtml opendocument openoffice.org" />
+		<base href="." />
+	</head>
+	<body>
+		<link rel="stylesheet" type="text/css" href="../xmloff.css" media="screen" />
+		<h1>
+			<a name="XSL_transformation_from__27OpenOffice.org_XML_27_to__27XHTML_1.0_27"></a>XSL transformation from 'OpenOffice.org XML' to 'XHTML 1.0'</h1>
+		<h2>Contents</h2>
+		<ul>
+			<li>
+				<a href="#Abstract">Abstract</a>
+			</li>
+			<li>
+				<a href="#Use_without_Office__28stand-alone_29">Use without Office (stand-alone)</a>
+			</li>
+			<li>
+				<a href="#Overview_over_XSLT_stylesheets">Overview over XSLT stylesheets</a>
+			</li>
+			<li>
+				<a href="#Add-On_Support_for_Master_Documents__28stand-alone_only_29">Add-On Support for Master Documents (stand-alone only)</a>
+			</li>
+			<li>
+				<a href="#Feedback">Feedback</a>
+			</li>
+		</ul>
+		<h2>
+			<a name="Abstract"></a>Abstract</h2>
+		<p>The filter creates <a href="http://www.w3.org/TR/xhtml1/">strict XHTML 1.0</a> from the <a href="http://xml.openoffice.org/general.html">OpenOffice.org XML</a> format, which was the standard XML format of OpenOffice.org 1.x. Since OpenOffice.org 2.0 the default document format changed to the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS Open Document Format for Office Applications (OpenDocument)</a>. The filter can only be used with OpenDocument i [...]
+		<p>The XHTML export filter has matured since it's beginning early 2000, were it was first part of a commercial product named StarPortal/Webtop. In conjunction with OpenOffice.org the stylesheets had been open-sourced.</p>
+		<p>Now as a sample filter, it is an optional installation component of OpenOffice.org 1.x/2.x, installed together with the 'XSLT sample filter' package. Within the Office the filter can be used when choosing the XHTML export from File-&gt;Export...</p>
+		<p>The XHTML transformation is being used for creation of the <a href="http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.xhtml">Developers's Guide</a> of the <a href="http://api.openoffice.org/SDK/">OpenOffice.org Software Development Kit (SDK)</a> from OpenOffice.org documents.</p>
+		<h2>
+			<a name="Use_without_Office__28stand-alone_29"></a>Use without Office (stand-alone)</h2>
+		<p>The XHTML export filter can be used without an Office to create XHTML files of OpenOffice.org 1.x documents. The filter will NOT work stand-alone with the new default OpenDocument format, but are still working in OpenOffice.org 2.x as the Office offers the functionality to map internally from OpenDocument to the earlier XML format for XSLT filters (cp. Tools-&gt;XML Filter Settings). <br/>The filter comprises of a set of XSLT stylesheets and will work in combination of many XML pars [...]
+		<ul>
+			<li>
+				<a href="http://xml.apache.org/xalan-j/index.html">Apache Xalan processor</a>
+			</li>
+			<li>
+				<a href="http://www.blnz.com/xt/index.html">XT processor</a>
+			</li>
+			<li>or any other XSLT processor supporting the <a href="http://exslt.org/exsl/index.html">http://exslt.org/common</a> node-set function.</li>
+		</ul>
+		<p>The <a href="http://xml.apache.org/xalan-j/index.html">Apache Xalan processor</a> is being used in the Office by default. It has been bundled with OpenOffice.org together with the <a href="http://xerces.apache.org/">Xerces XML parser</a>.</p>
+		<h2>
+			<a name="Overview_over_XSLT_stylesheets"></a>Overview over XSLT stylesheets </h2>
+		<p>All stylesheets can be installed by choosing as optional part of the Office installation ('XSLT sample filter'). They are located &lt;OFFICE_PATH&gt;/share/xslt.  </p>
+		<p>To view them online, you may browse the <a href="http://framework.openoffice.org/source/browse/framework/filter/source/xslt/">CVS</a> and choose the 'download' link beyond the latest version of a stylesheet.</p>
+		<div>
+			<table border="0" cellspacing="0" cellpadding="0" class="infotable">
+				<colgroup>
+					<col width="236"/>
+					<col width="369"/>
+					<col width="803"/>
+				</colgroup>
+				<thead>
+					<tr>
+						<td colspan="3">Overview over XSLT stylesheets</td>
+					</tr>
+					<tr>
+						<th>
+Path
+</th>
+						<th>
+Document
+</th>
+						<th>
+Description
+</th>
+					</tr>
+				</thead>
+				<tbody>
+					<tr>
+						<td>
+common
+</td>
+						<td>
+measure_conversion.xsl
+</td>
+						<td>
+Measure conversions (e.g. inch to cm) usable for all import and export XSLT filter.
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common
+</td>
+						<td>
+body.xsl
+</td>
+						<td>
+Common mapping mechanisms of elements of languages similar to XHTML (WML, other XML for small devices, et alias)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common
+</td>
+						<td>
+table_of_content.xsl
+</td>
+						<td>
+Common mapping mechanisms of tables
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/styles
+</td>
+						<td>
+style_collector.xsl
+</td>
+						<td>
+Common mechanisms to flatening the style hierarchy of the OpenOffice.org styles
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/styles
+</td>
+						<td>
+style_mapping_css.xsl
+</td>
+						<td>
+Common mapping of OpenOffice.org styles to CSS
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/styles
+</td>
+						<td>
+style_mapping_html32.xsl
+</td>
+						<td>
+Common mapping of OpenOffice.org styles to HTML 3.2 (not used any longer, once needed for PALM HTML 3.2 subset)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/table
+</td>
+						<td>
+table.xsl
+</td>
+						<td>
+Common mechanisms to map OpenOffice.org tables to HTML (once shared by XHTML and PALM HTML)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/table
+</td>
+						<td>
+table_cells.xsl
+</td>
+						<td>
+Common mechanisms to map OpenOffice.org table cells to HTML (once shared by XHTML and PALM HTML)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/table
+</td>
+						<td>
+table_columns.xsl
+</td>
+						<td>
+Common mechanisms to map OpenOffice.org table columns to HTML (once shared by XHTML and PALM HTML)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/common/table
+</td>
+						<td>
+table_rows.xsl
+</td>
+						<td>
+Common mechanisms to map OpenOffice.org table rows to HTML (once shared by XHTML and PALM HTML)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+ooo2xhtml.xsl
+</td>
+						<td>
+The starting stylesheet for XHTML transformations
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+body.xsl
+</td>
+						<td>
+Special XHTML mappings of body elements to XHTML
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+header.xsl
+</td>
+						<td>
+Special XHTML mappings of header elements to XHTML
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+table.xsl
+</td>
+						<td>
+Special XHTML mappings of table elements to XHTML
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+master_chapter_numbering.xsl
+</td>
+						<td>
+Special OpenOffice.org Master document mappings (only standalone useable with Java extension s.b.)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+master_document.xsl
+</td>
+						<td>
+Special OpenOffice.org Master document mappings (only standalone useable with Java extension s.b.)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+master_refs_workaround.xsl
+</td>
+						<td>
+Special OpenOffice.org Master document mappings (only standalone useable with Java extension s.b.)
+</td>
+					</tr>
+					<tr>
+						<td>
+export/xhtml
+</td>
+						<td>
+master_usability_links.xsl
+</td>
+						<td>
+Special OpenOffice.org Master document mappings (only standalone useable with Java extension s.b.)
+</td>
+					</tr>
+				</tbody>
+			</table>
+		</div>
+		<p></p>
+		<h2>
+			<a name="Add-On_Support_for_Master_Documents__28stand-alone_only_29"></a>Add-On Support for Master Documents (stand-alone only)</h2>
+		<p>Aside of the plain XSLT stylesheets some Java extension has been implemented for the transformation of master documents (sxg) to XHTML. Basically the extension triggers a new XSL transformation for each referenced child document that is linked from a master document.</p>
+		<p>This enables the following features once necessary for the creation of the Development Guide: </p>
+		<ul>
+			<li>If references are being used in a content table the XHTML output references to the created XHTML child documents.</li>
+			<li>The sequence of numbered chapters of child documents (not aware of their master document by design) are made feasible by parameter for the indent of chapter start of the child document (otherwise all children chapters would start with '1'). </li>
+			<li>It is no longer necessary to unzip the XML files of the (compressed) OpenOffice.org documents. The Java class replaces, if necessary (dependent on the suffix) the path/input URL with a JAR URL.
+</li>
+		</ul>
+		<p>This add-on is only useable with XT. The sources are bundled in a <a href="master_document_support.zip">ZIP</a>.</p>
+		<h2>
+			<a name="Feedback"></a>Feedback</h2>
+		<p>Any comment is welcome and should be posted to the XML developer mailing list <a href="mailto:dev@xml.openoffice.org">dev@xml.openoffice.org</a>. For subscription information or archives, see the this project's <a href="http://xml.openoffice.org/servlets/ProjectMailingListList">mailing list section</a>. <br/>
+Anyone from community is welcome to join the project. The current issues and enhancements filed for XHTML export are <a href="http://www.openoffice.org/issues/buglist.cgi?issue_status=NEW&issue_status=STARTED;&issue_status=REOPENED;&email1=;&emailtype1=exact;&emailassigned_to1=1;&email2=;&emailtype2=exact;&emailreporter2=1;&issueidtype=include;&issue_id=;&changedin=;&votes=;&chfieldfrom=;&chfieldto=Now;&chfieldvalue=;&short_desc=xhtml;&short_desc_type=substring;&long_desc=;&long_desc_typ [...]
+	</body>
+</html>
diff --git a/content/xml/uses.html b/content/xml/uses.html
new file mode 100644
index 0000000..8b396c9
--- /dev/null
+++ b/content/xml/uses.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html><head>
+<title>XML/OpenDocument Tools at OpenOffice.org</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Tools">OpenDocument related tools</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Tools">Wiki</a>.
+</body>
+</html>
+
diff --git a/content/xml/xfilter.html b/content/xml/xfilter.html
new file mode 100644
index 0000000..ac49dcb
--- /dev/null
+++ b/content/xml/xfilter.html
@@ -0,0 +1,128 @@
+<!DOCTYPE html>
+<html><head>
+<title>XML Filter Tools</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>XML Filter Tools</h1>
+
+<p>It's the purpose of these tools to load XML-based filter components
+and to execute them stand-alone. The basic concept of XML-based filter
+components are described in the <a href="filter/">OOo Guide to XML
+Filters</a>.</p>
+
+<p><strong>Note:</strong> There have been some questions on what you
+can actually do with xfilter. <em>If</em> a filter was written
+according to the <a href="filter/">XML-based filter</a> concept, then
+it can be used with the tool. Unfortunately, OpenOffice.org currently
+does <em>not</em> include any such filters. The reason is that the
+concept is fairly new, and most filters (including the MS filters)
+have been developed before that. StarOffice 6.0, which is based on
+OpenOffice.org but includes (among others; see FAQ) some additional
+filters has three new filters that can be used with the xfilter
+tool.</p>
+
+
+<h2>Use</h2>
+
+<ol>
+
+ <li>You need:
+  <ul>
+   <li>an installed OOo</li>
+   <li>xfilter binaries for that build</li>
+   <li>the regcomp binary from the ODK</li>
+  </ul>
+ </li>
+
+ <li>Copy the files for your platform into the OOo program directory</li>
+
+ <li>Call the starter script with parameters for the component name
+ and input file. The starter script will register the libraries and
+ then call the actual xfilter program.</li>
+
+</ol>
+
+<p>Example:</p>
+
+<ul>
+ <li>Windows:
+<pre>
+&gt; copy xfilter.exe xfiltermi.dll xfilter.bat <i>&lt;OOo directory&gt;</i>\program
+&gt; cd <i>&lt;OOo directory&gt;</i>\program
+&gt; xfilter.bat com.sun.comp.hwpimport.HwpImportFilter input.hwp
+  </pre>
+ </li>
+ <li>*nix:
+  <pre>
+&gt; cp xfilter libxfilter??.so xfilter.sh <i>&lt;OOo directory&gt;</i>/program
+&gt; cd <i>&lt;OOo directory&gt;</i>/program
+&gt; xfilter.sh  com.sun.comp.hwpimport.HwpImportFilter input.hwp
+  </pre>
+ </li>
+</ul>
+
+
+<h2>Implementation Detail</h2>
+
+<p>The program consists of a starter application, which initializes
+the <a href="http://udk.openoffice.org/">UNO runtime</a> and the <a
+href="http://ucb.openoffice.org/">UCB</a> to provide for UNO component
+instantiation and input/output functionality, respectively. Then, the
+starter program instantiates the filter component (as given on the
+command line), and imitates the use of the component through the <a
+href="http://api.openoffice.org/common/ref/com/sun/star/document/XImporter.html">XImporter</a>
+and <a
+href="http://api.openoffice.org/common/ref/com/sun/star/document/XFilter.html">XFilter</a>
+interfaces.</p>
+
+<p>Limitations in the emulation of the OOo filter invocation are:
+ <ul>
+  <li>The <code>XImporter::setTargetDocument()</code> call received an
+  empty reference where the document model is expected</li>
+
+  <li>The <code>XFilter::filter()</code> call receives a
+  <a href="http://api.openoffice.org/common/ref/com/sun/star/document/MediaDescriptor.html">MediaDescriptor</a>,
+  which contains only an URL and an opened
+  XInputStream for the input file.</li>
+  <li>Additional services or components usually provided for and
+  initialized by OOo may not be available.</li>
+ </ul>
+<p>
+
+<p>In order to generate output on the console, the <code>com.sun.comp.Writer.XMLImporter</code> component, which is usually instantiated by the filter component, needs to be replaced by a dummy implementation that simply outputs the XML data to the standard console output. This dummy implementation is given in the xfilter DLL/lib (xfiltermi.dll/libxfilter??.so).</p>
+
+<p>StarOffice Filter components, on which the xfilter tool has been tested:
+ <ul>
+  <li><code>com.sun.comp.hwpimport.HwpImportFilter</code></li>
+  <li><code>com.sun.comp.WPSimport.IWPSImportFilter</code></li>
+  <li><code>com.sun.comp.jsimport.IchitaroImportFilter</code></li>
+ </ul>
+</p>
+
+
+<h2>Source code</h2>
+
+<p>The source code for this probably isn't very interesting, but you
+can obtain it from the <code>xml/filtertools</code> directory in the
+CVS archive. You can also browse it <a
+href="http://xml.openoffice.org/source/browse/xml/filtertools/source/">online</a>.</p>
+
+<h2>Binaries</h2>
+
+<p>Binaries for a few platforms can be downloaded here:
+
+<ul>
+ <li><a href="xfilter/xfilter.641.wntmsci7.pro.zip">Windows, SRC641</a> 
+     (OpenOffice.org 1.0, StarOffice 6.0)</li>
+</ul>
+
+<hr>
+
+<p>
+ <small>
+  Please direct comments and suggestions to the <a href="mailto:dev@xml.openoffice.org">xml-dev</a> mailing list (<a href="http://xml.openoffice.org/servlets/SummarizeList?listName=dev">archive</a>) or to <a href="mailto:dvo@openoffice.org">dvo</a>.
+ </small>
+</p></body>
+</html>
+
diff --git a/content/xml/xforms/index.html b/content/xml/xforms/index.html
new file mode 100644
index 0000000..b5b3e50
--- /dev/null
+++ b/content/xml/xforms/index.html
@@ -0,0 +1,10 @@
+<html>
+<head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+</body>
+</html>
+
diff --git a/content/xml/xmerge/background.html b/content/xml/xmerge/background.html
new file mode 100644
index 0000000..f2ab0c4
--- /dev/null
+++ b/content/xml/xmerge/background.html
@@ -0,0 +1,258 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>Background of XMerge</title>
+  <link rel="stylesheet" type="text/css" href="xmloff.css"
+ media="screen">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>Background of XMerge<br>
+</h1>
+<!-- no current top news!
+<h2><strong>Top News</str
+ong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<p>Xmerge came out of project Starlite. The goal of Starlite was to
+provide mobility to StarOffice documents. The Starlite
+team developed
+spreadsheet and document viewer applications with limited editing
+capabilities for PalmOS. These applications were designed to
+synchronize with the StarWriter and StarCalc applications on the
+desktop. <br>
+</p>
+<p>Project ZenSync was the second phase of project Starlite to enable
+synchronization between StarPortal (a web-based version of its
+StarOffice) and an expanded set of
+small-device applications. The team designed and developed an
+architecture that would allow third parties to plug-in their converters
+to support their proprietary document formats. This work was enhanced
+by the team in Ireland (led by Brian Cameron).</p>
+<p></p>
+<table cellpadding="4" cellspacing="1"
+ style="background-color: rgb(255, 255, 255); width: 400px;">
+  <tbody>
+    <tr>
+      <td colspan="2"
+ style="background-color: rgb(0, 49, 90); text-align: center; width: 150px;"><font
+ color="#ffffff" face="arial, helvetica" size="2"><b>StarLite
+Team<br>
+      </b></font></td>
+    </tr>
+    <tr>
+      <th bgcolor="#99ccff" align="center" style="width: 150px;"><font
+ color="#00315a" face="arial, helvetica" size="2"><b> Name</b></font><br>
+      </th>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b>Function</b></font></th>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Akhil Arora</td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Tech
+Lead<br>
+      </td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Eileen
+Bugee</td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Visual
+designer</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Eric
+Bergman</td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Human
+factors design</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">David
+Proulx</td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">StarWriter
+for PalmOS</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Herbie
+Ong</td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Converters
+for StarWriter</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Paul
+Rank<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">StarCalc
+for PalmOS</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Raju
+Pallath<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Quality</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Stephen
+Mak<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Converters
+for StarCalc</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Denis
+Antrushin<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">StarCalc
+for PalmOS<br>
+      </td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Maline
+Minasandram<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Manager<br>
+      </td>
+    </tr>
+<!--
+<tr>
+<td bgcolor="#f0f0f0" valign="top"><a href="...">...</a></td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+</tr>
+-->
+  </tbody>
+</table>
+<br>
+At this point the project was transfered to Dublin, Ireland. The first
+step was to refactor the code from the ZenSync converter
+library/framework so that filters could be written not just
+for palm devices but any device. This included writing a registry
+manager to keep track of which filters were included and
+what formats could be converted. Next, filters for Pocket Excel
+and Pocket Word were written. Once this was completed an Active Sync
+conduit was written so that the framework could be used to convert
+Pocket PC
+files on a handheld to StarOffice files on a PC automatically through
+ActiveSync. The decision was then taken to open source the project,
+naming it XMerge and
+make it available on OpenOffice. This involved hosting the code on
+OpenOffice CVS, adding the web pages and writing the documentation for
+filter writers. Once hosted on the website a FlatXML and DocBook filter
+were added. The final step in the project was to include XMerge in
+StarOffice. <br>
+<br>
+<table cellpadding="4" cellspacing="1"
+ style="background-color: rgb(255, 255, 255); width: 550px;">
+  <tbody>
+    <tr>
+      <td colspan="2" bgcolor="#00315a" align="center"
+ style="width: 150px;"><font color="#ffffff" face="arial, helvetica"
+ size="2"><b>XMerge
+Team<br>
+      </b></font></td>
+    </tr>
+    <tr>
+      <th bgcolor="#99ccff" align="center" style="width: 150px;"><font
+ color="#00315a" face="arial, helvetica" size="2"><b> Name</b></font><br>
+      </th>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b>Function</b></font></th>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Brian
+Cameron<br>
+      </td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Tech
+Lead<br>
+      </td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Aidan
+Butler<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">FlatXML
+&amp; Docbook filter, Integration into StarOffice</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Mike Hayes<br>
+      </td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Code
+design work, Code refactoring, Pocket Excel filter</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Darren
+Kenny<br>
+      </td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Code
+design work, OpenOffice web hosting</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Martin
+Maher<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Pocket
+Excel filter, Code refactoring</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Mark
+Murnane<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Pocket
+Word filter, ActiveSync, Integration into StarOffice</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">James
+Cleere<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Manager<br>
+      </td>
+    </tr>
+<!--
+<tr>
+<td bgcolor="#f0f0f0" valign="top"><a href="...">...</a></td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+</tr>
+-->
+  </tbody>
+</table>
+<!--
+  older optimization ideas ... currently not relevant 
+   <tr>
+    <td><a href="optimization.html">Optimization  Ideas</a></td>
+    <td>This page contains a list of oppurtunities for speed optimizations for
+    the XML filters. Additionally, the current status of our optimization
+    efforts is listed <a href="current_optimization_status.html">
+    here</a>. </td>
+    <td>HTML, ca.&nbsp;15KB</td>
+   </tr>
+-->
+</body>
+</html>
diff --git a/content/xml/xmerge/docbook/DocBookTags.html b/content/xml/xmerge/docbook/DocBookTags.html
new file mode 100644
index 0000000..db3ab93
--- /dev/null
+++ b/content/xml/xmerge/docbook/DocBookTags.html
@@ -0,0 +1,951 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+
+<HTML>
+<head>
+	
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE>DocBook Filters - Tag Names</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.1 BETA1 (Win32)">
+	<META NAME="AUTHOR" CONTENT="James Cleere">
+	<META NAME="CREATED" CONTENT="20021002;9513700">
+	<META NAME="CHANGED" CONTENT="20021008;18512300">
+	
+	<STYLE>
+		<!-- 
+		BODY,DIV,TABLE,THEAD,TBODY,TFOOT,TR,TH,TD,P { font-family:"Albany"; font-size:x-small }
+		 -->
+	</STYLE>
+	
+</head>
+
+<body TEXT="#000000">
+<TABLE FRAME=BOX CELLSPACING=0 COLS=4 RULES=GROUPS BORDER=1>
+	<COLGROUP><COL WIDTH=193></COLGROUP>
+	<COLGROUP><COL WIDTH=86></COLGROUP>
+	<COLGROUP><COL WIDTH=86></COLGROUP>
+	<COLGROUP><COL WIDTH=258></COLGROUP>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><B><U><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000">Tag Name</FONT></U></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=LEFT><B><U>Imported </U></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=LEFT><B><U>RoundTrip</U></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><B><U>Comment</U></B></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;abstract&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;address&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;affiliation&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;appendix&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;application&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;articleinfo&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;article&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;author&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;authorblurb&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=47 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;authorgroup&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=47 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=47 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=47 ALIGN=LEFT>Does not currently maintain author grouping. A group containing 2 authors, will be imported as just 2 authors </TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;book&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;bookinfo&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;chapter&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;citetitle&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;city&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;command&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;computeroutput&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;copyright&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;country&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;date&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;email&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;emphasis&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;entry&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;example&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;figure&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;filename&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;firstname&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;firstterm&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000">&lt;footnote&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;function&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;glossary&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;glossdef&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;glossterm&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;graphic&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>Requires support for inline nested tags</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;guibutton&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>&ldquo;</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;guiicon&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>&ldquo;</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;guilabel&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>&ldquo;</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;guimenu&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>&ldquo;</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;guimenuitem&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>&ldquo;</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;guisubmenu&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;highlight&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;holder&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>Part of CopyRight</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;imageobject&gt; </FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>Not fully implemented</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;imagedata&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>&ldquo; &ldquo; </TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;index&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;indexentry&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;indexterm&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;informalexample&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;informaltable&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;inlinegraphic&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;inlinemediaobject&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;itemizedlist&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;keycap&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;keycombo&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;keysym&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;legalnotice&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;listitem&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>Problem with StarOffices nesting of lists</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;literal&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;literallayout&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;markup&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;mediaobject&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;member&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;menuchoice&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;note&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;olink&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;option&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;orderedlist&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;para&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;part&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;partintro&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;phrase&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;postcode&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;preface&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;primary&gt;  - indexing tag </FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;procedure&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;publisher&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;releaseinfo&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;replaceable&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;revhistory&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;revision&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;revnumber&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;row&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;screeninfo&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;screenshot&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;secondary&gt; &ndash; indexing tag</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;sectX&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;sect2&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;sect3&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;sect4&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;sect5&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;see&gt; - index </FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;seealso&gt; - index </FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000">&lt;subscript&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;superscript&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;surname&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;systemitem&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;table&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;tbody&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;term&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;tertiary&gt; -  index</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;textobject&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=LEFT><BR></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=LEFT><BR></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;tgroup&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;thead&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;tip&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;title&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;ulink&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;userinput&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;variablelist&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT>Staroffice does not nest lists correctly</TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;varlistentry&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;xref&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;colspec&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B>X</B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;warning&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B> </B></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=20 ALIGN=LEFT><FONT FACE="Times New Roman" SIZE=3 COLOR="#000000"> &lt;step&gt;</FONT></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=LEFT><BR></TD>
+			<TD WIDTH=86 HEIGHT=20 ALIGN=LEFT><BR></TD>
+			<TD WIDTH=258 HEIGHT=20 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD WIDTH=193 HEIGHT=17 ALIGN=LEFT><BR></TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=CENTER SDVAL="60" SDNUM="6153;"><B>60</B></TD>
+			<TD WIDTH=86 HEIGHT=17 ALIGN=CENTER><B><BR></B></TD>
+			<TD WIDTH=258 HEIGHT=17 ALIGN=LEFT><BR></TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<!-- ************************************************************************** -->
+</body>
+
+</HTML>
diff --git a/content/xml/xmerge/docbook/UserGuide.html b/content/xml/xmerge/docbook/UserGuide.html
new file mode 100755
index 0000000..5bde582
--- /dev/null
+++ b/content/xml/xmerge/docbook/UserGuide.html
@@ -0,0 +1,2 @@
+<!DOCTYPE html> <HTML> <head> 	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252"> 	<TITLE>Getting Started With DocBook on OpenOffice</TITLE> 	<META NAME="GENERATOR" CONTENT="OpenOffice.org 643  (Win32)"> 	<META NAME="CREATED" CONTENT="20021017;16373992"> 	<META NAME="CHANGED" CONTENT="20021018;11220018"> 	<STYLE> 	<!-- 	H2.western { font-family: "Albany", sans-serif; font-size: 14pt; font-style: italic } 		H2.cjk { font-family: "HG Mincho Light J"; font-size: 14pt [...]
+Load the DocBookTemplate.stw Template so that the required Docbook specific styles are available.Display the Style list by pressing <B>F11</B>. Now choose 'All Styles', so that all available styles are displayed.</P> <P ALIGN=CENTER STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><IMG SRC="images/ParagraphStyles.png" NAME="Graphic3" ALIGN=BOTTOM BORDER=1></FONT> </P> <P STYLE="margin-bottom: 0cm"><BR> </P> <P STYLE="margin-bottom: 0cm"><BR> </P> <H2 CLASS="western">Navigating through a  [...]
diff --git a/content/xml/xmerge/docbook/index.html b/content/xml/xmerge/docbook/index.html
new file mode 100644
index 0000000..6a3e45f
--- /dev/null
+++ b/content/xml/xmerge/docbook/index.html
@@ -0,0 +1,196 @@
+<!DOCTYPE html>
+<html>
+<head>
+<title>DocBook Filters - Read and write docbook xml using OpenOffice.org</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+	<h1>DocBook Filters - Read and write docbook xml using OpenOffice.org</h1>
+	<!--<h1>User Guide for DocBook on OpenOffice.org</h1>-->
+	<p>
+The project goal is to explore the possibility of using OpenOffice.org as a WYSIWYG editor of XML content. The principle is to edit structured documents using styles. These styles are then transformed to XML tags on export.
+	</p>
+	<p>
+Anyone from community is welcome to join the project. The current issues and enhancements filed for DocBook are <a href="http://www.openoffice.org/issues/buglist.cgi?issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=docbook&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_fil [...]
+	</p>	
+	<p>
+This page shows how to enable and use the DocBook filters. It also shows the location of the stylesheets so that users can download and use the latest transformations. The filter provided on this page is based on earlier releases of the DocBook filter. New features include:
+	<ul>
+	<li>Support for nested tags</li>
+	<li>Support for unresolved entities</li>
+	<li>Increased range of supported DocBook tags (index, xref, id attributes for sect etc.)</li>
+	<li>Use of new Tools -&gt; XML Filter Settings dialog in OpenOffice.org</li>
+	</ul>
+	</p>
+
+	<h2>Enabling the DocBook XSLT's in OpenOffice.org</h2>
+	<p>
+	For these releases there are three different ways of enabling the DocBook filters.
+	</p>
+
+	<h3>1. Download the DocBook XSLT Stylesheets and OpenOffice.org Style Template</h3>
+	<p>
+	This method ensures that the most recent stylesheets and OpenOffice.org style template are used for import and export. To import, export and modify DocBook documents in OpenOffice.org, it is necessary to download the following:
+	<ul><li>The relevant XSLT stylesheets for the XML transformations (<a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">All available here</a>)</li>
+	<li>An OpenOffice.org style template that contains custom styles corresponding to DocBook tags (<a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">Available here</a>)</li>
+	</ul>
+	The most recent stylesheets support the import and export of DocBook documents with article or chapter as the top-level tag. The different stylesheets required for each of these operation are listed below:
+	</p>
+
+	<br><br>
+
+	<table width="50%" border="1" cellpadding="3">
+	<caption align="top"><b>Stylesheets required for import</b></caption>
+	<thead>
+	<tr>
+	<th>Article</th>
+	<th>Chapter</th>
+	</tr>
+	</thead>
+	<tbody>
+	<tr>
+	<td align="center" valign="middle"><a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">docbooktosoffheadings.xsl</a></td>
+	<td align="center" valign="middle"><a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">docbooktosoffheadings.xsl</a></td>
+	</tr>
+	</tbody>
+	</table>
+
+	<br>
+
+	<table width="50%" border="1" cellpadding="3">
+	<caption align="top"><b>Stylesheets required for export</b></caption>
+	<thead>
+	<tr>
+	<th>Article</th>
+	<th>Chapter</th>
+	</tr>
+	</thead>
+	<tbody>
+	<tr>
+	<td align="center" valign="middle"><a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">sofftodocbookheadings_article.xsl</a></td>
+	<td align="center" valign="middle"><a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">sofftodocbookheadings_chapter.xsl</a></td>
+	</tr>
+	</tbody>
+	</table>
+
+	<br>
+
+	<b>OpenOffice.org Template required for Article and Chapter documents:</b> 
+	<ul><li><a href="../downloads/DocBookTemplate.stw">DocBookTemplate.stw</a></li></ul> <br>
+
+	<h3>Creating a new DocBook filter</h3>
+	<p>
+	<ul>
+	<li>Go to Tools -&gt; XML Filter Settings...</li> 
+	<li>Set <i>Filter Name</i> and <i>Name of File Type</i> to <i>DocBook (Chapter)</i></li>
+	<li>Go to the Transformation tab</li>
+	<li>Set DocType to &lt;chapter&gt;</li>
+	<li>For <i>XSLT for Export</i> browse to the chapter export stylesheet (sofftodocbookheadings_chapter.xsl).</li>
+	<li>For <i>XSLT for Import</i> browse to the chapter import stylesheet (docbooktosoffheadings.xsl).</li>
+	<li>For <i>Template for Import</i> browse to the style template (DocBookTemplate.stw).</li>
+	<li>Click OK and close the XSLT Filter Setting dialog</li>
+	</ul> <br>
+	To create a DocBook Article filter, the above steps can be repeated with <i>article</i> replacing <i>chapter</i>
+	</p>
+
+
+	<h3>2. Download the DocBook XSLT Jar Packages for Article or Chapter</h3>
+	<p>
+	This method of enabling the DocBook filters is more convenient, but it does not guarantee that the most recent stylesheets and OpenOffice.org template are used. 
+	<b>TBD</b>
+	</p>
+
+	<h3>3. Download the DocBook UNO component for Article only</h3>
+	<p>
+	The DocBook UNO component adds filter support for the retention of unresolved XML entities.
+	<ul>
+	<li>Download the<a href="../downloads/DocBookFilter.zip"> DocBookFilter </a></li>
+	<li>Unzip it to the &lt;OOo install Dir&gt;/</li>
+	<li>Run pkgchk in the &lt;OOo install Dir&gt;/program dir</li>
+	<li>The DocBook Article filter will now import DocBook unresolved entities as OpenOffice.org set variables</li>
+	</ul>	
+	</p>
+
+	<h2>How to Import a DocBook document</h2>
+	<p>A DocBook article or chapter document can now be opened using the File -&gt; Open dialog.
+	<ul>
+	<li>Go to File -&gt; Open...</li>
+	<li>Browse to the DocBook document.</li>
+	<li>Click OK</li>
+	</ul>
+	The DocBook XSLT filter should automatically determine the root element of the document and import it with the matching XSLT filter.<br>
+	Alternatively, it is possible to browse manually to the desired DocBook filter in the <i>File Type</i> combo-box in the File -&gt; Open dialog. 
+	</p>
+
+	<h2>How to Export a DocBook document</h2>
+	<p>The DocBook document can also be exported using the File -&gt; Save As dialog.
+	<ul>
+	<li>Go to File -&gt; Save As...</li>
+	<li>Browse to the location where the document is to be saved</li>
+	<li>Click Save</li>
+	</ul>
+	Again, the DocBook XSLT filter should automatically determine the file type and export with the matching XSLT filter.<br>
+	Alternatively, it is possible to browse manually to the desired DocBook filter in the <i>File Type</i> combo-box in the File -&gt; Save As dialog.
+	</p>
+
+	<h2>Using OpenOffice.org Headings and Styles for different DocBook tags</h2>
+
+	<h3>Using OpenOffice.org styles to represent DocBook tags</h3>
+	<p>The style template supplies all of the custom styles that are currently supported. Once a DocBook document has been imported to OpenOffice.org, the available DocBook specific styles can be viewed using the Stylist.
+	<!-- needs screen shot of recent template's Stylist here
+	<img src="stylist.png" align="right" hspace="10" vspace="10"/>
+-->
+	On import, each of the supported DocBook tags will be mapped to formatted OpenOffice.org content. Similarly, to modify the imported DocBook document, OpenOffice.org text styles can be used to represent the DocBook tags marking-up the text. <br> <br>
+
+	<b>NOTE:</b> A new DocBook document can be created in OpenOffice.org by opening the DocBookTemplate.stw. The document can then be saved as a DocBook document, and the new content will be represented as DocBook mark-up. <br> <br> 
+
+	<i>How to create new DocBook content</i>:
+	<ul>
+	<li>Press <b>F11</b> to display the Stylist</li>
+	<li>Select <b>Custom Styles</b> in the Stylist combo-box</li>
+	<li>Click the <b>Character Styles</b> icon (second from left on the Stylist)</li>
+	<li>Double-click the <b>SubScript</b> style</li>
+	<li>Enter text in the OpenOffice.org document</li>
+	<li>On exporting as DocBook, the text formatted as the <b>SubScript</b> custom style will be marked-up with the DocBook tag <b>&lt;subscript&gt;</b></li>
+	</ul>
+	
+	</p>
+
+	<p>
+	</p>
+
+	<p>
+	<i>How to create DocBook sections</i>: <br> <br> 
+	Initially the DocBook project used OpenOffice.org sections to enforce the nesting of DocBook sections.
+	Feedback has shown that authors wish to use the common word processing styles such as Heading1, Heading2, etc. The following instructions describe how to create a &lt;sect1&gt; that contains a &lt;sect2&gt;
+	<ul>
+	<li>Press <b>F11</b> to display the Stylist</li>
+	<li>Select <b>All Styles</b> in the Stylist combo-box</li>
+	<li>Click the <b>Paragraph Styles</b> icon (first in the left on the Stylist)</li>
+	<li>Double-click the <b>Heading 1</b> style</li>
+	<li>Enter the text to be the &lt;sect1&gt; title</li>
+	<li>All the text below this heading will now be the content of the DocBook &lt;sect1&gt;</li>
+	<li>Enter other DocBook styles, tables, etc.</li>
+	<li>Enter other DocBook styles, tables, etc. to be included in &lt;sect1&gt;</li>
+	<ul>
+	<li>Double-click the <b>Heading 2</b> style</li></li>
+	<li>Enter the text to be the &lt;sect2&gt; title</li>
+	<li>All the text below this heading will now be the content of the DocBook &lt;sect2&gt;</li>
+	<li>Enter other DocBook styles, tables, etc. to be included in &lt;sect2&gt;</li>
+	</ul>
+	<li>This nesting of DocBook sect's using OpenOffice headings can go as far as &lt;sect4&gt; / Heading 4</li>
+	</ul>	
+	</p>
+	<br>
+
+	<p>
+	<img src="images/Navigator.gif" align="left" hspace="10" vspace="10"/>
+	<i>Navigating through the document:</i><br><br>
+	If you wish to see how DocBook sections are nested as OpenOffice.org headings, use the F5 key to Display the Navigator window. Expand the headings tag, to display the layout of the headings within the document. You can skip to the start of a given DocBook section/OpenOffice.org heading, by double-clicking on it. 
+	</p>
+
+	<p>
+	For further information on supported DocBook tags see: <a href="supported_tag_table.html">Supported Tags</a>
+	</p>
+</body>
+</html>
diff --git a/content/xml/xmerge/docbook/supported_tag_table.html b/content/xml/xmerge/docbook/supported_tag_table.html
new file mode 100644
index 0000000..5f6a595
--- /dev/null
+++ b/content/xml/xmerge/docbook/supported_tag_table.html
@@ -0,0 +1,1156 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+
+<HTML>
+<head>
+	
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>DocBook Supported Tags Table</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.1 Beta 2 (Solaris Sparc)">
+	<META NAME="CREATED" CONTENT="20030603;16532800">
+	<META NAME="CHANGED" CONTENT="20030611;10294700">
+	
+	<STYLE>
+		<!-- 
+		BODY,DIV,TABLE,THEAD,TBODY,TFOOT,TR,TH,TD,P { font-family:"Albany"; font-size:x-small }
+		 -->
+	</STYLE>
+	
+</head>
+
+<body TEXT="#000000">
+<TABLE FRAME=BOX CELLSPACING=0 COLS=5 RULES=GROUPS BORDER=1>
+	<COLGROUP><COL WIDTH=238></COLGROUP>
+	<COLGROUP><COL WIDTH=162></COLGROUP>
+	<COLGROUP><COL WIDTH=85></COLGROUP>
+	<COLGROUP><COL WIDTH=133></COLGROUP>
+	<COLGROUP><COL WIDTH=194></COLGROUP>
+	<TBODY>
+		<TR>
+			<TD WIDTH=238 HEIGHT=23 ALIGN=CENTER><B><I><FONT SIZE=4>DocBook Categories</FONT></I></B></TD>
+			<TD WIDTH=162 ALIGN=CENTER><B><I><FONT SIZE=4>Tag Name</FONT></I></B></TD>
+			<TD WIDTH=85 ALIGN=CENTER><B><I><FONT SIZE=4>Import</FONT></I></B></TD>
+			<TD WIDTH=133 ALIGN=CENTER><B><I><FONT SIZE=4>Round Trip</FONT></I></B></TD>
+			<TD WIDTH=194 ALIGN=CENTER><B><I><FONT SIZE=4>OOorg Mapping</FONT></I></B></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;abstract&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;address&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;affiliation&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Component</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;appendix&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;application&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;articleinfo&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#meta_information">Meta Information</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Component</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;article&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Author</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;author&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Author</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;authorblurb&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Author</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;authorgroup&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Top Level</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;book&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;bookinfo&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#meta_information">Meta Information</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;caption&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Component</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;chapter&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;chapterinfo&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#meta_information">Meta Information</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;citetitle&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;city&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;colspec&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;command&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;comment&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;computeroutput&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Copyright Legal</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;copyright&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;country&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;edition&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;date&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;email&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;emphasis&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;entry&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;example&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;figure&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;filename&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;firstname&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;firstterm&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;footnote&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#link">Link</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;function&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Glossary</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;glossary&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Glossary</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;glossdef&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Glossary</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;glossterm&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;graphic&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;guibutton&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;guiicon&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;guilabel&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;guimenu&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;guimenuitem&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;guisubmenu&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;highlight&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Copyright Legal</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;holder&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;imageobject&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;imagedata&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;index&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;indexentry&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;indexterm&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;informalexample&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;informaltable&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;inlinegraphic&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;inlinemediaobject&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;itemizedlist&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;keycap&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;keycombo&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;keysym&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Copyright Legal</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;legalnotice&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Link</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;link&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#link">Link</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;listitem&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Formatting</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;literal&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Formatting</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;literallayout&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Formatting</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;markup&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;mediaobject&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;member&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;menuchoice&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Admonition</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;note&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#link">Link</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;orgname&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Link</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;olink&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#link">Link</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;option&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;orderedlist&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;para&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;part&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;partintro&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;phrase&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;postcode&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Component</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;preface&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#toplevel_element">Top-Level Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;primary&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;primaryie&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Procedure</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;procedure&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;publisher&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Meta Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;releaseinfo&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#meta_information">Meta Information</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;remark&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;replaceable&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Revision</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;revhistory&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Revision</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;revision&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Revision</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;revnumber&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#nested_element">Nested Element</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;row&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;screeninfo&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;screenshot&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;secondary&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;secondaryie&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Sections</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;sect1&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#sections">Sections</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Sections</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;sect2&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#sections">Sections</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Sections</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;sect3&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#sections">Sections</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Sections</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;sect4&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#sections">Sections</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Sections</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;sect5&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#sections">Sections</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;see&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;seealso&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Procedure</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;step&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;subscript&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>In Line</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;superscript&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;surname&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Operating Environment</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;systemitem&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;table&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;tbody&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;term&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;tertiary&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Index</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;tertiaryie&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#index">Index</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Graphics</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;textobject&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#graphics">Graphics</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;tgroup&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Table</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;thead&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#table">Table</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Admonition</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;tip&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>General</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;title&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Link</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;ulink&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#link">Link</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>User Interfaces</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;userinput&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;variablelist&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>List</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;varlistentry&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#lists">Lists</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Admonition</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;warning&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Link</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;xref&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3>X</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#link">Link</A></FONT></TD>
+		</TR>
+	</TBODY>
+	<TBODY>
+		<TR>
+			<TD HEIGHT=19 ALIGN=LEFT><FONT SIZE=3>Personal Information</FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3>&lt;year&gt;</FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=CENTER><FONT SIZE=3><BR></FONT></TD>
+			<TD ALIGN=LEFT><FONT SIZE=3><A HREF="http://xml.openoffice.org/xmerge/docbook/tag_usage.html#inline_elements">In-Line</A></FONT></TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<!-- ************************************************************************** -->
+</body>
+
+</HTML>
diff --git a/content/xml/xmerge/docbook/tag_usage.html b/content/xml/xmerge/docbook/tag_usage.html
new file mode 100644
index 0000000..cb26d69
--- /dev/null
+++ b/content/xml/xmerge/docbook/tag_usage.html
@@ -0,0 +1,319 @@
+<!DOCTYPE html>
+<html>
+<title>
+DocBook tag usage in OpenOffice.org
+</title>
+<head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>DocBook tags in OpenOffice.org</h1>
+
+
+<h2>Contents</h2>
+<ol>
+<li><a href="#toplevel_elements"><b>Top Level Elements</b></a></li>
+<li><a href="#meta_information"><b>Meta Information</b></a></li>
+<li><a href="#nested_elements"><b>Nested Elements</b></a></li>
+<li><a href="#inline_elements"><b>In-Line Elements</b></a></li>
+<li><a href="#sections"><b>Sections</b></a></li>
+<li><a href="#tables"><b>Tables</b></a></li>
+<li><a href="#lists"><b>Lists</b></a></li>
+<li><a href="#links"><b>Links</b></a></li>
+<li><a href="#graphics"><b>Graphics</b></a></li>
+<li><a href="#index"><b>Index</b></a></li>
+</ol>
+
+<br>
+
+<p>
+For the following instructions to work, ensure that the DocBook stylesheets have been enabled. See the <a href="user_guide.html">User Guide</a> if this has not already been done. Currently the stylesheets only support &lt;article&gt; and &lt;chapter&gt; as top-level elements.</p>
+<p>
+The Stylist and Navigator also need to be displayed:
+<ul>
+<li>Press <b>F11</b> to display the Stylist</li>
+<li>Depending on the DocBook tag to be used, the following options are available:</li>
+<ul>
+<li>Select either <b>Custom Styles</b> or <b>All Styles</b> in the Stylist combo-box</li>
+<li>Click either the <b>Paragraph Styles</b> icon (first in the left on the Stylist) or the <b>Character Styles</b> icon (second from the left on the Stylist)</li>
+</ul>
+<li>Press <b>F5</b> to display the Navigator</li>
+<li>The Headings tab can be expanded to navigate through the DocBook sections of the document.</li>
+</ul>	
+</p>
+
+<br>
+
+<a name="toplevel_elements"><h2>1. Top-Level Elements</h2></a>
+<!-- <appendix> <article> <book> <chapter> <part> <partintro> <preface> -->
+
+	<h3>To import an existing Article or Chapter</h3>
+	<p>
+	In the File Open dialog select the appropriate DocBook filter (Article or Chapter) in the File Type combo-box. An existing DocBook document can then be imported to OpenOffice.org.
+	</p>
+
+	<h3>To export an Article or Chapter</h3>
+	<p>
+	Similarly, in the File Save As dialog select the appropriate DocBook filter in the File Type combo-box.<br>
+	<b>NOTE:</b> It is possible with the current filter to import an article and export it as a chapter, or go from chapter to article. 
+	</p>
+
+	<h3>Creating an Article or Chapter</h3>
+	<p>
+	It is possible to create and save a new DocBook document in OpenOffice.org. 
+	<ul>
+	<li>Go to File -&gt; Open</li>
+	<li>Select OpenOffice Text Document Template (*.stw) as the File Type</li>
+	<li>Open the DocBookTemplate.stw (downloaded when enabling the DocBook stylesheets)</li>
+	<li>Begin entering DocBook content as described in the sections below.</li>
+	<li>Export the document as either a DocBook Chapter or Article</li>
+	</ul>	
+	</p>
+		
+<br>
+<a name="meta_information"><h2>2. Meta Information</h2></a>
+<!-- <articleinfo> <bookinfo> <chapterinfo> <releaseinfo> -->
+	<p>
+	The info sections currently supported match the top-level elements: &lt;articleinfo&gt; and &lt;chapterinfo&gt;
+	</p>
+	<h3>Creating an Articleinfo</h3>
+	<p>
+	The ArticleInfo can contain the meta information about the Article, such as author details and copyright.
+	<ul>
+	<li>The cursor should be at the top of the document</li>
+	<li>Open the Insert Section dialog.</li>
+	<li>Set the name of the new section to <i>ArticleInfo</i> and Insert</li>
+	<li>Go to Custom Paragraph styles in the Stylist and select Document Title</li>
+	<li>Enter the document title</li>
+	<li>Create the Authorgroup (this is an example of using <a href="#nested_elements">nested elements</a>):</li>
+	<ul>
+	<li>Go to All Character styles in the Stylist and select Default</li>
+	<li>Press return to create a new line and enter the first author's name</li>
+	<li>Highlight the author's name</li>
+	<li>In the Insert Bookmark dialog enter <i>author_0</i></li>
+	<li>Repeat the above 3 lines to create the second author's name, this time using <i>author_1</i></li>
+<!-- shouldn't have to create the new line above the names???? -->
+	<li>Create a new line above the author names</li>
+	<li>Highlight both the names and the empty line above them</li>
+	<li>In the Insert Bookmark dialog enter <i>authorgroup_0</i></li>
+	</ul>
+	<li>In the File Save As dialog, export the document as a DocBook Article.</li>
+	</ul>
+	The above steps can also be followed to create a Chapterinfo, replacing Chapter for Article were necessary.
+	</p>
+
+<br>
+<a name="nested_elements"><h2>3. Nested Elements</h2></a>
+<!-- <authorgroup> <glossary> <legalnotice> <menuchoice> <publisher> <revhistory> <revision> <revnumber> -->
+	<p>Early in the DocBook project there were difficulties mapping nested DocBook XML elements to the internal OpenOffice.org XML format. An example of how nested tags are now supported is the menuchoice element that can contain several guimenu elements.
+	</p>
+	<p>
+	<b>NOTE:</b> This is the initial fix for the problem of nesting DocBook XML tags in OpenOffice.org. The main purpose was to retain the information on a round-trip import and export of a DocBook document. It is not ideally suited to creating DocBook content in OpenOffice.org.<br>
+	</p>
+	<h3>Nesting Guimenus and Guimenuitem inside a Menuchoice</h3>
+	<ul>
+	<li>Press return to create a new paragraph</li>
+	<li>Go to Custom Character styles in the Stylist and select Guimenu</li>
+	<li>Enter the Guimenu text</li>
+	<li>Select Guimenuitem in the Stylist</li>
+	<li>Enter the Guimenuitem text</li>
+	<li>Highlight the Guimenu and Guimenuitem text</li>
+	<li>In the Insert Bookmark dialog enter the text <i>menuchoice_0</i> and click OK</li>
+	</ul>
+	<p>
+	OpenOffice.org bookmarks with reserved names are used to represent the parent element when nesting tags. The convention used is to follow the element name by an underscore and a number. The first element in the document will be numbered 0 (e.g. menuchoice_0) and subsequent elements of the same type will increment this number (e.g. menuchoice_1 menuchoice_2 etc.). For another example of how to use nested tags, see <a href="#meta_information"> Meta Information </a>where an Authorgroup is  [...]
+	</p>
+
+
+<br>
+<a name="inline_elements"><h2>4. In-Line Elements</h2></a>
+<!-- gui* and para -->
+	<p>DocBook in-line elements are, in general, mapped to OpenOffice.org Custom Styles.
+	</p>
+	<p>
+	The following instructions show how to create a DocBook subscript element.
+	<ul>
+	<li>Go to Custom Character styles in the Stylist and select Subscript</li>
+	<li>Enter the subscript text</li>
+	</ul>
+	The same procedure can be used for all of the DocBook Custom Character styles.
+	</p>
+
+<br>
+<a name="sections"><h2>5. Sections</h2></a>
+<!-- sect* -->
+	<p> Initially the DocBook project used OpenOffice.org sections to enforce the nesting of DocBook sections. Feedback has shown that authors wish to use the common word processing styles such as Heading1, Heading2, etc. The following instructions describe how to create a &lt;sect1&gt; that contains a &lt;sect2&gt; 
+	</p>
+	<ul>
+	<li>Select <b>All Styles</b> in the Stylist combo-box</li>
+	<li>Click the <b>Paragraph Styles</b> icon (first in the left on the Stylist)</li>
+	<li>Double-click the <b>Heading 1</b> style</li>
+	<li>Enter the text to be the &lt;sect1&gt; title</li>
+	<li>All the text below this heading will now be the content of the DocBook &lt;sect1&gt;</li>
+	<li>Enter other DocBook styles, tables, etc.</li>
+	<li>Enter other DocBook styles, tables, etc. to be included in &lt;sect1&gt;</li>
+	<ul>
+	<li>Double-click the <b>Heading 2</b> style</li></li>
+	<li>Enter the text to be the &lt;sect2&gt; title</li>
+	<li>All the text below this heading will now be the content of the DocBook &lt;sect2&gt;</li>
+	<li>Enter other DocBook styles, tables, etc. to be included in &lt;sect2&gt;</li>
+	</ul>
+	<li>This nesting of DocBook sect's using OpenOffice headings can go as far as &lt;sect4&gt; / Heading 4</li>
+	</ul>
+
+
+<br>
+<a name="tables"><h2>6. Tables</h2></a>
+<!-- <colspec> <entry> <informaltable> <row> <table> <tbody> <tgroup> <thead> -->
+	<p>
+	Formal and Informal DocBook tables are represented by a standard OpenOffice.org tables.<br>
+	<br>
+	<i>Creating a Table</i>	
+	<ul>
+	<li>Go to Insert -&gt; Table...</li>
+	<li>Set the table properties using the Insert Table dialog</li>
+	<li>The table name will become the table's id</li>
+	<li>Fill in the content of the table</li>
+	<li>Right-click on the table, and enter the table's &lt;title&gt; as the Caption</li>
+	</ul>
+	</p>
+	<i>Creating an Informaltable</i>
+	<p>An &lt;informaltable&gt; is constructed in the same fashion as the formal table above, the only difference is that the table Caption is not specified.</p>
+
+
+<br>
+<a name="lists"><h2>7. Lists</h2></a>
+<!-- <itemizedlist> <listitem> <member> <orderedlist> <term> <variablelist> <varlistentry> -->
+	<p>
+	The various DocBook lists are represented by custom and standard OpenOffice.org list styles.
+	</p>
+	<h3>Creating a Varlist containing Varlistentrys</h3>
+	<ul>
+	<li>Select <b>Custom Styles</b> in the Stylist combo-box</li>
+	<li>Click the <b>Paragraph Styles</b> icon (first in the left on the Stylist)</li>
+	<li>Double-click the <b>VarList Term</b> style</li>
+	<li>Enter text to be contained in the varlist term</li>
+	<li>Press the return key to enter text in the next varlist term</li>
+	</ul>
+
+	<h3>Creating an Orderedlist containing Listitems</h3>
+	<ul>
+	<li>Toggle the numbering to on by clicking the Numbering On/Off icon</li>
+	<li>Enter text to be contained in the listitem</li>
+	<li>Press the return key to enter text in the next listitem</li>
+	</ul>
+
+	<h3>Creating an Unorderedlist containing Listitems</h3>
+	<ul>
+	<li>Toggle the bullets to on by clicking the Bullets On/Off icon</li>
+	<li>Enter text to be contained in the listitem</li>
+	<li>Press the return key to enter text in the next listitem</li>
+	</ul>
+
+<br>
+<a name="links"><h2>8. Links</h2></a>
+<!-- <footnote> <link> <note> <olink> <ulink> <xref> -->
+	<p>The different methods of linking available in DocBook are supported in OpenOffice.org
+	</p>
+
+	<!--<h3>How to create a Link</h3>
+	<p>
+	<b>TBD</b>
+	</p>
+
+	<h3>How to create an Olink</h3>
+	<p>
+	<b>TBD</b>
+	</p>
+
+	<h3>How to create a Ulink</h3>
+	<p>
+	<b>TBD</b>
+	</p>-->
+
+	<h3>How to create a Footnote</h3>
+	<p>
+	<ul>
+	<li>Format the properties of the footnote in the Insert Footnote dialog.</li>
+	<li>Press OK and enter the footnote text at the bottom of the OOo page.</li>
+	<li></li>
+	<li></li>
+	<li></li>
+	</ul>	
+	<b>TBD</b>
+	</p>
+
+	<h3>How to create a Note</h3>
+	<p>
+	<ul>
+	<li>Go to Insert -&gt; Note...</li>
+	<li>Enter the text and click OK.</li>
+	<li>The text will be exported as &lt;note&gt; &lt;remark&gt; your text here &lt;/remark&gt; &lt;/note&gt; </li>
+	</ul>	
+	</p>
+
+	<h3>How to create an Xref</h3>
+	<p>
+	There is support for &lt;xref&gt; with a linkend attribute. If the element to be referenced does not already have an id attribute then an id can be created with an OpenOffice.org cross-reference. <br><br>
+	<i>Create an id attribute for a &lt;sect1&gt;</i>
+	<ul>
+	<li>Highlight the sect1 title</li>
+	<li>Go to Insert -&gt; Cross-reference...</li>
+	<li>Set <i>Type</i> to <i>Set Reference</i></li>
+	<li>Set <i>Name</i> to the desired value of the id attribute</li>
+	<li>Click Insert</li>
+	</ul>
+	<i>Create the &lt;xref&gt;</i>
+	<ul>
+	<li>Place cursor where the &lt;xref&gt; is to be located</li>
+	<li>Go to Insert -&gt; Cross-reference...</li>
+	<li>Set <i>Type</i> to <i>Insert Reference</i></li>
+	<li>From <i>Selection</i> choose the id for the &lt;sect1&gt; (this corresponds to the linkend attribute)</li>
+	<li>Choose Reference from the Format list.</li>
+	<li>Click Insert</li>
+	</ul>
+	</p>
+
+	<h3>Link, Ulink and Olink</h3>
+	<p>
+	The filter has round trip support for importing and exporting DocBook links.
+	</p>
+
+
+<br>
+<a name="graphics"><h2>9. Graphics</h2></a>
+<!-- <figure> <graphic> <imageobject> <imagedata> <inlinegraphic> <inlinemediaobject> <mediaobject> <screeninfo> <screenshot> <textobject> -->
+	<p>
+	</p>
+	<h3>How to create a MediaObject</h3>
+	<p>
+	<b>TBD</b>
+	</p>
+
+<br>
+<a name="index"><h2>10. Index</h2></a>
+<!-- <index> <indexentry> <indexterm> <primary> <primaryie> <secondary> <secondaryie> <see> <seealso> <tertiary> <tertiaryie> -->
+	<h3>How to create an Indexterm</h3>
+	<p>
+	<ul>
+	<li>If the document does not already contain any DocBook sections see <a href="#sections">Sections</a>. </li>
+	<li>Highlight the section title</li>
+	<li>Go to Insert -&gt; Indexes and Tables -&gt; Entry...</li>
+	<li>Set Index to Alphabetical Index</li>
+	<li>Set 1st Key to the desired content of &lt;primary&gt;</li>
+	<li>Set 2nd Key to the desired content of &lt;secondary&gt;</li>
+	<li>Click Insert</li>
+	</ul>	
+	</p>
+	<p>
+	<b>NOTE:</b> After discussions with authors the decision was made to only support simplified indexterms in the future. Few authors use spanning indexterms with startofrange and endofrange values or reference elements with a zone attribute.  
+	</p>
+
+	<h3>How to create an Index</h3>
+	<p>
+	At present it is not possible to create a DocBook index in OpenOffice.org. However, the import and export filters should retain any index tags in an existing DocBook document.	
+	</p>
+
+
+</body>
+</html>
diff --git a/content/xml/xmerge/docbook/temp_test_only.html b/content/xml/xmerge/docbook/temp_test_only.html
new file mode 100644
index 0000000..3837375
--- /dev/null
+++ b/content/xml/xmerge/docbook/temp_test_only.html
@@ -0,0 +1,252 @@
+<html>
+<head>
+<title>DocBook Filters - Read and write docbook xml using OpenOffice.org</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+<a name="top"></a>
+
+<h1>DocBook Filters - Read and write docbook xml using OpenOffice.org</h1>
+
+<p>Goal is to explore the possibility of using OpenOffice.org as a WYSIWYG editor of XML content.
+The principle is to edit structured documents using styles.  These styles are then transformed to XML tags on export.</p>
+
+<p>This page shows how to enable and use the DocBook filters.  It also shows the location of the stylesheets so that users can download and use the latest transformations.</p>
+
+
+<p>Initially the project used OpenOffice.org sections to enforce nesting of DocBook sections.
+Feedback has shown that authors wish to use the common word processing styles such as Heading1, Heading2, etc.  The stylesheets and templates shipped with OOo1.1 Beta use OpenOffice.org sections.
+Links are available below for stylesheets which use OOo headings and instructions on how to install these stylesheets.
+Stylesheets currently only support DocBook Articles. Book and Chapter support is planned.</p>
+
+
+<p>Currently stylesheets are packaged in a JAR.  The content of the JAR is explained later in this document. It is planned that future OOo will be able to use the import and export XSLTs directly.</p>
+
+
+<p>To see what is available and get an impression of how it works look at :<p> 
+
+
+<ol>
+   <li>A <!--<a href="http://xml.openoffice.org/xmerge/downloads/docbooktemplate.xml">--><a href="http://xml.openoffice.org/xmerge/downloads/gedit.xml">Sample DocBook </a>Document</li>
+   <li>The corresponding <!--<a href="http://xml.openoffice.org/xmerge/downloads/docbooktemplate.sxw>">--><a href="http://xml.openoffice.org/xmerge/downloads/gedit.sxw">Writer (.sxw) file</a> after importing the docbook file.<br><b> Note :</b> Nested sections supported. See applied or custom styles in the stylist for DocBook tags which have been supported. </li>
+<!--
+   <li><a href="http://xml.openoffice.org/xmerge/downloads/gedit.html">HTML generated</a> from the sample DocBook file for supported tags. <br><b>Note :</b> this is a one-way transformation as there is information loss. </li>
+-->
+</ol>
+
+
+<p><b>Note :</b> See also Eric Bellot's <a href="http://www.chez.com/ebellot/ooo2sdbk">OOo2sdbk</a></p>
+
+
+
+<h2>How to Enable DocBook in OpenOffice1.1 Beta</h2>
+
+<p>The DocBook filters are installed during OpenOffice.org setup by selecting "<font face="Arial">Custom Installation</font>" and in the "<font face="Arial">Optional Components</font>" section, selecting the "<font face="Arial">Mobile Device Filters</font>".</p>
+
+<p>To enable the DocBook filter, the following file must be edited: <br> <b>&lt;OOo Install Dir&gt;/share/registry/data/org/openoffice/Office/TypeDetection.xcu;</b></p>
+
+
+<ul>
+   <li>Search for the line &lt;node oor:name="DocBook File" oor:op="replace"&gt; </li>
+   <li>Before the corresponding &lt;/node&gt; tag add the following lines:</li>
+</ul>
+<ul>
+   &lt;prop oor:name="Installed" oor:type="xs:boolean"&gt;
+   <ul>
+      &lt;value>true&lt;/value&gt;
+   </ul>
+   &lt;/prop&gt;
+</ul>
+<ul>
+   <li>Similarly for XHTML except search for the line &lt;node oor:name="XHTML File" oor:op="replace"&gt; </li>
+   <li>Similarly for Flat XML File except search for the line &lt;node oor:name="Flat XML File" oor:op="replace"&gt; </li>
+</ul>
+
+<p>Once the filter has been enabled, run OOo to see DocBook available in the OpenOffice.org "File of Type" comb-box in both the Open and Save/As dialogs. <b>Hint :</b> Type D in the "File of Type" combo-box maybe more than once.</p>
+
+<p><b>NOTE :</b> In order for the Java based filters to work correctly, and Java Runtime Environment needs to be specified during setup.
+JRE1.4 or greater is recommended as it contains an XML Parser (Crimson) and an XSLT processor (Xalan).
+JRE1.3 can also be used, if a parser e.g. Xerces or Crimson, and the Xalan XSLT processor are made available.</p>
+
+
+
+
+<h2>Using OpenOffice.org to create and edit DocBook XML</h2>
+
+<h3>Creating a DocBook Template</h3>
+
+It is not possible to use a predefined template to supply the DocBook styles in OpenOffice.org. To do this you must do the following:
+
+<ul>
+<!--   <li>Save a blank Writer document as DocBook</li>
+   <li>Open the document again in Writer</li> -->
+
+   <!-- <li>Download a simple <a href="http://xml.openoffice.org/xmerge/downloads/gedit.xml">DocBook XML Document</a></li> -->
+   <li>Download the associated <a href="http://xml.openoffice.org/xmerge/downloads/DocBookTemplate.stw">template</a></li>
+   <!-- <li>Open the document in OOo. as DocBook(*.xml)</li> -->
+   <li>Open the template on OOo</li>
+   <li>Press F11 and choose 'All Styles', so that all available DocBook styles are displayed.</li>
+</ul>
+
+<p>Review the <a href="http://xml.openoffice.org/xmerge/docbook/UserGuide.html">UserGuide</a> for information on using the filter.</p>
+
+
+
+
+<h2>Sections/Headings</h2>
+
+<h3>How to change the Stylesheet</h3>
+
+<p>The docbook filter uses the XMerge framework's XSLT processing functionality. The <a href="http://xml.openoffice.org/xmerge/downloads/docbook.jar">docbook.jar</a> contains a set of <!-- <a href="http://framework.openoffice.org/source/browse/framework/filter/source/docbook/">--> <a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">two XSLT style-sheets</a>, one for transforming from docbook to OpenOffice and one for transfo [...]
+
+<p>The file also contains a converter.xml file in the META-INF directory that contains information describing the supported mime-types, the style-sheet names and the XMerge plugin that it uses.</p>
+
+<p>To make changes:</p>
+<ul>
+  <li>Create a temp directory.
+  <ul>
+     <li>mkdir temp </li>
+  </ul></li>
+  <li>Unpack the jar to the temp directory: 
+  <ul>
+     <li>jar -xvf docbook.jar temp </li>
+  </ul></li>
+  <li>This will produce the following files in the temp directory:
+  <ul>
+     <li>META-INF/MANIFEST.MF </li>
+     <li>META-INF/converter.xml</li>
+<!--     <li>sofftodocbookheadings.xsl</li>
+     <li>docbooktosoffheadings.xsl</li>
+-->
+     <li>sofftodocbook.xsl</li>
+     <li>docbooktosoff.xsl</li>
+  </ul></li>
+</ul>
+
+<p>The two stylesheets can now be edited as required, or download the latest copies from <!--<a href="http://framework.openoffice.org/source/browse/framework/filter/source/docbook/">--><a href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/xslt/docbook/">here</a>. </p>
+
+<p>Repacking the jar:</p>
+<ul>
+  <li>cd temp</li>
+  <li>jar -cvf ../docbook.jar *</li>
+  <li>Copy the jar to &lt;OOo installation&gt;/program/class directory 
+  <li>Restart OpenOffice.org</a>
+</ul>
+
+<p>For example, to use the new XSLT stylesheets, replace the stylesheets in temp with the downloaded versions. The converter.xml file contains info regarding the file conversions that the filter supports. This information is used by XMerge when a conversion has been requested.</p>
+<ul>
+&lt;converters&gt;
+   <ul>   
+   &lt;converter type="staroffice/sxw" version="1.0"&gt;
+      <ul>
+      &lt;converter-display-name&gt;
+         <ul>
+         XSLT Transformation sxw
+         </ul>
+      &lt;/converter-display-name&gt;
+      </ul>
+      <ul>
+      &lt;converter-description&gt;
+         <ul>
+         Converter which performs xslt transformations
+         </ul>
+      &lt;/converter-description&gt;
+      </ul>
+      <ul>
+      &lt;converter-vendor&gt;
+         <ul>
+         OpenOffice.org 
+         </ul>
+      &lt;/converter-vendor&gt;
+      </ul>
+      <ul>
+      &lt;converter-class-impl&gt;
+         <ul>
+         org.openoffice.xmerge.converter.xml.xslt.PluginFactoryImpl
+         </ul>
+      &lt;/converter-class-impl&gt;
+      </ul>
+      <ul>
+      &lt;converter-xslt-serialize&gt;
+         <ul>
+         sofftodocbookheadings.xsl
+         </ul>
+      &lt;/converter-xslt-serialize&gt;
+      </ul>
+      <ul>
+      &lt;converter-xslt-deserialize&gt;
+         <ul>
+         docbooktosoffheadings.xsl
+         </ul>
+      &lt;/converter-xslt-deserialize&gt;
+      </ul>
+      <ul>
+      &lt;converter-target type="application/x-docbook" /&gt;
+      </ul>
+   &lt;/converter&gt;
+   </ul>
+&lt;/converters&gt;
+</ul>
+
+<h3>Currently Supported Tags</h3>
+
+<p>Click <a href="http://xml.openoffice.org/xmerge/docbook/DocBookTags.html">here</a> to obtain a list of currently supported DocBook tags.</p>
+
+
+<h3>ToDo</h3>
+<ul>
+   <li>Increase coverage of supported DocBook tags</li>
+   <li>XML Entity support. Entity references are lost currently. It may be possible to preserve them by treating them as fields.</li>
+   <li>ArticleInfo - Initially was going to use document properties but too many tags so this would probably be another section.</li>
+   <li>Images. (We have placeholders for required information).</li>
+   <li>Hyperlinks.</li>
+   <li>Chapters</li>
+   <li>References</li>
+</ul>
+
+
+<h3>Limitations</h3>
+<p>These are limitations which should be highlighted but are not blockers. In fact, sufficient interest in this project should drive requirements for enhancements.</p>
+
+<p>- No support in OOo for user as to which styles (tags) to use when. Must create and follow guidelines.</p>
+
+<p>- No validation for export.</p>
+
+
+<h3>Open Issues</h3>
+<ul>
+   <li>Do not support nested tags in text spans. 
+      <ul>
+      e.g Use:
+         <ul>
+            &lt;menuchoice&gt;&lt;guimenu&gt;File&lt;/guimenu&gt;&lt;guimenuitem&gt;New&lt;/guimenuitem&gt;&lt;/menuchoice&gt;
+         </ul>
+      to which in HTML appears as:
+         <ul>
+            Use File ->New
+         </ul>
+      </ul>
+   </li>
+   <li> Importing comments (Parser ignores, may have to use comment tag).  </li>
+   <li> Nested lists are split into three separate lists in SO and have to be exported as three separate lists. Breaks the round trip.</li>
+   <li> Styles are defined in the import stylesheet. </li>
+   <li>Would like to be able to import into an existing template.  </li>
+</ul>
+
+<!-- The Converter.xml file -->
+
+
+
+
+
+
+
+
+<br>
+
+<hr>
+
+</body>
+</html>
diff --git a/content/xml/xmerge/downloads/gedit.html b/content/xml/xmerge/downloads/gedit.html
new file mode 100644
index 0000000..63eaa41
--- /dev/null
+++ b/content/xml/xmerge/downloads/gedit.html
@@ -0,0 +1,201 @@
+<html><head><meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"><title>gedit Manual V2.1</title><meta name="generator" content="DocBook XSL Stylesheets V1.45"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article"><div class="titlepage"><div><h1 class="title"><a name="index"></a>gedit Manual V2.1</h1>
+
+         <h2>Introduction</h2></div></div><p>The gedit application is a simple text
+		editor. You can use gedit to create and edit text
+		files. You can use gedit plugins to perform a
+		variety of tasks related to text-editing from within the
+		gedit window.</p></div><div class="sect1"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="gedit-getting-started"></a>Getting Started</h2></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-to-start"></a>To Start gedit</h3></div></div><p>You can start gedit in the following ways:</p><div class="variablelist"><dl><dt><span class="term">Applications menu</span></dt><dd><p>Choose 
+    		Accessories-&gt;Text Editor. </p></dd><dt><span class="term">Command line</span></dt><dd><p>Type <b>gedit</b>, then press <b>Return</b>.</p></dd></dl></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-when-you-start"></a>When You Start gedit</h3></div></div><p>When you start gedit, the following window is displayed:</p><div class="figure"><p><a name="gedit-window"></a><b>Figure 1. gedit Window</b></p><div class="screenshot"><div class="media [...]
+		  elements: </p><div class="variablelist"><dl><dt><span class="term">Menubar</span></dt><dd><p>The menus on the menubar contain all of the commands you need
+				  to work with files in gedit.</p></dd><dt><span class="term">Toolbar</span></dt><dd><p> The toolbar contains a subset of the commands that you can
+				  access from the menubar.</p></dd><dt><span class="term">Display area</span></dt><dd><p> The display area contains the text of the file that you are
+				  editing. </p></dd><dt><span class="term">Statusbar</span></dt><dd><p>The statusbar displays information about current
+				  gedit  activity and contextual information about the
+				  menu items. </p></dd></dl></div><p>When you right-click in the gedit
+		  window, the application displays a popup menu. The popup menu contains the most
+		  common text editing commands. </p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-open-file"></a>To Open a File</h3></div></div><p>To open a file, choose 
+		  File-&gt;Open
+		  to display the Open File dialog. Select the file
+		  that you want to open, then click OK. The file is
+		  displayed in the gedit window. </p><p>You can open multiple files in gedit.
+		  The application displays one file at a time in the application window. The
+		  application adds a tab for each open file to the window. To display another
+		  open file, click on the tab that corresponds to the file. To create a new
+		   gedit window for each file that is open, drag the
+		  tab corresponding to each file to the desktop. You can also use the
+		  Documents menu to move between the open files.</p><p>The application records the paths and filenames of the last
+		  four files that you edited and displays the files as menu items on the File-&gt;Recent Files menu. 
+		  </p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-run-from-cmd-line"></a>To Open Multiple Files from a Command Line</h3></div></div><p>You can run gedit from a command line
+		  and open a single file or multiple files. To open multiple files from a command
+		  line, type the following command, then press <b>Return</b>:</p><p><b>gedit <i><tt>file1.txt file2.txt file3.txt</tt></i></b></p><p>When the application starts, the files that you specified are
+		  displayed in the gedit window.</p></div></div><div class="sect1"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="gedit-usage"></a>Usage</h2></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-create-new-file"></a>To Create a New File</h3></div></div><p>To create a new file, choose 
+		  File-&gt;New. The application displays a new file in the
+		  gedit window.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-save-file"></a>To Save a File</h3></div></div><p>You can save files in the following ways:</p><div class="itemizedlist"><ul><li><p>To save changes to the current file, choose 
+				File-&gt;Save or click Save
+				  on the toolbar. If the file does not have a filename, gedit 
+					 displays the Save As dialog. Enter a name for the file in the 
+Save
+				As dialog, then click OK.</p></li><li><p>To save a new file or to save an existing file under a new filename, choose 
+				File-&gt;Save
+				  As. Enter a name for the file in the Save
+				As dialog box, then click OK. </p></li><li><p>To save all of the files that are currently open in
+				gedit, choose 
+				File-&gt;Save
+				  All.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-edit-text"></a>To Edit Text</h3></div></div><p>You can edit the text of a file in the following ways:</p><div class="itemizedlist"><ul><li><p>Type new text from the keyboard. </p></li><li><p>Use the <b>Delete</b> key to delete text.
+				</p></li><li><p>Use the Cut,
+				Copy, Paste, and
+				Delete menu items to edit text. </p></li></ul></div><p>When you select text with the mouse,
+		  gedit automatically copies the selected text to a
+		  buffer. You can perform any of the following actions on the selected text:
+		  </p><div class="itemizedlist"><ul><li><p>To delete the selected text from the file and move the
+				selected text to a buffer, choose 
+				Edit-&gt;Cut.</p></li><li><p>To permanently delete the selected text from the file, choose 
+				Edit-&gt;Delete.</p></li><li><p>To insert the contents of the buffer at the cursor
+				position, middle-click or choose 
+				Edit-&gt;Paste. You must cut or copy text
+				before you can paste text into the file.</p></li><li><p>To select all of the text in a file, choose 
+				Edit-&gt;Select
+				  All. </p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-undo-redo-edits"></a>To Undo or Redo Edits</h3></div></div><p>To undo an edit, choose 
+		  Edit-&gt;Undo. To redo an edit, choose 
+		  Edit-&gt;Redo. The number of previous edits that you can undo is determined by
+		  the Set limit on undo levels to setting in the
+		  <a href="#gedit-prefs-undo" title="Undo">the section called &#8220;Undo&#8221;</a> tabbed section of the
+		  Preferences dialog. By default, the number of actions that you 
+		  can undo is 25.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-find-text"></a>To Find Text</h3></div></div><p>To search a file for a string, perform the following steps:</p><div class="orderedlist"><ol type="1"><li><p>Choose 
+				Search-&gt;Find
+				to display the Find dialog.</p></li><li><p>Type the string that you want to find in the
+				Search for field.</p></li><li><p>Select one of the following options:</p><div class="itemizedlist"><ul><li><p>Search from the beginning of the
+					 document</p></li><li><p>Search from the cursor position
+					 </p></li></ul></div></li><li><p>Select the Case sensitive option
+				to only find occurrences of the string that match the case of the text that you
+				type. </p></li><li><p>Click Find to search the file
+				for the first occurrence of the string. If gedit
+				finds the string, the application moves the cursor to the string, and selects
+				the string.</p></li><li><p>To find the next occurrence of the string, click
+				Find Next.</p></li><li><p>To finish the search, click
+				Close. </p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-find-replace-text"></a>To Find and Replace Text</h3></div></div><p>To search a file for a string, and replace the string with an
+		  alternative string, perform the following steps:</p><div class="orderedlist"><ol type="1"><li><p>Choose 
+				Search-&gt;Replace
+				to display the Replace dialog.</p></li><li><p>Type the string that you want to find in the
+				Search for field. </p></li><li><p>Type the string that you want to use to replace the
+				string that you find in the Replace with field.</p></li><li><p>Select one of the following options:</p><div class="itemizedlist"><ul><li><p>Search from the beginning of the
+					 document</p></li><li><p>Search from the cursor
+					 position</p></li></ul></div></li><li><p>Select the Case sensitive option
+				to only find occurrences of the string that match the case of the text that you
+				enter. </p></li><li><p>Click Find to search the file
+				for the first occurrence of the string. If gedit
+				finds the string, the application moves the cursor to the string, and selects
+				the string. </p></li><li><p>Click on Replace to replace the
+				occurrence of the string with the text that you typed in the Replace
+				with field. Click on Replace All to replace
+				all occurrences of the string.</p></li><li><p>To find the next occurrence of the string, click
+				Find Next.</p></li><li><p>To finish the search, click
+				Close. </p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-open-from-uri"></a>To Open a File from a URI</h3></div></div><p>To open a file from a Uniform Resource Identifier (URI), perform one of the following steps:</p><div class="itemizedlist"><ul><li><p>Choose File-&gt;Open Location
+to display the Open from URI
+dialog. Enter the URI of the 
+		file that you want to
+open, then click Open.</p></li><li><p>Type <b>gedit <i><tt>http://...</tt></i></b> at a command line, where
+		<i><tt>http://...</tt></i> is the URI of the file that you want to open, then press
+		<b>Return</b>.</p></li></ul></div><p>The application opens the file located at the URI in readonly mode.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-pipe-output"></a>To Pipe the Output of a Command to a File</h3></div></div><p>You can use gedit to pipe the output of
+		  a command to a text file. For example, to pipe the output of an <b>ls
+		  </b> command to a text file, type the following command, then press
+		  <b> Return</b>:</p><p><b>ls | gedit</b></p><p>The output of the <b>ls</b> command is displayed in a
+		  new text file in the gedit window.</p><p>Alternatively, you can use the Shell Output plugin to pipe command
+		  output to the current file. To use the Shell Output plugin, perform the
+		  following steps:</p><div class="orderedlist"><ol type="1"><li><p>Load the Shell Output plugin. See <a href="#gedit-install-plugins" title="To Load gedit Plugins">the section called &#8220;To Load gedit Plugins&#8221;</a> for 
+			information about how to load a plugin.</p></li><li><p>Choose 
+				Edit-&gt;Insert Shell
+				  Output
+				to display the Shell output dialog.
+				</p></li><li><p>Type the shell command that you want to execute in the
+				Shell command field.</p></li><li><p>Edit the Working directory field
+				if necessary. By default, the Shell Output plugin executes the command you
+				specify in the current directory.</p></li><li><p>Click Run. The Shell Output
+				plugin executes the command and inserts the text output into the current file.
+				</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-goto-line"></a>To Go to a Specific Line</h3></div></div><p>To go to a specific line in the current file, perform the following
+		  steps:</p><div class="orderedlist"><ol type="1"><li><p>Choose 
+				Search-&gt;Goto
+				  Line
+				to display the Goto line dialog.</p></li><li><p>Type the number of the line that you want to move the
+				cursor to in the Line number field.</p></li><li><p>Click Goto line. The application
+				moves the cursor to the line number that you specify.</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-input-mode"></a>To Change the Input Mode</h3></div></div><p>To change the input mode, right-click in the text window, then select Input Methods. 
+		The Insert Unicode control character menu item provides character layout 
+		options that are useful for working with non-Latin character sets.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-print-file"></a>To Print a File</h3></div></div><p>You can use gedit to perform the
+		  following print operations:</p><div class="itemizedlist"><ul><li><p>Print a file to a printer. </p></li><li><p>Print the output of the print command to a file.</p></li></ul></div><p>If you print to a file, gedit sends the
+		  output of the file to a pre-press format file. The most common pre-press
+		  formats are PostScript and Portable Document Format (PDF).</p><p>To preview the pages that you want to print, choose
+		File-&gt;Print Preview
+to display the gedit - Print Preview
+		 dialog.</p><p>To print the current file to a printer or a file, choose 
+		File-&gt;Print
+		to display the Print dialog.</p><p>The Print dialog allows you to specify the following
+		print options:</p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="print-dialog-job"></a>Job Tabbed Section</h4></div></div><div class="variablelist"><dl><dt><span class="term">Print range </span></dt><dd><p>Select one of the following options to determine how 
+				many pages to print:</p><div class="itemizedlist"><ul><li><p>All</p><p>Select this option to print all of the pages in the file.</p></li><li><p>Selection</p><p>Select this option to print the selected text only. This option
+				is only available if you selected text.</p></li></ul></div><p>Default: All.</p></dd><dt><span class="term">Copies </span></dt><dd><p>Use this spin box to specify the number of copies of the file that
+				you want to print.</p><p>Default: 1.</p></dd><dt><span class="term">Collate </span></dt><dd><p>If you are printing multiple copies of the file, select this option
+				to collate the printed copies.</p><p>Default: unselected.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="print-dialog-printer"></a>Printer Tabbed Section</h4></div></div><div class="variablelist"><dl><dt><span class="term">Printer </span></dt><dd><p>Use this drop-down list box to select the printer to which you want
+				to print the file.</p><p>Default: Gnome default printer.</p></dd><dt><span class="term">Settings </span></dt><dd><p>Use this drop-down list box to select the printer settings. To configure
+				the printer, click Configure.</p><p>Default: Default.</p></dd><dt><span class="term">Location </span></dt><dd><p>Use this drop-down list box to select the print destination. To print the
+				file to a printer, choose lpr. To print the file
+				to a print file, choose File. If you select File,
+				type the name of the output file in the text box provided.</p><p>Default: lpr.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="print-dialog-paper"></a>Paper Tabbed Section</h4></div></div><div class="variablelist"><dl><dt><span class="term">Paper size </span></dt><dd><p>Use this drop-down list box to select the size of the paper to 
+				which you want to print the file.</p><p>Default: A4.</p></dd><dt><span class="term">Width </span></dt><dd><p>Use this spin box to specify the width of the paper. Use the
+				Centimeters drop-down list box to change the 
+				measurement unit for specifying the paper size.</p><p>Default: 21.00 centimeters.</p></dd><dt><span class="term">Height </span></dt><dd><p>Use this spin box to specify the height of the paper.</p><p>Default: 29.70 centimeters.</p></dd><dt><span class="term">Page orientation </span></dt><dd><p>Use this drop-down list box to select the page orientation.</p><p>Default: Portrait.</p></dd><dt><span class="term">Layout </span></dt><dd><p>Use this drop-down list box to select the page layou [...]
+				of each layout that you select is displayed in the Preview
+				area.</p><p>Default: Plain.</p></dd></dl></div></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-use-plugins"></a>To Use the gedit Plugins</h3></div></div><p>A plugin is a supplementary program that enhances the functionality
+		  of an application. The gedit plugins enable you to
+		  perform a variety of functions related to text editing from within the
+		   gedit window. The following table lists the plugins
+		  that are available.</p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr valign="top"><th valign="top"><p>Plugin Name</p></th><th valign="top"><p>Purpose</p></th></tr></thead><tbody><tr valign="top"><td><p>ASCII table</p></td><td><p>Displays a dialog that contains an ASCII table. You can use the ASCII table to insert characters into a file.</p></td></tr><tr valign="top"><td><p>Compare files</p></td><td><p>Compares two files and displays the differ [...]
+			This plugin uses the diff program to compare the files.</p></td></tr><tr valign="top"><td><p>CVS ChangeLog</p></td><td><p>Opens the log messages associated with CVS commit commands.</p></td></tr><tr valign="top"><td><p>Insert Date/Time</p></td><td><p>Inserts the current date and time into a file.</p></td></tr><tr valign="top"><td><p>Shell Output</p></td><td><p>Inserts the text output of a shell command into a file. </p></td></tr><tr valign="top"><td><p>Tag list</p></td><td><p>Displays [...]
+			insert a tag into a file. </p></td></tr><tr valign="top"><td><p>User name</p></td><td><p>Inserts the username of the current user into the file. </p></td></tr><tr valign="top"><td><p>Word count</p></td><td><p>Counts the number of lines, words, characters with spaces, characters without spaces, and bytes in the current file. The plugin
+			displays the results in a Word count window. </p></td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-install-plugins"></a>To Load gedit Plugins</h3></div></div><p>To load gedit plugins, choose 
+		  Edit-&gt;Plugin Manager. 
+		  The Plugin Manager dialog displays the following information:</p><div class="itemizedlist"><ul><li><p>A list of the plugins that are available.</p></li><li><p>A Configure plugin button. You can use this button to open a 
+		  configuration dialog for the plugins that you can configure.</p></li><li><p>A brief description of each plugin. To display a description,
+		  select the plugin from the list of plugins.</p></li><li><p>Details about the author of the plugin and the name of the module.</p></li></ul></div><p>To load a plugin, select the check box next to the name of the plugin. The gedit application
+		adds the plugin to the appropriate gedit menu, as described in the following table.</p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr valign="top"><th valign="top"><p>Plugin Name</p></th><th valign="top"><p>Added to Menu</p></th></tr></thead><tbody><tr valign="top"><td><p>ASCII table</p></td><td><p>View-&gt;ASCII Table</p></td></tr><tr valign="top"><td><p>Compare files</p></td><td><p>File-&gt;Compare files</p></td></tr><tr valign="top"><td><p>CVS [...]
+		  click Close.</p></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-customize-bars"></a>To Customize the Toolbar and Statusbar</h3></div></div><p>To display or hide the toolbar, choose View-&gt;Toolbar. To customize how gedit
+		  displays the toolbar, choose View-&gt;Customize Toolbar, then select one of the following 
+		  menu items:</p><div class="itemizedlist"><ul><li><p>Desktop Default: display the default toolbar.</p></li><li><p>Icon: display icons only.</p></li><li><p>Icon and Text: display icons and text.</p></li></ul></div><p>To display or hide the statusbar, choose View-&gt;Statusbar. To customize how gedit
+		  displays the statusbar, choose View-&gt;Customize Statusbar, then select one of the following 
+		  menu items:</p><div class="itemizedlist"><ul><li><p>Show Cursor Position: display the line number
+		  and column number where the cursor is located.</p><p>Default: selected.</p></li><li><p>Show Overwrite Mode: display the editing mode.
+		  If the editor is in insert mode, the statusbar contains the word INS. If the editor is in 
+		  overwrite mode, the statusbar contains the word OVR.</p><p>Default: selected.</p></li></ul></div></div></div><div class="sect1"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="gedit-prefs"></a>Settings</h2></div></div><p>To configure gedit, choose 
+		Edit-&gt;Preferences.</p><p>The Preferences dialog contains the following
+		categories:</p><div class="itemizedlist"><ul><li><p><a href="#gedit-prefs-editor" title="Editor">the section called &#8220;Editor&#8221;</a></p></li><li><p><a href="#gedit-prefs-print" title="Print">the section called &#8220;Print&#8221;</a></p></li></ul></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-prefs-editor"></a>Editor</h3></div></div><p>The Editor category is subdivided into the following 
+	 subcategories:</p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-fontsandcolors"></a>Fonts and Colors</h4></div></div><div class="variablelist"><dl><dt><span class="term">Use default theme font </span></dt><dd><p>Select this option to use the default system font for the text in the gedit text window. </p><p>Default: unselected.</p></dd><dt><span class="term">Font used by the editor </span></dt><dd><p>This field displays the font that gedit uses to [...]
+				Click on the button to specify the font type, style, and size to use for text. </p><p>Default: Courier Medium 12 point.</p></dd><dt><span class="term">Use default theme colors </span></dt><dd><p>Select this option to use the default theme colors in the gedit text window. </p><p>Default: selected.</p></dd><dt><span class="term">Text color </span></dt><dd><p>Click on the Text color button to
+				  display the color selector dialog. Select a color to use to display text in the gedit
+				text window. </p><p>Default: black.</p></dd><dt><span class="term">Background color </span></dt><dd><p>Click on the Background color button to
+				  display the color selector dialog. Select a background color for the gedit
+				text window. </p><p>Default: white.</p></dd><dt><span class="term">Selected text color </span></dt><dd><p>Click on the Selected text color button to
+				  display the color selector dialog. Select a color to use to display selected text.
+				</p><p>Default: white.</p></dd><dt><span class="term">Selection color </span></dt><dd><p>Click on the Selection color button to
+				  display the color selector dialog. Select a background color to use to highlight a text selection.
+				  </p><p>Default: blue.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-tabs"></a>Tabs</h4></div></div><div class="variablelist"><dl><dt><span class="term">Set tabs width equivalent to </span></dt><dd><p>Use this spin box to specify the width of the space that
+				   gedit inserts when you press the
+				  <b>Tab</b> key. </p><p>Default: 8 characters.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-wrapmode"></a>Wrap Mode</h4></div></div><div class="variablelist"><dl><dt><span class="term">Wrap mode </span></dt><dd><p>Select one of the following options to determine how 
+				gedit wraps text in the gedit
+				window:
+</p><div class="itemizedlist"><ul><li><p>Never wrap lines</p><p>Select this option to never wrap lines. The text that you type is displayed in one line until you press 
+				<b>Return</b>.</p></li><li><p>Wrap lines at word boundaries</p><p>Select this option to wrap text onto the next line, at a word level, when you reach the text window boundary. </p></li><li><p>Wrap lines at character boundaries</p><p>Select this option to wrap text onto the next line, at a character level, when you reach the text window boundary.</p></li></ul></div><p>Default: Wrap lines at character boundaries.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div>< [...]
+				gedit window. </p><p>Default: unselected.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-save"></a>Save</h4></div></div><div class="variablelist"><dl><dt><span class="term">Create a backup copy of files before saving </span></dt><dd><p>Select this option create a backup copy of a file each time you save the file. The backup 
+				copy of the file has a <tt>.bak</tt> extension.</p><p>Default: unselected.</p></dd><dt><span class="term">Autosave current file every </span></dt><dd><p>Select this option to automatically save the current file at regular intervals. Use the spin box
+				to specify the interval at which you want to save the file.</p><p>Default: unselected, 10 minutes.</p></dd><dt><span class="term">When saving </span></dt><dd><p>Select one of the following save options:</p><div class="itemizedlist"><ul><li><p>Always use UTF-8 encoding (faster)</p><p>Select this option to save files using UTF-8 bit encoding.</p></li><li><p>Use current locale when possible</p><p>Select this option to save files using the current locale. You can set up locales for
+				different input methods. </p></li><li><p>Use current locale only if the file already uses it</p><p>Select this option to save a file using the current locale if the file was already saved in the current locale.</p></li></ul></div><p>Default: Always use UTF-8 encoding (faster)</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-undo"></a>Undo</h4></div></div><div class="variablelist"><dl><dt><span class="term">Set limit on und [...]
+				can undo. Use the spin box to specify the maximum number of actions that you
+				can undo. </p><p>Default: selected, 25 actions.</p></dd></dl></div></div></div><div class="sect2"><div class="titlepage"><div><h3 class="title"><a name="gedit-prefs-print"></a>Print</h3></div></div><p>The Print category is subdivided into the following 
+	 subcategories:</p><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-page"></a>Page</h4></div></div><div class="variablelist"><dl><dt><span class="term">Print page headers </span></dt><dd><p>Select this option to include a header on each page that you
+				  print. You can not configure the header. </p><p>Default: selected.</p></dd><dt><span class="term">Wrap lines (at character boundaries) </span></dt><dd><p>Select this option to automatically wrap text at a character level when you print
+				  a file. The application counts wrapped lines as one line for line numbering purposes.
+				  </p><p>Default: selected.</p></dd><dt><span class="term">Print line numbers every
+			 </span></dt><dd><p>Select this option to include line numbers when you print a
+				  file. Use the spin box to specify how often to print the line numbers, for
+				  example every 5 lines, every 10 lines, and so on. </p><p>Default: unselected, 1 line.</p></dd></dl></div></div><div class="sect3"><div class="titlepage"><div><h4 class="title"><a name="gedit-prefs-fonts"></a>Fonts</h4></div></div><div class="variablelist"><dl><dt><span class="term">Font used to print the body </span></dt><dd><p>Click on this button to select the font to use to print the body text of a 
+				file.</p><p>Default: Courier 9.0.</p></dd><dt><span class="term">Font used to print headers </span></dt><dd><p>Click on this button to select the font to use to print the headers in a 
+				file.  </p><p>Default: Helvetica 11.0.</p></dd><dt><span class="term">Font used to print line numbers
+			 </span></dt><dd><p>Click on this button to select a font to use to print line numbers.</p><p>Default: Helvetica 8.0.</p></dd></dl></div><p>To reset the fonts to the default fonts for printing a file from gedit
+		click on the Restore default fonts button.</p></div></div></div></div></body></html>
diff --git a/content/xml/xmerge/downloads/index.html b/content/xml/xmerge/downloads/index.html
new file mode 100644
index 0000000..bdef230
--- /dev/null
+++ b/content/xml/xmerge/downloads/index.html
@@ -0,0 +1,186 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+  	   
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=iso-8859-1">
+  <title>XMerge - Downloads section</title>
+     	 	   
+  <meta name="GENERATOR" content="StarOffice 6.0  (Solaris Sparc)">
+  	   
+  <meta name="CREATED" content="20020717;15440100">
+  	   
+  <meta name="CHANGED" content="20020718;17025700">
+</head>
+  <body lang="en-US">
+   
+<h1>Available downloads</h1>
+   
+<h2>Mobile Device Support</h2>
+   
+<p>The Mobile Device Support Pack installs three separate sets of components 
+to your OpenOffice installation &#8211; the <a href="#XmlFilterAdapter">XmlFilterAdapator</a>, 
+the XMergeBridge and current set of available XMerge <a
+ href="http://xml.openoffice.org/xmerge/index.html#plug-ins">plugins</a>.</p>
+   
+<h3>Prerequisites</h3>
+   
+<ul>
+  	<li>The Mobile Device Support Pack is designed to work with OpenOffice 
+1.0.  	    It should also work with OpenOffice 642 and OpenOffice 643.  		It 
+has also been tested with StarOffice 6.0. There isn't currently a  		way to
+make it work with other builds. If there's a demand for supporting  		other 
+builds then we'll make the necessary updates. 		</li>
+  	<li>You must have JRE 1.4 or above installed for the installer to work.
+ 		<br>
+ You must have JRE 1.4 or above installed and configured for use with OpenOffice 
+to have access 		to the plugins within OpenOffice. </li>
+ 
+</ul>
+   
+<h3>Instructions</h3>
+   
+<ol>
+  	<li>     
+    <p>Download the <a
+ href="http://xml.openoffice.org/xmerge/downloads/XMergeInstall.jar">XMergeInstall.jar</a> 
+file.</p>
+  	</li>
+   <li>     
+    <p>For all installations ensure that you have completely quit 	OpenOffice 
+&#8211; this includes shutting down the quick-starter if 	it is running. Once the 
+installation starts, follow the instructions 	on screen.</p>
+  	</li>
+   <li>     
+    <p>Start the installation<br>
+     <b>Windows</b>: The 	XMergeInstall.jar files should be executable by 
+either 	double-clicking on it from Explorer or by typing <code>java -jar
+	XMergeInstall.jar</code> at the command line.<br>
+     <b>Unix</b>: Type 	<code>java -jar XMergeInstall.jar</code> (<b>Note</b>: 
+on Solaris 	2.6 and above, make the JAR file executable and type 	./XMergeInstall.jar 
+at the command line.)</p>
+  </li>
+ 
+</ol>
+  <a name="XmlFilterAdapter"> 
+<h3>About the XmlFilterAdapator</h3>
+ </a>  
+<p>OpenOffice filters make use of a generic filter specification called the 
+<code>XmlFilterAdaptor</code>. This implements many of the same interfaces 
+that most filters use, but it does not do any of the actual filtering itself. 
+The <code>XmlFilterAdaptor</code> can be used to instantiate a lower level 
+filter, and pass user defined data to it. Using this implementation, the user
+can specify a filtering module that can be instantiated by the <code>XmlFilterAdaptor</code>, 
+in order to carry out the filtering logic.</p>
+   
+<p>In order to maintain the pluginable nature of the XMerge framework, there 
+needs to be a bridge between the <code>XmlFilterAdaptor</code> and the XMerge 
+plugins, that will drive the plugins, without the requirement to change the 
+operation of the plugins themselves. This bridge is known as the XMergeBridge, 
+and is part of the XMerge project.</p>
+   
+<p>The XMergeInstaller installs the XmlFilterAdapater, the XMergeFilterBridge 
+and all available XMerge Plugins to your OpenOffice installation. Thereafter 
+the filters are accessible from the <b><font face="Arial, sans-serif">File|Open
+</font></b><font face="Thorndale">and <b><font
+ face="Arial, sans-serif">File|Save As </font></b>menu.<br>
+ </font></p>
+ 
+<h2><br>
+ </h2>
+ 
+<h2>ActiveSync Support</h2>
+ The ActiveSync XMerge Filter allows synchronisation of Writer and Calc documents 
+with a Microsoft Pocket PC device. &nbsp;This filter invokes XMerge from your
+OpenOffice/StarOffice installation.<br>
+ <br>
+ 
+<h3>Prerequisites</h3>
+ 
+<ul>
+   <li>XMerge<br>
+   </li>
+   <li>Java Runtime Environment 1.4</li>
+   <li>Windows 95 (with IE 4/5), Windows 98, Windows ME, Windows 2000, Windows 
+XP</li>
+   <li>ActiveSync 3.5</li>
+ 
+</ul>
+ The ActiveSync support requires an update to some of the XMerge code. &nbsp;If 
+you downloaded the Mobile Device Support Pack prior to the evening of 30th 
+July 2002, then you will need the update. &nbsp;An updated <code>xmerge.jar</code>
+file is included in the ActiveSync download. &nbsp;This file should be copied 
+in place of your current xmerge.jar.<br>
+ 
+<h3>Instructions</h3>
+ 
+<ol>
+   <li>Download the <a
+ href="http://xml.openoffice.org/xmerge/downloads/xmergesync.zip">xmergesync.zip</a> 
+file.<br>
+     <br>
+   </li>
+   <li>Disconnect your device from ActiveSync.<br>
+     <br>
+   </li>
+   <li>Unzip the two files in the archive. &nbsp;Copy the XMergeSync.dll
+file to a suitable location, e.g. <i>&lt;OO Installation Directory&gt;/program</i>.<br>
+     <br>
+   </li>
+   <li>At the command prompt, go to the directory in which you unpacked the 
+files and run the regutil.exe program giving it to the fully qualified path 
+of the XMergeSync.dll file.<br>
+     <br>
+     
+    <pre>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C:\Temp&gt; regutil "C:\Program Files\OpenOffice\program\XMergeSync.dll"</pre>
+     <br>
+   </li>
+   <li>Reconnect your device to ActiveSync.<br>
+     <br>
+   </li>
+   <li>You may need to configure ActiveSync to convert the files. &nbsp;<br>
+     <br>
+     
+    <ul>
+       <li>Open the ActiveSync program on the desktop machine.<br>
+         <br>
+       </li>
+       <li>Open the Options dialog either by clicking on the icon or by <i>Tools 
+-&gt; Options</i>.<br>
+         <br>
+       </li>
+       <li>If you have a partnership setup, you will need to select the <i>Rules</i> 
+tab on the dialog. &nbsp;Then click the <i>Conversion Settings </i>button. 
+&nbsp;If not, then the <i>Rules </i>tab will be presented by default.<br>
+         <br>
+       </li>
+       <li>Click on the <i>Desktop to Device</i> tab and scroll down the
+list. &nbsp;You should see entries for the OpenOffice/StarOffice Spreadsheet
+and Text Documents in the list of file types. <br>
+         <br>
+ &nbsp; &nbsp; Select on the Spreadsheet entry and verify that the mobile 
+device type is set to <i>Pocket Excel Workbook</i>.<br>
+         <br>
+ &nbsp; &nbsp; Select on the Text Document entry and verify that the mobile 
+device type is set to <i>Pocket Word Document - Pocket PC</i>.<br>
+         <br>
+       </li>
+       <li>If the types are not set to convert then double click on the type 
+to bring up the <i>Edit Conversion Settings</i> dialog. &nbsp;Select the correct
+type from the drop-down list.</li>
+     
+    </ul>
+     <br>
+     <br>
+   </li>
+   <li>If you wish to convert Pocket PC documents to OpenOffice/StarOffice 
+equivalents automatically, repeat the procedure in step 6 on the <i>Device 
+to Desktop</i> tab for the <i>Pocket Excel Workbook</i> and <i>Pocket Word 
+Document - Pocket PC</i> file types.</li>
+ 
+</ol>
+ <br>
+     <br>
+ 
+</body>
+</html>
diff --git a/content/xml/xmerge/index.html b/content/xml/xmerge/index.html
new file mode 100644
index 0000000..5af58d7
--- /dev/null
+++ b/content/xml/xmerge/index.html
@@ -0,0 +1,375 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>Document Editing on Small Devices - XMerge</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>Document Editing on Small Devices - XMerge</h1>
+<!-- no current top news!
+<h2><strong>Top News</strong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<a href="background.html" class="ProjectName">Background</a> | <a
+ href="index.html#overview" class="ProjectName">Overview</a> | <a
+ href="index.html#status" class="ProjectName">News and Updates</a> | <a
+ href="index.html#future" class="ProjectName">Proposed Future Projects</a>
+| <a href="index.html#plugin-ins" class="ProjectName">Plugins</a> | <a
+ href="index.html#doc" class="ProjectName">Documentation and Resources</a>
+| <a href="index.html#build" class="ProjectName">Building XMerge</a>
+<p align="justify"><strong>Project Owner:</strong> <a
+ href="mailto:Svante.Schubert [AT].sun.com">Svante Schubert</a><br>
+<small>(Please use the provided <a
+ href="http://xml.openoffice.org/servlets/ProjectMailingListList">mailing
+lists</a> for discussion of the XML based file format and related
+issues.)</small> </p>
+<a name="overview"></a>
+<br>
+<h2>Overview</h2>
+<p> </p>
+<p>The goals of the Document Editing on Small Devices project is to:<br>
+</p>
+<ul>
+  <li>Allow for the editing of rich format documents on small devices,
+using 3rd party applications native to the device to do the editing.</li>
+  <li>Support the most widely used small devices, namely:</li>
+  <ul>
+    <li>Palm</li>
+    <li>PocketPC</li>
+  </ul>
+  <li>Provide the ability to merge edits made in the small device's
+lossy format back into the original richer format document maintaining
+it's original style.</li>
+  <li>Take advantage of the open and well defined OpenOffice.org XML
+document format.</li>
+  <li>Provide a framework with the ability to have plugin-able Convert,
+Diff and Merge implementations. It should be possible determine a
+converter's capabilities at run-time.</li>
+</ul>
+<p> </p>
+<p> The XMerge SDK provides a Java-based framework for converting
+documents between different formats using conversion plugins to read
+and write each format. More about what plugins are available can be
+found in the <a href="#plug-ins">plugin section</a> below.</p>
+<p>In addition to format conversion, the XMerge SDK provides a
+framework for merging changes in one document format (usually a simpler
+or lower quality format) into an original document (typically in a
+richer format). The benefit of merging &nbsp;is that richer styles or
+content in the original document are retained, while the edits made to
+the simpler format can be applied or merged into the original document.<br>
+</p>
+<p> To meet these goals there are two significant interfaces in XMerge:</p>
+<ul>
+  <li>the Conversion API's, used by applications to use a supported
+format conversion</li>
+  <li>the Plugin SPI, which is used by developers who want to add
+conversion support for a new document format.</li>
+</ul>
+All plugins are designed to support the OpenOffice.org
+XML file format on one side and the device format on the other, the
+framework is able to support "chaining" of conversions, also known as
+an "Any-to-Any" conversion, eg. convert from a Palm document to a
+PocketPC document through the intermediate OpenOffice.org XML file
+format.<br>
+<p> </p>
+<a name="status"></a>
+<h2>News and updates</h2>
+<ul>
+  <li><b>Mobile Device Support in OpenOffice</b><br>
+The Mobile Device Support Pack for OpenOffice 1.0 is now available.
+Grab it <a href="downloads/index.html">here</a><br>
+This mini-install integrates XMerge plugins into OpenOffice using the
+upcoming
+XmlFilterAdapter. Try it out and let us know how it goes. </li>
+  <li><b>ActiveSync and OpenOffice</b><br>
+ActiveSync Support has been added. &nbsp;You can now sync OpenOffice
+Writer and Calc documents to and from a Pocket PC device. ActiveSync
+will
+automatically invoke XMerge plugins to perform the appropriate
+conversions.
+&nbsp;You can get the filter from the <a href="downloads/index.html">downloads
+section</a>. </li>
+  <li><b>Nokia Communication Word Processor Format Support</b><br>
+Nick Richards has taken on the writing of a plugin for the PsiWord
+format.
+PsiWord is the format used by the word processor on the <a
+ href="http://www.nokia.com/phones/9210/">Nokia 9210 Communicator</a>,
+the Symbian based PDA/phone and other PDA's running the EPOC OS. <br>
+Nick is looking for others to help in writing the plugin, so if you can
+spare the time he can be reached at <a
+ href="mailto:nedrichards@openoffice.org">nedrichards@openoffice.org</a>
+  </li>
+  <li><b>Writer2LaTeX XMerge Plugin</b><br>
+    <a>Henrik Just has now implemented his </a><a
+ href="http://www.hj-gym.dk/%7Ehj/writer2latex/">Writer2LaTeX </a>converter
+as an XMerge plugin. This means that now his converter can now be used
+as an OpenOffice.org export filter as well as being able to perform
+standalone command line conversions. For more information and the
+latest versions, visit <a
+ href="http://www.hj-gym.dk/%7Ehj/writer2latex/">Henrik's web-page.</a></li>
+</ul>
+<a name="future"></a><br>
+<h2>Proposed future projects</h2>
+<ul>
+  <li>Synchronisation support for devices, could be any of the
+following:</li>
+  <ul>
+    <li>Application on small device that pulls down a document in
+desired format and synchronises back.</li>
+    <li>Desktop synchronisation integration (eg. HotSync).<em></em></li>
+  </ul>
+  <li>New plugins for other small document formats.</li>
+  <li>Enhancements to existing plugins</li>
+  <li>Alternate implementations to the diff and merge engines</li>
+  <li>Support for OpenOffice.org presentations.</li>
+  <li>Provision of a parser independent "XMLWriter". This would in
+theory allow XMerge to work with any XML parser with DOM level
+2 support.</li>
+</ul>
+<a name="plug-ins"></a>
+<h2>Plugins</h2>
+<table cellpadding="4" cellspacing="1" bgcolor="#f0f0f0" width="100%">
+  <tbody>
+    <tr align="center">
+      <th bgcolor="#99ccff" width="20%"><font color="#00315a"
+ face="Arial, Helvetica" size="2"><b> Platform</b></font></th>
+      <th bgcolor="#99ccff" width="20%"><font color="#00315a"
+ face="Arial, Helvetica" size="2"><b> Plug-in Name</b></font></th>
+      <th bgcolor="#99ccff"><font color="#00315a"
+ face="Arial, Helvetica" size="2"><b> Description</b></font></th>
+      <td valign="top" bgcolor="#99ccff">Current Status<br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top">Any<br>
+      </td>
+      <td valign="top" width="20%">XSLT<br>
+      <code></code></td>
+      <td valign="top">The XSLT plug-in, makes use of the <a
+ href="http://xml.apache.org/xalan-j/index.html">Xalan XSLT</a>
+processor, in order to translate an xml document to and from a
+specified xml/xhtml format.<br>
+      </td>
+      <td valign="top">Source Available<br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top">Palm<br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top" width="20%"><a
+ href="plugins/aportisdoc.html">AportisDoc</a><br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top">Plugin for editing StarWriter
+documents in the AportisDoc format originally developed by Aportis
+Technology Corporation.&nbsp; However Aportis as of 31st Dec 2002 were
+acquired by <a href="http://www.ultrasoft.com/BrainForest/">UltraSoft</a>.
+There are still<a
+ href="http://www.google.com/search?hl=en&amp;lr=&amp;ie=UTF-8&amp;oe=UTF-8&amp;q=aportisdoc+format+palm&amp;spell=1">
+many palm applications</a> that use the Aportisdoc format. This plugin
+supports merging of textual changes. </td>
+      <td valign="top" bgcolor="#f0f0f0">Source Available<br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top">Palm<br>
+      </td>
+      <td valign="top" bgcolor="#f0f0f0"><a href="plugins/minicalc.html">MiniCalc</a><br>
+      </td>
+      <td valign="top" bgcolor="#f0f0f0">Sample implementation for
+editing StarCalc spreadsheets with <a
+ href="http://www.solutionsinhand.com">MiniCalc</a> on the Palm. This
+plugin
+supports merging of textual changes.<br>
+      </td>
+      <td valign="top" bgcolor="#f0f0f0">Source Available<br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top">PocketPC<br>
+      </td>
+      <td valign="top"><a href="plugins/pocketword.html">Pocket
+Word</a><br>
+      </td>
+      <td valign="top">Support of editing text documents through
+PocketWord<br>
+      </td>
+      <td valign="top">Source Available</td>
+    </tr>
+    <tr>
+      <td valign="top">PocketPC<br>
+      </td>
+      <td valign="top"><a href="plugins/pocketexcel.html">Pocket
+Excel</a><br>
+      </td>
+      <td valign="top">Support for editing spreadsheets in PocketExcel<br>
+      </td>
+      <td valign="top">Source Available<br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<i>*Follow links for more information and screen-shots.</i> <a
+ name="doc"></a>
+<h2>Documentation and Resources</h2>
+<table cellpadding="4" cellspacing="1" bgcolor="#ffffff" width="100%">
+  <tbody>
+    <tr>
+      <td colspan="3" bgcolor="#00315a" align="center"><font
+ color="#ffffff" face="arial, helvetica" size="2"><b> Documentation for
+the XMerge SDK</b></font></td>
+    </tr>
+    <tr>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b> Document</b></font></th>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b> Summary</b></font></th>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b> Format and Size</b></font></th>
+    </tr>
+    <tr>
+      <td bgcolor="#f0f0f0" valign="top"><a href="docs/XMerge_sdk.pdf">XMerge
+Document Conversion SDK</a> <br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top">A developer's guide for the
+XMerge SDK. Describes how to use the client API, implement plugins,
+testing and installing plug-ins.<br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top"> PDF, 180K<br>
+      </td>
+    </tr>
+    <tr>
+      <td bgcolor="#f0f0f0" valign="top"><a href="docs/XSLTPlugin.pdf">XSLT
+Plugin Implementation</a><br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top">Describes the XSLT converter
+plugin, how to use it and also how to implement further XSLT plugins.<br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top"> PDF, 11K<br>
+      </td>
+    </tr>
+    <tr>
+      <td bgcolor="#f0f0f0" valign="top"><a
+ href="docs/xmerge_javadoc.zip"> XMerge JavaDocs</a> <br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top"> Generated from JavaDoc
+comments in the sources.<br>
+      </td>
+      <td bgcolor="#f0f0f0" valign="top"> ZIP, &nbsp;364K<br>
+      </td>
+    </tr>
+<!--
+<tr>
+<td bgcolor="#f0f0f0" valign="top"><a href="...">...</a></td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+</tr>
+-->
+  </tbody>
+</table>
+<!--<p><br>
+       </p>
+
+<p><br>
+       </p>
+         <a name="build"></a>-->
+<a name="build"></a><br>
+<h2>Building XMerge</h2>
+<p> The following document describes the process for building the
+OpenOffice.org XMerge project, either standalone or as part of the
+OpenOffice.org build environment. </p>
+<h3>Requirements</h3>
+The following tools are necessary in order to build the XMerge project.<br>
+<ul>
+  <li><a href="http://java.sun.com/j2se/1.3/" target="_blank"> Java 1.3
+or 1.4</a> </li>
+  <li><a href="http://java.sun.com/xml/archive.html" target="_blank">JAXP
+1.0</a> or <a href="http://xml.apache.org/xerces-j/index.html"
+ target="_blank"> Xerces-J</a> </li>
+  <li><a href="http://jakarta.apache.org/ant/index.html" target="_blank">Ant</a>
+  </li>
+  <li><a href="http://xml.apache.org/xalan-j/index.html" target="_blank">Xalan-J
+2.2</a> </li>
+</ul>
+<p><b>Note:</b> Java 1.4 includes the Crimson XML parser and Xalan. If
+using
+Java 1.4 the only requirement is Ant.</p>
+<p><b>N.B.</b> Xalan 2.3 splits the XSLT classes between two JAR files.
+The build environment expects the XSLT classes to be contained in <code>xalan.jar</code>
+only.</p>
+<h3>Obtaining the source</h3>
+The source for XMerge is maintained under CVS control as part of the
+XML project. &nbsp;<br>
+<br>
+See the XML Project's <a
+ href="http://xml.openoffice.org/servlets/ProjectSource" target="_blank">
+Source page</a> for information on obtaining and contributing to source
+code.<br>
+<br>
+If using CVS, setup your CVS access according to the
+Source page and checkout the <tt>xmerge</tt> module.<br>
+<pre>  <tt>% cvs -d:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs co oo/xml/xmerge</tt></pre>
+<br>
+The source can also be downloaded as a ZIP file <a
+ href="xmerge_src.zip"> here.</a><br>
+<h3>Building in a Standalone Environment<br>
+</h3>
+<p> To build XMerge in a standalone environment, copy all of the jar
+files mentioned above and the Xalan-J archive into a directory.</p>
+<p>You will need to include the Ant binary directory in your PATH.
+&nbsp;Ant requires that the JAVA_HOME variable also be set.<br>
+</p>
+<p> Wrapper scripts have been provided to execute the build. &nbsp; On
+a UNIX based system use:</p>
+<pre>&nbsp;&nbsp;&nbsp; <tt>% build_xmerge -jars &lt;jar_location&gt; </tt><tt>[-debug | optimize]</tt></pre>
+<p>and on Windows use :<br>
+</p>
+<pre>    <tt>C:\XMerge&gt; build_xmerge.bat -jars &lt;jar_location&gt;</tt><tt> [-debug | -optimize]</tt></pre>
+<p>where &lt;jar_location&gt; is the directory containing the required
+JAR files.</p>
+<p><b>Note:</b> If using Java 1.4 the jar file location can be given as
+any
+directory as Java 1.4 includes the XML and XSLT class files.</p>
+<p>The scripts also support building a debug version and an optimized
+version. &nbsp;Simply specify <tt>-debug</tt> or <tt>-optimize</tt>
+as options. &nbsp; These options are mutually exclusive. &nbsp;If both
+are set, the first one encountered will be used for build purposes.</p>
+<br>
+<h3>Building as part of OpenOffice.org</h3>
+<p> Setup your OpenOffice.org build environment as detailed in the <a
+ href="http://www.openoffice.org/documentation.html#guides">OpenOffice.org
+build documents</a>.<br>
+</p>
+<p> To build XMerge, you will also need to copy the Ant and Xalan-J Jar
+files into your solver's bin directory, e.g.
+${SOLARVER}/642/{platform}/bin.<br>
+</p>
+<p> Once these files are present simply execute the build:<br>
+</p>
+<pre>    <tt>% build</tt></pre>
+<p>The build will execute and JAR files and documentation will be
+contained in a platform-named directory created in the <i>xmerge</i>
+directory.<br>
+</p>
+<h3>Running the Test Driver command-line utility<br>
+</h3>
+<p>Once the sources have been built, you can test the plugins using the
+test Driver command-line utility.&nbsp;<br>
+<br>
+To this you will need to know the location of all the JAR files that
+were built, this will vary depending on the mechanism used to build.
+You
+will also need the location of the JAR files that you downloaded as
+stated
+in the Requirements section above. <br>
+</p>
+<p>Once you have all of this, you execute the &nbsp;test Driver as
+follows:<br>
+</p>
+<pre>    % java -cp &lt;jar_location&gt; org.openoffice.xmerge.test.Driver -from &lt;mime-type&gt; -to &lt;mime-type&gt; [-merge &lt;original file&gt;] &lt;file&gt;... <br></pre>
+<p>The from and to mime-types to use will depend on the type of
+documents being converted. The "-merge" option is only usable when
+converting from the device format to the OpenOffice.org document.<br>
+</p>
+<br>
+</body>
+</html>
diff --git a/content/xml/xmerge/plugins/aportisdoc.html b/content/xml/xmerge/plugins/aportisdoc.html
new file mode 100755
index 0000000..51ef0a6
--- /dev/null
+++ b/content/xml/xmerge/plugins/aportisdoc.html
@@ -0,0 +1,184 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+    
+  <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+  <title>xml.openoffice.org</title>
+</head>
+    <body>
+  
+<h1>XMerge AportisDoc Plugin</h1>
+  <br>
+  
+<h2><font color="#cc0000">Overview</font></h2>
+  <br>
+            The AportisDoc plugin converts text data between OpenOffice Writer
+    format   and AportisDoc's binary Palm DataBase file format. <br>
+<br>
+The AportisDoc format is a plain-text format and does not support any formatting
+options.<br>
+  <br>
+<table cellpadding="4" cellspacing="1" bgcolor="#f0f0f0" width="50%">
+  <tbody>
+    <tr align="center">
+      <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Category</b></font></th>
+        <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Feature</b></font></th>
+        <th bgcolor="#00315a" width="20%"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Supported</b></font></th>
+      </tr>
+      <tr>
+        <td valign="top" bgcolor="#99ccff" align="center">&nbsp;<font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Document Elements</b></font><br>
+       </td>
+        <td valign="top" bgcolor="#99ccff"><br>
+        </td>
+        <td width="20%" valign="top" bgcolor="#99ccff"><br>
+        </td>
+      </tr>
+      <tr>
+        <td valign="top"><br>
+        </td>
+        <td valign="top"><font face="Arial, Helvetica" size="2">Paragraphs<br>
+        </font>      </td>
+        <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+        </font>      </td>
+      </tr>
+      <tr>
+        <td valign="top"><br>
+        </td>
+        <td valign="top"><font face="Arial, Helvetica" size="2">Styles<br>
+        </font>      </td>
+        <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+        </font>      </td>
+      </tr>
+      <tr>
+        <td valign="top"><br>
+        </td>
+        <td valign="top"><font face="Arial, Helvetica" size="2">Tables<br>
+        </font>      </td>
+        <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+        </font>      </td>
+      </tr>
+      <tr>
+        <td valign="top"><br>
+        </td>
+        <td valign="top"><font face="Arial, Helvetica" size="2">Lists<br>
+        </font>      </td>
+        <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+        </font>      </td>
+      </tr>
+      <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Images</font><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">no</font><br>
+       </td>
+     </tr>
+                                       
+  </tbody>
+</table>
+<br>
+  
+<h2><font color="#cc0000">Using the AportisDoc plugin</font></h2>
+  <br>
+          The AportisDoc plugin is invoked in the same manner as all other
+XMerge     plugins. &nbsp; Once the framework has been made aware of the
+plugin,   the    only thing needed to use it is to specify its MIME type
+as a source   or destination   type for conversion. &nbsp;The MIME type is
+specified in   the <code>converter.xml</code>     file included in the <code>aportisdoc.jar</code> 
+     file. &nbsp;Currently,  this is set to <code>application/x-aportisdoc</code> 
+    .<br>
+  <br>
+          For example, to use the AportisDoc plugin in conjunction with the 
+  test   driver supplied with the XMerge framework:<br>
+  <br>
+  
+<blockquote>    
+  <pre>% java org.openoffice.xmerge.test.Driver -from staroffice/sxw -to application/x-aportisdoc Test.sxw<br><br>% java.org.openoffice.xmerge.test.Driver -from application/x-aportisdoc -to staroffice/sxw Test.pdb<br></pre>
+    </blockquote>
+    <br>
+    
+<h2><font color="#cc0000">Features</font></h2>
+         The plugin currently supports conversion to plain-text only, as
+this  is what AportisDoc supports.<br>
+    <br>
+    <br>
+    <img src="images/origdoc.jpg" alt="StarWriter Document image"
+ width="817" height="592" border="1">
+    <br>
+  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; <i>Original 
+ StarWriter Document </i><br>
+    <br>
+  Converts to<br>
+    <br>
+  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <img
+ src="images/pdborig.jpg" alt="pdborig" width="269" height="409"
+ border="1">
+   &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp;  &nbsp;&nbsp; <img src="images/pdbmod.jpg" alt="pdbmod"
+ width="269" height="409" border="1">
+    <br>
+  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <i>&nbsp;&nbsp;&nbsp; 
+ Converted Document&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; Converted 
+ Document with Edits</i><br>
+    <br>
+    
+<h2><font color="#cc0000">Merging&nbsp;</font></h2>
+  &nbsp; &nbsp;When changes have been made on the small device, the user
+can  either choose to convert the modified AportisDoc Palm Database to a
+reduced  content and style StarWriter file, or the user can choose to merge
+the content  changes made with the original StarWriter Document. In this
+way, new edits  can be retained whilst also retaining document styles and
+formatting . To  merge the modified AportisDoc DataBase, the XMerge test
+driver program may  be used again.<br>
+    <br>
+  &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;    
+<div align="center">    
+<pre>% java.org.openoffice.xmerge.test.Driver -from application/x-aportisdoc -to staroffice/sxw -merge Test.sxw Test.pdb</pre>
+    </div>
+    <br>
+  &nbsp;&nbsp;&nbsp; <br>
+  &nbsp;<br>
+    <img src="images/moddoc.jpg" alt="StarWriter Document modified"
+ width="822" height="565" border="1">
+    <br>
+    
+<div align="left">    
+<blockquote>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 
+ &nbsp;&nbsp;&nbsp;<i> &nbsp; Original StarWriter Document with Merged &nbsp;Edits</i><br>
+      </blockquote>
+      </div>
+      
+<h2><font color="#cc0000">Building the plugin</font></h2>
+        The AportisDoc plugin is built as part of the XMerge framework. &nbsp;Its 
+    classes are stored in <code>aportisdoc.jar</code>. &nbsp;See <a
+ href="http://xml.openoffice.org/xmerge/index.html#build">  Building XMerge</a> 
+  for more instructions.<br>
+      <br>
+      <br>
+      <br>
+      <br>
+      <br>
+      <br>
+</body>
+</html>
diff --git a/content/xml/xmerge/plugins/minicalc.html b/content/xml/xmerge/plugins/minicalc.html
new file mode 100755
index 0000000..9167180
--- /dev/null
+++ b/content/xml/xmerge/plugins/minicalc.html
@@ -0,0 +1,213 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+         
+  <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+  <title>xml.openoffice.org</title>
+  
+</head>
+<body>
+ 
+<h1>XMerge MiniCalc Plugin</h1>
+ <br>
+ 
+<h2><font color="#cc0000">Overview</font></h2>
+ <br>
+           The MiniCalc plugin converts text data between OpenOffice Calc
+  format   and MiniCalc's binary Palm DataBase file format. <br>
+ <br>
+<table cellpadding="4" cellspacing="1" bgcolor="#f0f0f0" width="50%">
+  <tbody>
+    <tr align="center">
+      <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Category</b></font></th>
+      <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Feature</b></font></th>
+      <th bgcolor="#00315a" width="20%"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Supported</b></font></th>
+    </tr>
+    <tr>
+      <td valign="top" bgcolor="#99ccff" align="center"><font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Formula</b></font> 
+     </td>
+      <td valign="top" bgcolor="#99ccff"><br>
+      </td>
+      <td width="20%" valign="top" bgcolor="#99ccff"><br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Cell References<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Add/Sub/Multiply/Divide<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Integers +
+Floating Points<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Functions<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top" bgcolor="#99ccff" align="center"><font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Formatting</b></font>
+     </td>
+      <td valign="top" bgcolor="#99ccff"><br>
+      </td>
+      <td width="20%" valign="top" bgcolor="#99ccff"><br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Font<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Bold, Italic,
+Underline</font></td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Colour<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+      </font>      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Alignment<br>
+      </font>      </td>
+      <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+      </font>      </td>
+    </tr>
+                                                
+  </tbody>
+</table>
+ 
+<h2><font color="#cc0000">Using the MiniCalc plugin</font></h2>
+ <br>
+         The MiniCalc plugin is invoked in the same manner as all other XMerge
+   plugins. &nbsp; Once the framework has been made aware of the plugin, the
+   only thing needed to use it is to specify its MIME type as a source  or
+destination   type for conversion. &nbsp;The MIME type is specified in  the
+<code>converter.xml</code>     file included in the minicalc<code>.jar</code>
+     file. &nbsp;Currently,  this is set to <code>application/x-minicalc</code>
+    .<br>
+ <br>
+         For example, to use the MiniCalc plugin in conjunction with the
+test   driver supplied with the XMerge framework:<br>
+ <br>
+ 
+<blockquote>         
+  <pre>% java org.openoffice.xmerge.test.Driver -from staroffice/sxc -to application/x-minicalc Test.sxc<br><br>% java.org.openoffice.xmerge.test.Driver -from application/x-minicalc -to staroffice/sxc Test.pdb<br></pre>
+   </blockquote>
+   <br>
+      
+<h2><font color="#cc0000">Features</font></h2>
+This converter supports basic spreadsheet functionality. It does not support
+embedded graphics or styles, as these are not supported by MiniCalc.<br>
+   <br>
+   <br>
+   <img src="images/spreadsheetorig.jpg" alt="StarCalc SpreadSheet Orig"
+ width="925" height="562" border="1">   <br>
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; <i>Original
+StarCalc Document </i><br>
+   <br>
+ Converts to<br>
+   <br>
+ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<img
+ src="images/mpdborig.jpg" alt="PDBOrig" width="271" height="410"
+ border="1">  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp; &nbsp;  &nbsp;&nbsp; <img src="images/mpdbmod.jpg" alt="PDB mod"
+ width="271" height="410" border="1">   <br>
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <i>&nbsp;&nbsp;&nbsp;
+Converted Document&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; Converted
+Document with Edits</i><br>
+   <br>
+      
+<h2><font color="#cc0000">Merging&nbsp;</font></h2>
+ &nbsp; &nbsp;When changes have been made on the small device, the user can
+either choose to convert the modified MiniCalc Palm Database to a reduced
+content and style StarCalc file, or the user can choose to merge the content
+changes made with the original StarCalc Document. In this way, new edits
+can be retained whilst also retaining document styles and formatting . To
+merge the modified MiniCalc DataBase, the XMerge test driver program may be
+used again.<br>
+   <br>
+ &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;       
+<div align="center">      
+<pre>% java.org.openoffice.xmerge.test.Driver -from application/x-minicalc -to staroffice/sxc -merge Test.sxc Test.pdb</pre>
+   </div>
+   <br>
+ &nbsp;&nbsp;&nbsp; <br>
+ &nbsp;<br>
+   <img src="images/spreadsheetmod.jpg" alt="StarCalc SpreadSheet Mod"
+ width="923" height="566" border="1">   <br>
+      
+<div align="left">      
+<blockquote>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp;<i> &nbsp; Original StarCalc Document with Merged &nbsp;Edits</i><br>
+     </blockquote>
+     </div>
+          
+<h2><font color="#cc0000">Building the plugin</font></h2>
+       The MiniCalc plugin is not currently built as part of the XMerge framework.
+<br>
+     <br>
+     <br>
+     <br>
+     <br>
+     <br>
+          <br>
+</body>
+</html>
diff --git a/content/xml/xmerge/plugins/pexcel_formulas.html b/content/xml/xmerge/plugins/pexcel_formulas.html
new file mode 100644
index 0000000..1675ae1
--- /dev/null
+++ b/content/xml/xmerge/plugins/pexcel_formulas.html
@@ -0,0 +1,330 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+	      
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=iso-8859-1">
+  <title>Supporting Formula in Pocket Excel plugin for xMerge</title>
+      	 	      
+  <meta name="GENERATOR" content="StarOffice 6.0  (Solaris Sparc)">
+	      
+  <meta name="CREATED" content="20020912;17575800">
+	      
+  <meta name="CHANGEDBY" content="Martin Maher">
+	      
+  <meta name="CHANGED" content="20020917;12581300">
+	      
+  <style>
+	<!--
+		@page { size: 21.59cm 27.94cm; margin-left: 3.18cm; margin-right: 3.18cm; margin-top: 2.54cm; margin-bottom: 2.54cm }
+	-->
+	</style>
+</head>
+<body lang="en-US">
+<p style="margin-bottom: 0cm; text-decoration: none;"><font size="4"
+ style="font-size: 16pt;"><b>Supporting Formula in Pocket Excel plugin for
+xMerge</b></font></p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4"><b>Overview</b></font></p>
+<p style="margin-bottom: 0cm;">The difficulty in supporting formula conversion
+from xml in StarOffice to binary equivalents in Excel comes from the fact
+that there are very basic differences between the two formats. Pocket Excel
+uses obviously binary records to store formula, StarOffice uses a String.
+In the case of Pocket Excel, postfix (Reverse Polish) notation is used and
+in StarOffice the formula is stored infix notation. This means that we must
+identify the operators and operands (as well as functions) in the formula
+in order to convert from one notation to another. This process we call parsing
+and in many ways is similar to what a compiler does when interpreting source
+code. The next step is to convert to and from postfix notation. This can
+be done in three  ways using either stacks, binary trees or combinations
+of both. Once this has been done all that remains is token substitution where
+a String is converted to or from a series of bytes.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4"><b>The Issues</b></font></p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><b>Parsing</b></p>
+<p style="margin-bottom: 0cm;">Parsing is the first operation to be performed
+on any formula encountered in either Pocket Excel or StarOffice. Parsing
+is the single most important aspect of formula conversion because all tokens
+must be correctly identified in order for the following two steps to be successful.
+The parser must be able to correctly identify operators, operands. Operands
+in there simplest terms consist of either a numeric value or a cell reference.
+Operators include binary operators (+,-,*,/) or unary operators(-). These
+are the simplest as</p>
+<p style="margin-bottom: 0cm;">the operands are easily identified. A more
+complicated type of operator however is the function. These are more difficult
+as they can contain any number of parameters. The parameters can be of almost
+any type, numeric, cell references, cell ranges, or other functions. Consider
+the following formula :-</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=SUM(AA11:AA22, 1000, C3+4, AVERAGE(D44:D55))</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">This is a valid formula and the parser needs
+to be able to identify each token</p>
+<p style="margin-bottom: 0cm;">in order for the RPN conversion to be correctly
+completed.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><i>Pocket Excel Formula Parsing</i></p>
+<p style="margin-bottom: 0cm;">In the case of pocket excel the formula must
+be parsed from a series of bytes in postfix (Reverse Polish) notation to
+a string in infix notation. This is not really a parser as we simply convert
+the bytes to their equivalent string representations. Tokens in this way
+can easily be identified and no lexical scanning is required. Postfix notation
+does not have to concern itself with operator precedence or parenthesis hence
+this must be taken care of during paring. For example consider the following
+postfix statement </p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=AB+C*</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">This would be translated to infix notation
+</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=A+B*C</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">However because of operator precedence it
+is required the we used parenthesis</p>
+<p style="margin-bottom: 0cm;">to ensure that it is calculated in the right
+order.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=(A+B)*C</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><i>StarCalc Formula Parsing</i></p>
+<p style="margin-bottom: 0cm;">In the case of StarOffice formula Parsing
+the formula must be parsed from a String to a series of bytes. Again operators
+precedence is important along with the use of parenthesis. Also the parser
+must have the ability to parse nested functions and complex arguments (eg.
+=A1*3-(SUM(C1:A1, D1+40, AVERAGE(D2:D5))) ).</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><b>RPN Conversion</b></p>
+<p style="margin-bottom: 0cm;">Consider the formula </p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">SUM(A1, A2, 3+4*SUM(B3:B9),D1)</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">this notation is called infix and is the one
+that is used in StarCalc. However in Pocket Excel this formula would appear
+in postfix notation (also called Reverse Polish)</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">A1 A2 3 4  B3:B9 SUM * + D1 SUM</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">There are two ways in which postfix can be
+converted from/to infix. One is to use a Binary tree and read the tree from
+right to left to get postfix and from left to right to get infix. The problem
+with this method is it doesn't take into account functions which can have
+more than two parameters. </p>
+<p style="margin-bottom: 0cm;">The other way of implementing conversion is
+to use Stacks. This solves the problem of function parameters but the code
+is more complex. For example in order to take into account that natural operator
+precedence might be overruled by parenthesis the Stack method will need to
+take into account parenthesis (possibly nested). </p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><b>Token substitution</b></p>
+<p style="margin-bottom: 0cm;">Token substitution must take account of the
+different ways in which data is stored in each format. For example in StarOffice
+cell references are stored as Strings in the same way as they appear in the
+spreadsheet (e.g. A12, C23, B4:B12). However in Pocket Excel Cell references
+are stored as 0 based indexes so A1 is represented in binary as</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">44&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; 00&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; C0&nbsp;&nbsp;
+&nbsp; &nbsp;&nbsp; 00</p>
+<p style="margin-bottom: 0cm;">Cell Ref.&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; Row	&nbsp;&nbsp;&nbsp;
+Column (bits 0-7)</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">This is just a substitution for a simple cell
+reference. There are other types of cell references, cell ranges and functions.
+This needs to well designed code as it will need to be expanded as additional
+features are supported. Also due to the large amount of objects it is not
+practical to have an object for each operator and operand. Obviously token
+substitution needs to be supported in both directions.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4"><b>Proposed Solution</b></font></p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><b>Parsing</b></p>
+<p style="margin-bottom: 0cm;">We have written a top-down parser that will
+be able to handle infix to postfix parsing with one addition. This  addition
+is handling parameters within functions.  This is not a trivial addition
+as there can be any number of parameters and the parameters themselves can
+be any combination of cell references, cell ranges, functions or other formula.
+The BNF notation for this parser is</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><i>&lt;expression&gt; ::= &lt;unary op&gt;
+&lt;term&gt; [&lt;addop&gt; &lt;term&gt;]</i></p>
+<p style="margin-bottom: 0cm;"><i>&lt;term&gt;       ::= &lt;factor&gt; [&lt;mulop&gt;
+factor]</i></p>
+<p style="margin-bottom: 0cm;"><i>&lt;factor&gt;     ::= &lt;integer&gt; |
+&lt;variable&gt; | &lt;expression&gt; | &lt;function&gt;</i></p>
+<p style="margin-bottom: 0cm;"><i>&lt;function&gt; ::= &lt;ident&gt; [ &lt;expression&gt;
+]</i></p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">Parsing from postfix to infix is made simpler
+by the fact that we will be reading in a series of bytes which will give
+the  exact content of each token. In this case what is required is a converter
+as opposed to a parser. This will generate a series of objects (see token
+substitution) which are passed to the RPN converter.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><b>RPN Conversion</b></p>
+<p style="margin-bottom: 0cm;">In order to overcome the problem with Binary
+trees and function parameters we have decided to write a Stack implementation.
+This means the code to implement this is more complicated but is flexible
+enough to handle most formula.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><i>From Infix to Postfix</i></p>
+<p style="margin-bottom: 0cm;">In this case we push operators on to a Stack.
+When we come across an operator we check for precedence with the next operand
+and if it is greater we also push this onto the stack.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=A1+SUM(3*B1+4, C1)</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<ul>
+	<li>         
+    <p style="margin-bottom: 0cm;">First token is A1 which we put 	into our
+output string</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">the next token is + which we push 	on
+the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">The next token is the function SUM 	with
+two arguments which again is an operator which we put on the 	stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">Next is 3 which as an operand we 	put
+in the output string  	</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">Next is * which goes on the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">B1 is an operand we put in the 	output
+string  	</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">+ but this has less precedence so 	we
+pop * off the stack  into the output string and + goes on the 	stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">4 operand in the output strings</p>
+  </li>
+</ul>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><i>From Postfix to Infix</i></p>
+<p style="margin-bottom: 0cm;">From postfix to infix we again use stack.
+In this case however we use it as a temporary storage space for operands.
+We push operands onto the stack and when we come across a operator we pop
+the operands off the stack and use them as operands for that operator. If
+the completed statement is a parameter to a function it needs to be pushed
+back onto the stack and the remainder of the function parsed.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=A1 A2 3 4 B3:B9 SUM * + D1 SUM 3 +</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<ul>
+	<li>         
+    <p style="margin-bottom: 0cm;">First token A1 is an operand it 	goes
+on the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">next is A2 again on the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">next is 3 again on the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">next is 4 again on the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">next is B3:B9 again on the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">next is SUM with 1 argument so pop 	one
+operand off the stack B3:B9 and insert it into the SUM function</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">The next is a * operator so we 	prepend
+that to the SUM statement and pop another operand 4 off the 	stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">The next is a + operator so we 	prepend
+that to the SUM statement and pop another operand 3 off the 	stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">The next is another operand so 	know that
+parameter is finished so we push it onto the stack and 	then push D1 onto
+the stack as well.</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">The next is SUM with 3 arguments 	so we
+pop 3 arguments of the stack</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">The next is an operand so we know 	to
+push the statement completed in the last step needs to be pushed 	onto the
+stack and then we push on  3 as well</p>
+	</li>
+  <li>         
+    <p style="margin-bottom: 0cm;">the last token is a plus so we end 	up
+with</p>
+  </li>
+</ul>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;">=SUM(A1, A2, 3+4*SUM(BS:B9), D1)+3</p>
+<p style="margin-bottom: 0cm;">  </p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><b>Token Substitution</b></p>
+<p style="margin-bottom: 0cm;">The best solution is to use generic objects
+for tokens. We will have two basic object classes. One called OperatorToken
+and one called OperandToken. Each of these will have a value variable as
+well as type. The type will describe forms of an operator or operand e.g.
++ , A1, SUM(). The parser will parse a string or a series of bytes into a
+Vector of these objects which will be used by the RPN converter to convert
+to or from postfix notation. These classes will be derived from a Token interface
+to facilitate this. </p>
+<p style="margin-bottom: 0cm;">We will also have to describe a Constants
+interface to describe the various hex codes that exist for each object. One
+area we have not decided what to do yet is converting to or from bytes. Obviously
+we need a separate one for each operator but it is not practical to have
+one object  for each operator.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<br>
+</body>
+</html>
diff --git a/content/xml/xmerge/plugins/pocketexcel.html b/content/xml/xmerge/plugins/pocketexcel.html
new file mode 100644
index 0000000..5a57acc
--- /dev/null
+++ b/content/xml/xmerge/plugins/pocketexcel.html
@@ -0,0 +1,204 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>XMerge Pocket Word Plugin</title>
+  <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h1>XMerge Pocket Excel Plugin</h1>
+<br>
+<h2>Overview</h2>
+The Pocket Excel plugin converts between OpenOffice StarCalc XML format
+and Pocket Excel's binary file format.&nbsp; It currently supports
+reading and writing of files in Pocket Excel format 2.0. A <a
+ href="http://xml.openoffice.org/xmerge/xmerge_src.zip">zipfile</a>
+containing the complete source is available. If you just want to browse
+the source online it is available <a
+ href="http://xml.openoffice.org/source/browse/xml/xmerge/java/org/openoffice/xmerge/converter/xml/sxc/pexcel/">
+here.</a><br>
+<br>
+<h2>Using the Pocket Excel plugin</h2>
+<br>
+The Pocket Excel plugin is invoked in the same manner as all other
+XMerge plugins. &nbsp; Once the framework has been made aware of the 
+plugin,  the    only thing needed to use it is to specify its MIME type
+as a source  or destination   type for conversion. &nbsp;The MIME type
+is specified  in  the <code>converter.xml</code> file included in the<code>
+pexcel.jar</code> file. &nbsp;Currently,  this is set to <code>application/x-pocket-excel</code>
+.<br>
+<br>
+For example, to use the Pocket Excel plugin in conjunction with  the
+test driver supplied with the XMerge framework:<br>
+<br>
+<blockquote>
+  <pre>% java org.openoffice.xmerge.test.Driver -from staroffice/sxc -to x-application/x-pocket-excel Test.sxc<br><br>% java.org.openoffice.xmerge.test.Driver -from application/x-pocket-excel -to staroffice/sxc Test.pxl<br></pre>
+</blockquote>
+<div align="left"><br>
+<h2>Features</h2>
+In addition to basic text and number conversion there are two main
+categories of features supported in this converter. Below is a simple
+table outlining the two categories and the features they support.<br>
+<br>
+<pre style="font-style: italic;">Summary of Supported Features</pre>
+<span style="font-style: italic;"></span>
+<table cellpadding="4" cellspacing="1" bgcolor="#f0f0f0" width="50%">
+  <tbody>
+    <tr align="center">
+      <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Category</b></font></th>
+      <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Features Supported<br>
+      </b></font></th>
+    </tr>
+    <tr>
+      <td valign="top" bgcolor="#99ccff" align="center"><font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Formula</b></font> </td>
+      <td valign="top" bgcolor="#99ccff"><br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Cell
+References<br>
+      </font> </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Add/Sub/Multiply/Divide<br>
+      </font> </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Integers
++ Floating Points<br>
+      </font> </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Functions<br>
+      </font> </td>
+    </tr>
+    <tr>
+	 <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Name
+Definitions<br>
+      </font></td>
+    </tr>
+    <tr>
+      <td valign="top" bgcolor="#99ccff" align="center"><font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Formatting</b></font> </td>
+      <td valign="top" bgcolor="#99ccff"><br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Font<br>
+      </font> </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Bold,
+Italic, Underline</font></td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Colour<br>
+      </font> </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Alignment
+(Horizontal &amp; Vertical)<br>
+      </font> </td>
+    </tr>
+  </tbody>
+</table>
+<div style="text-align: left;">
+<pre><span style="font-style: italic;"></span></pre>
+</div>
+The first is formula features. In Pocket Excel like most other
+spreadsheet applications any cell that starts with an "=" is considered
+to be a formula. This formula is made up of operands and operators. In
+addition to simple operators (such as addition,
+subtraction,multiplication and division) this converter also supports
+the 140 function operators available in pocket excel. StarCalc has of
+course many more functions than this but in the case where a sxc
+document has functions not supported in pocket excel the cell containing
+them is converted to an error cell in the pocket excel document.
+Operand support includes numbers, cell references (absolute, relative,
+3D and cell ranges) and name definitions.<br>
+<br>
+The second set of features supported in this converter relate to cell
+formatting. All the basic formatting is supported in this converter. The
+following is a&nbsp; list of these features<br>
+<ul>
+  <li>Bold, Italic and Underline,</li>
+  <li>Colour (background and foreground)</li>
+  <li>Alignment (Horizontal &amp; Vertical)</li>
+  <li>Font</li>
+  <li>Row and Column Width</li>
+  <li>Borders</li>
+  <li>Windows freezes and Splits</li>
+</ul>
+<br>
+<h2>ScreenShots</h2>
+Below are some screenshots to highlight the conversion capability of
+this filter. <br>
+<br>
+<pre style="font-style: italic;">StarCalc view of a spreadsheet</pre>
+<img style="width: 861px; height: 442px;" alt="" title=""
+ src="images/formula_sxc.jpg"><br>
+<br>
+<br>
+<pre style="font-style: italic;">Pocket Excel view of the converted file</pre>
+<div align="center">
+<div align="left"> <img src="images/formula_pxl.jpg" title="" alt=""
+ style="width: 352px; height: 496px;"><br>
+</div>
+<div align="left">
+<h2><a name="To_Do"></a>To Do</h2>
+I would divide this ToDo list into two categories. The first would be
+features which are already support but could be done better. These I
+think should include.<br>
+<br>
+<ul>
+  <li> Handling of unsupported functions</li>
+</ul>
+<br>
+The second area are features that are not yet implemented<br>
+<br>
+<ul>
+  <li> Number Formatting</li>
+  <li>Merge cells<br>
+  </li>
+</ul>
+<ul>
+</ul>
+<h2>Building the plugin</h2>
+The Pocket Excel plugin is built as part of the XMerge framework.
+&nbsp;Its classes are stored in <code>pexcel.jar</code>. &nbsp;See <a
+ href="../index.html#build"> Building XMerge</a> for more instructions.<br>
+</div>
+</div>
+</div>
+<!-- end footer --> &nbsp;&nbsp; <br>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+<br>
+</body>
+</html>
diff --git a/content/xml/xmerge/plugins/pocketword.html b/content/xml/xmerge/plugins/pocketword.html
new file mode 100644
index 0000000..b2cdd8d
--- /dev/null
+++ b/content/xml/xmerge/plugins/pocketword.html
@@ -0,0 +1,373 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>XMerge Pocket Word Plugin</title>
+                                                                     
+  <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+</head>
+  <body>
+                   
+<h1>XMerge Pocket Word Plugin</h1>
+          <br>
+                   
+<h2>Overview</h2>
+          <br>
+          The Pocket Word plugin converts text data between OpenOffice Writer 
+  format   and Pocket Word's binary file format. &nbsp;Specifically, it has 
+  been targeted   at the version of Pocket Word supplied with Windows CE 
+3.0  handheld devices.   &nbsp;The plugin has been tested with Pocket PC 2000
+and Pocket PC 2002.<br>
+          <br>
+The following table outlines the supported features of the Pocket Word plugin:<br>
+<br>
+<table cellpadding="4" cellspacing="1" bgcolor="#f0f0f0" width="50%">
+  <tbody>
+    <tr align="center">
+      <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Category</b></font></th>
+       <th bgcolor="#00315a"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Feature</b></font></th>
+       <th bgcolor="#00315a" width="20%"><font color="#ffffff"
+ face="Arial, Helvetica" size="2"><b>Supported</b></font></th>
+     </tr>
+     <tr>
+       <td valign="top" bgcolor="#99ccff" align="center">&nbsp;<font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Document Elements</b></font><br>
+      </td>
+       <td valign="top" bgcolor="#99ccff"><br>
+       </td>
+       <td width="20%" valign="top" bgcolor="#99ccff"><br>
+       </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Paragraphs<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+       </font>      </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Styles<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+       </font>      </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Tables<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+       </font>      </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Lists<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+       </font>      </td>
+     </tr>
+     <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Images</font><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">no</font><br>
+      </td>
+    </tr>
+    <tr>
+       <td valign="top" bgcolor="#99ccff" align="center"><font
+ color="#00315a" face="Arial, Helvetica" size="2"><b>Formatting</b></font> 
+     </td>
+       <td valign="top" bgcolor="#99ccff"><br>
+       </td>
+       <td width="20%" valign="top" bgcolor="#99ccff"><br>
+       </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Font<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">no<br>
+       </font>      </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Bold, Italic, 
+Underline</font></td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+       </font>      </td>
+     </tr>
+     <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Strikethrough,
+Highlight</font><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">yes</font><br>
+      </td>
+    </tr>
+    <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Colour<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes<br>
+       </font>      </td>
+     </tr>
+     <tr>
+       <td valign="top"><br>
+       </td>
+       <td valign="top"><font face="Arial, Helvetica" size="2">Alignment<br>
+       </font>      </td>
+       <td width="20%" valign="top"><font face="Arial, Helvetica"
+ size="2">yes</font></td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">Indentation</font><br>
+      </td>
+      <td valign="top"><font face="Arial, Helvetica" size="2">no</font><br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<br>
+                   
+<h2>Using the Pocket Word plugin</h2>
+          <br>
+        The Pocket Word plugin is invoked in the same manner as all other 
+XMerge    plugins. &nbsp; Once the framework has been made aware of the plugin,
+ the    only thing needed to use it is to specify its MIME type as a source
+ or destination   type for conversion. &nbsp;The MIME type is specified in
+ the <code>converter.xml</code>     file included in the <code>pocketword.jar</code> 
+   file. &nbsp;Currently,  this is set to <code>application/x-pocket-word</code> 
+  .<br>
+        <br>
+        For example, to use the Pocket Word plugin in conjunction with the
+ test   driver supplied with the XMerge framework:<br>
+        <br>
+               
+<blockquote>                        
+  <pre>% java org.openoffice.xmerge.test.Driver -from staroffice/sxw -to application/x-pocket-word Test.sxw<br><br>% java.org.openoffice.xmerge.test.Driver -from application/x-pocket-word -to staroffice/sxw Test.psw<br></pre>
+        </blockquote>
+               
+<div align="left"><br>
+               
+<h2>Features</h2>
+       The plugin currently supports conversion of most of the document formatting 
+   features supported by Pocket Word (i.e. those which a user can create from
+   scratch in Pocket Word). &nbsp;The list of supported features currently 
+ includes:<br>
+       <br>
+             
+<table cellpadding="2" cellspacing="2" border="0" width="95%"
+ align="right">
+         <tbody>
+           <tr>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Bold<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Highlight<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+           </tr>
+           <tr>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Italic<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Alignments<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+           </tr>
+           <tr>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Underline<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Bulleting <br>
+               </li>
+                                                       
+      </ul>
+             </td>
+           </tr>
+           <tr>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Strikethrough<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+             <td valign="top">                                           
+     
+      <ul>
+               <li>Colour<br>
+               </li>
+                                                       
+      </ul>
+             </td>
+           </tr>
+                           
+  </tbody>       
+</table>
+             
+<blockquote><br>
+       </blockquote>
+       <br>
+       <br>
+       <br>
+       <br>
+       <br>
+  <br>
+       <br>
+ <br>
+ <br>
+       The following screenshots show some Writer files converted into Pocket 
+  Word  documents:<br>
+  <br>
+  <br>
+  <br>
+             
+<div align="center"><img src="images/conversion-sxw.jpg"
+ alt="Image showing formatted StarWriter file." width="801" height="426"
+ border="1">
+       <br>
+      <br>
+      <br>
+           
+<div align="left"><br>
+      <br>
+           
+<table cellpadding="2" cellspacing="2" border="0" width="100%">
+        <tbody>
+          <tr>
+            <td valign="top" align="center"><img
+ src="images/conversion-ppc2k.jpg" alt="Pocket PC 2000 Screenshot"
+ width="240" height="320" border="1">
+            <br>
+            </td>
+            <td valign="top" align="center"><img
+ src="images/conversion-ppc2002.jpg" alt="Pocket PC 2002 Screenshot"
+ width="240" height="320" border="1">
+            <br>
+            </td>
+          </tr>
+          <tr>
+            <td valign="top" align="center"><i>Pocket PC 2000</i><br>
+            </td>
+            <td valign="top" align="center"><i>Pocket PC 2002</i><br>
+            </td>
+          </tr>
+                       
+  </tbody>      
+</table>
+      <br>
+      <br>
+      <br>
+      </div>
+             
+<div align="left">      
+<h2>To Do</h2>
+      There are a few features of Pocket Word which are not handled by the
+ converter.   &nbsp;Some of them relate to features of Pocket Word and some
+ relate to StarOffice  features which have no mapping in the Pocket Word
+application.<br>
+      <br>
+           
+<h3>Fonts<br>
+      </h3>
+      <br>
+     The most significant missing feature is the use of fonts. &nbsp; Files 
+ generated  by Pocket Word store data about each on-screen line in a paragraph. 
+ &nbsp;This  data consists of the number of characters and the screen space 
+ occupied by  those characters. &nbsp;Calculating this from a Java based environment
+ is  no easy task. &nbsp;<br>
+      <br>
+      Initial attempts to make use of the <code>java.awt.FontMetrics</code> 
+  class were unsuccessful  as the values returned do not correspond to values 
+ returned with similar calls on a Pocket PC device. &nbsp;<br>
+      <br>
+      Tests with the ActiveSync supplied MS Word -&gt; Pocket Word converter
+  show  that there is some method of bypassing the requirement for these
+line   descriptors.  &nbsp;That method, however, is not known.<br>
+      <br>
+      Finally, while Pocket Word supports TrueType/OpenType fonts, it has 
+only   4 default fonts. &nbsp; As a compensatory measure the plugin could 
+make use  of the <code>style.xml</code> file within a Writer document to substitute
+ similar fonts,  e.g. <i>Courier New</i> for monospace fonts, <i>Arial/Helvetica</i>
+   for sans  serif fonts and <i>Times New Roman</i>  for serif fonts. &nbsp;By
+ making use  of the TrueType fonts distributed with the Java environment,
+cross-platform  availability is assured.<br>
+      <br>
+           
+<h3>Other Features</h3>
+      Support for a number of other features could be added. &nbsp;These
+include:<br>
+      <br>
+           
+<ul>
+        <li>Tables</li>
+        <li>Images</li>
+        <li>Page margins</li>
+           
+</ul>
+      <br>
+           
+<h2>Building the plugin</h2>
+      The Pocket Word plugin is built as part of the XMerge framework. &nbsp;Its
+   classes are stored in <code>pocketword.jar</code>. &nbsp;See <a
+ href="../index.html#build">Building XMerge</a> for more instructions.<br>
+      </div>
+             
+<div align="left"><br>
+       </div>
+       </div>
+       </div>
+                    <br>
+</body>
+</html>
diff --git a/content/xml/xmerge/starlite.html b/content/xml/xmerge/starlite.html
new file mode 100644
index 0000000..681924c
--- /dev/null
+++ b/content/xml/xmerge/starlite.html
@@ -0,0 +1,248 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <link rel="stylesheet" type="text/css" href="xmloff.css"
+ media="screen">
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>Background of XMerge<br>
+</h1>
+<!-- no current top news!
+<h2><strong>Top News</str
+ong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<p>Xmerge came out of project Starlite. The goal of Starlite was to
+provide mobility to StarOffice documents. The Starlite
+team developed
+spreadsheet and document viewer applications with limited editing
+capabilities for PalmOS. These applications were designed to
+synchronize with the StarWriter and StarCalc applications on the
+desktop. <br>
+</p>
+<p>Project ZenSync was the second phase of project Starlite to expand
+the
+synchronization capabilities to work with an expanded set of
+small-device applications. </p>
+<table cellpadding="4" cellspacing="1"
+ style="background-color: rgb(255, 255, 255); width: 400px;">
+  <tbody>
+    <tr>
+      <td colspan="2"
+ style="background-color: rgb(0, 49, 90); text-align: center; width: 150px;"><font
+ color="#ffffff" face="arial, helvetica" size="2"><b>StarLite Team<br>
+      </b></font></td>
+    </tr>
+    <tr>
+      <th bgcolor="#99ccff" align="center" style="width: 150px;"><font
+ color="#00315a" face="arial, helvetica" size="2"><b> Name</b></font><br>
+      </th>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b>Function</b></font></th>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Akhil Arora</td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Tech
+Lead<br>
+      </td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Eileen
+Bugee</td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Visual
+designer</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Eric
+Bergman</td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Human
+factors design</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">David
+Proulx</td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">StarWriter
+for PalmOS</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Herbie
+Ong</td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Converters
+for StarWriter</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Paul
+Rank<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">StarCalc
+for PalmOS</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Raju
+Pallath<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Quality</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Stephen
+Mak<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Converters
+for StarCalc</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Denis
+Sharypov<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">StarCalc
+for PalmOS<br>
+      </td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Maline
+Minasandram<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Manager<br>
+      </td>
+    </tr>
+<!--
+<tr>
+<td bgcolor="#f0f0f0" valign="top"><a href="...">...</a></td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+</tr>
+-->
+  </tbody>
+</table>
+<br>
+At this point the project was transfered to Dublin, Ireland. The first
+step was to refactor the code so that filters could be written not just
+for palm devices but any device. This included writing a registry for
+xmerge so that it could keep track of which filters were included and
+what formats they could convert to/from. Next, filters for Pocket Excel
+and Pocket Word were written. Once this was completed an Active Sync
+conduit was written so that XMerge could be used to convert Pocket PC
+files on a handheld to StarOffice files on a PC automatically through
+ActiveSync. The decision was then taken to open source the project and
+make it available on OpenOffice. This involved hosting the code on
+OpenOffice CVS, adding the web pages and writing the documentation for
+filter writers. Once hosted on the website a FlatXML and DocBook filter
+were added. The final step in the project was to include XMerge in
+StarOffice. <br>
+<br>
+<table cellpadding="4" cellspacing="1"
+ style="background-color: rgb(255, 255, 255); width: 550px;">
+  <tbody>
+    <tr>
+      <td colspan="2" bgcolor="#00315a" align="center"
+ style="width: 150px;"><font color="#ffffff" face="arial, helvetica"
+ size="2"><b>XMerge Team<br>
+      </b></font></td>
+    </tr>
+    <tr>
+      <th bgcolor="#99ccff" align="center" style="width: 150px;"><font
+ color="#00315a" face="arial, helvetica" size="2"><b> Name</b></font><br>
+      </th>
+      <th bgcolor="#99ccff" align="center"><font color="#00315a"
+ face="arial, helvetica" size="2"><b>Function</b></font></th>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Brian
+Cameron<br>
+      </td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Tech
+Lead<br>
+      </td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Aidan
+Butler<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">FlatXML
+&amp; Docbook filter, Integration into StarOffice</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Mike Hayes<br>
+      </td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Code
+design work, Code refactoring, Pocket Excel filter</td>
+    </tr>
+    <tr>
+      <td valign="top"
+ style="width: 150px; background-color: rgb(240, 240, 240);">Darren
+Kenny<br>
+      </td>
+      <td valign="top" style="background-color: rgb(240, 240, 240);">Code
+design work, OpenOffice web hosting</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Martin
+Maher<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Pocket
+Excel filter, Code refactoring</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">Mark
+Murnane<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Pocket
+Word filter, ActiveSync, Integration into StarOffice</td>
+    </tr>
+    <tr>
+      <td
+ style="vertical-align: top; width: 150px; background-color: rgb(240, 240, 240);">James
+Cleere<br>
+      </td>
+      <td
+ style="vertical-align: top; background-color: rgb(240, 240, 240);">Manager<br>
+      </td>
+    </tr>
+<!--
+<tr>
+<td bgcolor="#f0f0f0" valign="top"><a href="...">...</a></td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+<td bgcolor="#f0f0f0" valign="top">...</td>
+</tr>
+-->
+  </tbody>
+</table>
+<!--
+  older optimization ideas ... currently not relevant 
+   <tr>
+    <td><a href="optimization.html">Optimization  Ideas</a></td>
+    <td>This page contains a list of oppurtunities for speed optimizations for
+    the XML filters. Additionally, the current status of our optimization
+    efforts is listed <a href="current_optimization_status.html">
+    here</a>. </td>
+    <td>HTML, ca.&nbsp;15KB</td>
+   </tr>
+-->
+</body>
+</html>
diff --git a/content/xml/xml_advocacy.html b/content/xml/xml_advocacy.html
new file mode 100644
index 0000000..a290f70
--- /dev/null
+++ b/content/xml/xml_advocacy.html
@@ -0,0 +1,331 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE>The StarOffice XML based file format</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="AUTHOR" CONTENT="Daniel Vogelheim">
+	<META NAME="CREATED" CONTENT="20010803;16470900">
+	<META NAME="CHANGEDBY" CONTENT="Daniel Vogelheim">
+	<META NAME="CHANGED" CONTENT="20010821;15101200">
+	<STYLE>
+	<!--
+		@page { margin: 2cm }
+		P { margin-bottom: 0.21cm; text-align: justify }
+		H1 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 16pt }
+		H2 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 14pt; font-style: normal }
+		H3 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 12pt }
+	-->
+	</STYLE>
+</head>
+<body>
+<P ALIGN=JUSTIFY STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=5>The
+StarOffice XML based file format</FONT></FONT></P>
+<P ALIGN=JUSTIFY STYLE="margin-top: 0.2cm; margin-bottom: 2cm; page-break-after: avoid">
+<FONT FACE="Arial, sans-serif"><FONT SIZE=3>To boldly go where no
+office suite has gone before</FONT></FONT></P>
+<H1>1Introduction</H1>
+<P>StarOffice 6.0 and OpenOffice.org use a new, XML based file format
+for all its documents. The constituent parts of an office document,
+content, layout and meta information, are stored as XML streams
+inside a ZIP file, along with embedded graphics and objects contained
+in the document.</P>
+<P>Before musing on the technical virtues and uses of the XML based
+file format, it should be noted that the format as well as the
+OpenOffice.org application, which serves as a reference
+implementation for the format, are available under a GNU license.
+This open and free licensing guarantees that you are not at the mercy
+of a single company for improvements and fixes of the format or its
+supporting software, thus providing very strong protection for all
+investments and efforts you put into this format. Additionally, Sun
+aims at standardizing the format, thus providing any interested
+parties with a way to participate in the evolution of the format.</P>
+<P>The next chapter will introduce several features of the XML
+format, followed by a chapter in which benefits can be derived from
+these features for various types of users. Finally, a conclusion will
+be presented.</P>
+<H1>2How It Works &#150; The Means</H1>
+<P>This chapter will highlight several technicalities of the XML
+based file format. The following chapter will then show how to put
+these into use.</P>
+<H2>2.1Separation of Content, Layout, and Meta Information</H2>
+<P STYLE="font-style: normal">An office document contains content,
+for example the text of a letter, or the data in a spreadsheet, along
+with layout information, which describes how the content should look
+like. Also part of document is meta information like who edited a
+document and how it is called, or additional information such as
+images or embedded objects. To a user, these are inseparable parts of
+a single document. But for processing the document, it makes sense to
+separate them such that they can be read, interpreted and modified
+independently of each other. To facilitate this, the StarOffice XML
+file format stores content, layout, meta information, images and
+embedded objects in separate streams of a ZIP based package file. The
+whole file contains the whole document, the individual streams
+contain the constituent parts of the document.</P>
+<H2>2.2Standards Based</H2>
+<P>When creating the XML based file format, we tried to gain as much
+as was possible from related standards. The very use of XML is one
+example. The ZIP format we use for packages are in widespread use.
+Many elements and attributes are borrowed from HTML, XSL-FO, XLink,
+Dublin Core, or SVG. For Math, we use MathML. This allows easy
+transformation from and into those formats, and also it allows people
+to quickly understand our format, if they are already familiar with
+those formats we make use of.</P>
+<H2>2.3Uniform Representation of Formatting and Layout Information</H2>
+<P>The StarOffice and OpenOffice.org applications distinguish between
+formatting through styles and <I>direct</I> formatting, which means
+applying formatting directly to text or cell ranges. In the XML
+format, these different ways to format a document use the same
+style-based representation. The <I>direct</I> formatting is
+automatically converted into <I>automatic styles</I>,  which is a
+style-based formatting equivalent of the <I>direct</I> formatting the
+user applied to the document.</P>
+<H2>2.4Structured Format</H2>
+<P STYLE="font-style: normal">A primary design goal of the XML format
+was to represent all structured information contained in an document
+as XML structures, thus making the document fully accessible to
+standard XML tools.  This is a quite different solution to, for
+example, an XHTML/CSS solution, where all CSS formatting information
+is encoded in a text-only format. This way, all layout information
+appears as a single string to an XSLT processor, making it very hard
+to process the layout information in any way.</P>
+<H2>2.5Idealized Format</H2>
+<P><SPAN STYLE="font-style: normal">Our XML file format is a properly
+designed file format, as opposed </SPAN>to a mere XML dump o<SPAN STYLE="font-style: normal">f
+core structures with all their implementation details and
+limitations. The documents are represented in a way which is easy to
+understand and use, and not in a way which is easy to implement. This
+allows the format to abstract application peculiarities and therefore
+the format may also be used by applications other than StarOffice and
+OpenOffice.org. Throughout the development of the format, great care
+was taken to make sure the file format is easy to process. Also, the
+idealized representation makes it easier to improve the StarOffice
+and OpenOffice.org applications without having to make major changes
+to the format itself.</SPAN></P>
+<H2>2.6Common Format Across All Office Applications</H2>
+<P STYLE="font-style: normal">The same format is used across all
+office applications. Similar concepts in the different applications
+always use the same XML representation. For example, spreadsheet
+tables and word processor tables share a common XML representation,
+even though their implementations and limitations are quite
+different. This has great advantages when processing or generating
+StarOffice files: The same code works for all applications. For
+example, a single XSLT style sheet can process both spreadsheets and
+text documents.</P>
+<H2>2.7Open For Extensions and Supplemental Information</H2>
+<P STYLE="font-style: normal">Arbitrary XML attributes may be
+attached to style information and will be preserved when editing such
+a modified file with StarOffice. Because all formatting information
+is uniformly represented as styles, and because any document content
+can be formatted using styles, this allows arbitrary information to
+be attached to any part of the document content. Further means to add
+supplemental information, such as allowing complete streams to be
+part of the packages, may be added.</P>
+<H1>3What You Gain &#150; The Ends</H1>
+<P>The previous chapter has highlighted several features and
+mechanisms of our new file format. This chapter will look at how this
+helps different groups of users.</P>
+<H2>3.1Office Users</H2>
+<P>To the user of StarOffice and OpenOffice.org, the main benefits
+may be summarized as increased robustness, openness, document
+longevity, and version interoperability. In additional, the user will
+gain additional benefits as the document processing and additional
+solutions described in the following chapters become reality.</P>
+<H3>Increased Robustness</H3>
+<P>To a user, their own documents are usually valuable resources,
+into which lots of time and effort has been invested. What happens,
+if through an error in the used hardware or software used, the
+documents become corrupted? With a binary format, the user is at the
+mercy of the original application: If it can still read or recover
+the document, all is well. If not, the document is lost. 
+</P>
+<P STYLE="font-style: normal">XML makes it easy to ignore and
+tolerate problems in the documents, so the likelihood of lost
+documents is reduced. Additionally, the human readable/editable
+nature of XML allows advanced users or service personnel to inspect
+corrupt files and restore the documents, even without specialized
+tools or very much in-depth knowledge.</P>
+<H3>Document Archiving</H3>
+<P>For some users, long-term storage of documents is important. With
+binary file formats, documents can be read only as long as the
+supporting application as well as the system it runs on exists. XML,
+being a text based and human readable format, allows files to be read
+even if the original application (or the OS, or the hardware it ran
+on) are not available anymore. Additionally, the thorough
+documentation of the format allows the files to be fully interpreted.</P>
+<H3>Version Interoperability</H3>
+<P>A well-known problem with office documents is a file format
+versioning problem: New versions of the office suite usually come
+with a new version of a file format, which the older version don't
+know about. To be able read the newer documents, users find
+themselves forced to upgrade their application.</P>
+<P>Contrast this with an XML based format: XML is extensible, making
+it easy to to add new features to the format without loosing the
+ability to read older files. Older applications will simply ignore
+the new (and, to them, unknown) content, thus reading the newer files
+as well as they can. The result is a high degree of forwards and
+backwards compatibility. 
+</P>
+<H3>Documented and Transparent File Content</H3>
+<P>With the XML file format, the user can finally inspect the content
+of files that are being sent or received. If yet another macro virus
+threatens your organization, a simple combination of unzip and grep
+allows you to check for suspicious content. If you want to make sure
+that files you send to other people don't contain sensitive
+information, then now you can simply look at them. Or if you need to
+quickly find a certain document, just use Unix grep or the Windows
+Explorer context menu  to search through the meta information, which
+are stored as plain text.</P>
+<H2>3.2Document Processing and Developers</H2>
+<P>Advanced users and developers may want to make use of the new
+freedom the StarOffice XML file brings them, and use and process
+StarOffice files with other tools and applications. There are several
+advantages for them:</P>
+<H3>Standards Based and Openness</H3>
+<P>The StarOffice XML file format relies on many standards in
+addition to the actual XML standard itself: It makes use of elements
+and attributes from HTML, XLink, XSL-FO, Dublin Core, and SVG.
+Developers familiar with these can easily pick up on the StarOffice
+format. Also, a developer has a wide choice of tools and code
+libraries for many programming languages that allow processing and
+manipulation of XML or ZIP files.</P>
+<P>This use of established standards is particularly useful for
+making office documents available outside of traditional PC
+applications. For example, by transforming our office documents into
+HTML, you can make them available through the World Wide Web. Similar
+transformations are  into WAP or XSL-FO are possible. 
+</P>
+<P>An example of transforming our documents into HTML is available on
+the OpenOffice.org website, and another one is available through the
+xml.com website (see reference at the end of this paper). 
+</P>
+<H3>Easy Import and Export of Other File Formats</H3>
+<P>Import and export of other '<I>foreign</I>' file formats can be
+accomplished by converting the document into the XML file format.
+This approach has several advantages:</P>
+<OL>
+	<LI><P>The XML file format provides the developer with a clean,
+	documented target.</P>
+	<LI><P>Due to XML's human readability, debugging becomes much
+	easier.</P>
+	<LI><P>The file format and the StarOffice API hide the details of a
+	particular office version, so the developer doesn't have to
+	recompile and update the import/export component for every new
+	version of StarOffice.</P>
+	<LI><P>Several XML based import or export components may be chained
+	to each other. This can be used to convert between two
+	non-StarOffice formats.</P>
+	<LI><P>Import and Export components can be integrated into
+	StarOffice and OpenOffice.org, or they can be used stand-alone. In
+	the latter mode, they could be used e.g. for batch conversion of
+	many files. Also, they can be used to view StarOffice XML documents
+	without having to start the full StarOffice application.</P>
+</OL>
+<H3>Leverage Available Infrastructures</H3>
+<P>Being based on XML and ZIP, the StarOffice file format can be used
+with the growing number of widely available tools that can process
+these formats. Examples are:</P>
+<OL>
+	<LI><P>XML viewers and editors</P>
+	<P>Any of the available XML viewers can be used to examine the
+	document content. XML Editors can be used to manually make changes
+	to the document content or its layout.</P>
+	<LI><P>XML transformations</P>
+	<P>XML transformation tools and libraries, such as XSLT engines or
+	XPathScript (Perl), can be used to automatically edit, modify or
+	generate StarOffice documents.</P>
+	<LI><P>XML Databases</P>
+	<P>There is a growing number of XML aware database and storage
+	products. These may be used to store, index, query and manipulate
+	StarOffice documents.</P>
+	<LI><P>ZIP tools</P>
+	<P>With the package mechanism using the well-known ZIP format,
+	standard ZIP tools may be used to change the package content. For
+	example, using any ZIP tool, embedded graphics can be changed from
+	low resolution to high resolution ones before giving a document to a
+	print shop.</P>
+</OL>
+<H2>3.3Solution Providers</H2>
+<P>A generic office suite may not be the right solution for everyone.
+Often, significant improvements to productivity can be achieved by
+using custom software solutions tailored exactly to the requirements
+of a particular organization. StarOffice and OpenOffice.org can
+become part of such a solution, supplying office functionality as
+part of an larger, fully integrated package. Solution providers who
+want to integrate StarOffice or OpenOffice.org into their software
+will find the XML file format along with the open StarOffice API to
+be the enabling features for this.</P>
+<H3>StarOffice as Editor Component</H3>
+<P>The StarOffice API enables the use of StarOffice as an editor
+component. In this mode of operation, StarOffice may appear as an
+edit area within the custom application, controlled through the API.
+The custom application only needs to represent its own data in the
+StarOffice XML file format and hand it to the StarOffice component.
+When the editing is done, the custom application can then convert the
+XML data stream back into its own, native format for storage or
+further processing.</P>
+<H3>Search Engines / Knowledge Management Systems</H3>
+<P STYLE="font-style: normal">The use of XML makes office documents
+accessible to search engines and more advanced knowledge management
+systems. Since the full document structure is available as XML,
+knowledge management system could easily extract or value document
+content based on how or where it is contained in the document.</P>
+<P STYLE="font-style: normal">Search engines can usually been
+configured for different file types. To index and search StarOffice
+XML files, all that is necessary is to teach the search engine to run
+the venerable 'unzip' command on each file before processing it.</P>
+<H3>Document Management</H3>
+<P STYLE="font-style: normal">StarOffice and OpenOffice.org are
+ideally suited for integration into document management systems.
+Here, a key feature is the ability to attach additional data to
+documents or parts of documents. A document management system can use
+this to include additional information into the documents while still
+keeping the documents fully editable by the user. As detailed above,
+StarOffice and OpenOffice.org may additionally be used as editing
+components inside the document management system.</P>
+<H3>Partial Editing and Two-way Conversion</H3>
+<P>Custom applications may want to modify or update office documents
+based on specific data or computations. XML makes it easy to identify
+specific parts of a document and to replace them. The separation of
+content and layout further helps this because it allows changing one
+without having to change the other.</P>
+<P>A similar approach is to extract data from a StarOffice document
+and process it in some way. Then, merge the new data into the
+document again, or just recreate the document based on the new data.
+Such back-and-forth conversions are simplified by XML's nature, and
+the content/layout separation.</P>
+<P>This technique could be used to support StarOffice documents (or
+parts of documents) on resource constrained devices, such as PDAs. 
+</P>
+<H3>StarOffice as Layout Engine</H3>
+<P><SPAN STYLE="font-style: normal">At the end of the data processing
+chain, a </SPAN>custom application may need to present data to users
+or generate printable documents, summaries and reports. When using
+StarOffice, this can be achieved by converting the presentation data
+into the StarOffice XML file format, and loading it into StarOffice
+for layout and printing. This way, the full power of StarOffice can
+be leveraged for professionally looking documents without having to
+recreate the entire formatting and layout logic. Once again, the
+separation of content and layout helps, as it allows painless
+generation of the plain content data, which can then be combined with
+professional, artistic layout information.</P>
+<H1>4Conclusion</H1>
+<P>The upcoming StarOffice 6.0 and OpenOffice.org both feature a new
+XML based file format, which stores document content, layout, and
+meta information as XML inside of a ZIP package, along with embedded
+graphics and objects. This organization as well as many details in
+the XML format itself provide many advantages to various groups of
+users, creating a win-win situation for all end users, developers and
+solution providers that make use of it.</P>
+<H1>5Online Resources and Further information</H1>
+<P ALIGN=LEFT>OpenOffice.org XML Homepage: <A HREF="http://xml.openoffice.org/">http://xml.openoffice.org/</A></P>
+<P ALIGN=LEFT>StarOffice/OpenOffice.org XML based file format
+definition: <A HREF="http://xml.openoffice.org/xml_specification.pdf">http://xml.openoffice.org/xml_specification.pdf</A></P>
+<P ALIGN=LEFT>The StarOffice/OpenOffice.org API:
+<A HREF="http://api.openoffice.org/">http://api.openoffice.org/</A></P>
+<P ALIGN=LEFT>&#147;Adventures with OpenOffice and XML&#148; by Matt
+Sergeant: <A HREF="http://www.xml.com/pub/a/2001/02/07/openoffice.html">http://www.xml.com/pub/a/2001/02/07/openoffice.html</A></P>
+<P ALIGN=LEFT>OpenOffice.org Filter-Development Using XML:
+<A HREF="http://xml.openoffice.org/filter/">http://xml.openoffice.org/filter/</A></P>
+</body>
+</HTML>