index.docbook

来自「KDE下的西门子手机管理程序」· DOCBOOK 代码 · 共 525 行 · 第 1/2 页

<!DOCTYPE book PUBLIC  "-//KDE//DTD DocBook V3.1-Based Variant V1.0//EN" [
 <!ENTITY ksiemens  "<application>ksiemens</application>">
 <!ENTITY % addindex "IGNORE">
 <![ %addindex; [ <!ENTITY kdedocindex SYSTEM "docindex.docbook"> ]]>
]>
<!-- kdoctemplate v0.8 October 1 1999 -->

<!--
This template was designed by: David Rugge [e-mail]
with lots of help from: Eric Bischoff [e-mail]
and Frederik Fouvry [e-mail]
of the KDE DocBook team.

You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.

In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags> and attributes is relevant ;
- also, quote all attributes.

Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->

<!-- ---------------------------------------------------------------- -->

<!-- The language must be changed in the <book> tag for translations. -->

<book id="ksiemens" lang="en">

<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->

<bookinfo>

<title>The KSiemens Handbook</title>

<authorgroup>
<author>
<firstname></firstname>
<othername></othername>
<surname>Matthias Welwarsky</surname>
</author>
</authorgroup>

<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
 of your application, and a few relevant keywords. -->

<keywordset>
<keyword>KDE</keyword>
<keyword>KSiemens</keyword>
</keywordset>

<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(Major.minor.lesser), it could be used by automation scripts -->

<date>Wed Jan 17 10:34:49 CET 2001</date>
<releaseinfo>0.1</releaseinfo>

<!-- Brief revision history.
Unlike the preceeding information, this is not mandatory.
Try to keep this section brief.
This is the history of the *documentation* (the history of the *application*
goes to the introduction), but nothing prevents you from using the same
release numbers for both the application the documentation. 
-->

<revhistory>
<revision>
<revnumber></revnumber>
<date></date>
<authorinitials></authorinitials>
<revremark>Cleaned up a few typos.
</revremark>
</revision>
<revision>
<revnumber>0.1
</revnumber>
<date>Wed Jan 17 10:34:49 CET 2001</date>
<authorinitials></authorinitials>
<revremark>Initial release.
</revremark>
</revision>
</revhistory>

<!-- Abstract about this handbook -->

<abstract>
<para>
This Handbook describes <application>KSiemens</application> Version 0.1
<application>KSiemens</application>
</para>
</abstract>

</bookinfo>

<!-- The contents of the documentation beginS here.  Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->

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

<!-- The introduction chapter contains a brief introduction for the application
that explains what it does, where to get new versions of the app, where to
report problems, and a brief revision history of the app. Basically a long
version of the abstract. -->

<para>
The complete user manual to <application>KSiemens</application>, version 0.1
</para>

<!-- Note that the revhistory tags apply to the documentation version and not to
the app version. That is why we use an ItemizedList here. -->

<sect1 id="ksiemens-revhistory">
<title>KSiemens Revision History</title>
<para>
<itemizedlist>
<listitem><para>
0.1 - first public release
</para></listitem>
</itemizedlist>
</para>
</sect1>
</chapter>

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

<sect1 id="getting-ksiemens">
<title>How to obtain KSiemens</title>

<para>
<application>KSiemens</application> is part of the KDE project
<ulink url="http://www.kde.org">http://www.kde.org</ulink>.
<application>KSiemens</application> can be found on
<ulink url="ftp://ftp.kde.org/pub/kde/">ftp://ftp.kde.org/pub/kde/</ulink>, the
main ftp site of the KDE project. </para>
</sect1>

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

<!--
List any special requirements for your application here. This should include:
.Libraries or other software that is not included in kdesupport,
kdelibs, or kdebase.
.Hardware requirements like amount of RAM, disk space, graphics card
capabilities, screen resolution, special expansion cards, etc.
.Operating systems the app will run on. If your app is designed only for a
specific OS, (you wrote a graphical LILO configurator for example) put this
information here.
-->

<para>
In order to successfully use <application>KSiemens</application>, you need KDE 1.1. Foobar.lib is required
in order to support the advanced <application>KSiemens</application> features. <application>KSiemens</application> uses about 5 megs of
memory to run, but this may vary depending on your platform and
configuration.
</para>

<para>
All required libraries as well as <application>KSiemens</application> itself can be found
on <ulink url="ftp://ftp.kapp.org"> The <application>KSiemens</application> home page</ulink>.
</para>

</sect1>

<sect1 id="compilation">
<title>Compilation and installation</title>

<para>
In order to compile and install KSiemens on your system, type the following in the base
directory of the KSiemens distribution:
<screen width="40">
<prompt>%</prompt> <userinput>./configure</userinput>
<prompt>%</prompt> <userinput>make</userinput>
<prompt>%</prompt> <userinput>make install</userinput>
</screen>
</para>

<para>Since KSiemens uses autoconf and automake you should have not trouble compiling it.
Should you run into problems please report them to the author at <ulink url="mailto:[e-mail]"> Matthias Welwarsky</ulink>.</para>

</sect1>

<sect1 id="configuration">
<title>Configuration</title>

<para>Don't forget to tell your system to start the <filename>dtd</filename>
dicer-toaster daemon first, or KSiemens won't work !</para>

</sect1>

</chapter>

<chapter id="using-kapp">
<title>Using KSiemens</title>

<!-- This chapter should tell the user how to use your app. You should use as
many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
your application. -->

<para>

<!-- Note that all graphics should be in .png format. Use no gifs because of
patent issues. -->

<screenshot>
<screeninfo>Here's a screenshot of <application>KSiemens</application></screeninfo>
<graphic fileref="screenshot.png" format="png"></graphic>
</screenshot>
</para>


<sect1 id="kapp-features">
<title>More KSiemens features</title>

<para>It slices! It dices! and it comes with a free toaster!</para>
<para>
The Squiggle Tool <guiicon><inlinegraphic fileref="squiggle.png" format="png"></inlinegraphic></guiicon> is used to draw squiggly lines all
over the <application>KSiemens</application> main window. It's not a bug, it's a feature!
</para>

</sect1>
</chapter>

<chapter id="commands">
<title>Command Reference</title>

<!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of the
application windows and their menubar and toolbar commands for easy reference.
Also include any keys that have a special function but have no equivalent in the
menus or toolbars. This may not be necessary for small apps or apps with no tool
or menu bars. -->

<para></para>

<sect1 id="kapp-mainwindow">
<title>The main KSiemens window</title>
<para></para>

<sect2>
<title>The File Menu</title>
<para>
<variablelist>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>n</keycap></keycombo>
</shortcut>
<guimenu>File</guimenu>