Up to this point in the documentation, we have been focusing on text. That is about to change!
This chapter will discuss inserting a table of contents, graphics, page numbers, links to web pages and how to insert other types of KOffice data into a document.
This chapter will also cover document information and its relationship to document variables.
KWord can store information about the author and the document in the same file as the text and data of the document.
Entering this information into KWord has two potential benefits:
This information will always be available for reference. This is especially important in situations where there are many possible authors (employees) and hundreds (or thousands) of documents.
The information supplied here, can be inserted automatically into the document as a document variable.
To enter document information, simply select -> from the menubar. This will bring up a dialog box with two tabs.
The first tab is labeled Author and has blanks to enter the authors name, title, company and contact information (email address, telephone numbers and physical address).
Every value entered in this dialog can be inserted as a document variables.
At the bottom of the dialog is a button labeled . Clicking on this button will automatically insert your information contained in the KDE address book into this KWord document information dialog.
You must inform the KDE address book which entry corresponds to your information.
To do this, open the KDE address book, select the entry that contains your name and address. Now select ->from the menubar in the KDE address book. This only needs to be performed once.
KWord will now insert the entered information when the button is clicked.
The second tab is labeled Document. Enter a document title, subject lines, keywords and an abstract.
Both the document title and the abstract can be accessed through document variables.
When finished entering the information, click to apply the changes. If any document variables were changed, KWord will update their values throughout the document.
Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team