LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Added Tabatha's notes on openoffice 1.1

This commit is contained in:
emmajane 2003-12-08 00:50:25 +00:00
parent d4223a2db9
commit 7ad181c5b4
1 changed files with 144 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

145
LDP/guide/docbook/LDP-Author-Guide/tools-word-processors.xml
View File

@ -56,6 +56,8 @@
</ulink>.
</para>
<section id="ooo-1-0">
<title>Open Office 1.0.x</title>
<para>
OOo has been tested by LDP volunteers with mostly positive
results. Thanks to Charles Curley
@ -125,7 +127,148 @@ or whether
thing, it would be nice to know which native OOo styles map to
which DocBook elements. It would also be nice to know how to
map one's own OOo styles to DocBook elements.
</para> </section>
</para>
</section>
<section id="ooo-1-1">
<title>Open Office 1.1</title>
<para>
<ulink url="http://www.merlinmonroe.com">Tabatha Marshall</ulink>
offers the following additional information for OOo 1.1.
</para>
<blockquote>
<para> First problem was I tried to do everything on version
1.0.1. That was
obviously a problem. I have RH8, and it was installed via rpm packages,
so I ripped it out and did a full, new install of OpenOffice 1.1.
It took a while to find out 1.1 was a requirement for XML to work.
</para>
<para>
<para>
During the install process I believe I was offered the choice to install
the XML features. I have a tendency to do full installs of my office
programs, so I selected everything.
</para>
<para>
I can't offer any advice to those trying to update their current
OO 1.1. Their <quote>3 ways</quote> aren't documented very well at the site
(<ulink url="http://xml.openoffice.org">xml.openoffice.org</ulink>) and as of this writing, I can't even find THAT
on their site anymore. I think more current documentation is needed
there to walk people through the process. Most of this was unclear
and I had to pretty much experiment to get things working.
</para>
<para>
Well, after I installed everything I had some configuration to do.
I opened the application, and got started by opening a new file,
choosing templates, then selecting the DocBook template. A nice menu
of <guisubmenu>Paragraph Styles</guisubmenu> popped up for me, which are the names for all those
tags, I noticed (you can see I don't use WYSIWYG often).
</para>
<para>
With a blank doc before me (couldn't get to the <guisubmenu>XML Filter
Settings</guisubmenu> menu unless some type of doc was opened), I went into
<guimenu>Tools</guimenu> --&gt; <guimenuitem>XML
Filter Settings</guimenuitem>, and edited the entry for DocBook file.
I configured mine as follows:
</para>
<itemizedlist>
<listitem>
<para>
<guilabel>Doctype</guilabel>
<userinput>-//OASIS//DTD DocBook XML V4.2//EN</userinput>
</para>
</listitem>
<listitem>
<para>
<guilabel>DTD</guilabel>
<userinput>http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd</userinput>
</para>
</listitem>
<listitem>
<para>
<guilabel>XSLT for export</guilabel>
<userinput>/usr/local/OpenOffice.org1.1.0/share/xslt/docbook/ldp-html.xsl</userinput>
</para>
</listitem>
<listitem>
<para>
<guilabel>XSLT for import</guilabel>
<userinput>/usr/local/OpenOffice.org1.1.0/share/xslt/docbook/docbooktosoffheadings.xsl</userinput>
(this is the default)
</para>
</listitem>
<listitem>
<para>
<guilabel>Template for import</guilabel>
<userinput>/home/tabatha/OpenOffice/user/template/DocBook
File/DocBookTemplate.stw</userinput>
</para>
</listitem>
</itemizedlist>
<para>
At first, if I opened an XML file that had even one parsing error, it
would just open the file anyway and display the markup in OO. I have
many XML files that use &amp;copy; and other types of entities which show
up as parse errors (depending on the encoding) even though they can be
processed through. But today I was unable to open any of those files.
I got input/output errors instead. Still investigating that one.
</para>
<para>
However when you do successfully open a document (one parsing with no
errors), it puts it automatically into WYSIWYG based on the markup,
and you can then work from the paragraph styles menu like any other
such editor.
</para>
<para>
To validate the document, I used <guimenu>Tools --> <guimenuitem>XML
Filter Settings</guimenuitem>, then
clicked the <guibutton>Test XSLTs</guibutton> button. On my screen, I set up the XSLT
for export to be <filename>ldp-html.xsl</filename>. If you test and there are errors,
a new window pops up with error messages at the bottom, and the lines
that need to be changed up at the top. You can change them there and
progress through the errors until they're all gone, and keep testing
until they're gone.
</para>
<para>
If you want to open a file to see the source instead of the processed
results, go to <guimenu>Tools</guimenu> --> <guimenuitem>XML Filter
Settings</guimenuitem> --> <guimenuitem>Test XSLTs</guimenuitem>, and then
under the <menuchoice>Import</menuchoice> section, check the
<guilabel>Display Source</guilabel> box. My import XSLT
is currently <filename>docbooktosoffheadings.xsl</filename> (the default) and the template
for import is <filename>DocBookTemplate.stw</filename> (also default).
</para>
<para>
I think this might work for some people, but unfortunately not for me.
I've never used WYSIWYG to edit markup. <application>Emacs with
PSGML</application> can tell me
what my next tag is no matter where I am, validate by moving through
the trouble spots, and I can parse and process from command line.
</para>
<para>
With OpenOffice, you have to visit <ulink
url="http://xml.openoffice.org/filters.html">http://xml.openoffice.org/filters.html</ulink>
to find conversion tools.
</para> </blockquote>
</section> </section>
<section id="wordperfect"> <!-- I don't run Windows - can someone please
confirm this information is still true? --> <title>WordPerfect 9 (Corel