Optimizing and Your System
While should work quite nice out of the box, there may well be some things to optimize to get the best out of . This chapter shows you what you might want to do to achieve the best results with your new office suite.

Optimizing Font Output
Fonts are a difficult topic on X Windows. In this section we'll cover some problems that are frequently reported by people using . Some problems are not just 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 Font HOWTO from which I've taken the following information. You will find more details there.

How to Get Nicely Scaled Fonts on Screen
STUFF

How to Get Correct Printout
While automatically can handle all X11 fonts on screen, printout can pose a problem: on most systems, printing is done via ghostscript. Now, while knows the font names used by X Windows, it does normally not know the font names used by ghostscript. tries to guess these names, which unfortunately doesn't work all of the time.
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 ghostscript how to translate the (guessed) font names uses to its own font names. This can be done by adding lines to a file called Fontmap. An alias line in Fontmap looks like the following example:

An alias in the ghostscript Fontmap

/Algerian-Roman /Algerian       ;

Please note that a space before the ';' is mandatory. In this example, Algerian-Roman is the name uses for Algerian. You'll have to add such lines for the fonts doesn't display correctly. To make this task easier, Donovan Rebbechi has written a perl script you can find at http://pegasus.rutgers.edu/~elflord/font_howto/kwdfont. Assuming that you have a fontfile /usr/share/ghostscript/fonts/fontfile.ttf you'll enter kwdfont /usr/share/ghostscript/fonts/fontfile.ttf to get the appropriate aliases. The script should mork in most cases. As mentioned, you should have a look at the Font HOWTO for more accurate and in-depth information.

Customizing the
While comes out of the box with a (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 to her needs, I reduced the 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,
Thanks to the action concept of and , you can freely customize menu bars and tool bars. Unfortunately, at the moment, there are no easy-to-use dialogs to do this. stores its configuration in 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 document works (or HTML, which is a subset of ). [The action concept needs to be discussed in more detail -- kt.]
Normally, each application has at least two of those files: one describing the of the shell (basically, that's what you see if there is no document open) and one describing the of the respective part (that's what you see normally). For example, for , these two files are named kword_shell.rc and kword.rc.
Here's a simple example of such an rc-file.

An example of a simple rc-file

<!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>