<!DOCTYPE book PUBLIC  "-//KDE//DTD DocBook V3.1-Based Variant V1.0//EN" [
 <!ENTITY KOffice   "<application>KOffice</application>">
 <!ENTITY KWord   "<application>KWord</application>">
 <!ENTITY KSpread   "<application>KSpread</application>">
 <!ENTITY % addindex "IGNORE">
 <![ %addindex; [ <!ENTITY kdedocindex SYSTEM "docindex.docbook"> ]]>
]>

<book lang="en">
<bookinfo>
<title>KOffice</title>
<subtitle>A General Introduction</subtitle>
<authorgroup>
<author>
  <firstname>Jost</firstname>
  <surname>Schenck</surname>
  <affiliation>
  <address><email>jost@schenck.de</email></address>
  </affiliation> 
</author>
</authorgroup> 

<date>21/03/2000</date>
<releaseinfo>0.01.01</releaseinfo>

<revhistory>
<revision>
<revnumber>0.1.1</revnumber>
<date>21/03/2000</date>
<authorinitials>KT</authorinitials>
<revremark>Proof-read version of 0.1.0. Also,
some minor changes (couldn't stop myself :)</revremark>
</revision>
<revision>
<revnumber>0.1.0</revnumber>
<date>27/01/2000</date>
<authorinitials>JS</authorinitials>
<revremark>First made available to the CVS</revremark>
</revision>
</revhistory>

<abstract>
<para>
&KOffice; is an integrated office suite for the K Desktop Environment (KDE).
</para>
</abstract>

<keywordset>
<keyword>KDE</keyword>
<keyword>KOffice</keyword>
</keywordset>

</bookinfo>


<chapter id="todo">
<title>Still to be done in this manual</title>

<para>
This is a list of things which still need work in this manual:
</para>

<itemizedlist>
<listitem><para>
Write this list.
</para></listitem>
<listitem><para>
Just about everything else.
</para></listitem>
</itemizedlist>

<para>
If anyone wants to help, let me know at the email address
below. Thanks.
</para>

<para>
Jost <email>jost@schenck.de</email>
</para>

</chapter>


<chapter ID="introduction">
<title>Introduction</title>

<sect1 id="intro-intro">
<title>Introduction</title>

<para>
&KOffice; is an integrated office suite for the K Desktop Environment (KDE).
&KOffice; currently consists of the following programs:
</para>

<simplelist type=vert columns=1>
<member>KWord (a frames-based wordprocessor)</member>
<member>KSpread (a spreadsheet application)</member> 
<member>KPresenter (screen and slide presentations)</member>
<member>KIllustrator (a vector drawing application)</member>
<member>KImageShop (a bitmap image editor)</member>
<member>Katabase (a database application)</member>
<!-- IS KFORMULA DEAD? --> 
<member>KFormula (an editor for mathematical formulae)</member>
<member>KChart (a charts/graphs drawing application)</member>
<member>KImage (an image viewer)</member>
</simplelist>

<para>
Because they are based on the KParts component model, KOffice
programs are designed to work very well with each other. Any KOffice
component can be embedded in another KOffice document. For
instance, you can insert a table which you created in KSpread
directly into a KWord document. In this way, complex, compound
documents can be created using KOffice programs.
</para>

<para>
A plug-in mechanism makes it easy to extend the functionality of
KOffice. Already, there are two applications, a macro recorder and
a calculator, which show how this can be done.
</para>

<para>
This manual only covers the general features of &KOffice;, those that
are common to most or all programs in the suite. For detailed information
about the different programs, have a look at the other manuals.
FIXME LINK!
</para>

</sect1>


<sect1 id="WhoReads">
<title>What parts of this guide should I read?</title>

<note><para>
This section is not yet written.
</para></note>

</sect1>

</chapter> 


<chapter id="Installation">
<title>Installation</title>

<sect1 id="Requirements">
<title>System Requirements</title>

<para>
In order to install and use KOffice you must have:
</para>

<itemizedlist>
<listitem><para>
A functioning Unix system (for example, Linux or BSD)
with a configured X Window System (for example, XFree86).
</para></listitem>
<listitem><para>
The Qt 2.1 libraries from Troll Tech. See
<ulink url="ftp://ftp.troll.no/">ftp://ftp.troll.no/</ulink>
for more information.
</para></listitem>
<listitem><para>
The K Desktop Environment 2.0 (KDE 2.0). KOffice cannot be compiled
with earlier versions of KDE. Information on obtaining and installing
KDE 2.0 can be found at:
<ulink url="http://www.kde.org">http://www.kde.org.</ulink>
</para></listitem>
<listitem><para>
Permission to install software on your computer. If you are on a
stand-alone system, this should not be a problem. However, if you are
using a networked computer, check with your administrator first.
</para></listitem>
</itemizedlist>

<para>
Please note that, while you need the KDE 2.0 libraries on your system,
you can still use KOffice in a different desktop environment (for example,
KDE 1.1, UDE or GNOME).
</para>

<para>
If you plan on <link linkend="FromSource">compiling KOffice from
source code</link> you will also need:
</para>

<itemizedlist>
<listitem><para>
Automake 1.4 or newer.  This can be downloaded from:
<ulink url="ftp://ftp.gnu.org/pub/gnu/automake/">ftp://ftp.gnu.org/pub/gnu/automake/</ulink>
</para></listitem>
<listitem><para>
Autoconf 2.13 or later.  This can be downloaded from:
<ulink url="ftp://ftp.gnu.org/pub/gnu/autoconf/">ftp://ftp.gnu.org/pub/gnu/autoconf/</ulink>
</para></listitem>
<listitem><para>
A C++ compiler which supports exceptions (preferably egcs 1.1.x). This can be downloaded from
<ulink url="http://egcs.cygnus.com/">http://egcs.cygnus.com/</ulink>
</para></listitem>
<listitem><para>
Troll Tech's Qt 2.1 development packages. These can be downloaded from
<ulink url="ftp://ftp.troll.no/">ftp://ftp.troll.no/</ulink>
</para></listitem>
</itemizedlist>

<para>
Once you have determined that your system meets these requirements,
you should decide whether you want to compile the source code
or install from pre-compiled binary packages.
</para>

<para>
If you want to obtain the most current binary version of KOffice,
you can find more information by following this link:
<link linkend="GettingBinaries">Getting Binary Packages</link>.
</para>

<para>
If pre-compiled binaries are not available for your system, you can download
the source code and compile it yourself.  Instructions on where to obtain the
current source code (and what to do with the source code once you have it)
can be found by following this link:
<link linkend="GettingSource">Getting the source code</link>.
</para> 

<note><para>
Please see the <ulink url="http://koffice.kde.org">KOffice homepage</ulink>
for further details. That is where you can always find the most up-to-date
information on both source and binary distributions!
</para></note>

</sect1>


<sect1 id="GettingBinaries">
<title>Getting Binary Packages</title>

<para>
You can download the most current binaries from:
</para>

<para>
<ulink url="http://koffice.kde.org/">http://koffice.kde.org/</ulink>
</para>

<para>
or from one of many mirror sites. The current list of mirror sites
can be found at:
</para>

<para>
<ulink url="http://www.kde.org/mirrors.html">http://www.kde.org/mirrors.html</ulink>
</para>

<note><para>
It is important that you use a binary package which is compatible with your system.
If you use the Linux operating system and are unable to find a binary package
at the KOffice web site or one of its mirrors, you may be able to obtain one
from the website of your distribution.
</para></note>

</sect1>


<sect1 id="FromBinaries">
<title>From Binary Packages</title>

<para>
To install &KOffice; from precompiled binaries, you should:
</para>

<orderedlist numeration="arabic">
<listitem><para>
Ensure your computer has all of the required software installed and
in working condition (excluding KOffice of course). You can find the
system requirements by following this link:
<link linkend="Requirements">System Requirements</link>.
</para></listitem>
<listitem><para>
Download the KOffice binary into a temporary directory.
</para></listitem>
<listitem><para>
If the filename ends in .rpm (Redhat Package Management file),
KOffice can be installed with the following command:
<screen>
<prompt>$</prompt> <command>rpm -U <replaceable>filename</replaceable></command>
</screen>
If the filename ends in .deb (Debian Package file), KOffice can be
installed with the following command:
<screen>
<prompt>$</prompt> <command>dpkg -i <replaceable>filename</replaceable></command>
</screen>
If the filename ends in .tar.gz or .tgz (a tarball file), KOffice can be
installed with the following command:
<screen>
<prompt>$</prompt> <command>cd /</command>
<prompt>$</prompt> <command>tar -xzvf <replaceable>filename</replaceable></command>
</screen>
</para></listitem>
<listitem><para>
That's all. KOffice should now be installed on your system.
</para></listitem>
</orderedlist>

<note><para>
If you have a graphical front-end for package management, such as
KPackage or GnoRPM, installed on your system, you may find that more
convenient to use than a command line. Consult the program's
documentation to find out how to install with it.
</para></note>

</sect1>


<sect1 id="GettingSource">
<title>Getting Source Code</title>

<para>
You can download the current source code from:
</para>

<para>
<ulink url="http://koffice.kde.org/">http://koffice.kde.org/</ulink>
</para>

<para>
or from one of many mirror sites. The current list of mirror sites
can be found at:
</para>

<para>
<ulink url="http://www.kde.org/mirrors.html">http://www.kde.org/mirrors.html</ulink>
</para>

</sect1>


<sect1 id="FromSource">
<title>From Source Code</title>

<para>
If you want to build KWord from source code, you should:
</para>

<orderedlist numeration="arabic">
<listitem><para>
Ensure your computer has all the required software installed and
in working condition (excluding KOffice of course). You can find
the system requirements by following this link:
<link linkend="Requirements">System Requirements</link>.
</para></listitem>
<listitem><para>
Download the KOffice source file (***insert filenames (srpm and tar)
here***) into a temporary directory.
</para></listitem>
<listitem><para>
If the filename ends in .src.rpm (Redhat Package Management file),
the source code for KOffice can be installed with:
<screen>
<prompt>$</prompt> <command>rpm -U <replaceable>filename</replaceable></command>
</screen>
If the filename ends in .src.tar.gz or .src.tgz (a tarball file),
the source code for KOffice can be installed with:
<screen>
<prompt>$</prompt> <command>tar -xzvf <replaceable>filename</replaceable></command>
</screen>
</para></listitem>
<listitem><para>
The source code for KOffice should now be installed on your
system.
</para></listitem>
</orderedlist>

<para>
STUFF
</para>

</sect1>


<sect1 id="CompilingProblems">
<title>Problems with Compilation</title>

<para>
Problems STUFF
</para>

</sect1>

</chapter>


<chapter id="firststeps">
<title>First steps in &KOffice;</title>
<para></para>
</chapter>

<chapter id="kparts">
<title>KParts - the building blocks of &KOffice;</title>

<para>
Each &KOffice; application is designed to fulfill very specific needs.
For example, &KSpread; is a program for manipulating spreadsheets,
while &KWord; is a program for word processing. By focusing on a
specific area, each program aims for perfection in exactly this
area. However, depending on what you do with &KOffice;, you'll often 
want to take advantage of functionality provided by different applications, 
but in the <emphasis>same</emphasis> document.
</para>

<para>
Suppose that you are preparing a document in &KWord; and want to illustrate
some point using a table. While &KWord; provides its own functionality for
the insertion of tables, this may not be enough for your needs. For example,
you may want to use certain currency data formats or to do calculations using
spreadsheet formulae. Now, some &KWord; programmer certainly
<emphasis>could</emphasis> try to implement this functionality. However,
&KWord; would never be as good as &KSpread; in this field; and if it tried
to implement all the functionality you might possibly need, it would end up
becoming unreasonably complex and the source code would become impossible
to maintain.
</para>

<para>
The alternative to this is KParts. Its philosophy is simple: let every 
application do what it does best. [I think this para needs more
elaboration -- kt.]
</para>


<sect1 id="compounddocs">
<title>Compound documents with KParts</title>

<para> 
With KParts, your documents can use <emphasis>all</emphasis> functionality
offered by <emphasis>all</emphasis> &KOffice; applications. You can take
advantage of this by inserting so-called "parts" into your document. Every
one of those parts is essentially another document, that is, "a document
within a document". 
</para>

<para>
In the example mentioned above, you would simply insert a &KSpread;
part into your &KWord; document. Then, whenever you edit your table,
&KSpread; would take control in the background. Control would return to
&KWord; when you stop working on the table and start working on text
again. The only change you would notice is that the toolbars and
menus, while editing the table, reflect the functionality of &KSpread;
instead of that of &KWord;. This ability to include the functionality
of one application in another is called "embedding".
</para>

</sect1>


<sect1 id="kpartstryit">
<title>Using KParts in your document</title>

<para>
If you have never worked with compound documents, you may find them confusing
at first. The following step-by-step instructions show you that using
KParts is just as easy as working with a single application.
</para>

<procedure>
<title>Inserting a &KSpread; part into a &KWord; application</title>
<step><para>
Start &KWord;. You can do that either from the panel or by typing
<command>kword</command> at the command line.
</para></step>
<step><para>
Start a new, blank document. You may want to type some sample text.
</para></step>
<step><para>
Chose "Create KSpread table frame" from the "Tools" menu. (FIXME: I think
this menu structure was supposed to be changed). You'll notice that the mouse
cursor has changed to a cross. This form of the cursor indicates that you
are supposed to select an area.
</para></step>
<step><para>
Press the left mouse button where you want the upper left corner of
your table to be, hold it and drag it to the lower right corner. Release
the button. That's it--you're done.
</para></step>
</procedure>

<para>
Easy, isn't it? You should now see a table frame in your &KWord; document.
Now, click inside the table to see what happens. You'll notice that:
</para>

<itemizedlist>
<listitem><para>
Your menu bar and tool bars have changed. They now reflect those
of &KSpread;.
</para></listitem>
<listitem><para>
Your table frame now contains the elements of a &KSpread; view,
with scroll bars, a tab bar for the selection of tables, etc.
</para></listitem>
</itemizedlist>

<para>
Try editing the table. You'll see that it's not different from using
&KSpread;. In fact you <emphasis>are</emphasis> using &KSpread;.
</para>

<para>
Now click somewhere into your &KWord; document, outside of the table area.
The menu bar and tool bars should change back to those of &KWord;, the 
elements of the &KSpread; view should disappear. Your table stays and still
reflects all of the changes you've applied to it.
</para>

<para>
KParts are easy to use. Try inserting other parts or even parts in parts.
</para>

</sect1>


</chapter>


<chapter id="customization">
<title>Optimizing &KOffice; and Your System</title>

<para>
While &KOffice; should work quite nice out of the box, there may well be some things
to optimize to get the best out of &KOffice;. This chapter shows you what you might want to do
to achieve the best results with your new office suite.
</para>

<sect1 id="thefontissue"><title>Optimizing Font Output</title>
<para>
Fonts are a difficult topic on X Windows. In this section we'll cover some problems that are
frequently reported by people using &KOffice;. Some problems are not just &KOffice;s fault, but
depend on your system configuration, which is why you may need to modify system configuration
files in order to solve them. If you don't have access to the root account on your system, please
ask your system operator about this and point him or her to this manual. As the topic of fonts is
too complex to cover all of it here, you may want to consult the 
<ulink url="http://pegasus.rutgers.edu/~elflord/font_howto/html/">Font HOWTO</ulink> from which
I've taken the following information. You will find more details there.
</para>
<sect2><title>How to Get Nicely Scaled Fonts on Screen</title>
<para>
STUFF
</para>
</sect2>
<sect2><title>How to Get Correct Printout</title>
<para>
While &KOffice; automatically can handle all X11 fonts <emphasis>on screen</emphasis>, printout 
can pose a problem: on most systems, printing is done via <application>ghostscript</application>. Now,
while &KOffice; knows the font names used by X Windows, it does normally <emphasis>not</emphasis>
know the font names used by ghostscript. &KOffice; tries to guess these names, which unfortunately
doesn't work all of the time.
</para>
<para>
This problem can be solved, although this is not that easy. Actually, maybe you are using a distribution
which has done most work for you already (so if you have no reason to complain about printout you can
skip this section). What you have to do is to tell <application>ghostscript</application> how to 
translate the (guessed) font names &KOffice; uses to its own font names. This can be done by adding
lines to a file called <filename>Fontmap</filename>. An alias line in <filename>Fontmap</filename>
looks like the following example:</para>
<example><title>An alias in the ghostscript Fontmap</title>
<screen>
	/Algerian-Roman /Algerian       ;</screen>
</example>
<para>
Please note that a space before the ';' is mandatory. In this example, Algerian-Roman is the name 
&KOffice; uses for Algerian. You'll have to add such lines for the fonts &KOffice; doesn't display correctly.
To make this task easier, Donovan Rebbechi has written a perl script you can find at 
<ulink url="http://pegasus.rutgers.edu/~elflord/font_howto/kwdfont">http://pegasus.rutgers.edu/~elflord/font_howto/kwdfont</ulink>.
Assuming that you have a fontfile <filename>/usr/share/ghostscript/fonts/fontfile.ttf</filename> you'll enter
<screen>
kwdfont /usr/share/ghostscript/fonts/fontfile.ttf
</screen>
to get the appropriate aliases. The script should mork in most cases. As mentioned, you should
have a look at the <ulink url="http://pegasus.rutgers.edu/~elflord/font_howto/html/">Font HOWTO</ulink>
for more accurate and in-depth information.
</para>
</sect2>
</sect1>

<sect1 id="customgui">
<title>Customizing the &KOffice; GUI</title>

<para>
While &KOffice; comes out of the box with a GUI (graphical user interface)
that should suit most people's needs, there are good reasons why you may
want to change the way the programs look. My mother, for example, is a bit
afraid of buttons and menu entries she doesn't understand. To tailor &KOffice;
to her needs, I reduced the GUI to a bare minimum of functionality. As she
only needs to write letters and use certain templates, there is no need for
much more functionality than saving, loading, printing, etc.
</para>

<para>
Thanks to the "action" concept of Qt and KDE, you can freely customize
&KOffice; menu bars and tool bars. Unfortunately, at the moment, there are no
easy-to-use dialogs to do this. &KOffice; stores its GUI configuration in
XML files and you'll have to edit those. Hopefully, this situation will
change in the future; for now, you'll need some basic knowledge of how
an XML document works (or HTML, which is a subset of XML). [The
"action" concept needs to be discussed in more detail -- kt.]
</para>

<para>
Normally, each &KOffice; application has at least two of those XML files:
one describing the GUI of the shell (basically, that's what you see if
there is no document open) and one describing the GUI of the respective part
(that's what you see normally). For example, for &KWord;, these two XML files
are named <filename>kword_shell.rc</filename> and <filename>kword.rc</filename>.
</para>

<para> 
Here's a simple example of such an rc-file.
</para>

<example>
<title>An example of a simple rc-file</title>
<screen>
<![ CDATA [
<!DOCTYPE QConfig ><QConfig>
<MenuBar>
 <Menu name="Edit"><text>Edit</text>
  <Action name="edit_cut"/>
  <Action name="edit_copy"/>
  <Action name="edit_paste"/>
  <Separator/>
  <Action name="edit_find"/>
 </Menu>
 <Menu name="Insert"><text>Insert</text>
  <Action name="insert_picture"/>
  <Action name="insert_clipart"/>
  <Menu name="Variable"><text>Variable</text>
   <Action name="insert_var_datefix"/>
   <Action name="insert_var_datevar"/>
  </Menu>
 </Menu>
</MenuBar>
<ToolBars>
 <ToolBar name="edit_toolbar" position="right">
  <Action name="edit_cut"/>
  <Action name="edit_copy"/>
  <Action name="edit_paste"/>
 </ToolBar>
</ToolBars>
</QConfig>
]]>
</screen>
</example>

</sect1>

</chapter>


<chapter id="moreinfo">
<title>How to get more information</title>

<sect1 id="othermanuals">
<title>Other &KOffice; manuals</title>

<para>
For detailed information on the different &KOffice; applications,
please consult their respective manuals.
[FIXME: how do I provide links to them? Do we need set-tag?]
</para>

</sect1>


<sect1 id="links">
<title>Links</title>

<para>
The following links should be useful if you're looking for more information
about KDE or KOffice.
</para>

<itemizedlist>
<listitem><para>
<ulink url="http://koffice.kde.org">The &KOffice; homepage</ulink>. Here you
can find information on how to get and install &KOffice;, news about &KOffice;
development, screenshots etc.
</para></listitem>
<listitem><para>
<ulink url="http://www.kde.org">The K Desktop Environment (KDE)</ulink>. The
most advanced and absolutely free desktop environment for unix-like operating
systems. &KOffice; makes use of the KDE libraries.
</para></listitem>
<listitem><para>
<ulink url="http://www.troll.no">Troll Tech</ulink>. The creators of the
C++-toolkit Qt. KDE and &KOffice; make use of Qt.
</para></listitem>
</itemizedlist>

</sect1>

</chapter>


<chapter id="programmersinfo">
<title>Programming &KOffice;</title>

<para>
If you want to do &KOffice; development, the following resources
might be of interest:
</para>

<itemizedlist>
<listitem><para>
At <ulink url="http://developer.kde.org">http://developer.kde.org</ulink>
you'll find many documents about programming with Qt and KDE. Here you can
find the online version of the complete KDE library documentation.
</para></listitem>
<listitem><para>
Use <application>kdoc</application> (in the <filename>kdoc</filename>
CVS module) to generate your own KDE library documentation.
</para></listitem>
<listitem><para>
In the &KOffice; sources you'll find an example application
in the <filename>example</filename> directory.
</para></listitem>
</itemizedlist>

</chapter>


<chapter id="faq">
<title>Frequently Asked Questions</title>

<para>
</para>

</chapter>


<chapter id="legal">
<title>Copyright and Licensing</title>

<para>
KOffice is copyrighted by the KOffice team.
KOffice is licensed mainly under the terms of the
<ulink url="common/gpl-license.html">GNU GPL</ulink>.
</para>

<para>
Some programs are licensed under the terms of the
Artistic License. FIXME: put artistic-license.html in common!
</para>

<para>
This manual is copyright by Jost Schenck. It can be distributed
freely, as long as this copyright notice is included. You may change
it as long as you send me the changes or commit them to KDE CVS.
I'll not be liable for anything resulting from the use of this
manual.
</para>

<para>
The other KOffice manuals are copyrighted by their respective authors.
</para>

</chapter>


<glossary id="glossary">
<title>Glossary</title>
<!-- To be put into the glossary:
embedding, XML, MORE! -->

<glossdiv><title>?</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>A</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>B</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>C</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>D</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>E</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>F</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>G</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>H</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>I</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>J</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>K</title>
<glossentry id="glosskde">
<glossterm>KDE</glossterm>
<glossdef><para>
The K Desktop Environment (<acronym>KDE</acronym>) is a completely
free desktop environment for unix-like operating systems.
&KOffice; uses the KDE-2.0 libraries. See
<ulink url="http://www.kde.org">http://www.kde.org</ulink>
for details.
</para></glossdef>
</glossentry>
<glossentry id="glosskparts">
<glossterm>KParts</glossterm>
<glossdef><para>
KParts is a technology that allows the embedding of components
("<link linkend="glosspart">parts</link>") in an application.
This way, you can create compound documents in &KOffice;,
e.g. a &KWord; document containing a &KSpread; table.
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>L</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>M</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>N</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>O</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>P</title>
<glossentry id="glosspart">
<glossterm>Part</glossterm>
<glossdef><para>
A part is an application which can be embedded into other
<link linkend="glosskparts">KParts</link> applications.
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>Q</title>
<glossentry id="glossqt">
<glossterm>Qt</glossterm>
<glossdef><para>
Qt is the underlying toolkit that was used for KDE and &KOffice;.
See <ulink url="http://www.troll.no">http://www.troll.no</ulink>
for details.
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>R</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>S</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>T</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>U</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>V</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>W</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>X</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>Y</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

<glossdiv><title>Z</title>
<glossentry>
<glossterm>
</glossterm>
<glossdef><para>
</para></glossdef>
</glossentry>
</glossdiv>

</glossary>


<![ %addindex; [ &kdedocindex; ]]>
</book>
