summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authortoma <toma@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2009-11-25 17:56:58 +0000
committertoma <toma@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2009-11-25 17:56:58 +0000
commit4aed2c8219774f5d797760606b8489a92ddc5163 (patch)
tree3f8c130f7d269626bf6a9447407ef6c35954426a /doc
downloadtdebase-4aed2c8219774f5d797760606b8489a92ddc5163.tar.gz
tdebase-4aed2c8219774f5d797760606b8489a92ddc5163.zip
Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.
BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdebase@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Diffstat (limited to 'doc')
-rw-r--r--doc/Makefile.am5
-rw-r--r--doc/faq/Makefile.am4
-rw-r--r--doc/faq/TODO35
-rw-r--r--doc/faq/about.docbook72
-rw-r--r--doc/faq/configkde.docbook250
-rw-r--r--doc/faq/contrib.docbook164
-rw-r--r--doc/faq/desktop.docbook97
-rw-r--r--doc/faq/filemng.docbook207
-rw-r--r--doc/faq/getkde.docbook79
-rw-r--r--doc/faq/index.docbook136
-rw-r--r--doc/faq/install.docbook726
-rw-r--r--doc/faq/intro.docbook93
-rw-r--r--doc/faq/kdeapps.docbook158
-rw-r--r--doc/faq/misc.docbook219
-rw-r--r--doc/faq/moreinfo.docbook154
-rw-r--r--doc/faq/nonkdeapps.docbook106
-rw-r--r--doc/faq/notrelated.docbook232
-rw-r--r--doc/faq/panel.docbook193
-rw-r--r--doc/faq/qt.docbook76
-rw-r--r--doc/faq/questions.docbook160
-rw-r--r--doc/faq/sound.docbook55
-rw-r--r--doc/faq/tips.docbook137
-rw-r--r--doc/faq/webbrowse.docbook222
-rw-r--r--doc/faq/winmng.docbook134
-rw-r--r--doc/glossary/Makefile.am2
-rwxr-xr-xdoc/glossary/checkxrefs10
-rw-r--r--doc/glossary/index.docbook296
-rw-r--r--doc/glossary/kdeprintingglossary.docbook1387
-rw-r--r--doc/kappfinder/Makefile.am5
-rw-r--r--doc/kappfinder/man-kappfinder.1.docbook81
-rw-r--r--doc/kate/Makefile.am3
-rw-r--r--doc/kate/TODO6
-rw-r--r--doc/kate/advanced.docbook1242
-rw-r--r--doc/kate/configdialog01.pngbin0 -> 44641 bytes
-rw-r--r--doc/kate/configdialog02.pngbin0 -> 25384 bytes
-rw-r--r--doc/kate/configuring.docbook1595
-rw-r--r--doc/kate/fundamentals.docbook621
-rw-r--r--doc/kate/highlighted.pngbin0 -> 4797 bytes
-rw-r--r--doc/kate/highlighting.docbook931
-rw-r--r--doc/kate/index.docbook293
-rw-r--r--doc/kate/kate.pngbin0 -> 81016 bytes
-rw-r--r--doc/kate/man-kate.1.docbook165
-rw-r--r--doc/kate/mdi.docbook266
-rw-r--r--doc/kate/menus.docbook1438
-rw-r--r--doc/kate/mimetypechooser.pngbin0 -> 15823 bytes
-rw-r--r--doc/kate/part.docbook671
-rw-r--r--doc/kate/plugins.docbook28
-rw-r--r--doc/kate/regular-expressions.docbook664
-rw-r--r--doc/kate/unhighlighted.pngbin0 -> 3471 bytes
-rw-r--r--doc/kcontrol/Makefile.am6
-rw-r--r--doc/kcontrol/arts/Makefile.am2
-rw-r--r--doc/kcontrol/arts/index.docbook201
-rw-r--r--doc/kcontrol/arts/midi.docbook24
-rw-r--r--doc/kcontrol/background/Makefile.am2
-rw-r--r--doc/kcontrol/background/index.docbook383
-rw-r--r--doc/kcontrol/bell/Makefile.am2
-rw-r--r--doc/kcontrol/bell/index.docbook74
-rw-r--r--doc/kcontrol/cache/Makefile.am2
-rw-r--r--doc/kcontrol/cache/index.docbook69
-rw-r--r--doc/kcontrol/clock/Makefile.am2
-rw-r--r--doc/kcontrol/clock/index.docbook74
-rw-r--r--doc/kcontrol/colors/Makefile.am2
-rw-r--r--doc/kcontrol/colors/index.docbook132
-rw-r--r--doc/kcontrol/cookies/Makefile.am2
-rw-r--r--doc/kcontrol/cookies/index.docbook211
-rw-r--r--doc/kcontrol/crypto/Makefile.am2
-rw-r--r--doc/kcontrol/crypto/index.docbook205
-rw-r--r--doc/kcontrol/desktop/Makefile.am2
-rw-r--r--doc/kcontrol/desktop/index.docbook84
-rw-r--r--doc/kcontrol/desktopbehavior/Makefile.am2
-rw-r--r--doc/kcontrol/desktopbehavior/index.docbook198
-rw-r--r--doc/kcontrol/ebrowsing/Makefile.am2
-rw-r--r--doc/kcontrol/ebrowsing/index.docbook156
-rw-r--r--doc/kcontrol/email/Makefile.am2
-rw-r--r--doc/kcontrol/email/index.docbook103
-rw-r--r--doc/kcontrol/energy/Makefile.am2
-rw-r--r--doc/kcontrol/energy/index.docbook110
-rw-r--r--doc/kcontrol/filemanager/Makefile.am2
-rw-r--r--doc/kcontrol/filemanager/index.docbook297
-rw-r--r--doc/kcontrol/filemanager/kfileman1.pngbin0 -> 7883 bytes
-rw-r--r--doc/kcontrol/filemanager/kfileman2.pngbin0 -> 9224 bytes
-rw-r--r--doc/kcontrol/filetypes/Makefile.am2
-rw-r--r--doc/kcontrol/filetypes/index.docbook338
-rw-r--r--doc/kcontrol/fonts/Makefile.am2
-rw-r--r--doc/kcontrol/fonts/index.docbook121
-rw-r--r--doc/kcontrol/helpindex/Makefile.am2
-rw-r--r--doc/kcontrol/helpindex/index.docbook144
-rw-r--r--doc/kcontrol/icons/Makefile.am2
-rw-r--r--doc/kcontrol/icons/index.docbook233
-rw-r--r--doc/kcontrol/index.docbook637
-rw-r--r--doc/kcontrol/kcmaccess/Makefile.am4
-rw-r--r--doc/kcontrol/kcmaccess/index.docbook179
-rw-r--r--doc/kcontrol/kcmcss/Makefile.am2
-rw-r--r--doc/kcontrol/kcmcss/index.docbook257
-rw-r--r--doc/kcontrol/kcmfontinst/Makefile.am2
-rw-r--r--doc/kcontrol/kcmfontinst/index.docbook76
-rw-r--r--doc/kcontrol/kcmkonsole/Makefile.am2
-rw-r--r--doc/kcontrol/kcmkonsole/index.docbook177
-rw-r--r--doc/kcontrol/kcmlaunch/Makefile.am2
-rw-r--r--doc/kcontrol/kcmlaunch/index.docbook70
-rw-r--r--doc/kcontrol/kcmnotify/Makefile.am2
-rw-r--r--doc/kcontrol/kcmnotify/index.docbook151
-rw-r--r--doc/kcontrol/kcmsmserver/Makefile.am2
-rw-r--r--doc/kcontrol/kcmsmserver/index.docbook109
-rw-r--r--doc/kcontrol/kcmstyle/Makefile.am2
-rw-r--r--doc/kcontrol/kcmstyle/index.docbook189
-rw-r--r--doc/kcontrol/kcmtaskbar/Makefile.am2
-rw-r--r--doc/kcontrol/kcmtaskbar/index.docbook142
-rw-r--r--doc/kcontrol/kdm/Makefile.am2
-rw-r--r--doc/kcontrol/kdm/index.docbook518
-rw-r--r--doc/kcontrol/keyboard/Makefile.am2
-rw-r--r--doc/kcontrol/keyboard/index.docbook90
-rw-r--r--doc/kcontrol/keys/Makefile.am2
-rw-r--r--doc/kcontrol/keys/index.docbook191
-rw-r--r--doc/kcontrol/khtml/Makefile.am2
-rw-r--r--doc/kcontrol/khtml/index.docbook352
-rw-r--r--doc/kcontrol/khtml/nsplugin.docbook91
-rw-r--r--doc/kcontrol/kwindecoration/Makefile.am2
-rw-r--r--doc/kcontrol/kwindecoration/index.docbook98
-rw-r--r--doc/kcontrol/language/Makefile.am2
-rw-r--r--doc/kcontrol/language/index.docbook218
-rw-r--r--doc/kcontrol/mouse/Makefile.am2
-rw-r--r--doc/kcontrol/mouse/index.docbook493
-rw-r--r--doc/kcontrol/netpref/Makefile.am2
-rw-r--r--doc/kcontrol/netpref/index.docbook109
-rw-r--r--doc/kcontrol/panel/Makefile.am2
-rw-r--r--doc/kcontrol/panel/index.docbook244
-rw-r--r--doc/kcontrol/panelappearance/Makefile.am3
-rw-r--r--doc/kcontrol/panelappearance/index.docbook122
-rw-r--r--doc/kcontrol/passwords/Makefile.am2
-rw-r--r--doc/kcontrol/passwords/index.docbook84
-rw-r--r--doc/kcontrol/performance/Makefile.am2
-rw-r--r--doc/kcontrol/performance/index.docbook102
-rw-r--r--doc/kcontrol/proxy/Makefile.am2
-rw-r--r--doc/kcontrol/proxy/index.docbook197
-rw-r--r--doc/kcontrol/proxy/socks.docbook56
-rw-r--r--doc/kcontrol/screensaver/Makefile.am2
-rw-r--r--doc/kcontrol/screensaver/index.docbook203
-rw-r--r--doc/kcontrol/screenshot.pngbin0 -> 103581 bytes
-rw-r--r--doc/kcontrol/smb/Makefile.am2
-rw-r--r--doc/kcontrol/smb/index.docbook106
-rw-r--r--doc/kcontrol/spellchecking/Makefile.am2
-rw-r--r--doc/kcontrol/spellchecking/index.docbook88
-rw-r--r--doc/kcontrol/useragent/Makefile.am2
-rw-r--r--doc/kcontrol/useragent/index.docbook117
-rw-r--r--doc/kcontrol/windowmanagement/Makefile.am2
-rw-r--r--doc/kcontrol/windowmanagement/index.docbook63
-rw-r--r--doc/kdcop/Makefile.am4
-rw-r--r--doc/kdcop/index.docbook78
-rw-r--r--doc/kdebugdialog/Makefile.am3
-rw-r--r--doc/kdebugdialog/index.docbook134
-rw-r--r--doc/kdeprint/Makefile.am3
-rw-r--r--doc/kdeprint/add-printer-wiz.docbook290
-rw-r--r--doc/kdeprint/cr32-action-wizard.pngbin0 -> 606 bytes
-rw-r--r--doc/kdeprint/cups-config.docbook2072
-rw-r--r--doc/kdeprint/cups-filterarchitecture-kivio-70Percent-scaled.pngbin0 -> 100464 bytes
-rw-r--r--doc/kdeprint/cupsaddprinterwizard1.pngbin0 -> 70554 bytes
-rw-r--r--doc/kdeprint/cupsaddprinterwizard2_backendselection.pngbin0 -> 76444 bytes
-rw-r--r--doc/kdeprint/cupsaddprinterwizard3_networkscan.pngbin0 -> 70820 bytes
-rw-r--r--doc/kdeprint/cupsaddprinterwizard3_networkscan_results.pngbin0 -> 90883 bytes
-rw-r--r--doc/kdeprint/cupsaddprinterwizard4_networkscan_config.pngbin0 -> 10607 bytes
-rw-r--r--doc/kdeprint/cupsoptions.docbook602
-rw-r--r--doc/kdeprint/cupsserverconfig_browse_relay_add_button.pngbin0 -> 2562 bytes
-rw-r--r--doc/kdeprint/cupsserverconfig_browsingmasks_add_button.pngbin0 -> 2294 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration10_browsinggeneral.pngbin0 -> 14678 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration11_browsingconnections.pngbin0 -> 15433 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration11_browsingmasks.pngbin0 -> 15493 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration12_browsingtimeouts.pngbin0 -> 14109 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration14_browsingrelay.pngbin0 -> 14903 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration15a_resourceallprinters_defineaccess.pngbin0 -> 15822 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration15b_resourceallprinters_defineaccess.pngbin0 -> 5870 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration15c_resourceallprinters_defineaccess.pngbin0 -> 5470 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration1_welcome.pngbin0 -> 31316 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration2_general.pngbin0 -> 15870 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration3_logging.pngbin0 -> 16490 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration4_directories.pngbin0 -> 17728 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration5_HTTP.pngbin0 -> 15010 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration6_encryption.pngbin0 -> 15083 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration7_miscellanious.pngbin0 -> 15943 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration8_networkgeneral.pngbin0 -> 15538 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration9_networkclients.pngbin0 -> 14998 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration_resourceadminaccessmasks.pngbin0 -> 47480 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration_resourceadminaddprinters.pngbin0 -> 30334 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration_resourceadminaddprinters_defineaccess.pngbin0 -> 43890 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration_resourceadminauthorization.pngbin0 -> 30503 bytes
-rw-r--r--doc/kdeprint/cupsserverconfiguration_securityoverview.pngbin0 -> 16804 bytes
-rw-r--r--doc/kdeprint/extensions.docbook57
-rw-r--r--doc/kdeprint/external-command.docbook25
-rw-r--r--doc/kdeprint/final-word.docbook117
-rw-r--r--doc/kdeprint/getting-started.docbook143
-rw-r--r--doc/kdeprint/highlights.docbook518
-rw-r--r--doc/kdeprint/index.docbook200
-rw-r--r--doc/kdeprint/kcontrol-icon.pngbin0 -> 1202 bytes
-rw-r--r--doc/kdeprint/kcontrolcenter-printmanager-jobcontrol-2.pngbin0 -> 10761 bytes
-rw-r--r--doc/kdeprint/kcron_to_be_printed.pngbin0 -> 10637 bytes
-rw-r--r--doc/kdeprint/kdeprint-jobviewer.pngbin0 -> 11220 bytes
-rw-r--r--doc/kdeprint/kprinter-as-netscape-printcommand.pngbin0 -> 8210 bytes
-rw-r--r--doc/kdeprint/kprinter-kivio.pngbin0 -> 11149 bytes
-rw-r--r--doc/kdeprint/kprinter.pngbin0 -> 12568 bytes
-rw-r--r--doc/kdeprint/kprinter_called_from_run_command.pngbin0 -> 6068 bytes
-rw-r--r--doc/kdeprint/kprinter_with_kcron_developer_special.pngbin0 -> 11245 bytes
-rw-r--r--doc/kdeprint/lpd.docbook18
-rw-r--r--doc/kdeprint/lpr-bsd.docbook25
-rw-r--r--doc/kdeprint/lprng.docbook7
-rw-r--r--doc/kdeprint/ps-boxes.pngbin0 -> 441 bytes
-rw-r--r--doc/kdeprint/rlpr.docbook18
-rw-r--r--doc/kdeprint/steinbruch_scaled.pngbin0 -> 116567 bytes
-rw-r--r--doc/kdeprint/tech-overview.docbook280
-rw-r--r--doc/kdeprint/theory.docbook690
-rw-r--r--doc/kdesu/Makefile.am5
-rw-r--r--doc/kdesu/index.docbook320
-rw-r--r--doc/kdesu/man-kdesu.1.docbook179
-rw-r--r--doc/kdm/Makefile.am6
-rw-r--r--doc/kdm/index.docbook1472
-rw-r--r--doc/kdm/kdmrc-ref.docbook2316
-rw-r--r--doc/kfind/Makefile.am4
-rw-r--r--doc/kfind/index.docbook363
-rw-r--r--doc/kfind/man-kfind.1.docbook79
-rw-r--r--doc/khelpcenter/Makefile.am6
-rw-r--r--doc/khelpcenter/background.pngbin0 -> 128431 bytes
-rw-r--r--doc/khelpcenter/bgtable.pngbin0 -> 25929 bytes
-rw-r--r--doc/khelpcenter/contact.docbook138
-rw-r--r--doc/khelpcenter/help.docbook740
-rw-r--r--doc/khelpcenter/index.docbook82
-rw-r--r--doc/khelpcenter/kdelogo2.pngbin0 -> 6833 bytes
-rw-r--r--doc/khelpcenter/khelpcenter.pngbin0 -> 1687 bytes
-rw-r--r--doc/khelpcenter/konq.css68
-rw-r--r--doc/khelpcenter/lines.pngbin0 -> 259 bytes
-rw-r--r--doc/khelpcenter/lines2.pngbin0 -> 198 bytes
-rw-r--r--doc/khelpcenter/pointers.pngbin0 -> 268 bytes
-rw-r--r--doc/khelpcenter/shadow1.pngbin0 -> 184 bytes
-rw-r--r--doc/khelpcenter/support.docbook102
-rw-r--r--doc/khelpcenter/welcome.docbook60
-rw-r--r--doc/khelpcenter/whatiskde.docbook129
-rw-r--r--doc/kicker/Makefile.am5
-rw-r--r--doc/kicker/bookmarks_icon.pngbin0 -> 2272 bytes
-rw-r--r--doc/kicker/desktop_icon.pngbin0 -> 6881 bytes
-rw-r--r--doc/kicker/index.docbook2434
-rw-r--r--doc/kicker/k_menu_icon.pngbin0 -> 5340 bytes
-rw-r--r--doc/kicker/man-appletproxy.1.docbook101
-rw-r--r--doc/kicker/man-kicker.1.docbook88
-rw-r--r--doc/kicker/printsys_icon.pngbin0 -> 2588 bytes
-rw-r--r--doc/kicker/quickbrowser_icon.pngbin0 -> 3482 bytes
-rw-r--r--doc/kicker/recent_docs_icon.pngbin0 -> 3271 bytes
-rw-r--r--doc/kicker/screenshot_left.pngbin0 -> 18674 bytes
-rw-r--r--doc/kicker/screenshot_right.pngbin0 -> 11764 bytes
-rw-r--r--doc/kicker/taskbar_group.pngbin0 -> 4496 bytes
-rw-r--r--doc/kicker/terminals_icon.pngbin0 -> 2009 bytes
-rw-r--r--doc/kicker/windowlist_icon.pngbin0 -> 2801 bytes
-rw-r--r--doc/kinfocenter/Makefile.am6
-rw-r--r--doc/kinfocenter/cdinfo/Makefile.am3
-rw-r--r--doc/kinfocenter/cdinfo/index.docbook51
-rw-r--r--doc/kinfocenter/devices/Makefile.am3
-rw-r--r--doc/kinfocenter/devices/index.docbook60
-rw-r--r--doc/kinfocenter/dma/Makefile.am3
-rw-r--r--doc/kinfocenter/dma/index.docbook64
-rw-r--r--doc/kinfocenter/index.docbook341
-rw-r--r--doc/kinfocenter/interrupts/Makefile.am3
-rw-r--r--doc/kinfocenter/interrupts/index.docbook70
-rw-r--r--doc/kinfocenter/ioports/Makefile.am3
-rw-r--r--doc/kinfocenter/ioports/index.docbook64
-rw-r--r--doc/kinfocenter/memory/Makefile.am3
-rw-r--r--doc/kinfocenter/memory/index.docbook108
-rw-r--r--doc/kinfocenter/nics/Makefile.am3
-rw-r--r--doc/kinfocenter/nics/index.docbook45
-rw-r--r--doc/kinfocenter/opengl/Makefile.am2
-rw-r--r--doc/kinfocenter/opengl/index.docbook47
-rw-r--r--doc/kinfocenter/partitions/Makefile.am3
-rw-r--r--doc/kinfocenter/partitions/index.docbook56
-rw-r--r--doc/kinfocenter/pci/Makefile.am3
-rw-r--r--doc/kinfocenter/pci/index.docbook57
-rw-r--r--doc/kinfocenter/pcmcia/Makefile.am3
-rw-r--r--doc/kinfocenter/pcmcia/index.docbook38
-rw-r--r--doc/kinfocenter/processor/Makefile.am3
-rw-r--r--doc/kinfocenter/processor/index.docbook56
-rw-r--r--doc/kinfocenter/protocols/Makefile.am3
-rw-r--r--doc/kinfocenter/protocols/index.docbook39
-rw-r--r--doc/kinfocenter/samba/Makefile.am4
-rw-r--r--doc/kinfocenter/samba/index.docbook207
-rw-r--r--doc/kinfocenter/scsi/Makefile.am3
-rw-r--r--doc/kinfocenter/scsi/index.docbook56
-rw-r--r--doc/kinfocenter/sound/Makefile.am3
-rw-r--r--doc/kinfocenter/sound/index.docbook51
-rw-r--r--doc/kinfocenter/usb/Makefile.am3
-rw-r--r--doc/kinfocenter/usb/index.docbook43
-rw-r--r--doc/kinfocenter/xserver/Makefile.am3
-rw-r--r--doc/kinfocenter/xserver/index.docbook56
-rw-r--r--doc/kioslave/Makefile.am4
-rw-r--r--doc/kioslave/bzip.docbook29
-rw-r--r--doc/kioslave/bzip2.docbook29
-rw-r--r--doc/kioslave/cgi.docbook24
-rw-r--r--doc/kioslave/data.docbook47
-rw-r--r--doc/kioslave/file.docbook20
-rw-r--r--doc/kioslave/finger.docbook33
-rw-r--r--doc/kioslave/fish.docbook66
-rw-r--r--doc/kioslave/floppy.docbook51
-rw-r--r--doc/kioslave/ftp.docbook43
-rw-r--r--doc/kioslave/gopher.docbook39
-rw-r--r--doc/kioslave/gzip.docbook30
-rw-r--r--doc/kioslave/help.docbook17
-rw-r--r--doc/kioslave/http.docbook25
-rw-r--r--doc/kioslave/https.docbook21
-rw-r--r--doc/kioslave/imap.docbook31
-rw-r--r--doc/kioslave/imaps.docbook17
-rw-r--r--doc/kioslave/index.docbook93
-rw-r--r--doc/kioslave/info.docbook36
-rw-r--r--doc/kioslave/lan.docbook23
-rw-r--r--doc/kioslave/ldap.docbook23
-rw-r--r--doc/kioslave/mac.docbook53
-rw-r--r--doc/kioslave/mailto.docbook17
-rw-r--r--doc/kioslave/man.docbook86
-rw-r--r--doc/kioslave/mrml.docbook26
-rw-r--r--doc/kioslave/news.docbook20
-rw-r--r--doc/kioslave/nfs.docbook39
-rw-r--r--doc/kioslave/nntp.docbook41
-rw-r--r--doc/kioslave/pop3.docbook13
-rw-r--r--doc/kioslave/pop3s.docbook14
-rw-r--r--doc/kioslave/print.docbook170
-rw-r--r--doc/kioslave/rlan.docbook11
-rw-r--r--doc/kioslave/rlogin.docbook31
-rw-r--r--doc/kioslave/sftp.docbook19
-rw-r--r--doc/kioslave/smb.docbook56
-rw-r--r--doc/kioslave/smtp.docbook16
-rw-r--r--doc/kioslave/tar.docbook18
-rw-r--r--doc/kioslave/telnet.docbook17
-rw-r--r--doc/kioslave/thumbnail.docbook28
-rw-r--r--doc/kioslave/webdav.docbook65
-rw-r--r--doc/kioslave/webdavs.docbook17
-rw-r--r--doc/klipper/Makefile.am4
-rw-r--r--doc/klipper/index.docbook511
-rw-r--r--doc/klipper/screenshot.pngbin0 -> 967 bytes
-rw-r--r--doc/kmenuedit/Makefile.am3
-rw-r--r--doc/kmenuedit/done.pngbin0 -> 47674 bytes
-rw-r--r--doc/kmenuedit/index.docbook521
-rw-r--r--doc/kmenuedit/itemname.pngbin0 -> 7163 bytes
-rw-r--r--doc/kmenuedit/kmenueditmain.pngbin0 -> 40179 bytes
-rw-r--r--doc/kmenuedit/new.pngbin0 -> 9348 bytes
-rw-r--r--doc/kmenuedit/selecticon.pngbin0 -> 45475 bytes
-rw-r--r--doc/kmenuedit/selectinternet.pngbin0 -> 17293 bytes
-rw-r--r--doc/knetattach/Makefile.am2
-rw-r--r--doc/knetattach/index.docbook349
-rw-r--r--doc/knetattach/screenshot.pngbin0 -> 25179 bytes
-rw-r--r--doc/knetattach/screenshot1.pngbin0 -> 41777 bytes
-rw-r--r--doc/knetattach/screenshot2.pngbin0 -> 30550 bytes
-rw-r--r--doc/knetattach/screenshot3.pngbin0 -> 66693 bytes
-rw-r--r--doc/knetattach/screenshot4.pngbin0 -> 43020 bytes
-rw-r--r--doc/kompmgr/Makefile.am3
-rw-r--r--doc/kompmgr/index.docbook433
-rw-r--r--doc/konqueror/Makefile.am4
-rw-r--r--doc/konqueror/basics.docbook386
-rw-r--r--doc/konqueror/bookmarks.docbook129
-rw-r--r--doc/konqueror/browser.docbook482
-rw-r--r--doc/konqueror/cmndline.pngbin0 -> 52222 bytes
-rw-r--r--doc/konqueror/commands.docbook1210
-rw-r--r--doc/konqueror/config.docbook137
-rw-r--r--doc/konqueror/credits.docbook182
-rw-r--r--doc/konqueror/dirtree.pngbin0 -> 50215 bytes
-rw-r--r--doc/konqueror/dragdrop.pngbin0 -> 47960 bytes
-rw-r--r--doc/konqueror/faq.docbook169
-rw-r--r--doc/konqueror/filemanager.docbook898
-rw-r--r--doc/konqueror/index.docbook110
-rw-r--r--doc/konqueror/introduction.docbook64
-rw-r--r--doc/konqueror/konqorg.pngbin0 -> 86855 bytes
-rw-r--r--doc/konqueror/man-kbookmarkmerger.1.docbook112
-rw-r--r--doc/konqueror/parts.pngbin0 -> 34160 bytes
-rw-r--r--doc/konqueror/path-complete.docbook82
-rw-r--r--doc/konqueror/plugins.docbook162
-rw-r--r--doc/konqueror/save-settings.docbook92
-rw-r--r--doc/konqueror/shortcut1.pngbin0 -> 30880 bytes
-rw-r--r--doc/konqueror/shortcut2.pngbin0 -> 14159 bytes
-rw-r--r--doc/konqueror/sidebar.docbook201
-rw-r--r--doc/konsole/Makefile.am3
-rw-r--r--doc/konsole/index.docbook1465
-rw-r--r--doc/konsole/konsole.pngbin0 -> 8848 bytes
-rw-r--r--doc/konsole/tabbar.pngbin0 -> 3641 bytes
-rw-r--r--doc/kpager/Makefile.am3
-rw-r--r--doc/kpager/index.docbook381
-rw-r--r--doc/kpager/screenshot.pngbin0 -> 7604 bytes
-rw-r--r--doc/kpager/settings.pngbin0 -> 8917 bytes
-rw-r--r--doc/ksplashml/Makefile.am4
-rw-r--r--doc/ksplashml/index.docbook1354
-rw-r--r--doc/ksysguard/Makefile.am4
-rw-r--r--doc/ksysguard/index.docbook496
-rw-r--r--doc/kwrite/Makefile.am4
-rw-r--r--doc/kwrite/index.docbook2952
-rw-r--r--doc/kxkb/Makefile.am4
-rw-r--r--doc/kxkb/index.docbook358
-rw-r--r--doc/kxkb/layout.pngbin0 -> 27006 bytes
-rw-r--r--doc/kxkb/switching.pngbin0 -> 13163 bytes
-rw-r--r--doc/kxkb/xkb.pngbin0 -> 20695 bytes
-rw-r--r--doc/quickstart/Makefile.am3
-rw-r--r--doc/quickstart/index.docbook1340
-rw-r--r--doc/userguide/Makefile.am4
-rw-r--r--doc/userguide/a-window.pngbin0 -> 86896 bytes
-rw-r--r--doc/userguide/accessibility.docbook168
-rw-r--r--doc/userguide/amarok-icon.pngbin0 -> 2647 bytes
-rw-r--r--doc/userguide/amarok.pngbin0 -> 14673 bytes
-rw-r--r--doc/userguide/base-kde-applications.docbook441
-rw-r--r--doc/userguide/browser-fine-tuning.docbook71
-rw-r--r--doc/userguide/burning-cds.docbook38
-rw-r--r--doc/userguide/control-center.docbook922
-rw-r--r--doc/userguide/creating-graphics.docbook48
-rw-r--r--doc/userguide/credits-and-license.docbook315
-rw-r--r--doc/userguide/customizing-desktop.docbook365
-rw-r--r--doc/userguide/desktop.pngbin0 -> 38608 bytes
-rw-r--r--doc/userguide/email.docbook254
-rw-r--r--doc/userguide/extragear-applications.docbook199
-rw-r--r--doc/userguide/file-sharing.docbook109
-rw-r--r--doc/userguide/font-installation.docbook79
-rw-r--r--doc/userguide/getting-help.docbook213
-rw-r--r--doc/userguide/glossary.docbook38
-rw-r--r--doc/userguide/groupware-kontact.docbook614
-rw-r--r--doc/userguide/index.docbook611
-rw-r--r--doc/userguide/internet-shortcuts.docbook80
-rw-r--r--doc/userguide/juk-icon.pngbin0 -> 2599 bytes
-rw-r--r--doc/userguide/juk.pngbin0 -> 74846 bytes
-rw-r--r--doc/userguide/kaboodle-icon.pngbin0 -> 2070 bytes
-rw-r--r--doc/userguide/kaboodle.pngbin0 -> 21032 bytes
-rw-r--r--doc/userguide/kcalc-systray.pngbin0 -> 5311 bytes
-rw-r--r--doc/userguide/kcontrol.pngbin0 -> 84846 bytes
-rw-r--r--doc/userguide/kde-as-root.docbook52
-rw-r--r--doc/userguide/kde-edutainment.docbook342
-rw-r--r--doc/userguide/kde-for-admins.docbook2747
-rw-r--r--doc/userguide/kde-office.docbook321
-rw-r--r--doc/userguide/kmag.pngbin0 -> 24008 bytes
-rw-r--r--doc/userguide/kmousetool.pngbin0 -> 30666 bytes
-rw-r--r--doc/userguide/kmouth.pngbin0 -> 17835 bytes
-rw-r--r--doc/userguide/kmouth2.pngbin0 -> 21497 bytes
-rw-r--r--doc/userguide/kmouth3.pngbin0 -> 45978 bytes
-rw-r--r--doc/userguide/knode-identity.pngbin0 -> 49777 bytes
-rw-r--r--doc/userguide/knode-mail-account.pngbin0 -> 43215 bytes
-rw-r--r--doc/userguide/knode-news-account.pngbin0 -> 25150 bytes
-rw-r--r--doc/userguide/knode-start.pngbin0 -> 27701 bytes
-rw-r--r--doc/userguide/konq-sidebar.pngbin0 -> 30404 bytes
-rw-r--r--doc/userguide/konq-simple.pngbin0 -> 94848 bytes
-rw-r--r--doc/userguide/konsole-intro.docbook126
-rw-r--r--doc/userguide/kopete.pngbin0 -> 18060 bytes
-rw-r--r--doc/userguide/kppp-dialer-tab.pngbin0 -> 13648 bytes
-rw-r--r--doc/userguide/kppp-wizard.pngbin0 -> 22471 bytes
-rw-r--r--doc/userguide/messaging-intro.docbook188
-rw-r--r--doc/userguide/migrator-applications.docbook272
-rw-r--r--doc/userguide/migrator-dictionary.docbook38
-rw-r--r--doc/userguide/net-connection-setup.docbook238
-rw-r--r--doc/userguide/networking-with-windows.docbook128
-rw-r--r--doc/userguide/noatun-icon.pngbin0 -> 2767 bytes
-rw-r--r--doc/userguide/noatun.pngbin0 -> 16375 bytes
-rw-r--r--doc/userguide/oggfolder.pngbin0 -> 88475 bytes
-rw-r--r--doc/userguide/open-file-dialog.pngbin0 -> 71366 bytes
-rw-r--r--doc/userguide/panel-and-desktop.docbook325
-rw-r--r--doc/userguide/pdf-files.docbook40
-rw-r--r--doc/userguide/playing-audiocds.docbook142
-rw-r--r--doc/userguide/playing-movies.docbook48
-rw-r--r--doc/userguide/playing-music.docbook150
-rw-r--r--doc/userguide/printer-setup.docbook47
-rw-r--r--doc/userguide/printing-from-apps.docbook40
-rw-r--r--doc/userguide/programs-and-documents.docbook565
-rw-r--r--doc/userguide/programs-controlling.docbook39
-rw-r--r--doc/userguide/removable-disks.docbook140
-rw-r--r--doc/userguide/rip.pngbin0 -> 20916 bytes
-rw-r--r--doc/userguide/ripsettings.pngbin0 -> 52908 bytes
-rw-r--r--doc/userguide/screen-captures.docbook38
-rw-r--r--doc/userguide/services.pngbin0 -> 77067 bytes
-rw-r--r--doc/userguide/shared-sessions.docbook46
-rw-r--r--doc/userguide/splash-screen.pngbin0 -> 42044 bytes
-rw-r--r--doc/userguide/standard-menu-entries.docbook319
-rw-r--r--doc/userguide/switching-sessions.docbook92
-rw-r--r--doc/userguide/the-filemanager.docbook291
-rw-r--r--doc/userguide/titlebar-menu.pngbin0 -> 45043 bytes
-rw-r--r--doc/userguide/troubleshooting-network-x.docbook41
-rw-r--r--doc/userguide/troubleshooting-no-open.docbook49
-rw-r--r--doc/userguide/under-the-hood.docbook521
-rw-r--r--doc/userguide/usenet.docbook251
-rw-r--r--doc/userguide/where-next.docbook40
-rw-r--r--doc/userguide/windows-how-to.docbook559
-rw-r--r--doc/userguide/your-kde-account.docbook79
-rw-r--r--doc/visualdict/Makefile.am4
-rw-r--r--doc/visualdict/index.docbook349
-rw-r--r--doc/visualdict/pict1.pngbin0 -> 1170 bytes
-rw-r--r--doc/visualdict/pict10.pngbin0 -> 2673 bytes
-rw-r--r--doc/visualdict/pict11.pngbin0 -> 994 bytes
-rw-r--r--doc/visualdict/pict12.pngbin0 -> 1525 bytes
-rw-r--r--doc/visualdict/pict13.pngbin0 -> 3952 bytes
-rw-r--r--doc/visualdict/pict14.pngbin0 -> 2950 bytes
-rw-r--r--doc/visualdict/pict15.pngbin0 -> 523 bytes
-rw-r--r--doc/visualdict/pict16.pngbin0 -> 9268 bytes
-rw-r--r--doc/visualdict/pict17.pngbin0 -> 956 bytes
-rw-r--r--doc/visualdict/pict18.pngbin0 -> 558 bytes
-rw-r--r--doc/visualdict/pict19.pngbin0 -> 19326 bytes
-rw-r--r--doc/visualdict/pict2.pngbin0 -> 926 bytes
-rw-r--r--doc/visualdict/pict20.pngbin0 -> 1562 bytes
-rw-r--r--doc/visualdict/pict21.pngbin0 -> 30371 bytes
-rw-r--r--doc/visualdict/pict22.pngbin0 -> 1241 bytes
-rw-r--r--doc/visualdict/pict23.pngbin0 -> 19677 bytes
-rw-r--r--doc/visualdict/pict3.pngbin0 -> 10710 bytes
-rw-r--r--doc/visualdict/pict4.pngbin0 -> 2493 bytes
-rw-r--r--doc/visualdict/pict5.pngbin0 -> 4428 bytes
-rw-r--r--doc/visualdict/pict6.pngbin0 -> 46304 bytes
-rw-r--r--doc/visualdict/pict7.pngbin0 -> 5969 bytes
-rw-r--r--doc/visualdict/pict8.pngbin0 -> 2178 bytes
-rw-r--r--doc/visualdict/pict9.pngbin0 -> 5850 bytes
500 files changed, 67064 insertions, 0 deletions
diff --git a/doc/Makefile.am b/doc/Makefile.am
new file mode 100644
index 00000000..6812bd2d
--- /dev/null
+++ b/doc/Makefile.am
@@ -0,0 +1,5 @@
+
+KDE_LANG = en
+KDE_DOCS = AUTO
+SUBDIRS = $(AUTODIRS)
+
diff --git a/doc/faq/Makefile.am b/doc/faq/Makefile.am
new file mode 100644
index 00000000..9c7a6607
--- /dev/null
+++ b/doc/faq/Makefile.am
@@ -0,0 +1,4 @@
+
+KDE_LANG = en
+KDE_DOCS = khelpcenter/faq
+
diff --git a/doc/faq/TODO b/doc/faq/TODO
new file mode 100644
index 00000000..42a37ca2
--- /dev/null
+++ b/doc/faq/TODO
@@ -0,0 +1,35 @@
+TODO:
+
+- Cull any questions that are specific to KDE =< 3.4
+- Look into reorganising sections to make finding things much easier.
+
+
+
+I'm keeping this in here for the amusement factor. Every time I look at it I rememeber that while I'm not a very good FAQ maintainer, physos wasn't much better ;)
+
+Last modified by physos 2002-12-27
+
+Before 3.2 release
+_________________________________________________
+
+- Split up the monolith docbook (done)
+- Get rid of 1.1.2 stuff (confusion)
+- check if things are still working
+ * compile tutorials for the various OS's
+ * workarounds still needed?
+ * workarounds still working?
+ * answers are still valid?
+ * easier solutions?
+- complete revision ?
+- New structure ?
+- Find maintiners for single parts
+- what needs to be added ?
+
+[22:15:47] <lauri> 1: move the faq (and other kdebase docs) up to kdebase/doc/<subdir>
+so that docs.kde.org will pick them up and generate them
+[22:16:05] <lauri> then remove the copies on www.kde.org, put in redirects to the new
+location, and have one, autogenerated and searchable copy all the time
+[22:16:17] <physos> sounds nice
+[22:16:24] <physos> will look into it
+
+
diff --git a/doc/faq/about.docbook b/doc/faq/about.docbook
new file mode 100644
index 00000000..89c7b603
--- /dev/null
+++ b/doc/faq/about.docbook
@@ -0,0 +1,72 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="about">
+<title>About this <acronym>FAQ</acronym></title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>What can I do to help out with this <acronym>FAQ</acronym>?</para>
+</question>
+
+<answer>
+
+<para>First, send us any errors that you may find. Also, any
+suggestions that you might have, are appreciated. Better yet, send us
+everything that you think is unclear, and if possible, send us what
+you think would be a clearer solution. The email address of the current maintainer is <email>jhall@kde.org</email>.
+</para>
+
+<para>Second, send us your solutions of those frequently-asked
+questions which are still not in this <acronym>FAQ</acronym>. We will
+put them in as soon as possible.</para>
+
+<para>Last but not least, please make full use of this
+<acronym>FAQ</acronym>. Read this <acronym>FAQ</acronym> (and other
+relevant documentation) well before asking questions on the various
+&kde; mailing lists or newsgroups.</para>
+
+<note><para> You might also want to consider becoming a
+<acronym>FAQ</acronym> maintainer. Please refer to <xref
+linkend="FAQ-maintainer-HOWTO"/> for more details. </para></note>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="FAQ-maintainer-HOWTO">
+<para>How do I become a <acronym>FAQ</acronym> maintainer?</para>
+</question>
+
+<answer>
+<para>Actually, it is very easy to become an <acronym>FAQ</acronym>
+maintainer, and we are always in need of fresh blood. :-) Just send
+us an email at <email>kde-doc-english@kde.org</email>.
+</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+sgml-omittag:nil
+sgml-shorttag:nil
+sgml-namecase-general:nil
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:true
+sgml-parent-document:("index.docbook" "book" "chapter")
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
+
diff --git a/doc/faq/configkde.docbook b/doc/faq/configkde.docbook
new file mode 100644
index 00000000..f0cb4d2b
--- /dev/null
+++ b/doc/faq/configkde.docbook
@@ -0,0 +1,250 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd">
+-->
+<chapter id="configure">
+<title>Configuring &kde;</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>How do I set the language used by &kde;?</para>
+</question>
+
+<answer>
+<para>There are two ways to set the language &kde; uses in the
+messages it will display:</para>
+
+<variablelist>
+<varlistentry><term>Using the <application>&kde; Control Center</application></term>
+<listitem><para>Fire up the <application>&kde; Control Center</application> and select
+<guimenu>Regional &amp; Accessibility</guimenu> followed by
+<guimenuitem>Country/Region &amp; Language</guimenuitem>. You can select your language and location
+here. If &kde; cannot find a translation in the first language
+chosen, it will fall back on the default language. This is usually
+(American) English by default.</para>
+<note><para>Using the <application>&kde; Control Center</application> is the preferred way of choosing
+languages in &kde;.</para></note></listitem>
+</varlistentry>
+<varlistentry><term>Using the <envar>LANG</envar> environment variable</term>
+<listitem><para>The second method uses the standard locale setting on
+your system. To change the language, simply set the environment
+variable <envar>LANG</envar> accordingly. For example, if your shell
+is <application>bash</application>, execute
+<userinput><command>export</command> <envar>LANG</envar>=de</userinput>
+to set German as the language used.</para></listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is there any keyboard switcher for international keyboards for
+&kde;?</para>
+</question>
+<answer>
+<para>
+Yes, you can configure it using the <application>&kde; Control Center</application>
+<guimenu>Regional &amp; Accessibility</guimenu>
+<guimenuitem>Keyboard Layout</guimenuitem>
+ configuration page.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I replace the standard text login screen with the
+&kde; login screen?</para>
+</question>
+<answer>
+<note><para>Your distribution/&UNIX; flavor may have its own setup tools to
+change this (&eg; <application>YaST</application> on &SuSE; &Linux;). This will
+be the safest way to enable the &kde; login screen. However, if for some reason
+you do not wish to use these tools, the following instructions may be useful.</para></note>
+<para>First, you need to change to the <quote>xdm runlevel</quote> (runlevel 5 on
+&RedHat; and &SuSE; systems) by editing your
+<filename>/etc/inittab</filename> file. In the file, you should have
+a line saying <userinput>id:3:initdefault:</userinput>. Change it to
+<userinput>id:5:initdefault:</userinput>. Now, at the end of the file,
+comment out the following line:
+<literal>x:5:respawn:/usr/bin/X11/xdm -nodaemon</literal> and
+replace it with
+<userinput>x:5:respawn:<replaceable>/opt/kde/</replaceable>bin/kdm
+-nodaemon</userinput>.
+<note><para>The location of &kdm; may differ on your
+system.</para></note></para>
+<para>For changes to take effect immediately, type <command>init
+5</command> (for &RedHat; systems) at the shell prompt.
+<caution><para>It is risky to initiate a graphical login without
+checking beforehand whether it works. If it fails to work, you would
+be in for a hard time getting back....</para></caution></para>
+</answer>
+<answer>
+<para>
+For FreeBSD, you should edit the file <filename>/etc/ttys</filename>
+and change one of the lines that look like
+<programlisting>ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure</programlisting>
+to instead say <userinput>ttyv8 "/usr/local/bin/kdm -nodaemon" xterm
+off secure</userinput>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+
+<para>I would like to click the &LMB; anywhere on the
+desktop and have the <guimenu>K</guimenu> menu displayed.</para>
+</question>
+<answer>
+<para>Open the <application>&kde; Control Center</application> and
+choose <menuchoice><guisubmenu>Desktop</guisubmenu>
+<guisubmenu>Behavior</guisubmenu></menuchoice>. You
+can now choose the behavior of mouse clicks on the desktop. To have
+the <guimenu>K</guimenu> menu open from a single &LMB; click, change
+the entry labeled <guilabel>Left button</guilabel> to say
+<guilabel>Application Menu</guilabel>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Where do I find information regarding &kde; themes?</para>
+</question>
+<answer>
+<para>Go to <ulink
+url="http://kde.themes.org/">http://kde.themes.org/</ulink> or <ulink
+url="http://www.kde-look.org">http://www.kde-look.org</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I change &MIME; Types?</para>
+</question>
+<answer>
+<para>If you are using &konqueror;, do this instead: first, open a
+&konqueror; window and choose
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
+Konqueror</guimenuitem></menuchoice>, then <guilabel>File Associations</guilabel>. Find the type you want to change
+(&eg; <literal>text/english</literal> or
+<literal>image/gif</literal>), and set the application preference order
+to whatever you want.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>&kde; (&kdm;) does not read my
+<filename>.bash_profile</filename>!</para>
+</question>
+<answer>
+<para>The login managers<application>xdm</application> and &kdm; do
+not run a login shell, so <filename>.profile</filename>,
+<filename>.bash_profile</filename>, &etc; are not
+sourced. When the user logs in, <application>xdm</application> runs
+<command>Xstartup</command> as root and then
+<command>Xsession</command> as user. So the normal practice is to add
+statements in <filename>Xsession</filename> to source the user
+profile. Please edit your <filename>Xsession</filename> and
+<filename>.xsession</filename> files.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I use &TrueType; fonts in &kde;?</para>
+</question>
+<answer>
+
+<para>You need to install &TrueType; font support into your &X-Window; configuration.
+Please take a look at <ulink
+url="http://x.themes.org/">x.themes.org</ulink> for the fonts, and
+<ulink url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/">xfsft:
+&TrueType; Font Support For X11</ulink> or <ulink
+url="http://X-TT.dsl.gr.jp/">X-&TrueType; Server Project Home
+Page</ulink> for the font servers.</para>
+
+<para>If you have a bunch of &TrueType; fonts from &Microsoft;
+&Windows;, edit the <filename>XF86Config</filename> file to get the
+fonts from the font folder. Then just tell &kde; to use these new
+fonts with the font administrator utility.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is it possible to enter, show and work with the Euro Symbol in
+&kde;?</para>
+</question>
+<answer>
+<para>Yes and no. For details, look here: <ulink
+url="http://www.koffice.org/kword/euro.php">http://www.koffice.org/kword/euro.php</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>How do I run a program at &kde; startup?</para></question>
+
+<answer><para>There are many ways to do that. If what you want to do
+is to run some scripts that would set some environment variables (for
+example, to start <command>gpg-agent</command>, <command>ssh-agent</command> and others), you can put
+these scripts into <filename class="directory">$<envar>KDEHOME</envar>/env/</filename> and make sure their names end in
+<literal role="extension">.sh</literal>. $<envar>KDEHOME</envar> is
+usually a folder named <filename class="directory">.kde</filename>
+(note the period at the beginning) in your home
+folder. If you want scripts to be executed for all &kde; users, you can
+put them under <filename class="directory">$<envar>KDEDIR</envar>/env/</filename>, where $<envar>KDEDIR</envar> is the prefix &kde; was
+installed to (you can find this out using the command
+<userinput><command>kde-config</command> --prefix</userinput>).</para>
+<para>If you wish to start a program after &kde; has started, you may want to use the
+<filename class="directory">Autostart</filename> folder. To add
+entries to the <filename class="directory">Autostart</filename> folder:
+<orderedlist>
+<listitem><para>Open &konqueror;.</para>
+</listitem>
+<listitem><para>Select <menuchoice><guimenu>Go</guimenu><guimenuitem>Autostart</guimenuitem>
+</menuchoice> from the menubar.</para>
+</listitem>
+<listitem><para>Right-click in the window view area and select <menuchoice><guisubmenu>Create New</guisubmenu><guisubmenu>File</guisubmenu><guimenuitem>Link to
+Application</guimenuitem>
+</menuchoice></para>
+</listitem>
+<listitem><para>Click on the <guilabel>Application</guilabel> tab in
+the window that appears and enter the name of the command to run in
+the <guilabel>Command</guilabel> text box.</para>
+</listitem>
+</orderedlist>
+</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How can I allow more than one user to be logged in a at a time? Can &kde; do <quote>fast user switching</quote>?</para>
+</question>
+<answer>
+
+<para>To enable more than one user to log in at one time on the same
+computer (sometimes referred to as <quote>fast user switching</quote>) you
+need to tell the program that logs you in that it can use more than one
+session (or, in &X-Window; terms, <quote>display</quote>) at a time.</para>
+
+<para>In &kde;, this program is called &kdm; which stands for <quote>&kde;
+Display Manager</quote>. If you are not using &kdm; as your login screen
+then you will need to consult the documentation for the software you are using on how to
+accomplish multiple sessions.</para>
+
+<para>By default, this will be configured at installation time automatically
+if &kdm; supports virtual terminals on your system (currently Linux only).
+If it was not configured automatically, consult the &kdm; manual, section
+<ulink url="help:/kdm/kdmrc-xservers">Specifying permanent &X-Server;s</ulink>.
+After modifying kdmrc, you will have to let &kdm; know about it; just
+invoke <command>killall -HUP kdm</command>.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/doc/faq/contrib.docbook b/doc/faq/contrib.docbook
new file mode 100644
index 00000000..807050ba
--- /dev/null
+++ b/doc/faq/contrib.docbook
@@ -0,0 +1,164 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+
+<chapter id="contribute">
+<title>Contributing</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>How can I contribute to &kde;?</para>
+</question>
+<answer>
+<para>&kde; is a free software project that lives from voluntary
+contributions. Everybody is encouraged to contribute to &kde;. Not
+only programmers are welcome. There are many ways in which you can
+help to improve &kde;:</para>
+<itemizedlist>
+<listitem><para>Test the software.</para></listitem>
+<listitem><para>Send in bug reports. For more information on this,
+see <link linkend="bug-report">How do I submit a bug
+report?</link>.</para></listitem>
+<listitem><para>Write documentation or help files. You can get some
+information by visiting the <ulink
+url="http://i18n.kde.org/doc/">&kde; Editorial Team
+Home Page</ulink>.</para></listitem>
+<listitem><para>Translate programs, documentation, and help files.
+For more information on this, you should visit <ulink
+url="http://i18n.kde.org">The &kde; Translators' and Documenters' Web
+Site</ulink>.</para></listitem>
+<listitem><para>Draw nice icons or compose sound effects. You can
+visit the <ulink url="http://artist.kde.org/">&kde;
+artists page</ulink> to find out more.</para></listitem>
+<listitem><para>Write articles and books about &kde;. If you want to
+help spread the word about &kde;, simply send an email to
+<email>kde-pr@kde.org</email>. This will get you in touch
+with the &kde; public relations volunteers.</para></listitem>
+<listitem><para>Program new &kde; applications. Please refer to <xref
+linkend="programming"/> for more information.</para></listitem>
+<listitem><para> Of course, sponsors are also
+welcome. :-)</para></listitem>
+</itemizedlist>
+<para>There are several places to look for more information if you
+want to get involved in the development. The first step is to
+subscribe to some of the <ulink url="http://www.kde.org/mailinglists/">mailing
+lists</ulink>. You will soon see something
+that can be improved or added.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="bug-report">
+<para>How do I submit a bug report?</para>
+</question>
+<answer>
+<para>There is a bug tracking system available at <ulink
+url="http://bugs.kde.org">http://bugs.kde.org</ulink>. The
+system features a wizard to submit new bug reports and a
+list of all known bugs.</para>
+<para>The easiest way to submit a bug is to select
+<menuchoice><guimenu>Help</guimenu><guimenuitem>Report
+Bug...</guimenuitem></menuchoice> from the menu bar of the application
+with the bug. This will open a small dialog box with a link
+to the bug tracking system. Please make sure to follow the
+instructions of the bug reporting wizard.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="programming">
+<para>I want to program for &kde;. What should I do first?</para>
+</question>
+<answer>
+<para>Everybody is encouraged to develop software for &kde;. What you
+should do first depends strongly on your experience, &eg; whether you have
+already learned C++ or have experience with the &Qt; toolkit and so
+on.</para>
+<para>To get into &kde; programming, you will need some basic tools:
+<application>automake</application>,
+<application>autoconf</application>, and
+<application>egcs</application>. You should look to <ulink
+url="http://developer.kde.org/">http://developer.kde.org/</ulink>
+for more tips.</para>
+<para>Another excellent resource for learning &kde;
+programming is the &Qt;
+online tutorials. These are installed along with &Qt;. To view them,
+open <filename>$<envar>QTDIR</envar>/doc/html/index.html</filename> in
+&konqueror; and bookmark it. The tutorials
+can be found under "Using
+Qt". The source code for each lesson can be found in the <filename
+class="directory">$<envar>QTDIR</envar>/tutorial</filename>
+directory.</para>
+<para>There is, however, one thing that everybody interested in
+programming for &kde; should do: <emphasis>subscribe to the developers
+mailing list</emphasis>. To subscribe, you have to send an email to
+<ulink
+url="mailto:kde-devel-request@kde.org">kde-devel-request@kde.org</ulink>
+with the subject <userinput>subscribe
+<replaceable>your_email_address</replaceable></userinput>.
+<important><para>Please read <link linkend="subscribe">How to
+subscribe/unsubscribe to these lists</link> carefully. Everything
+said there applies to the development list as
+well.</para></important></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I get access to &kde; <acronym>SVN</acronym>?</para>
+</question>
+<answer>
+<para>The &kde; project uses <acronym>SVN</acronym> to develop the
+core parts of the software. Usually, when you have changed one of the
+parts (&eg; fixed a bug), and you want to commit this change, the best
+way is to create a patch against a current snapshot and send this
+patch to the developer/maintainer of the respective program.</para>
+<para>If you are doing this more or less regularly, there are instructions here on how to get write access to the <acronym>SVN</acronym> repository: <ulink url="http://developer.kde.org/documentation/other/developer-faq.html#q1.8">
+http://developer.kde.org/documentation/other/developer-faq.html#q1.8</ulink>. But be aware that more users will slow
+down <acronym>SVN</acronym> access for all developers, so we want to
+keep the number of people with direct <acronym>SVN</acronym> access
+reasonably small. But feel free to ask!</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Can I have read-only access to the <acronym>SVN</acronym> repository?</para>
+</question>
+<answer>
+<para>Yes. Instructions on how to get anonymous, read-only <acronym>SVN</acronym> access are here: <ulink url="http://developer.kde.org/source/anonsvn.html">
+http://developer.kde.org/source/anonsvn.html</ulink>
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Are there any <acronym>SVN</acronym> mirror sites for &kde;?</para>
+</question>
+<answer>
+<para>No, there are currently no anonymous <acronym>SVN</acronym> mirror sites for &kde;. If you're interested in setting one up, please contact <email>sysadmin@kde.org</email>
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I go about translating &kde; programs into my native
+language?</para>
+</question>
+<answer>
+<para>Look at the <ulink url="http://i18n.kde.org">The &kde;
+Translators' and Documenters' Web Site</ulink> to see whether your
+program is already translated (most are). Otherwise you will find
+information there on how to do it yourself.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
+
diff --git a/doc/faq/desktop.docbook b/doc/faq/desktop.docbook
new file mode 100644
index 00000000..da3de160
--- /dev/null
+++ b/doc/faq/desktop.docbook
@@ -0,0 +1,97 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="desktop">
+<title>The desktop</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>How do I add an application to the desktop?</para>
+</question>
+<answer>
+
+<para>Just choose the desired application from the <guimenu>K</guimenu> menu and drag and drop it to the Desktop.
+</para>
+<para>For applications not listed in the <guimenu>K</guimenu> menu,
+use the &RMB; on the desktop and choose <menuchoice><guimenuitem>Create New</guimenuitem><guisubmenu>File</guisubmenu>
+<guimenuitem>Link to Application...</guimenuitem></menuchoice> and fill in the configuration for the application you want to link to.
+</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I mount/unmount a device from the desktop?</para>
+</question>
+<answer>
+
+<para>First, make sure you are allowed to <command>mount</command>/<command>umount</command> the relevant device as a user.
+</para>
+<para>Then you can add any device via &RMB; on the desktop and then choosing <menuchoice><guimenu>Create New</guimenu><guimenuitem>Link to Device</guimenuitem></menuchoice> and then selecting the device of the type you wish to control from the desktop. Fill in the settings for the device in the dialog that appears and click <guilabel>OK</guilabel>. You can use the resulting desktop icon to mount/unmount the device from the desktop.
+</para>
+
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>Where are the icons kept?</para>
+</question>
+<answer>
+<para>The icons can be found only in <filename
+class="directory">$<envar>KDEDIRS</envar>/share/icons</filename> or <filename
+class="directory">$<envar>HOME</envar>/.kde/share/icons</filename> or
+<filename class="directory">$<envar>HOME</envar>/.kde2/share/icons</filename>. To use icons
+stored in other locations, you must either copy them into one of the
+above-mentioned fixed &kde; locations or make symlinks.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I use the mouse scroll wheel in &kde;?</para>
+</question>
+<answer>
+<para>Mouse wheel support comes with &Qt; 2.0 and above, so &kde; based on
+that will automatically support the use of the mouse scroll wheel if your system is configured correctly. Check your &X-Server; settings support the use of a scrollwheel if it is not working.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I launch applications in a particular desktop?</para>
+</question>
+<answer>
+<para>&kde; comes with a program called &kstart;.
+To start an <application>xterm</application> on the second desktop and then activate it use:
+
+<userinput><command>kstart</command> <option>--desktop
+2 --activate --window "xterm" </option>xterm</userinput>.</para>
+<para>Note that the <option>--window</option> option is important. It takes an
+argument which is a regular expression matching the title of the window to
+apply the settings to.</para>
+<para>Please read <command>kstart</command> <option>--help-all</option> for more magic
+available with &kstart; (and there is an abundance).
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Where do I save my files if I want them to appear directly on
+the desktop?</para>
+</question>
+<answer>
+<para><filename
+class="directory">$<envar>HOME</envar>/Desktop</filename>. You might
+need to refresh your desktop after you have saved your files.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/doc/faq/filemng.docbook b/doc/faq/filemng.docbook
new file mode 100644
index 00000000..bfe6d1e9
--- /dev/null
+++ b/doc/faq/filemng.docbook
@@ -0,0 +1,207 @@
+<!-- <?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd"> -->
+
+<chapter id="filemanager">
+<title>The File Manager</title>
+
+<para>&kde;'s file manager is &konqueror;. The
+&konqueror; home page is located at <ulink
+url="http://www.konqueror.org">http://www.konqueror.org</ulink> where a
+&konqueror; specific <acronym>FAQ</acronym> can be found.</para>
+
+<qandaset>
+
+
+<qandaentry>
+<question>
+<para>How can I change the appearance of a folder in
+&konqueror;?</para>
+</question>
+<answer>
+<para>Right-click the folder, select <guimenuitem>Properties</guimenuitem>,
+click on the large icon in the dialog which appears, and choose another
+icon.</para> <para>To change the icon displayed for entries in the
+<guimenu>K Menu</guimenu>, use the <application>Menu Editor</application>,
+located at <menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Menu
+Editor</guimenuitem></menuchoice>.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How can I do non-anonymous &FTP; transfers with &konqueror;?</para>
+</question>
+<answer>
+<para>Normally, if you enter a &URL; like
+<userinput>ftp://<replaceable>ftp.somehost.com</replaceable></userinput>,
+&konqueror; will attempt an anonymous login to the &FTP; server. If you
+want to login as a particular user, enter a &URL; like
+<userinput>ftp://<replaceable>username@ftp.somehost.com</replaceable></userinput>
+instead. &konqueror; will ask for your password and connect to the
+server.</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>How do I specify the startup folder for &konqueror;?</para>
+</question>
+<answer>
+
+<para>Using the &RMB;, click on the Home icon and choose
+<guimenuitem>Properties</guimenuitem>. Under the
+<guilabel>Application</guilabel> tab you will probably find something like
+<command>kfmclient openProfile filemanagement</command>; just append
+<filename class="directory">file:/whereever/you/want</filename> with the
+folder you would like &konqueror; to start in.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I rename files?</para>
+</question>
+<answer>
+<para>Simply <mousebutton>right</mousebutton> click on the file and select
+<guimenuitem>Rename</guimenuitem> or press the keyboard shortcut <keycap>F2</keycap> with a file selected.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Where did the delete entry from my right-click context menu go?</para>
+</question>
+<answer>
+<para>In &kde; 3.4 the delete context menu entries that bypass the
+trashcan are no longer displayed by default. To enable them, go to
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
+&konqueror;</guimenuitem></menuchoice > and select
+<guilabel>Behaviour</guilabel> in the iconbar to the left. Tick the checkbox
+<guilabel>Show 'Delete' context menu entries which bypass the
+trashcan</guilabel>.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>How do I configure the programs that &konqueror; uses to
+open different types of files?</para></question>
+<answer>
+<para>In order to configure file associations, you should go to the
+&kcontrolcenter; and choose the item <guimenuitem>File
+Associations</guimenuitem> under the category <guimenu>KDE
+Components</guimenu>.</para>
+<para>
+Suppose the default <acronym>PDF</acronym> viewer is now &kghostview; and
+you would prefer to use <application>KPDF</application> as a viewer. You
+would simply type <userinput>pdf</userinput> in the search box at the top of
+the dialog, choose <guimenuitem>pdf</guimenuitem> in the
+<guimenu>application</guimenu> group and move
+<application>KPDF</application> up. In the <guilabel>Embedding</guilabel>
+tab you can also choose which component other applications will use to
+display files (for example, when viewing files in &konqueror; or using
+&ark;'s embedded viewer).
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>When I try to click on a folder in &konqueror;, I get the
+message: <quote>There appears to be a configuration error. You have
+associated Konqueror with inode/directory, but it cannot handle this file
+type.</quote></para>
+</question>
+<answer>
+<para>You need to make sure that the embedding settings for inode/directory
+are correct:
+<orderedlist>
+<listitem><para>In &konqueror;, go to
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
+Konqueror</guimenuitem></menuchoice> and then to the <guilabel>File
+Associations</guilabel> page.</para></listitem> <listitem><para>Open
+inode->directory in the tree view.</para></listitem> <listitem><para>Click on
+the
+<guilabel>Embedding</guilabel> tab. Make sure that <guilabel>Left Click
+Action</guilabel> is set to <guilabel>Show file in embedded
+viewer</guilabel>, and by default <guilabel>Icon View (konq_iconview)</guilabel>
+is at the top
+of <guilabel>Services Preference Order.</guilabel></para></listitem>
+</orderedlist>
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry> <question> <para>What are <option>%i</option> and
+<option>%m</option> in the Execute line?</para> </question> <answer>
+<para>They are used by all &kde; applications (since they are implemented in
+<classname>KApplication</classname> and all good &kde; programs create a
+<classname>KApplication</classname> object before they even look at the
+command line arguments).</para> <para>A standard line for a &kde;
+application looks like this: <userinput><command>foo</command>
+<option>... %i %m -caption \"%c\"</option></userinput>. Pretty confusing,
+-but it has been designed in that way so that it can integrate legacy,
+non-&kde; applications as smoothly as possible. &konqueror;, when executing
+the line above, will extend the command to
+<userinput><command><replaceable>foo</replaceable></command> <option>-icon
+something.png -miniicon something_mini.png -caption \"The
+Foo\"</option></userinput>. Both the icon and the mini-icon as well as "The
+Foo" are properties defined in the <filename>.desktop</filename> file. If
+the icons are not defined, they simply default to the executable name
+<replaceable>foo</replaceable>.</para>
+
+<para>This way a user can change these things in &kmenuedit; for his or her
+applications. The <option>-caption</option> option is important, because no
+user will accept that the menu item <guimenuitem>Editor</guimenuitem> starts
+something called <guilabel>kedit-0.9pl4-build47</guilabel>. Instead, he
+expects a window called <guilabel>Editor</guilabel>. Furthermore these
+names are localized, <abbrev>i.e.</abbrev> an American user launches
+<guimenuitem>CD-Player</guimenuitem> and gets a window called
+<guilabel>CD-Player</guilabel> while a German user launches
+<guimenuitem>CD-Spieler</guimenuitem> and gets a window called
+<guilabel>CD-Spieler</guilabel>.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>How do I make &konqueror; start up without a menu bar?
+I can't save a view profile when the menu bar is invisible!</para>
+</question>
+
+<answer><para>The easiest way to do this is to edit &konqueror;'s
+configuration file manually. Add the following lines to
+<filename>~/.kde/share/config/konquerorrc</filename>:
+<programlisting>
+[KonqMainWindow]
+MenuBar=Disabled
+</programlisting>
+</para>
+
+<para>On restarting &konqueror;, the menubar should be hidden.</para>
+
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
+
+<!--Local variables:
+mode: xml
+sgml-omittag:nil
+sgml-shorttag:nil
+sgml-namecase-general:nil
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:true
+sgml-parent-document:("index.docbook" "book" "chapter")
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/doc/faq/getkde.docbook b/doc/faq/getkde.docbook
new file mode 100644
index 00000000..ceabb256
--- /dev/null
+++ b/doc/faq/getkde.docbook
@@ -0,0 +1,79 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="getting-kde">
+<title>Getting &kde;</title>
+
+<qandaset>
+<qandaentry>
+<question id="where-to-get-kde">
+<para>Where do I get &kde;?</para>
+</question>
+<answer>
+<!-- This needs a rewrite including informations about the latest version (link to the info page?)-->
+<para>The easiest way to get &kde; is to install a &Linux; distribution or another UNIX-like OS that ships with &kde;.
+You can find an up-to-date list of distributions that ship
+with &kde; <ulink url="http://www.kde.org/download/distributions.php">here</ulink>. For alternative methods of
+trying &kde; that do not require you to be running &Linux;, please see
+<ulink url="http://kde.org/try_kde">Try &kde;</ulink></para>
+
+<para>The main distribution site for &kde; is
+<ulink url="ftp://ftp.kde.org/">ftp.kde.org</ulink>. However, this site is
+often under heavy load, so you might prefer to use
+<ulink url="http://download.kde.org/">download.kde.org</ulink> which automatically
+redirects you to the mirror nearest to you.
+You can also have a look at the list of <ulink url="http://www.kde.org/ftpmirrors.html"> &kde; mirror sites</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What is the current version?</para>
+</question>
+<answer>
+
+<para>Currently, the latest stable version is 3.5.5</para>
+
+<para>The <ulink url="http://www.kde.org/info/3.5.5.php">&kde; 3.5.5 Info
+Page</ulink> contains a lot of information specific to this
+release.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Where do I find &kde; snapshots?</para>
+</question>
+<answer>
+<para>You can get the latest snapshots from <ulink
+url="ftp://ftp.kde.org/pub/kde/unstable/snapshots">ftp://ftp.kde.org/pub/kde/unstable/snapshots</ulink>.
+You might also want to consider setting up your own <acronym>SVN</acronym> client in order to
+maintain the latest snapshot at all times. Please refer to <ulink
+url="http://developer.kde.org/source/anonsvn.html">Anonymous <acronym>SVN</acronym> and &kde;</ulink> for further
+information.
+</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="where-to-get-qt">
+<para>Where do I get &Qt;?</para>
+</question>
+<answer>
+<para>&Qt; is a product of the Norwegian company Trolltech. You can
+always get the latest &Qt; version from their
+<ulink url="ftp://ftp.trolltech.com">&FTP; server</ulink>.</para>
+<para>
+And with most up-to-date &Linux; distributions, &Qt; is already
+included. Please see <xref linkend="prerequisites"/> for the version
+of &Qt; you need.</para>
+</answer>
+</qandaentry>
+
+
+</qandaset>
+</chapter>
diff --git a/doc/faq/index.docbook b/doc/faq/index.docbook
new file mode 100644
index 00000000..f114e399
--- /dev/null
+++ b/doc/faq/index.docbook
@@ -0,0 +1,136 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd" [
+ <!ENTITY kappname "&kde; Frequently Asked Questions">
+ <!ENTITY % addindex "IGNORE">
+ <!ENTITY % English "INCLUDE" > <!-- change language only here -->
+ <!ENTITY faq-about SYSTEM "about.docbook">
+ <!ENTITY faq-intro SYSTEM "intro.docbook">
+ <!ENTITY faq-getkde SYSTEM "getkde.docbook">
+ <!ENTITY faq-install SYSTEM "install.docbook">
+ <!ENTITY faq-panel SYSTEM "panel.docbook">
+ <!ENTITY faq-desktop SYSTEM "desktop.docbook">
+ <!ENTITY faq-winmng SYSTEM "winmng.docbook">
+ <!ENTITY faq-filemng SYSTEM "filemng.docbook">
+ <!ENTITY faq-webbrowse SYSTEM "webbrowse.docbook">
+ <!ENTITY faq-configkde SYSTEM "configkde.docbook">
+ <!ENTITY faq-kdeapps SYSTEM "kdeapps.docbook">
+ <!ENTITY faq-nonkdeapps SYSTEM "nonkdeapps.docbook">
+ <!ENTITY faq-tips SYSTEM "tips.docbook">
+ <!ENTITY faq-misc SYSTEM "misc.docbook">
+ <!ENTITY faq-notrelated SYSTEM "notrelated.docbook">
+ <!ENTITY faq-moreinfo SYSTEM "moreinfo.docbook">
+ <!ENTITY faq-contrib SYSTEM "contrib.docbook">
+ <!ENTITY faq-questions SYSTEM "questions.docbook" >
+ <!ENTITY faq-credits SYSTEM "credits.docbook">
+ <!ENTITY faq-sound SYSTEM "sound.docbook">
+ <!ENTITY faq-qt SYSTEM "qt.docbook">
+
+]>
+<!--Time-stamp: "2001-09-03 00:10:00 endres"-->
+<book lang="&language;">
+
+<bookinfo>
+<title>&kde; Frequently Asked Questions</title>
+
+<authorgroup>
+<author>
+<surname>The &kde; Team</surname>
+</author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+
+</authorgroup>
+
+<copyright>
+<year>1997</year>
+<year>1998</year>
+<year>1999</year>
+<year>2000</year>
+<year>2001</year>
+<year>2003</year>
+<year>2004</year>
+<year>2005</year>
+<holder>The &kde; Team</holder>
+</copyright>
+
+<legalnotice>&FDLNotice;</legalnotice>
+
+<date>2005-01-19</date>
+<releaseinfo>3.4</releaseinfo>
+
+<abstract> <para>This is a compilation of the most frequently asked
+questions about the K Desktop Environment. Please report any bugs,
+inconsistencies, or omissions you find in this &FAQ; to
+<email>kde-doc-english@kde.org</email>. Please do not mail your questions
+to this list. Post them to the &kde; mailing lists and newsgroups
+instead. They are monitored for this &FAQ;.</para> </abstract>
+
+<keywordset>
+<keyword>KDE</keyword>
+<keyword>FAQ</keyword>
+<keyword>question</keyword>
+<keyword>answer</keyword>
+</keywordset>
+</bookinfo>
+
+&faq-about;
+&faq-intro;
+&faq-getkde;
+&faq-install;
+&faq-panel;
+&faq-desktop;
+&faq-winmng;
+&faq-filemng;
+&faq-webbrowse;
+&faq-configkde;
+&faq-kdeapps;
+&faq-sound;
+&faq-nonkdeapps;
+&faq-tips;
+&faq-misc;
+&faq-qt;
+&faq-moreinfo;
+&faq-questions;
+&faq-contrib;
+
+<chapter id="credits">
+<title>Credits and License</title>
+
+<para>The current &FAQ; maintainers are:</para>
+
+<itemizedlist>
+<listitem><para>J Hall
+<email>jes.hall@kdemail.net</email></para></listitem>
+</itemizedlist>
+
+<para>Many of the answers in this &FAQ; are taken
+from the various &kde; mailing lists and newsgroups. Here is a
+<emphasis>big</emphasis> thank you to all of you who have contributed
+answers that eventually appear in this &FAQ;.</para>
+
+<para>Special thanks go to the former &FAQ;
+maintainers, Rainer Endres and Mr. Lee Wee Tiong </para>
+
+
+<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
+
+&underFDL;
+</chapter>
+
+&documentation.index;
+</book>
+
+<!--
+Local Variables:
+sgml-minimize-attributes:nil
+sgml-general-insert-case:lower
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:nil
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+End:
+-->
diff --git a/doc/faq/install.docbook b/doc/faq/install.docbook
new file mode 100644
index 00000000..6ab33ef7
--- /dev/null
+++ b/doc/faq/install.docbook
@@ -0,0 +1,726 @@
+<!-- <?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="install">
+<title>Installation instructions</title>
+
+<para>These are the generic installation instructions for the K
+Desktop Environment. Please complement your reading with the
+<filename>README</filename>s and <filename>INSTALL</filename>s that
+come along with the package. Please read them carefully and try to
+help yourself out if anything goes wrong. If you need further
+assistance, consider joining the &kde; mailing lists
+(see our web site instructions for joining the &kde;
+<ulink url="http://www.kde.org/mailinglists/">mailing
+lists</ulink>) or newsgroups.</para>
+
+
+<qandaset>
+
+
+<qandaentry>
+<question>
+<para>To the would-be converts</para>
+</question>
+<answer>
+
+<para>So you have heard the rumors. Or you have seen the screenshots.
+And you are dying to get hold of &kde;. But you know next to nothing
+about this whole <quote>alternative OS</quote> business. Don't worry!
+You only need to do some (well, maybe not some) reading, that's
+all!</para>
+
+<para>&kde; does not run on any version of &Microsoft; &Windows; or OS/2 (yet). To run
+&kde;, you need to have a &UNIX; system. Please refer to <xref
+linkend="platform"/> for more details.</para>
+
+<para>Decide on a platform and set it up for your system. This
+<acronym>FAQ</acronym> can not help you with this, since &kde;<ulink
+url="http://www.kde.org"> runs on many &UNIX;</ulink> platforms. </para>
+
+<!-- Taken out because we can not help with all platforms and KDEisnotLINUX -->
+
+<para>Finally, you are ready to commence the &kde; installation.
+Please start reading from the next section. To get &kde;, please
+refer to <xref linkend="where-to-get-kde"/>. Last but not least, if
+you encounter any problems while installing &kde;, please do not
+hesitate to make use of the &kde; <link
+linkend="mailing-lists">mailing lists</link> and <link
+linkend="newsgroups">newsgroups</link>. But do bear this in mind: no
+question is too silly to ask, but some are too silly to answer,
+especially when they are already answered in this <acronym>FAQ</acronym>.</para>
+<para>Good luck and have fun!</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What kind of hardware do I need to run &kde; ?</para>
+</question>
+<answer>
+<para>To run &kde; it is recommended that you have at least a pentium II processor, 64MB of memory and 500MB of free disk space for a basic installation. While &kde; may run on slower configurations than this, performance can be severely impaired. Generally, if your computer runs an &X-Server; already with other desktop environments or window managers it's probably fast enough to run &kde;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Available package formats</para>
+</question>
+<answer>
+
+
+<para>You can find several kinds of binary and source packages for
+different distributions and operating systems on the &kde-ftp;. The
+binary packages are not made by the &kde; Team, but by the
+distributors themselves, or some dedicated individuals. Please refer to
+<ulink url="http://dot.kde.org/986933826/">&kde; Package Policy
+Explained</ulink> for information about the &kde; Package Policy. The
+only <quote>official</quote> release is the source tar.bz2
+packages. Please refer to the <filename>README</filename>s and
+<filename>INSTALL</filename>s in the several binaries folders. For
+a list of the available packages for a release, refer to the relevant
+info page. For the latest release this is the <ulink
+url="http://www.kde.org/info/3.4.1.php">&kde; 3.4.1 Info
+Page</ulink>.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="prerequisites">
+<para>Prerequisites</para>
+</question>
+<answer>
+
+<!-- rewrite to make it more general, pointing to the according webpages? -->
+
+<para>For &kde; 3.4.1, you need the &Qt; library version 3.3 or greater.
+Please make sure you download the correct &Qt;. You will
+also need the header files, if you want to compile &kde;
+yourself. They are all available, at no cost, from <ulink
+url="http://www.trolltech.com/products/download">http://www.trolltech.com/download</ulink>.
+In addition, there are optional libraries that might improve &kde; if
+installed on your system. An example is OpenSSL which will enable
+&konqueror; to browse web pages securely and is needed in a version
+>=0.9.6. These should be provided by your distributor; if not, ask
+for an update.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Description of the base packages</para>
+</question>
+<answer>
+<para>The base distribution currently consists of twenty
+packages. Some are required, while others are optional. Each package
+is available in each of the aforementioned package formats.</para>
+<variablelist>
+<varlistentry>
+<term>kdelibs</term>
+<listitem>
+<para>Required</para>
+<para>This package contains shared libraries that are needed by all
+&kde; applications.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdebase</term>
+<listitem>
+<para>Required</para>
+<para>This package contains the base applications that form the core
+of the K Desktop Environment like the window manager, the terminal
+emulator, the control center, the file manager, and the panel.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>&arts;</term>
+<listitem>
+<para>Required</para>
+<para>The &arts; sound server. A powerful, network transparent sound
+server.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdeaddons</term>
+<listitem>
+<para>Optional</para>
+<para>Various plugins for &kate;, &kicker;, &knewsticker;, &konqueror; and &noatun; </para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdeartwork</term>
+<listitem>
+<para>Optional</para>
+<para>Additional wallpapers, themes, styles, sounds ...</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdebindings</term>
+<listitem>
+<para>Optional</para>
+<para>Various bindings for other languages, including &Java;, Perl, Python, ...</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdegames</term>
+<listitem>
+<para>Optional</para>
+<para>Various games like &kmahjongg;, &ksnake;, &kasteroids;, and
+&kpatience;.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdegraphics</term>
+<listitem>
+<para>Optional</para>
+<para>Various graphics-related programs like &PostScript; previewer,
+&DVI; previewer, and a drawing program.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdeutils</term>
+<listitem>
+<para>Optional</para>
+<para>Various desktop tools like a calculator, an editor and other
+nifty stuff.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdemultimedia</term>
+<listitem>
+<para>Optional</para>
+<para>Multimedia applications like a &CD; player and a mixer.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdenetwork</term>
+<listitem>
+<para>Optional</para>
+<para>Network applications. Currently contains the instant messaging client &kopete;, the
+download manager &kget;, and several other network-related programs.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdepim</term>
+<listitem>
+<para>Optional</para>
+<para>Personal information management tools. Contains the email client &kmail;, the newsreader &knode; and other related programs.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdeadmin</term>
+<listitem>
+<para>Optional</para>
+<para>System administration programs.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdeedu</term>
+<listitem>
+<para>Optional</para>
+<para>
+Educational and entertaining applications for &kde;'s younger users.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdeaccessibility</term>
+<listitem>
+<para>Optional</para>
+<para>
+KDE accessibility programs such as a screen magnifier and speech synthesizer front end.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdetoys</term>
+<listitem>
+<para>Optional</para>
+<para>Toys!</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdevelop</term>
+<listitem>
+<para>Optional</para>
+<para>A complete Integrated Development Environment for &kde; and Qt</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdewebdev</term>
+<listitem>
+<para>Optional</para>
+<para>Web development applications. Contains such applications as &quanta;, an integrated web development environment and other applications useful in web development</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>kdesdk</term>
+<listitem>
+<para>Optional</para>
+<para>KDE Software Development Kit. Contains a collection of applications and tools used by KDE Developers.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<para>&arts; and then kdelibs should be installed before everything
+else, and kdeaddons last. The other packages can be installed in any
+arbitrary order.</para>
+
+<para>Most package management tools will let you put all these
+packages in one folder and install them all at once, figuring out
+the dependencies as they go.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Installation instructions for the different package
+formats</para>
+</question>
+<answer>
+<para><important>
+<para>Please do not forget to read the <filename>README</filename> and <filename>INSTALL</filename> files if they are available.</para>
+</important></para>
+<variablelist>
+<varlistentry>
+<term>Installation of the Debian packages</term>
+<listitem>
+<para>The Debian packages install in accordance with the upcoming <acronym>FHS</acronym> (File
+Hierarchy Standard).</para>
+<procedure>
+<step performance="required"><para>become superuser</para></step>
+<step performance="required"><para>run <command>dpkg <option>-i
+<replaceable>packagename.deb</replaceable></option></command> for
+every package you want to install.</para></step>
+</procedure>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>Installation of the <acronym>RPM</acronym> packages</term>
+<listitem>
+<procedure>
+<title>To install binary <acronym>RPM</acronym>s</title>
+<step performance="required"><para>become superuser</para></step>
+<step performance="required"><para>execute <command>rpm <option>-ivh
+<replaceable>packagename.rpm</replaceable></option></command></para></step>
+</procedure>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>Installation of the source <filename>.tar.bz2</filename> files</term>
+<listitem>
+<para>Since there are always changes and updates to the way &kde; is compiled, please
+refer to <ulink url="http://developer.kde.org/build/index.html">Download and Install from Source</ulink> for the most up to date installation instructions for the source packages.
+</para>
+<para>The general approach should work in most cases though.
+</para>
+<para>The source <filename>.tar.bz2</filename> package installs into <filename
+class="directory">/usr/local/kde</filename> by default. You can
+override this setting by using the <option>--prefix</option> option of
+the <filename>configure</filename> script.</para>
+<procedure>
+<step performance="required"><para>unpack the packages with <command>tar <option>jxvf
+<replaceable>packagename.tar.bz2</replaceable></option></command></para></step>
+<step performance="required"><para>change folder to the package folder: <command>cd
+<replaceable>packagename</replaceable></command></para></step>
+<step performance="required"><para>configure the package: <command>./configure</command>
+<note><para>Some packages (notably kdebase) have special configuration
+options that might be applicable to your installation. Type
+<command>./configure <option>--help</option></command> to see the
+available options.</para></note></para></step>
+<step performance="required"><para>build the package: <command>make</command></para></step>
+<step performance="required"><para>install the package: <command>su <option>-c "make
+install"</option></command> (if you aren't already root). If you
+already are, just type <command>make
+<option>install</option></command>.</para></step>
+</procedure>
+</listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Post-installation procedures</para>
+</question>
+<answer>
+<para>First of all, please make sure that you have added &kde;'s binary
+installation folder (&eg; <filename
+class="directory">/usr/local/kde/bin</filename>) to your <envar>PATH</envar>
+and &kde;'s
+library installation folder to your <envar>LD_LIBRARY_PATH</envar> (only
+necessary on systems that do not support rpath; on &Linux; &ELF;, it
+should work without). This environment variable may be called
+differently on some systems, &eg; it is called
+<envar>SHLIB_PATH</envar> on &IRIX;. Then set the environment variable
+<envar>KDEDIR</envar> to the base of your &kde; tree, &eg; <filename
+class="directory">/usr/local/kde</filename>.
+<caution>
+<para>Please bear in mind that it is unwise to set
+<envar>LD_LIBRARY_PATH</envar> blindly. In the vast majority of cases it is
+unnecessary and can do more harm than good. There is a web page
+written by <ulink url="mailto:barr@cis.ohio-state.edu">Dave
+Barr</ulink> explaining the evils of <envar>LD_LIBRARY_PATH</envar> and it can be
+found at <ulink
+url="http://www.cis.ohio-state.edu/~barr/ldpath.html">http://www.cis.ohio-state.edu/~barr/ldpath.html</ulink>.</para>
+</caution>
+</para>
+<para>Even though you can use most of the &kde; applications simply by
+calling them, you can only benefit fully from &kde;'s advanced
+features if you use the &kde; window manager and its helper
+programs.</para>
+<para>In order to make it easy for you, we have provided a simple
+script called <filename>startkde</filename> which gets installed in <filename
+class="directory">$<envar>KDEDIR</envar>/bin</filename> and is therefore in your
+path.</para>
+<para>Edit the file <filename>.xinitrc</filename> in your home folder (make a backup
+copy first!), remove everything that looks like calling a window
+manager, and insert <command>startkde</command> instead. Restart the &X-Server;. If you use
+&kdm;/<application>xdm</application>, you will have to edit the file <filename>.xsession</filename> instead of
+<filename>.xinitrc</filename>. And if there is no <filename>.xinitrc</filename> or <filename>.xsession</filename> in your home
+folder, simply create a new one with just one line containing
+<command>startkde</command>.
+<note>
+<para>Some systems (notably &RedHat; &Linux;) use <filename>.Xclients</filename>
+instead.</para>
+</note></para>
+<para>This should present you with a new shining &kde; desktop. You
+can now start to explore the wonderful world of &kde;. In case you
+want to read some documentation first, there is a highly recommended
+<ulink
+url="http://www.kde.org/documentation/quickstart/index.html">Quick Start
+guide</ulink> available. Furthermore, every application has an online
+help that is available via the <guimenu>help</guimenu> menu.</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>Should I remove old version xyz before installing a new
+one?</para>
+</question>
+<answer>
+<para>In principle, this is not necessary. <acronym>RPM</acronym> and Debian packages
+should take care of all dependencies.</para>
+<para>If you compile the source code yourself, you should take more care.
+Instructions for running two different versions of &kde; on the same system are
+given at <ulink
+url="http://developer.kde.org/build/kde2-and-kde3.html">http://developer.kde.org/build/kde2-and-kde3.html</ulink>.
+However, please note that running two different versions of &kde; from source
+can lead to problems if you are not careful. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="startkde">
+<para>How do I start &kde;?</para>
+</question>
+<answer>
+<para>The most comfortable method to start &kde; is to use the
+<filename>startkde</filename> script. Simply put the line
+<command>startkde</command> at the end of your <filename>.xsession</filename>
+file (or your <filename>.xinitrc</filename> or <filename>.Xclients</filename>
+file if you are not using &kdm; or <application>xdm</application>). Please
+also remove the lines that start your previous window manager. If there is no
+<filename>.xsession</filename>, <filename>.xinitrc</filename>, or
+<filename>.Xclients</filename> in your home folder, simply create a new one
+that contains just one line: <command>startkde</command>.</para>
+</answer>
+</qandaentry>
+<!-- Still needed?
+<qandaentry>
+<question>
+<para>Whenever I start &kde;, it complains about "shadow passwords".
+Why?</para>
+</question>
+<answer>
+<para>When your system uses shadow passwords, the screensaver can only
+run properly if the suid bit is set. This bit gives the screensavers
+root privileges, which are needed to access the shadow passwords.
+<caution><para>The screensavers might be configured to secure the
+machine until the password is entered.</para></caution></para>
+<procedure>
+<title>Setting the suid bit on the screensavers</title>
+<step performance="required"><para>become root</para></step>
+<step performance="required"><para><command>chown root
+$<envar>KDEDIR</envar>/bin/*.kss</command></para></step>
+<step performance="required"><para><command>chmod u+s
+$<envar>KDEDIR</envar>/bin/*.kss</command></para></step>
+</procedure>
+<para>Alternatively, if you compile &kde; from source, you can use
+<command>./configure <option>with-shadow</option></command> to
+configure kdebase. Then the suid bit is set automatically during
+<command>make install</command>.</para>
+</answer>
+</qandaentry>
+-->
+<qandaentry>
+<question>
+<para>Is it possible to install &kde; in my home directory?</para>
+</question>
+<answer>
+<para>Yes, you can install &kde; in any folder you want. What you
+have to do depends on the kind of packages you want to install:</para>
+<procedure><title>Source packages</title>
+<step performance="required"><para>Configure and install the package using <command>configure
+<option>--prefix=<replaceable>/home/me</replaceable></option>;
+make; make install</command> to install into <filename
+class="directory">/home/me</filename>. Replace <replaceable>/home/me</replaceable> with your home directory, generally defined in <envar>$HOME</envar></para></step>
+<step performance="required"><para>Add the following to your init files. Please note that if
+it is not necessary for you to set <envar>LD_LIBRARY_PATH</envar>, it
+is better to leave it out.</para>
+
+<para>For csh or tcsh:</para>
+<programlisting>
+setenv KDEDIR /home/me
+
+if ( $?LD_LIBRARY_PATH ) then
+ setenv LD_LIBRARY_PATH $KDEDIR/lib:$LD_LIBRARY_PATH
+else
+ setenv LD_LIBRARY_PATH $KDEDIR/lib
+endif
+
+if ( ! $?LIBRARY_PATH ) then
+ setenv LIBRARY_PATH $LD_LIBRARY_PATH
+endif
+</programlisting>
+<para>For <application>bash</application>:</para>
+<programlisting>
+KDEDIR=/home/me
+PATH=$KDEDIR/bin:$PATH
+LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
+LIBRARY_PATH=$LD_LIBRARY_PATH
+export KDEDIR PATH LD_LIBRARY_PATH LIBRARY_PATH
+</programlisting></step>
+</procedure>
+<procedure><title><acronym>RPM</acronym> packages</title>
+<step performance="required"><para><command>rpm</command> allows you to use the
+<option>--prefix</option> option to select the folder you want to
+install to. For example, executing <command>rpm <option>-i
+--prefix=<replaceable>/home/me
+package.rpm</replaceable></option></command> will install the package
+to <filename
+class="directory">/home/me</filename>.</para></step>
+</procedure>
+<para><note>
+<para>Although &kde; will run from a user folder, there are some
+problems with programs that require suid root, &eg; the programs in
+the kdeadmin package. But since they are not meant to be run by users
+in the first place, this is nothing to worry about.</para>
+<para>However, on systems using shadow passwords, the screensavers
+have to be suid root to enable password access for unlocking the
+screen, so this option will not work.</para>
+</note></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para><command>startkde</command> fails with <errorname>can not connect to X
+server</errorname>. What is wrong?</para>
+</question>
+<answer>
+<para>You probably tried to start the X server with <command>startkde</command>. The X
+server is started with <command>startx</command>.
+<command>startkde</command> is the
+script that should be run from your <filename>.xinitrc</filename>, <filename>.xsession</filename>, or
+<filename>.Xclients</filename> to activate the window manager and the necessary server
+daemons for &kde;. See also <xref linkend="startkde"/>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>&kde; on &AIX;?</para>
+</question>
+<answer>
+<para>
+<!--
+<para>If you have trouble building &kde; on
+&AIX; check out Stefan Westerfeld's <ulink
+url="http://space.twc.de/~stefan/kde/aix.html">Running &kde; on
+Aix</ulink> page for lots of help on building &kde; on this
+exceptional &UNIX; variant.</para>
+-->
+<acronym>IBM</acronym> now officially support &kde; on &AIX;. You can find
+details at <ulink
+url="http://www.ibm.com/servers/aix/products/aixos/linux/index.html">http://www.ibm.com/servers/aix/products/aixos/linux/index.html</ulink>.
+There is also some older information at <ulink url="http://space.twc.de/~stefan/kde/aix.html">http://space.twc.de/~stefan/kde/aix.html</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>&kde; on a laptop?</para>
+</question>
+<answer>
+<para>If you can get &X-Window; to run on your laptop, you should not have any problem
+getting &kde; to run on it. In addition, you might find the following
+links helpful:</para>
+<itemizedlist>
+<listitem>
+<para><ulink url="http://www.linux-laptop.net/">http://www.linux-laptop.net/</ulink></para>
+</listitem>
+<listitem>
+<para><ulink url="http://www.sanpei.org/Laptop-X/note-list.html">http://www.sanpei.org/Laptop-X/note-list.html</ulink></para>
+</listitem>
+</itemizedlist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>I do not like the default &kde; folder after installation. How
+do I move it without breaking anything?</para>
+</question>
+<answer>
+<para>Assuming the default is <filename
+class="directory">/opt/kde</filename> and you want to move it to
+<filename class="directory">/usr/local/kde</filename>, here's what
+you have to do:</para>
+<procedure>
+<step performance="required"><para>change to superuser if you aren't already</para></step>
+<step performance="required"><para><command>mv /opt/kde /usr/local/kde</command></para></step>
+<step performance="required"><para><command>ln -s /usr/local/kde
+/opt/kde</command></para></step>
+</procedure>
+<para>This will put all your &kde; files in <filename
+class="directory">/usr/local/kde</filename> but everything is
+still accessible from <filename
+class="directory">/opt/kde</filename>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What files can I delete from my &kde; install folder? Can all the
+<filename>*.h</filename>, <filename>*.c</filename> and <filename>*.o</filename>
+files be safely removed?</para>
+</question>
+<answer>
+<para>There should not be any need to keep the <filename>.c</filename> and
+<filename>.o</filename> files, but you might want to keep the
+<filename>.h</filename> files, as they are used by includes if you ever want to
+compile your own &kde; programs. But if you wish to add patches to the source
+programs as they become available (rather than downloading everything again),
+then they should stay.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Will I lose my current settings when I upgrade &kde;?</para>
+</question>
+<answer>
+
+<para>No. In most cases &kde; will be able to transport your settings
+intact. You may need to reenter passwords in some applications (such
+as &kmail; or &knode;) but most other settings will be safe.</para>
+
+<para>There were mixed reports of results between some previous
+versions of &kde;. To be safe, you may like to back up your entire
+&kde; configuration. </para>
+
+<para>Settings are kept in the <filename
+class="directory">$<envar>HOME</envar>/.kde</filename> or <filename
+class="directory">$<envar>HOME</envar>/.kde2</filename> subfolder in your home
+folder. Copy your
+old <filename class="directory">.kde</filename>/<filename
+class="directory">.kde2</filename> folder to a backup location,
+install &kde; 3.2, and then copy back any necessary mail and news
+settings. That said, most people can make a direct upgrade, without
+removing the old <filename class="directory">.kde</filename> folder,
+ without a hitch.</para>
+<para>You can override the use of <filename
+class="directory">$<envar>HOME</envar>/.kde</filename> by setting the
+$<envar>KDEHOME</envar> variable.</para>
+</answer>
+</qandaentry>
+
+<qandaentry id="greyscreen">
+<question>
+<para>I upgraded &kde; and it seemed to go fine, but when I start it,
+I get a blank gray screen, and nothing happens. There are errors in
+the console about DCOPserver. What's going on?</para>
+</question>
+
+<answer>
+<para>
+&kde; uses several temporary files during its operation.
+These are usually to be found in the following locations:</para>
+<itemizedlist>
+<listitem><para><filename>~/.DCOPserver-*</filename> (there are usually two of these; one is a symlink to the other)</para></listitem>
+<listitem><para><filename>~/.kde/socket-<replaceable>hostname</replaceable></filename></para></listitem>
+<listitem><para><filename>~/.kde/tmp-<replaceable>hostname</replaceable></filename> which is normally a symlink to the next file:</para></listitem>
+<listitem><para><filename>/tmp/tmp-kde-<replaceable>USER</replaceable></filename></para></listitem>
+<listitem><para><filename>~/.kde/socket-<replaceable>hostname</replaceable></filename> which is also normally a symlink to:</para></listitem>
+<listitem><para><filename>/tmp/ksocket-<replaceable>USER</replaceable></filename></para></listitem>
+</itemizedlist>
+
+<para>If the symlinks get broken, usually because a
+<command>cron</command> or shutdown script is emptying out the
+<filename class="directory">/tmp</filename> folder, then strange
+things will happen. These files, and the symlinks, will all be
+created automatically at the start of &kde; so you can safely remove
+them <emphasis>while &kde; is not running</emphasis>.</para>
+
+<para>If you are only getting a gray screen when you start &kde;, or if you get an error message telling you to <errorname>Check your installation</errorname>, then shut down X and delete all the files listed above, then try to restart X.</para>
+
+<para>Normally (&ie; when not upgrading between &kde; versions) it's
+quite safe to leave these files intact, and you may shave a few
+seconds off your &kde; startup time by doing so.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Compiling kdebase gives me a <errorname>bin/sh: msgfmt: command
+not found</errorname> error!</para>
+</question>
+<answer>
+<para>You need the &GNU; <application>msgfmt</application> which is
+part of the &GNU; i18n package <application>gettext</application>.
+You should be able to download it from any
+&GNU; mirror.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I uninstall &kde; applications compiled from
+source?</para>
+</question>
+<answer>
+<para>You can uninstall your programs by typing <command>make
+uninstall</command> in the folder where you did <command>make
+install</command>. If you have already deleted that folder,
+then there is only one way, and it is not good: go to <filename
+class="directory">$<envar>KDEDIR</envar>/bin</filename> and start deleting files
+one by one.</para>
+<para>If you expect to find yourself in this situation, you might want to
+consider a program such as &GNU; <application>stow</application>, found at
+<ulink url="http://www.gnu.org/software/stow/stow.html">http://www.gnu.org/software/stow/stow.html</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="gif">
+<para>What is up with &GIF; support?</para>
+</question>
+<answer>
+<para>This has to do with issues with Unisys' &LZW; patent. &GIF;
+support is turned off from &Qt; 1.44 onwards by default. When you want to use
+&GIF;s and have the relevant license, recompile &Qt; with &GIF; support.
+<command>./configure <option>-gif</option></command>.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/doc/faq/intro.docbook b/doc/faq/intro.docbook
new file mode 100644
index 00000000..6f954679
--- /dev/null
+++ b/doc/faq/intro.docbook
@@ -0,0 +1,93 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="introduction">
+<title>Introduction</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>What is &kde;?</para>
+</question>
+<answer>
+<para>&kde; is the K Desktop Environment. It is a project initiated
+by <ulink url="mailto:ettrich@kde.org">Matthias Ettrich</ulink> in
+1996. The aim of the &kde; project is to connect the
+power of the &UNIX; operating systems with the comfort of a modern user
+interface.</para>
+<para>In short, &kde; will bring &UNIX; to the desktop!</para>
+<para>If you want further information about &kde;, have a look at
+<ulink url="http://www.kde.org/whatiskde">What is
+&kde;?</ulink></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="platform">
+<para>On which platforms can I expect &kde; to work?</para>
+</question>
+<answer>
+<para>&kde; is a Desktop Environment for all flavors of &UNIX;. While
+it is true that most &kde; developers use &Linux;, &kde; runs smoothly
+on a wide range of systems. You may, however, need to tweak the
+source code a bit to get &kde; to compile on a not-so-popular variant
+of &UNIX;, or if you are not using the &GNU; development tools, in
+particular the &gcc; compiler.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is &kde; a window manager?</para>
+</question>
+<answer>
+<para>No, &kde; is not a window manager. While &kde; includes a very
+sophisticated window manager (&kwin;), &kde; is much more than that.
+It is a full-blown Integrated Desktop Environment.</para>
+<para>&kde; provides a complete desktop environment, including a web
+browser, a file manager, a window manager, a help system, a
+configuration system, uncountable tools and utilities, and an ever
+increasing number of applications, including but not limited to mail
+and news clients, drawing programs, a &PostScript; and a &DVI; viewer
+and so forth.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is &kde; a <acronym>CDE</acronym>, &Windows; or &Mac;
+<acronym>OS</acronym> clone?</para>
+</question>
+<answer>
+<para>No, &kde; is not a clone. Specifically &kde; is not a
+<acronym>CDE</acronym> or &Windows; clone. While the &kde; developers
+have and will continue to glean the best features from all existing
+desktop environments, &kde; is a truly unique environment that has and
+will continue to go its own way.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is &kde; free software?</para>
+</question>
+<answer>
+<para>Yes, &kde; is free software according to the &GNU; General
+Public License. All &kde; libraries are available under the
+<acronym>LGPL</acronym> making commercial software development for the
+&kde; desktop possible, but all &kde; applications are licensed under
+the <acronym>GPL</acronym>.</para>
+<para>&kde; uses the <link linkend="qt">&Qt; C++ crossplatform
+toolkit</link>, which is also released (since version 2.2) under the
+<acronym>GPL</acronym>.</para>
+<para>It is absolutely legal to make &kde; and &Qt; available on
+&CD-ROM; free of charge. No runtime fees of any kind are
+incurred.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
diff --git a/doc/faq/kdeapps.docbook b/doc/faq/kdeapps.docbook
new file mode 100644
index 00000000..95ff1355
--- /dev/null
+++ b/doc/faq/kdeapps.docbook
@@ -0,0 +1,158 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="applications">
+<title>&kde; applications</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>&kppp;</para>
+</question>
+<answer>
+
+<para>Many &kde; users report problems using &kppp;. But before you
+complain about &kppp;, make sure you have already checked the
+following:</para>
+
+<itemizedlist>
+<listitem><para>Can you dialup to your <acronym>ISP</acronym> without using &kppp;? If you cannot, then perhaps &kppp; is not the culprit after
+all.</para></listitem>
+<listitem><para>Have you gone through the &kppp; documentation at
+least three times and followed its instructions and trouble-shooting
+suggestions?</para></listitem>
+</itemizedlist>
+<para>The &kppp; documentation can be accessed through the
+<application>&kde; Help Center</application>.
+ Last, but not least, the &kppp; homepage is at <ulink
+ url="http://ktown.kde.org/~kppp/">http://ktown.kde.org/~kppp/</ulink>.</para>
+<para>Now, if you still encounter problems, here's what might help you
+solve them:</para>
+<variablelist>
+<varlistentry><term>How do I change the &MTU; setting in &kppp;?</term>
+<listitem><para>Open up the &kppp; dialog box and select
+<guibutton>Setup</guibutton>. Choose an existing account and click
+<guibutton>Edit</guibutton>, or <guibutton>New</guibutton> to create a
+new dialup account. Select the <guilabel>Dial</guilabel> tab and
+click <guibutton>Arguments</guibutton>. Type what you want to change
+in the Argument textbox (&eg; <userinput>mtu 296</userinput>) and
+click <guibutton>Add</guibutton>. When you are satisfied, click
+<guibutton>Close</guibutton>.</para>
+<para>To check whether the options <quote>took</quote>, do one of the following:</para>
+<itemizedlist>
+<listitem>
+<para>In a terminal window, run
+<userinput><command>/sbin/ifconfig</command> ppp0</userinput> and look
+at the reported &MTU; in the output. It should match your
+request.</para>
+</listitem>
+<listitem><para>Add <option>debug</option> and <option>kdebug</option>
+(each on a separate line) to your
+<filename>/etc/ppp/options</filename> file and restart your
+&PPP; session. You will find debugging messages in
+<filename>/var/log/messages</filename>, including &MRU; and &MTU;
+settings.</para></listitem>
+</itemizedlist>
+<para>If you want, the &MRU; and &MTU; settings can be added to the
+<filename>options</filename> file, one complete setting per line, no
+quotes or dashes.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&kppp; connects at a slower speed than
+normal.</term>
+<listitem><para>The following might do the trick:</para>
+<itemizedlist>
+<listitem><para>Try executing <command>setserial
+spd_hi</command>.</para></listitem>
+<listitem><para>The default &MTU; value is 1500,
+which maybe too large
+for a dialup connection. Try changing it to a smaller value like
+<userinput>296</userinput>
+or <userinput>576</userinput>.</para></listitem>
+<listitem><para>Check in your <filename
+class="directory">$<envar>HOME</envar>/.kde/share/config</filename> for the
+<filename>kppprc</filename>. Ensure the correct modem speed is
+actually defined there.</para></listitem>
+</itemizedlist></listitem>
+</varlistentry>
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>&konsole;</para>
+</question>
+<answer>
+<variablelist>
+
+<varlistentry>
+<term>How do I page-up or page-down?</term>
+<listitem><para>Use <keycombo action="simul">
+<keycap>Shift</keycap><keycap>Page Up</keycap></keycombo>
+and <keycombo action="simul"><keycap>Shift</keycap><keycap>Pg
+Dn</keycap></keycombo>.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>How do I perform a simple <quote>copy</quote> from &konsole; to
+anything else?</term>
+<listitem><para>When I do a <command>ls</command>, first I select with
+the mouse the desired text, press
+<keycombo action="simul">&Ctrl;<keycap>C</keycap></keycombo>,
+then I make the target application active, point the mouse to the
+relevant part and press <keycombo
+action="simul">&Ctrl;<keycap>V</keycap></keycombo>.
+Alternatively, highlight the text by dragging with the &LMB; down and
+paste by clicking with the &MMB; (or both buttons if you are using a
+2 button mouse with 3 button emulation).
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Why can't &konsole; find the <quote>9x15</quote> and the 2
+<quote>console</quote> bitmap fonts installed with &kde;?</term>
+<listitem>
+
+<para><application>FontConfig</application> must find the three fonts
+installed in: <filename
+class="directory">$<envar>KDEDIR</envar>/share/fonts</filename>.
+ If
+the &kde; install does not install these fonts in a directory that
+already exists (&eg; <filename
+class="directory">/usr/share/fonts</filename>) then you must add this
+directory to the configuration file <filename
+class="directory">/etc/fonts/local.conf</filename>. This should be
+the first line after <quote>&lt;fontconfig&gt;</quote>. For example:
+<programlisting>
+&lt;fontconfig&gt;
+&lt;dir&gt;/usr/kde3/share/fonts&lt;/dir&gt;
+&lt;/fontconfig&gt;
+</programlisting>
+After adding the directory, run (as root):
+<userinput><command>fc-cache</command> -v</userinput> and check that
+it found the directory.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>&kmail;</para>
+</question>
+<answer>
+<para>&kmail; has its own home page at <ulink
+url="http://kmail.kde.org">http://kmail.kde.org</ulink> where an
+<acronym>FAQ</acronym> is available.</para>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
diff --git a/doc/faq/misc.docbook b/doc/faq/misc.docbook
new file mode 100644
index 00000000..61d2950f
--- /dev/null
+++ b/doc/faq/misc.docbook
@@ -0,0 +1,219 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="misc">
+<title>Miscellaneous questions</title>
+
+<qandaset>
+
+
+<qandaentry>
+<question>
+<para>Does &kde; support transparency and other visual effects provided by the new composite extension to X.org?</para>
+</question>
+<answer>
+<para> Yes! An exciting new feature for &kde; 3.4 is support for the new X composite extension. This allows for effects such as translucency and drop shadows for all windows, easily configurable through &kwin;'s configuration dialog. This requires you to be using X.org version 6.8.0 or newer and have:
+
+<screen>
+Section "Extensions"
+Option "Composite" "Enable"
+EndSection
+</screen>
+
+In your <filename>xorg.conf</filename>. If you have an nvidia graphics card and use the nvidia driver you can improve the performance of these effects by also adding the RenderAccel option to the Device section for your graphics card:
+
+<screen>
+Section "Device"
+ Identifier "nvidia-fx5200"
+ Driver "nvidia"
+ Option "RenderAccel" "true"
+</screen>
+Once you have configured X.org correctly, transparency and other effects can be enabled through the <menuchoice><guimenu>Desktop</guimenu><guimenuitem>Window Behavior</guimenuitem></menuchoice> &kcontrolcenter; module, under the <guilabel>Translucency</guilabel> tab.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What about &kde; programs that do not have icons? How do I get
+them into the menu?</para>
+</question>
+<answer>
+<para>Use &kmenuedit;. To access it use the &RMB; on the
+<guibutton>K</guibutton> button and select <guimenu>Menu Editor</guimenu>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Does &kde; have a graphical &FTP; client?</para>
+</question>
+<answer>
+<para>Yes, and it is none other than your favorite file
+manager, &konqueror;. You can drag and drop remote files into local
+folders.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I exit &kde;?</para>
+</question>
+<answer>
+<para>Simply click on the <guibutton>K</guibutton> button and select
+<guimenu>Logout</guimenu>. In addition, if you
+<mousebutton>right</mousebutton> click on an
+empty area of the desktop, you will be presented with a menu
+containing logout as one of the options.
+<note><para>Depending on your configuration of the &X-Window;, <keycombo
+action="simul">&Ctrl;&Alt;&Backspace;</keycombo>
+might also do the trick by killing the X server, but its use prevents
+session management and cannot be recommended.</para></note></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is there a program that checks for new mails at my
+<acronym>ISP</acronym> if and only if I am online?</para>
+</question>
+<answer>
+<para>&korn; will do the job. If you are not
+connected, it will just sit there (idling).</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is it really necessary to upgrade to the latest version?</para>
+</question>
+<answer>
+<para>We recommend to always use the latest stable release. If you
+don't, it will probably be difficult to get answers to your
+questions. If you have a problem with an old version, the answer will
+probably be <quote>Please upgrade and try again</quote>. Note that
+new versions also sometimes fix security problems.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I copy and paste in &kde;?</para>
+</question>
+<answer>
+<para>The simplest method is to use your mouse:</para>
+<procedure>
+<step performance="required"><para>Highlight the text you want to copy by holding down the
+&LMB; and dragging across the text. This adds the selected text to the clipboard.</para></step>
+<step performance="required"><para>Go to the destination area; depending on your configuration,
+you might need to click it using the &LMB; to give it
+focus.</para></step>
+<step performance="required"><para>Click the &MMB; to paste. If you have a two
+button mouse and are emulating a three button mouse, push both buttons
+simultaneously.</para></step>
+</procedure>
+
+<para>For more information about using the clipboard in &kde; please see the &klipper; hand book, accessed by typing <userinput><command>help:/klipper</command></userinput>
+into the &konqueror; address bar. </para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I convert the default &RedHat; menus into a menu in the
+<guimenu>K</guimenu> menu?</para>
+</question>
+<answer>
+<para>Click on the <guibutton>K</guibutton> button and select
+<menuchoice><guimenu>System</guimenu><guimenuitem>Appfinder</guimenuitem></menuchoice>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="CVS">
+<para>What is <acronym>CVS</acronym>?</para>
+</question>
+<answer>
+<para>It stands for Concurrent Versions System. It is a version
+control system and is based on <acronym>RCS</acronym> (Revision
+Control System), but
+offers more functionality. It is used to maintain source code under
+development. It will keep multiple versions of things (handy if you
+broke something and have to back up and get a clean old version), and
+allows people remote access over the Net to pick up the latest source
+code and even to check in new files if they have permission. It is
+also open source (you pay for support if you want it), and since it is
+free it is the system of choice for people writing more free products,
+such as &kde;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Does &kde; support dual screen (Xinerama)?</para>
+</question>
+<answer>
+<para>Yes, you need to have a multi-headed X server
+(&eg; MetroX or XFree86 4.0 and above) and a &kde; >= 2.2.1
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Why does Drag and Drop not work with Xinerama?</para>
+</question>
+<answer>
+<para>You should upgrade to XFree86 4.2.0 for this to work properly.</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>How do I check which version of &kde; I am using?</para>
+</question>
+<answer>
+<para>Fire up your <application>&kde; Control
+Center</application>. It comes up with an Info Screen including the version of &kde;
+The &kde; version is also included in the application's
+<guimenuitem>About</guimenuitem> dialog.
+</para>
+</answer>
+</qandaentry>
+
+
+
+<qandaentry>
+<question>
+<para>How do I go about creating themes and icons?</para>
+</question>
+<answer>
+<para>Go see <ulink
+url="http://artist.kde.org">http://artist.kde.org</ulink>.
+There is also a more informal community of &kde; related artists and
+artwork at <ulink url="http://kde-look.org">http://kde-look.org</ulink>.
+</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>How can I get to know about development updates?</para>
+</question>
+<answer>
+<para>You might want to subscribe to the various &kde; mailing lists
+available, especially kde-cvs, which lists all commits done to the
+&kde; <acronym>CVS</acronym> repository. Check <ulink
+url="http://lists.kde.org">http://lists.kde.org</ulink> if you want to
+read without subscribing.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
+
diff --git a/doc/faq/moreinfo.docbook b/doc/faq/moreinfo.docbook
new file mode 100644
index 00000000..9b28db3a
--- /dev/null
+++ b/doc/faq/moreinfo.docbook
@@ -0,0 +1,154 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="more-info">
+<title>Getting more information</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>Where is the &kde; homepage?</para>
+</question>
+<answer>
+<para>The &kde; homepage is located at <ulink
+url="http://www.kde.org">http://www.kde.org</ulink>. If you prefer a
+local mirror, there are several to choose from. For a current list of
+web site mirrors sorted by location, please visit <ulink
+url="http://www.kde.org/mirrors/web.php">http://www.kde.org/mirrors/web.php</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="mailing-lists">
+<para>Is there a &kde; mailing list?</para>
+</question>
+<answer>
+<para>There are several &kde; mailing lists. Each focuses on a different
+aspect of &kde;. Some are for developers, so they are not
+discussed in detail. Some of the more important lists that users
+might be interested in are:</para>
+<variablelist>
+<varlistentry><term>kde</term>
+<listitem><para>This is the main &kde; mailing list for general
+discussions.</para></listitem>
+</varlistentry>
+<varlistentry><term>kde-announce</term>
+<listitem><para>This list is used to announce new versions of &kde; as
+well as new tools and applications.</para></listitem>
+</varlistentry>
+<varlistentry><term>kde-look</term>
+<listitem><para>This is the list that deals with questions about look and
+feel, and general user interface considerations.</para></listitem>
+</varlistentry>
+</variablelist>
+<para>For the complete list of mailing lists available, please refer
+to <ulink
+url="http://www.kde.org/mailinglists/">http://www.kde.org/mailinglists/</ulink>.</para>
+<para>Please note that it is not a good idea to ask questions which are
+already answered in this &FAQ;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="subscribe">
+<para>How do I subscribe/unsubscribe to these lists?</para>
+</question>
+<answer>
+<para>To subscribe, send an email to list-request, that is:</para>
+<itemizedlist>
+<listitem><para><ulink
+url="mailto:kde-request@kde.org">kde-request@kde.org</ulink></para></listitem>
+<listitem><para><ulink url="mailto:kde-announce-request@kde.org">kde-announce-request@kde.org</ulink></para></listitem>
+<listitem><para><ulink url="mailto:kde-look-request@kde.org">kde-look-request@kde.org</ulink></para></listitem>
+</itemizedlist>
+<para>The email must contain <userinput>subscribe
+<replaceable>your_email_address</replaceable></userinput> in the
+subject.</para>
+<para>To unsubscribe, send an email to list-request, that is:</para>
+<itemizedlist>
+<listitem><para><ulink url="mailto:kde-request@kde.org">kde-request@kde.org</ulink></para></listitem>
+<listitem><para><ulink url="mailto:kde-announce-request@kde.org">kde-announce-request@kde.org</ulink></para></listitem>
+<listitem><para><ulink url="mailto:kde-look-request@kde.org">kde-look-request@kde.org</ulink></para></listitem>
+</itemizedlist>
+<para>The email must contain <userinput>unsubscribe
+<replaceable>your_email_address</replaceable></userinput> in the
+subject.
+<important><para>Never send subscribe/unsubscribe request to the
+mailing lists directly! Use the list-request
+instead.</para></important></para>
+<para>There is also a complete list of all &kde;-related mailing
+lists, and a web interface for subscribing and unsubscribing located
+at <ulink url="http://master.kde.org/mailman/listinfo">http://master.kde.org/mailman/listinfo</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is there a mailing list archive?</para>
+</question>
+<answer>
+
+<para>Yes, there is a searchable mailing list archive hosted by <ulink
+url="http://www.progressive-comp.com">Progressive Computer
+Concepts</ulink>. The &URL; is <ulink
+url="http://lists.kde.org">http://lists.kde.org</ulink>. There you
+will see a folder listing of the mailing lists. Note that you can
+only do a subject/author search at this level. You probably will not
+find what you want doing this kind of search.</para>
+
+<para>To do a body search, you have to enter one of the mailing lists.
+Just click on the folder you want to search (&eg; <quote>kde</quote>
+or <quote>kde-devel</quote>) and then the pull-down menu by the search
+box will default to <quote>Body</quote> searches. To be thorough, you
+should probably search the <quote>kde</quote>, <quote>kde-linux</quote>, and <quote>kde-devel</quote> folders. </para>
+
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="newsgroups">
+<para>Is there a newsgroup about &kde;?</para>
+</question>
+<answer>
+<para>Yes, there is! It is at <literal>comp.windows.x.kde</literal>.
+In addition, there is also a German newsgroup at
+<literal>de.alt.comp.kde</literal>. Please note that it is not a good
+idea to ask questions which are already answered in this
+&FAQ;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Are there any other &kde;-related
+&FAQ;s?</para>
+</question>
+<answer>
+<para>Yes. Here is a list of them:</para>
+<itemizedlist>
+<listitem><para><ulink
+url="http://www.kde.org/info/faq.php">&kde; &FAQ;</ulink></para></listitem>
+<listitem><para><ulink
+url="http://konqueror.org/faq/">&konqueror;
+&FAQ;</ulink></para></listitem>
+<listitem><para><ulink
+url="http://www.arts-project.org/doc/manual/index.html">aRts
+sound server documentation</ulink></para></listitem>
+
+<!-- Removed because the kmail FAQ is part of the KMail manual and not a -->
+<!-- separate document
+<listitem><para><ulink
+url="http://kmail.kde.org/manual/faq.html">&kmail;
+&FAQ;</ulink></para></listitem>
+-->
+
+</itemizedlist>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
+
diff --git a/doc/faq/nonkdeapps.docbook b/doc/faq/nonkdeapps.docbook
new file mode 100644
index 00000000..e0e73254
--- /dev/null
+++ b/doc/faq/nonkdeapps.docbook
@@ -0,0 +1,106 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="non-kde-apps">
+<title>&kde; with non-&kde; applications</title>
+
+<!-- FIXME: This seems to be obsolete. The only similar option is "Apply
+*colors* to -->
+
+<!-- non-kde apps" -->
+<qandaset>
+<qandaentry>
+<question>
+<para>My non-&kde; applications like &Emacs; and
+<application>kterm</application> are running amok with strange
+colors!</para>
+</question>
+<answer>
+<para>Start the <application>&kde; Control Center</application> and in
+<menuchoice><guimenu>Appearance &amp; Themes</guimenu><guimenuitem>
+Colors</guimenuitem></menuchoice> uncheck the <guilabel>Apply colors to
+non-KDE applications</guilabel> checkbox and click
+<guibutton>Apply</guibutton>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>How can I set my default web browser to be something other
+than &konqueror;?</para></question>
+<answer>
+<para>If you are using &kde; 3.3 or later, open up the &kcontrolcenter; and
+navigate to the <menuchoice><guimenu>KDE
+Components</guimenu><guimenuitem>Component
+Chooser</guimenuitem></menuchoice> panel. Select <guilabel>Web
+Browser</guilabel> from the list on the left, then select <guilabel>Open
+http and https URLs in the following browser:</guilabel> and type in the
+name of the browser (&eg; <application>mozilla</application>,
+<application>firefox</application>, <application>opera</application>, &etc;)
+in the textbox.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How can I configure the style and fonts of <acronym>GTK</acronym>
+applications within &kde; ?
+</para>
+</question>
+<answer>
+<para>
+The simplest way to achieve this is to download and compile the
+<acronym>gtk-qt</acronym> theme engine from <ulink
+url="http://www.freedesktop.org/Software/gtk-qt">
+http://www.freedesktop.org/Software/gtk-qt</ulink>. This theme engine makes
+your <acronym>GTK</acronym> applications look like your &kde; widget style
+by calling functions from &Qt; instead of drawing the styles itself. Once
+the theme engine has been installed, there will be a &kcontrolcenter; module
+under <menuchoice><guimenu>Appearance &amp; Themes</guimenu><guimenuitem>GTK
+Styles and Fonts</guimenuitem></menuchoice>.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>I have been hearing about this gecko kpart or &Qt; Mozilla, how do I
+get these?</para>
+</question>
+<answer>
+<para>
+Good luck! The &Qt; Mozilla code is in Mozilla cvs, and not very stable as
+of yet. In order to use it, you'll have to check out Mozilla from cvs
+according to these instructions:
+<ulink url="http://www.mozilla.org/cvs.html">
+http://www.mozilla.org/cvs.html</ulink>. Then, configure either the Mozilla
+suite or the Firefox browser with the option
+<command>--enable-default-toolkit=qt</command> in addition to any other
+options you would like to enable. More instructions on building Mozilla can
+be found <ulink url="http://www.mozilla.org/build">here</ulink>.
+</para>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+sgml-omittag:nil
+sgml-shorttag:nil
+sgml-namecase-general:nil
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:true
+sgml-parent-document:("index.docbook" "book" "chapter")
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+--> \ No newline at end of file
diff --git a/doc/faq/notrelated.docbook b/doc/faq/notrelated.docbook
new file mode 100644
index 00000000..fd66e1a6
--- /dev/null
+++ b/doc/faq/notrelated.docbook
@@ -0,0 +1,232 @@
+<!-- if you want to validate this file separately, uncomment this prolog:
+
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+
+-->
+
+<chapter id="not-kde">
+<title>Not really &kde;-related, but frequently asked nevertheless.</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>How do I change the screen resolution?</para>
+</question>
+<answer>
+<para>Use <keycombo
+action="simul">&Ctrl;&Alt;<keycap>+</keycap></keycombo> and <keycombo
+action="simul">&Ctrl;&Alt;<keycap>-</keycap></keycombo> to cycle through
+the resolutions you have defined in <filename>XF86Config</filename> (maybe under
+<filename class="directory">/etc/X11</filename>; poke around first).
+If you prefer to get your hands dirty, you can always edit the file
+directly. By placing your favorite resolution at the beginning (or
+making it the only one listed), &X-Window; will always start up with that
+resolution.
+<caution><para>Always make a backup copy of your <filename>XF86Config</filename> file
+<emphasis>before</emphasis> you start editing it. Errors in this file
+can render &X-Window; unusable.</para></caution>
+<note><para>These instructions are only valid if you are running
+version 3.3.x of the XFree86 server. If you are running XFree86 4.x,
+you must consult with the <ulink url="http://xfree.org">XFree86(TM):
+Home Page</ulink>.</para></note></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I change the color depth?</para>
+</question>
+<answer>
+<para>There is no way you can do this on the fly. You can either
+start &X-Window; using <command>startx <option> -bpp
+<replaceable>number</replaceable></option></command> where
+<replaceable>number</replaceable> can be 8, 16, 24 or 32, depending on
+the depth you want. Alternatively, if you are using
+<application>xdm</application>/&kdm;, you
+need to edit
+<filename>/etc/X11/xdm/Xservers</filename> (may vary) and enter
+<userinput>:0 local /usr/X11R6/bin/X -bpp 16</userinput> for 16 bit color
+depth.</para>
+<para>You can also edit the <filename>XF86Config</filename> file and add a line
+like <userinput>DefaultColorDepth
+<replaceable>number</replaceable></userinput> to Section "Screen".
+The next time you start X, it will run with the newly-configured color
+depth.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What can I do if I am using a 2-button mouse?</para>
+</question>
+<answer>
+<para>Go buy a 3-button one, or use third button emulation. The third
+button is emulated by pressing both the &LMB; and the &RMB;
+together. You would need to enable <option>Emulate3Buttons</option>
+in your <filename>XF86Config</filename> file. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What is a "sticky" window?</para>
+</question>
+<answer>
+<para>In a virtual desktop environment with multiple virtual desktops, a
+"sticky" window will stay put on the screen when you switch between
+desktops, as if sticking to the glass of the screen.
+<application>Xclock</application> is a typical candidate for sticking,
+as you need to run only one instance of it, and it always stays with
+you. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I replace the "X" mouse pointer with an arrow?</para>
+</question>
+<answer>
+<para>The various types of cursor available in X are defined in
+<filename class="headerfile">X11/cursorfont.h</filename>. You can
+change it using <command>xsetroot -cursor_name
+<replaceable>name_of_cursor</replaceable></command>. For example, I
+have the following in my <filename>.Xclients</filename>:</para>
+<screen>
+xsetroot -cursor_name left_ptr
+</screen>
+<para>This will create the common left-angled pointer. To see other
+alternatives, type <command>xfd -fn cursor</command>. And of course,
+do not forget that <command>man xsetroot</command> is your
+friend.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I extract/install diff files?</para>
+</question>
+<answer>
+<para>To generate a context-diff suitable for patching, use
+<command>diff -u <replaceable>old-file new-file</replaceable> &gt;
+<replaceable>patchfile</replaceable></command>. To apply the diff to
+a file (<abbrev>i.e.</abbrev> "patch the file"), execute
+<command>patch &lt; <replaceable>patchfile</replaceable></command>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I get &Linux; to mount the floppy device for use with both
+DOS and ext2 formatted floppies?</para>
+</question>
+<answer>
+<para>Just specify the filesystem type as auto in
+<filename>/etc/fstab</filename>. Auto detection works fine for DOS and
+ext2.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I start &kde; with the <keycap>Num Lock</keycap> on?</para>
+</question>
+<answer>
+<para>Have you tried <command>man setleds</command>? In addition, you
+might want to edit your
+<filename>$<envar>HOME</envar>/.Xmodmap</filename> and put the
+following lines in:</para>
+<screen>
+! redefines numeric keypad to be used without NumLock
+keycode 79 = 7
+keycode 80 = 8
+keycode 81 = 9
+
+keycode 83 = 4
+keycode 84 = 5
+keycode 85 = 6
+
+keycode 87 = 1
+keycode 88 = 2
+keycode 89 = 3
+
+keycode 90 = 0
+keycode 91 = comma
+keycode 86 = plus
+
+! deactivates NumLock key
+keycode 77 =
+</screen>
+<para>Other possible alternatives:</para>
+<itemizedlist>
+<listitem><para><application>xkeycaps</application>:
+<mousebutton>right</mousebutton> clicking should allow edits. You may
+have to do this as root.</para></listitem>
+<listitem><para><command>man XF86Config</command> and look under
+section Keyboard.</para></listitem>
+<listitem><para>Install <application>NumLockX</application>, which is
+available from <ulink
+url="http://dforce.sh.cvut.cz/~seli/en/numlockx">http://dforce.sh.cvut.cz/~seli/en/numlockx</ulink>.</para></listitem>
+</itemizedlist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I take window or desktop screenshots?</para>
+</question>
+<answer>
+<para>Use &ksnapshot;.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Is there a tool to make webpages?</para>
+</question>
+<answer>
+<para>Yes, and there are a lot of them out there, including
+<application>StarOffice</application>, <application>&Netscape; Composer</application>, and
+<application>XEmacs</application>.
+There are also many &kde; applications. To find the most current
+list, go to <ulink url="http://kde-apps.org">kde-apps.org: The
+Latest in &kde; Applications</ulink> and search for <emphasis>web
+development</emphasis>. Try as many as possible and choose the one
+most suitable to your needs.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What do all those acronyms like AFAIK mean?</para>
+</question>
+<answer>
+<para><screen>
+AAMOF: as a matter of fact
+AFAIK: as far as I know
+AISE: as I see it
+BFN: bye for now
+BION: believe it or not
+BRB: be right back
+BTW: by the way
+CMIIW: correct me if I am wrong
+FUD: fear, uncertainty, and doubt
+FWIW: for what it's worth
+FYI: for your information
+HTH: hope this helps
+IIRC: if I recall correctly
+IMHO: in my humble opinion
+LOL: laughing out loud
+MYOB: mind your own business
+PITA: pain in the ass
+ROTFL: rolling on the floor laughing
+RTFM: read the fine manual
+SOP: standard operating procedure
+TIA: thanks in advance
+YMMV: your mileage may vary
+</screen></para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter>
diff --git a/doc/faq/panel.docbook b/doc/faq/panel.docbook
new file mode 100644
index 00000000..5814dc61
--- /dev/null
+++ b/doc/faq/panel.docbook
@@ -0,0 +1,193 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+
+<chapter id="panel">
+<title>The panel</title>
+
+
+<qandaset>
+<qandaentry>
+<question>
+<para>How do I add applications to the &kde; panel (&kicker;)?</para>
+</question>
+<answer>
+<para>There are several ways to add an application to the panel, of
+which the easiest is to right-click on the panel, and from the context
+menu which appears, select <menuchoice><guimenu>Panel
+Menu</guimenu><guisubmenu>Add to
+Panel</guisubmenu><guisubmenu>Application
+Button</guisubmenu></menuchoice> and then the application for which
+you want to add a link.</para> <para>For more ways of adding buttons
+to the panel, refer to the &kicker; Handbook.</para>
+
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>Is it possible to change the <guibutton>K</guibutton> button of
+the panel to another picture?</para>
+</question>
+<answer>
+<para>The simplest way is to download a new icon theme with a &kmenu; icon
+you prefer from
+<ulink url="http://www.kde-look.org">http://www.kde-look.org</ulink> and
+install it using the &kcontrolcenter;.</para>
+<para>In order to change only the &kmenu; icon you can overwrite the
+<filename>kmenu.png</filename> image for every size in an icon theme set.
+So, for &kde; default icons this would be <filename>$<envar>KDEDIR</envar>/share/icons/default.kde/<replaceable>size</replaceable>/apps/kmenu.png</filename>,
+where <replaceable>size</replaceable> is one of the sizes included in the
+&kde; icon theme.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>
+After an upgrade my &kmenu; appears to be empty! How can I get my menu back?
+</para>
+</question>
+<answer>
+<para>
+In &kde; 3.2 and later local modifications to the &kmenu; are stored
+in
+<filename>$<envar>HOME</envar>/.config/menus/applications-kmenuedit.menu
+</filename>. Try moving this file out of the way and then issuing the
+command <userinput><command>kbuildsycoca</command>
+<option>--noincremental</option></userinput>. This should restore you to the
+default system menus.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>My desktop panel has disappeared. How can I get it
+back?</para>
+</question>
+
+<answer>
+
+<para>The panel disappearing is usually due to it crashing. This is
+most often caused by loading an applet that has a fatal bug or due to
+a bad installation of &kde; and/or the panel.</para>
+
+<para>The easiest way to get the panel back is to launch the
+<guilabel>Run Command</guilabel> window by pressing <keycombo
+action="simul">&Alt;<keycap>F2</keycap> </keycombo> and entering
+<userinput><command>kicker</command></userinput> and then pressing the
+<guibutton>OK</guibutton> button.</para>
+
+<para>If the panel continues to disappear, you may wish to either
+remove or edit by hand your
+<filename>$<envar>KDEHOME</envar>/share/config/kickerrc</filename>
+file, where <filename
+class="directory">$<envar>KDEHOME</envar></filename> is usually
+<filename class="directory">~/.kde</filename>. If you choose to edit
+it by hand, start by removing the applet entry groups.</para>
+
+</answer>
+</qandaentry>
+
+<qandaentry><question>
+<para>Where did the Icon Zooming option that used to be in &kicker; go?
+</para></question>
+<answer><para>
+Icon zooming was not actively maintained and had caused severe bugs and usability issues. It was replaced in &kde; 3.4 by the new mouse over effects, which combine esthetics with useful information.
+</para></answer>
+
+</qandaentry>
+
+<qandaentry>
+<question><para>How can I start an application minimized to the system
+tray?</para>
+</question>
+<answer>
+<para>Use <command>ksystraycmd</command>. For example, to start a &konsole; hidden
+in the system tray, run <userinput><command>ksystraycmd </command>
+<option>--hidden</option> <command>konsole</command></userinput>. For
+more information about <command>ksystraycmd</command>, see the section
+<quote>Advanced Window Management</quote> in the &kde;
+User Guide.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>How do I use the &Windows; key to open the &kmenu;?</para>
+</question>
+
+<answer><para>Previous versions of &kde; provided a trick to allow you to
+use the &Windows; key both as a modifier (so you could have shortcuts
+like <keycombo action="simul"><keysym>Win</keysym><keycap>R</keycap>
+</keycombo>), and as a regular key (so that pressing
+<keysym>Win</keysym> on its own could open the &kmenu;). This feature
+was removed for reasons of usability and accessibility, as well as
+keeping the code clean. For current versions of &kde;, you have two
+options: either use a different shortcut to open the &kmenu; (the
+default is <keycombo action="simul">&Alt;<keycap>F1</keycap>
+</keycombo>), or remap the <keysym>Win</keysym> key to be a regular
+key, rather than a modifier.</para>
+
+<para>If you choose to do the second, here's one way:
+
+<orderedlist>
+<listitem><para>Find the keycode for your <keysym>Win</keysym> key
+using <command>xev</command>: Run the command
+<userinput><command>xev</command></userinput> in a &konsole;, and
+press the <keysym>Win</keysym> key. Look in the output of
+<command>xev</command> for
+<computeroutput>keycode <replaceable>n</replaceable></computeroutput>,
+where <replaceable>n</replaceable> is the keycode of the
+<keysym>Win</keysym> key.</para>
+</listitem>
+
+<listitem><para>Use <command>xmodmap</command> to remap the
+<keysym>Win</keysym> key. An appropriate command is <userinput><command>xmodmap
+<option>-e</option> 'keycode
+<replaceable>n</replaceable>=Menu'</command></userinput>.</para>
+</listitem>
+
+<listitem><para>In the &kcontrolcenter;, go to
+<menuchoice><guimenu>Regional &amp;
+Accessibility</guimenu><guimenuitem>Keyboard Shortcuts</guimenuitem>
+</menuchoice> and set the shortcut for <guilabel>Popup Launch
+Menu</guilabel> to the <keysym>Win</keysym> key. You should now be
+able to popup the &kmenu; by pressing the <keysym>Win</keysym> key.</para>
+</listitem>
+
+<listitem><para>One more step is required to save the changes across
+settings: Create a file <filename>~/.kde/env/win-key.sh</filename>
+(create the directory if it doesn't exist), and add the
+<command>xmodmap</command> command you used previously to it. The
+change should now be applied every time you start &kde;.</para>
+</listitem>
+</orderedlist>
+</para>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+sgml-omittag:nil
+sgml-shorttag:nil
+sgml-namecase-general:nil
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:true
+sgml-parent-document:("index.docbook" "book" "chapter")
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/doc/faq/qt.docbook b/doc/faq/qt.docbook
new file mode 100644
index 00000000..446089ed
--- /dev/null
+++ b/doc/faq/qt.docbook
@@ -0,0 +1,76 @@
+<chapter id="licensing">
+<title>&Qt; and Licensing questions</title>
+
+<qandaset>
+
+<qandaentry>
+<question id="qt">
+<para>What is &Qt;, by the way?</para>
+</question>
+<answer>
+<para>&Qt; is a C++-based class library to build user interfaces. It
+also includes many utility classes like string classes and classes
+to handle input and output. It
+provides most of the widgets you will see in a &kde; application:
+menus, buttons, sliders, &etc;. &Qt; is a cross-platform library that
+allows you to write code that will compile on &UNIX; systems as well as
+&Windows; and embedded devices. You can learn more about &Qt; at <ulink
+url="http://www.trolltech.com">http://www.trolltech.com</ulink>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Why does &kde; use &Qt;?</para>
+</question>
+<answer>
+<para>&Qt; is a very sophisticated toolkit that provides everything that
+is needed to build a modern user interface. &Qt; is written in C++, thus
+allowing object-oriented development which ensures efficiency and
+code reuse in a project the size and scope of &kde;. In our opinion
+there is no better toolkit available for &UNIX; systems and that it
+would have been a grave mistake to try to build &kde; on anything but
+the best.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Why does &kde; not use gtk, xforms, xlib, whatever?</para>
+</question>
+<answer>
+<para>There are a number of toolkits available. To provide a
+consistent user interface and to keep used resources such as memory to
+a minimum, &kde; can use only one of them. &Qt; was selected for the
+reasons mentioned above.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>But &Qt; isn't free, is it?</para>
+</question>
+<answer>
+<para>It is! As of September 4, 2000, version 2.2 of the &Qt;
+libraries were licensed under the <acronym>GPL</acronym>, thereby
+fulfiling all aspects of <quote>free software</quote>.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Can I write commercial software for &kde;?</para>
+</question>
+<answer>
+<para>You can use the &kde; libraries to write <quote>commercial and
+closed source</quote> as well as <quote>commercial and open
+source</quote> software. If you write open source software you can
+use the &Qt; free edition. But if you write closed source software
+you may not use the &Qt; free edition; you need to obtain the &Qt;
+professional edition from Troll Tech. </para> <para>If you want more
+information, please contact <ulink
+url="http://www.trolltech.com">Troll Tech</ulink> directly.</para>
+</answer>
+</qandaentry>
+</qandaset>
+</chapter> \ No newline at end of file
diff --git a/doc/faq/questions.docbook b/doc/faq/questions.docbook
new file mode 100644
index 00000000..1f7db6b6
--- /dev/null
+++ b/doc/faq/questions.docbook
@@ -0,0 +1,160 @@
+
+<chapter id="questions">
+
+<title>Asking Questions</title>
+
+<para>Chances are, you have been linked to this document from IRC or a
+mailing list. You've asked a question, and someone has told you that you
+need how to ask more effectively. In order to get an appropriate, clear
+answer you need to ask an appropriate, clear question in a manner that's
+going to provide an incentive for people to take their time to help you. If
+you appear to be rude, lazy or use bad or unclear language then chances are
+your question will be ignored</para>
+
+<qandaset>
+<qandaentry>
+
+<question><para>What do I do before I ask?</para></question>
+
+<answer><para>Read the documentation and &FAQ; for the application. There is
+a wealth of &kde; documentation availible both in the help center and
+online. A lot of time and effort has gone into this documentation, and
+quite often the answer to your question is here. The general &kde; userguide
+can be found by typing
+<userinput><command>help:/userguide</command></userinput> into your
+&konqueror; addressbar.</para>
+
+<para>Search the web: Usually googling for a specific error message or
+searching mailing list archives can come up with a solution for you.</para>
+
+<para>Try it and see! Look through all the application options, read the
+What's this? and tooltips for the ones you're not sure about. If you're
+really unsure about an option save your data and then try it. As long as you
+use some common sense, you are very unlikely to break anything by clicking
+buttons.</para>
+
+<para>Above all, don't be lazy. If you show the people who you are asking
+that you are able to troubleshoot and research in a logical manner, you're
+showing them you're a reasonable person who is worth their time to
+help. It's your problem and not theirs so the legwork is yours to do. Save
+your helpers as much time as you can, they're busy people.</para> </answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>Where do I ask?</para></question>
+
+<answer><para>Usually the best place to ask a question is on the
+<acronym>IRC</acronym> channels and mailing lists devoted to user
+questions. Don't post simple questions about using &kde; to the devel
+channels and mailing lists, these are for technical discussions. Some good
+places are #kde on irc.freenode.net, and the &kde; mailing
+lists.</para></answer> </qandaentry>
+
+<qandaentry>
+<question><para>How do I ask?</para></question>
+
+<answer><para>Try to word your questions in a manner that gives the most
+information possible and is polite and courteous. Don't ask to ask, just
+ask!</para>
+
+<para>Q: &kde; sucks, it's being slow</para>
+
+<para>Is not a question that is likely to get you a useful answer. It does
+not give any useful information about troubleshooting the problem, and it
+starts out attacking the software in a way that isn't productive.</para>
+
+<para>Q: Since upgrading &kde; on Slackware &Linux; from version 3.2.3 to
+3.3.2 using sources, I have noticed it's being really slow &mdash; sometimes
+applications take up to 20 seconts to launch. I am using the same user
+configuration as I had with the previous version, and I have tried as a new
+user. I can't find anything about this on the mailing lists or by a google
+search. Could anyone point me to some information that could help?</para>
+
+<para>This question is polite, contains information to help people
+troubleshoot the problem and shows your helpers what avenues you have
+already tried.</para>
+
+<para>Don't assume automatically that the problem is the fault of
+&kde;. Proceed as though this is your error, otherwise you will quickly
+annoy people if it does indeed turn out to be your problem and not
+&kde;.</para>
+
+<para>Use clear language with correct spelling. Watch out for any
+ambiguities and make sure you think about what you say before you write
+it. If you are asked for clarification, give it as best you can. &kde; is a
+project where many of the users and developers are not native english
+speakers and if you don't use correct english, misunderstandings may
+ensue. Use the language appropriate to the channel or mailing list you are
+in &mdash; if you don't, people who might have been able to help you may
+ignore your message because it is not in a language they understand.</para>
+
+<para>Include all information that could be relevant, even if you're not
+sure. Have you upgraded other software or hardware on your system,
+particularly system libraries or a new kernel? These things could affect how
+&kde; performs. Even if you cannot see a link, someone else might.</para>
+
+<para>Don't paraphrase error messages. Paste in the exact error, and if it's
+more than a line or two don't paste them directly into an
+<acronym>IRC</acronym> channel. Use a paste service like <ulink
+url="http://www.rafb.net/paste/"> http://www.rafb.net/paste</ulink>. If you
+must type them in by hand, be sure you are 100% accurate. When you provide
+faulty information, your helpers cannot help you as easily. </para>
+
+<para>Follow up on your solution! Tell us if it worked, or if you have
+solved it yourself in the meantime. This helps us know for sure if our
+solution worked, and helps other users who may be searching mailing list
+archives for a solution to the problem themselves.</para> </answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>What do I do when told to look elsewhere?</para></question>
+
+<answer><para>When you're told <quote>google knows</quote> or <quote>google
+is your friend</quote> then chances are, you have not followed the above
+advice. You've not done your research, and the solution is probably one the
+helper knows very well to be easy to find. When you're linked to a
+<acronym>FAQ</acronym> or a usermanual don't ever say, <quote>No, I don't
+want to have to read this I want you to just tell me</quote>. This is very
+bad manners. If you cannot put in the effort to read the document, what is
+the incentive for your helper to put in the time and effort to help you? If
+you're told to go use google, take it graciously and do so.</para> </answer>
+</qandaentry> </qandaset>
+
+<para>Above all, use common courtesy. &kde; users and developers are usually
+volunteering their time out of an already very busy schedule, and like to
+know that you are appreciating that they are helping you for free. Be
+polite, say please and thank you and try to be pleasant and
+friendly. </para>
+
+<para> Does this seem like a lot of trouble to ask a question? If you want
+to be able to feel that people owe you an answer or support, then you're
+quite welcome to pay for commercial support from companies that support
+&kde; on &UNIX; platforms. If you don't want to pay money, then pay the
+people who do this for free with your politeness and appreciation :)</para>
+
+
+<para>If you think the answer to your question should be included in the
+&kde; &FAQ; please feel free to submit any patches or suggestions to the
+&kde; &FAQ; Maintainer, at <email>faq@kde.org</email></para>
+
+
+
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+sgml-omittag:nil
+sgml-shorttag:nil
+sgml-namecase-general:nil
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:0
+sgml-indent-data:true
+sgml-parent-document:("index.docbook" "book" "chapter")
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/doc/faq/sound.docbook b/doc/faq/sound.docbook
new file mode 100644
index 00000000..d7db604b
--- /dev/null
+++ b/doc/faq/sound.docbook
@@ -0,0 +1,55 @@
+<chapter id="sound">
+<title>Troubleshooting sound problems</title>
+
+<para>&kde; uses the &arts; sound system which is complex and powerful,
+making it difficult for some users to troubleshoot when things go
+wrong. Here are some tips to help you diagnose what it's doing when your
+sound misbehaves :</para>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>How can I troubleshoot sound related problems in &kde;?</para>
+</question>
+
+<answer><para> To check that sound is working independently of &arts;, make
+sure that <command>artsd</command> isn't running and then try playing sound
+through <application>XMMS</application> or another multimedia application
+that isn't a part of &kde;. If that application doesn't play sound, then
+your general sound setup is probably broken and it's not a &kde;
+problem.</para>
+
+<para>Try playing sound with
+<userinput><command>artsplay</command><option><replaceable>
+/path/to/some/soundfile</replaceable></option></userinput>. Try various
+formats, ogg, mp3 and wav. Any error messages there might be useful in
+pointing you in the right direction.</para>
+
+<para>Try setting the &arts; output method to <acronym>OSS</acronym>. In the
+&kcontrolcenter; go to <menuchoice><guimenu>Sound &amp; Multimedia</guimenu>
+<guimenuitem>Sound System</guimenuitem></menuchoice>. On the
+<guilabel>Hardware</guilabel> tab, under <guilabel>Select the audio
+device</guilabel> choose <guilabel>Open Sound System</guilabel>. If you are
+running <acronym>alsa</acronym> this will use the <acronym>OSS</acronym>
+emulation, which may give better or worse results.</para>
+
+<para>Running <userinput><command>artsd</command><option> -l
+0</option></userinput> from a terminal will give you a lot of debug output,
+some of which might help you to diagnose the problem. Trying this in
+conjunction with using <command>artsplay</command> in a second terminal can give a wealth of information. If an <application>artsd</application> instance is already running, exit it with <userinput><command>artsshell
+</command><parameter>terminate</parameter></userinput></para>
+</answer>
+</qandaentry>
+<qandaentry>
+<question><para>
+I've upgraded to the latest version of &kde; keeping my old configuration, and my system sounds don't work anymore!</para></question>
+<answer><para>
+Assuming you've installed &arts; correctly and you still have the codecs installed your previous &kde; installation needed, chances are this is a small problem with your <filename>knotifyrc</filename>. To confirm this, try creating an entirely new user and seeing if system notifications work under the new account. If they do, try moving your <filename>$<envar>KDEHOME</envar>/share/config/knotifyrc</filename> out of the way for your original user to see if this solves the problem.
+</para></answer>
+</qandaentry>
+
+
+</qandaset>
+
+</chapter>
+
diff --git a/doc/faq/tips.docbook b/doc/faq/tips.docbook
new file mode 100644
index 00000000..d4770909
--- /dev/null
+++ b/doc/faq/tips.docbook
@@ -0,0 +1,137 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+<chapter id="tips">
+<title>Useful tips</title>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>Reading documentation in &kde;</para>
+</question>
+<answer>
+<para>Pop up the <guilabel>Run Command</guilabel> window (<keycombo
+action="simul">&Alt;<keycap>F2</keycap></keycombo> by
+default) and type:
+<itemizedlist>
+<listitem>
+<para><command>man:<replaceable>command</replaceable></command> for man pages. It
+even unpacks on the fly if the man pages are gzipped.</para>
+</listitem>
+
+<listitem>
+<para><command>info:<replaceable>command</replaceable></command> for info
+pages.</para>
+</listitem>
+
+<listitem>
+<para><command>help:<replaceable>kdeappname</replaceable></command> for &kde;
+application help pages.</para>
+</listitem>
+
+</itemizedlist>
+</para>
+
+<para>You can also enter any of these in the <guilabel>Location</guilabel> text
+box in &konqueror;.</para>
+<para>Or you can use the <application>&kde; Help Center</application> if you are using &kde;
+2. Simply start the <application>&kde; Help Center</application> by clicking on the icon (the blue
+book with the yellow key) on the toolbar. Once the <application>&kde; Help Center</application> has
+loaded, the window on the left will contain an entry called
+<guilabel>Unix manual pages</guilabel>. Click once on this entry, and
+you can browse through all the installed manual pages on your
+system.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Move or resize windows quickly</para>
+</question>
+<answer>
+<para>To move a window, use <keycombo
+action="simul">&Alt;<mousebutton>left</mousebutton></keycombo> mouse
+button. <keycombo
+action="simul">&Alt;<mousebutton>right</mousebutton></keycombo> mouse
+button will resize the window. Last but not least, <keycombo
+action="simul">&Alt;<mousebutton>middle</mousebutton></keycombo> mouse button
+raises/lowers the window. The <application>&kde; Control Center</application>
+allows you to change these mouse bindings.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Killing windows in &kde;</para>
+</question>
+<answer>
+<para>There is a standard keybinding (<keycombo
+action="simul">&Ctrl;&Alt;&Esc;</keycombo>)
+that gives you a skull &amp; crossbones cursor. Click that cursor on a
+window to kill it. The keybindings are viewable/changeable from the
+<application>&kde; Control Center</application>.
+
+<caution><para>Using this option kills the program forcibly. Data may be lost,
+and some processes related to the program may remain active. Use only as a
+last resort.</para></caution>
+<!-- fixme: use only if necessary; processes might remain --></para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What if something is so wrong that I can't even get the skull
+&amp; crossbones cursor? How do I get out of a total lockup?</para>
+</question>
+<answer>
+<para>These kind of locks tend to occur when an application locks up
+while it has a so called <quote>mouse/keyboard grab</quote>. When that
+happens you can try to select a virtual text console with <keycombo
+action="simul">&Ctrl;&Alt;<keycap>F1</keycap></keycombo> and login. With the
+following command you will get a list of all running processes:</para>
+
+<screen><userinput> <command>ps</command> <option>-aux</option> | <command>more</command></userinput></screen>
+
+<para>By killing the process that has the mousegrab, your desktop will
+come to life again. Unfortunately you can't see which process that is,
+so you will have to find out through trial and error. To kill a process
+use:</para>
+
+<screen><userinput> <command>kill</command> <option>-9</option> <replaceable>pid</replaceable></userinput></screen>
+
+<para>Here <replaceable>pid</replaceable> is the process id of the
+process, which is the first number on each line reported by
+<command>ps</command> <option>-aux</option>.</para>
+
+<para>You can switch back to the desktop with <keycombo
+action="simul">&Ctrl;&Alt;<keycap>F7</keycap></keycombo> (or
+<keycap>F8</keycap> through <keycap>F9</keycap> depending on your
+operating system) to see if things work again. When you press
+<keycombo action="simul">&Alt;<keycap>Tab</keycap></keycombo> you should get a
+response from the window manager. If not, you need to get back to the
+text console and try to kill another process.</para>
+
+<para>Good candidates to kill are: the application you were working
+with, &kicker;, &klipper; and &kdesktop;.</para>
+</answer>
+</qandaentry>
+
+<!-- fixme: how to do in KDE2.x
+<qandaentry>
+<question>
+<para>Switching window managers on the fly in &kde; 1.x</para>
+</question>
+<answer>
+<para>If you want to switch your window manager on the fly, type the
+following into a terminal window: <command>kwmcom
+go:<replaceable>blackbox</replaceable></command>. This switches to
+Blackbox, but you can substitute any window manager you like.</para>
+</answer>
+</qandaentry>
+-->
+
+</qandaset>
+</chapter>
diff --git a/doc/faq/webbrowse.docbook b/doc/faq/webbrowse.docbook
new file mode 100644
index 00000000..b80c7ae1
--- /dev/null
+++ b/doc/faq/webbrowse.docbook
@@ -0,0 +1,222 @@
+<!-- <?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd"> -->
+
+<chapter id="webbrowser">
+<title>Webbrowsing with &konqueror;</title>
+<para>&konqueror; is &kde;'s open source, standards compliant webbrowser.
+It's home page is
+<ulink
+url="http://www.konqueror.org">http://www.konqueror.org</ulink> where a
+&konqueror; specific <acronym>FAQ</acronym> can be found.</para>
+
+<qandaset>
+
+<qandaentry>
+<question><para>Where does the name &konqueror; come from?</para></question>
+<answer><para>It's a word play on the other browsers' names. After the Navigator and the Explorer comes the Conqueror; it's spelled with a K to show that it's part of &kde;. The name change also moves away from <quote>kfm</quote> (the &kde; file manager, &konqueror;'s predecessor) which represented only file management.</para></answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>Can I run &konqueror; without running &kde;?</para></question>
+<answer><para>Yes. Just install &Qt;, kdelibs and kdebase, and from your favorite window manager just launch &konqueror;. It should work just fine, but if it doesn't (&kde; developers don't test that case often), report it to http://bugs.kde.org and try running "kdeinit" before running &konqueror;, it usually helps.
+This is of course the same for any other &kde; application. </para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>Why doesn't &konqueror; show the contents of an image's <sgmltag class="attribute">ALT</sgmltag> attribute in a tooltip?</para></question>
+<answer><para>
+There is no standard that states the <sgmltag class="attribute">ALT</sgmltag> attribute should appear as a tooltip. The specification calls for <sgmltag class="attribute">ALT</sgmltag> to be displayed in place of the image, as in text-mode only browsers such at lynx or w3m. Abusing the <sgmltag class="attribute">ALT</sgmltag> attribute is bad for accessibility. Tooltips are supposed to come from the <sgmltag class="attribute">TITLE</sgmltag> attribute and this is implemented in &konqueror;
+</para></answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I use &konqueror; as a web browser with a proxy?</para>
+</question>
+<answer>
+<para>&konqueror; can be used with &HTTP; and &FTP; proxies. To set
+up the proxy server in &konqueror;, just select
+<menuchoice><guimenu>Settings</guimenu><guisubmenu>Configure
+&konqueror;...</guisubmenu></menuchoice> from the &konqueror; menu and
+go to the <guilabel>Proxy</guilabel> tab.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question id="nsbookmark">
+<para>How do I import bookmarks from another browser into &konqueror; ?</para>
+</question>
+<answer>
+<para>To import bookmarks from another browser into &konqueror; select
+<guimenu>Bookmarks</guimenu><guimenuitem>Edit Bookmarks</guimenuitem>
+and then in the <application>Bookmark Editor</application> select
+<guimenu>File</guimenu><guimenuitem>Import</guimenuitem>. Then select
+the browser you would like to import bookmarks from. In the Open dialog,
+navigate to the location of the folder or file your bookmarks are
+contained in and click <guilabel>Open</guilabel>
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>How can I make &konqueror; only show certain bookmarks in the bookmarks toolbar?</para></question>
+<answer><para>In &konqueror; go to <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &konqueror;...</guimenuitem></menuchoice>. Then select <guilabel>Web Behaviour</guilabel> from the icon list. Under the <guilabel>Bookmarks</guilabel> heading, place a check in the box next to <guilabel>Show only marked bookmarks in bookmark toolbar</guilabel>. Now in the <application>Bookmark Editor</application> an option to <guilabel>Show in Toolbar</guilabel> appears on clicking with the &RMB; on any bookmark entry or in the <guimenu>Edit</guimenu> menu when the entry is highlighted. Folders can also be shown in the bookmarks toolbar in much the same way.</para></answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I fool a site into believing &konqueror; is &Netscape; or
+some other browser?</para>
+</question>
+<answer>
+<para>In &konqueror;, select
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
+Konqueror...</guimenuitem></menuchoice> and in the configuration
+dialog, select <guilabel>Browser Identification</guilabel>. Default
+and site-specific browser identifications can be set from here.</para>
+</answer>
+</qandaentry>
+<qandaentry>
+<question>
+<para>&konqueror; is taking a really long time to load webpages, what
+could cause this?</para></question>
+<answer>
+<para>Quite often &konqueror; loading webpages slowly is caused by
+<acronym>DNS</acronym> servers with broken <acronym>IPV6</acronym>
+support. Adding the following to <filename>/etc/profile</filename> or any
+other script that is sourced on login should solve this problem:
+<screen>
+export KDE_NO_IPV6=true
+</screen>
+for bourne compatible shells, and for C-style shells:
+<screen>
+setenv KDE_NO_IPV6 true
+</screen>
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I configure &konqueror; to run &Java; applets?</para>
+</question>
+<answer>
+<para>Choose
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
+&konqueror;...</guimenuitem></menuchoice> from &konqueror;'s menubar
+and then select <guilabel>Java &amp; Javascript</guilabel>. Set the
+<guilabel>Path to Java executable</guilabel> correctly. If it doesn't
+work, please check the <ulink
+url="http://www.konqueror.org/javahowto/">Konqueror + Java
+HOWTO</ulink>.</para>
+</answer>
+</qandaentry>
+
+
+<qandaentry>
+<question>
+<para>How do I block unrequested popup windows in &konqueror;?</para>
+</question>
+<answer>
+<para>&konqueror; has a new 'smart' policy for JavaScript popups. From the
+&konqueror; main window, select <menuchoice><guimenu>Settings</guimenu>
+<guimenuitem>Configure &konqueror;...</guimenuitem></menuchoice> and then
+<guilabel>Java &amp; JavaScript</guilabel>. On the
+<guilabel>JavaScript</guilabel> tab, under <guilabel>Global JavaScript
+Policies</guilabel> set the radio button beside <guilabel>Open new
+windows:</guilabel> to <guilabel>Smart</guilabel>.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Why doesn't my banking site work with &konqueror;? It pops up a new
+window with the login screen in other browsers, but not in
+&konqueror;.</para>
+</question>
+<answer>
+<para>
+Make sure you have Javascript enabled, and the default JavaScript web popups
+policy set to <guilabel>Ask</guilabel> or <guilabel>Allow</guilabel>. The
+<guilabel>Smart</guilabel> policy is not always sufficient for some banks.
+Many banks also require &Java; support. You can find more help on enabling
+this at <ulink
+url="http://www.konqueror.org/">http://www.konqueror.org/</ulink>.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Can &konqueror; use user-specified stylesheets, like those in the
+Firefox adblock extention?</para>
+</question>
+<answer>
+<para>Yes, you can set &konqueror; to use any kind of valid
+<acronym>css</acronym> stylesheet to filter webcontent or improve accessibility.
+From the &konqueror; main window simply click
+<menuchoice><guimenu>Settings</guimenu>
+<guimenuitem>Configure &konqueror;...</guimenuitem></menuchoice> and select
+<guilabel>Stylesheets</guilabel>. Set the radio button to
+<guilabel>Use user-defined stylesheet</guilabel> and browse to where the
+stylesheet you want to use is located. Alternatively, you can select
+<guilabel>Use accessibility stylesheet defined in "Customize"
+tab</guilabel> and then set your own options.</para>
+<para>
+An example of <acronym>css</acronym> rules that implement ad blocking can be
+found at:
+<ulink url="http://www.mozilla.org/support/firefox/adblock">
+http://www.mozilla.org/support/firefox/adblock</ulink>.
+</para>
+</answer>
+</qandaentry>
+<qandaentry>
+<question><para>
+Why does &konqueror; display a plain grey square when I try to view flash animations, even though the flash plugin is installed?
+</para></question>
+<answer><para>
+Under the latest versions of X.org, having the composite extension loaded can cause problems with the flash plugin. Try disabling the composite extension and see if normal flash operation is restored.
+</para></answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Why can't &konqueror; render &GIF; images?</para>
+</question>
+<answer>
+<para>It is because you did not enable &GIF; support in &Qt;. Please see
+<xref linkend="gif"/> for more details.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question><para>When I try to open a web page with &konqueror;, I get the
+message: <quote>There appears to be a configuration error. You have
+associated Konqueror with text/html, but it cannot handle this file
+type.</quote></para>
+</question>
+<answer>
+<para>You need to make sure that the embedding settings for the text/html
+<acronym>MIME</acronym> type are correct:
+<orderedlist>
+<listitem><para>In &konqueror;, go to
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
+&konqueror;...</guimenuitem></menuchoice> and then to the <guilabel>File
+Associations</guilabel> page.</para></listitem> <listitem><para>Open
+text->html in the tree view.</para></listitem> <listitem><para>Click on the
+<guilabel>Embedding</guilabel> tab. Make sure that <guilabel>Left Click
+Action</guilabel> is set to <guilabel>Show file in embedded
+viewer</guilabel>, and that <guilabel>KHTML (khtml)</guilabel> is at the top
+of <guilabel>Services Preference Order</guilabel>.</para></listitem>
+</orderedlist>
+</para>
+</answer>
+</qandaentry>
+
+</qandaset>
+</chapter>
+
+
diff --git a/doc/faq/winmng.docbook b/doc/faq/winmng.docbook
new file mode 100644
index 00000000..f3238475
--- /dev/null
+++ b/doc/faq/winmng.docbook
@@ -0,0 +1,134 @@
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+ "dtd/kdex.dtd">
+-->
+
+
+
+<chapter id="windowmanager">
+<title>The window manager</title>
+
+<para>The default window manager provided by &kde; is the K Window
+Manager (&kwin;). Please read <quote>The
+K Window Manager Handbook</quote> (which should be accessible from the
+<application>&kde; Help Center</application>) for usage information.</para>
+
+<qandaset>
+<qandaentry>
+<question>
+<para>Are there keyboard shortcuts for &kwin; operations?</para>
+</question>
+<answer>
+<para>Yes. Please refer to "The K Window Manager Handbook" for the
+list of shortcuts available.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>Can I define my own set of keyboard shortcuts?</para>
+</question>
+<answer>
+<para>Yes. Launch the
+<application>&kde; Control Center</application> and select
+<menuchoice><guimenu>Regional &amp; Accessibility</guimenu><guimenuitem>Keyboard Shortcuts</guimenuitem></menuchoice> to
+configure window manager bindings like maximizing windows, &etc;.
+</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>When I "iconify" a window, it disappears. Where does it
+go?</para>
+</question>
+<answer>
+<para>With many &X-Window; &GUI;s, the minimize button (a little dot) will
+erase the window that the program is running in and create, instead,
+an icon on the desktop. &kde; does not do this. Instead, when a
+window is iconified it is simply hidden (but the program is still
+running).</para>
+<para>There are a few ways to access <quote>disappeared</quote> windows:</para>
+<itemizedlist>
+<listitem>
+<para>If you are running the taskbar part of &kicker;,
+you can choose to have a list of tasks displayed on your desktop.
+Iconified tasks will have their names displayed in gray.</para>
+</listitem>
+<listitem>
+<para>If you click the &MMB; on the root window (&ie;,
+the background of the desktop), &kwin; will give you a list
+of all available tasks.</para>
+</listitem>
+</itemizedlist>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>How do I maximize windows only vertically or horizontally?</para>
+</question>
+<answer>
+<para>Provided your window is not already maximized, clicking on the
+maximize button with the &LMB;/&MMB;/&RMB; will
+maximize fully/vertically/horizontally respectively.</para>
+</answer>
+</qandaentry>
+
+<qandaentry>
+<question>
+<para>What is <quote>shading</quote> a window?</para>
+</question>
+<answer>
+<para>By <quote>shading</quote> a window we mean <quote>rolling up</quote> the window leaving just
+the title bar visible. You can do this by double clicking on the
+window title bar.</para>
+</answer>
+</qandaentry>
+
+<!-- This is kinda covered in desktop.docbook, but the question here -->
+<!-- is different, even if the answer is nearly the same -->
+<qandaentry>
+<question>
+<para>How can I start an application with special window options, like
+maximized/minimized/to stay on top?</para>
+</question>
+<answer>
+<para>Use the <command>kstart</command> command. As an example, to
+open &kcalc; with the <quote>Stay on Top</quote> option, use:
+<screen><prompt>%</prompt> <userinput><command>kstart</command> <option>--ontop</option> <option>kcalc</option></userinput></screen>
+</para>
+<para>For maximized windows, use the <option>--maximize</option>
+option, for minimized windows, use <option>--iconify</option>. You can
+see a full list of <command>kstart</command> options with
+<userinput><command>kstart</command>
+<option>--help-all</option></userinput>.</para>
+
+<warning><para>If you're using <command>kstart</command> to start
+applications at &kde; startup, you should use the
+<option>--window</option> option. See the &kde; User Guide, section
+<quote>Advanced Window Management</quote> for more information about
+this feature.</para>
+</warning>
+
+</answer>
+</qandaentry>
+
+<!-- Not sure this is still applicable
+<qandaentry>
+<question>
+<para>Is it possible to have FVWM2-like shadow frameworks for the
+placement of windows?</para>
+</question>
+<answer>
+<para>Yes. Run <application>&kde; Control Center</application> and select <guimenu>Look and Feel</guimenu>
+followed by <guisubmenu>Window Behavior</guisubmenu> and finally
+<guimenuitem>Advanced</guimenuitem>. There is a dialog option that
+allows you to set the placement policy you want.</para>
+</answer>
+</qandaentry>
+-->
+</qandaset>
+</chapter>
+
diff --git a/doc/glossary/Makefile.am b/doc/glossary/Makefile.am
new file mode 100644
index 00000000..e79a4684
--- /dev/null
+++ b/doc/glossary/Makefile.am
@@ -0,0 +1,2 @@
+KDE_LANG = en
+KDE_DOCS = khelpcenter/glossary
diff --git a/doc/glossary/checkxrefs b/doc/glossary/checkxrefs
new file mode 100755
index 00000000..6da64c18
--- /dev/null
+++ b/doc/glossary/checkxrefs
@@ -0,0 +1,10 @@
+#!/bin/sh
+DEFINED_ENTRIES=`sed -ne "s^.*<glossentry id=\"\(.*\)\">.*^\1^p" *.docbook`
+REFERENCED_ENTRIES=`sed -ne "s^.*<glossseealso otherterm=\"\(.*\)\">.*^\1^p" *.docbook | unique`
+
+# Check for entries which are referenced but not defined.
+for ENTRY in $REFERENCED_ENTRIES; do
+ if ! echo $DEFINED_ENTRIES | grep $ENTRY - > /dev/null 2>&1; then
+ echo "'$ENTRY' referenced but not defined!"
+ fi
+done
diff --git a/doc/glossary/index.docbook b/doc/glossary/index.docbook
new file mode 100644
index 00000000..4aba44c5
--- /dev/null
+++ b/doc/glossary/index.docbook
@@ -0,0 +1,296 @@
+<?xml version="1.0" ?>
+<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
+<!ENTITY % addindex "IGNORE">
+<!ENTITY % English "INCLUDE">
+<!ENTITY glossary-kdeprinting SYSTEM "kdeprintingglossary.docbook">
+
+
+]>
+
+
+<glossary id="glossary">
+
+&glossary-kdeprinting;
+
+ <glossdiv id="glossdiv-technologies">
+ <title>Technologies</title>
+ <glossentry id="gloss-ioslave">
+ <glossterm><acronym>IO</acronym> Slave</glossterm>
+ <glossdef><para><acronym>IO</acronym> Slaves enable &kde; applications to
+ access remote resources as easily as local resources (making them
+ <quote>network transparent</quote>). Remote resources (&eg; files) might
+ be stored on <acronym>SMB</acronym> shares or similar.</para>
+ <glossseealso otherterm="gloss-smb"><acronym>SMB</acronym></glossseealso>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-kio">
+ <glossterm><acronym>KIO</acronym></glossterm>
+ <glossdef><para>The &kde; Input/Output system which makes use of so-called
+ <quote><acronym>IO</acronym> Slaves</quote>.</para>
+ <glossseealso otherterm="gloss-ioslave"><acronym>IO</acronym>
+Slave</glossseealso>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-kparts">
+ <glossterm>KParts</glossterm>
+ <glossdef><para>KParts is an embedding technology which allows &kde;
+ applications to embed other &kde; applications. For example, the text
+ view used by &konqueror; is a KPart.</para>
+ <glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-ksycoca">
+ <glossterm><acronym>KSycoca</acronym></glossterm>
+ <glossdef><para><acronym>KSycoca</acronym> (&kde; <emphasis>Sy</emphasis>stem
+ <emphasis>Co</emphasis>nfiguration <emphasis>Ca</emphasis>che) is a
+ configuration cache which, for example, guarantees fast access to the menu
+ entries.</para>
+ <glossseealso
+otherterm="gloss-kbuildsycoca"><application>KBuildSycoca</application></glossseealso>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="glossdiv-xfree86">
+ <title>XFree86</title>
+ <glossentry id="gloss-antialiasing">
+ <glossterm>Antialiasing</glossterm>
+ <glossdef><para>If mentioned in context with &kde;, antialiasing often means
+ the smoothing of the fonts visible on the screen. &Qt; version 2.3.0
+ or higher used together with XFree86 4.x makes this possible under &kde;
+ as well.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-qt">&Qt;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-xserver">
+ <glossterm>&X-Server;</glossterm>
+ <glossdef><para>The &X-Server; represents a basic layer upon which the
+ various &GUI;s like &kde; are built. It manages the
+ basic mouse and keyboard input (from the local host as well as from
+ remote hosts) and provides elementary graphic routines to draw
+ rectangles and other primitives.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="glossdiv-applications">
+ <title>Applications</title>
+ <glossentry id="gloss-kbuildsycoca">
+ <glossterm><application>KBuildSycoca</application></glossterm>
+ <glossdef><para><application>KBuildSycoca</application> is a command line
+program and regenerates the
+ so-called <acronym>KSycoca</acronym>. This is useful, for example, if some
+or all modules in
+ &kcontrol; are missing.</para>
+ <glossseealso
+otherterm="gloss-ksycoca"><acronym>KSycoca</acronym></glossseealso>
+ <glossseealso otherterm="gloss-kcontrol">&kcontrol;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-kcontrol">
+ <glossterm>&kcontrol;</glossterm>
+ <glossdef><para>This is the project and filename of the &kde; control
+ center. &kcontrol; allows you to customize virtually
+ every configuration option of &kde;.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-kicker">
+ <glossterm>&kicker;</glossterm>
+ <glossdef><para>&kicker; is the nickname as well as project name of the
+ &kde; panel.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-panel">Panel</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-konqueror">
+ <glossterm>&konqueror;</glossterm>
+ <glossdef><para>&konqueror; is a filemanager, web browser, picture viewer
+ and more, and a core part of the &kde; project. You can
+ find more information about &konqueror; at <ulink
+ url="http://www.konqueror.org">www.konqueror.org</ulink>.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-ksirc">
+ <glossterm>&ksirc;</glossterm>
+ <glossdef><para>&ksirc; is the default <acronym>IRC</acronym> client,
+ which is shipped with &kde;. You can use &ksirc; to chat with anyone on
+ an <acronym>IRC</acronym> network.</para>
+ <glossseealso otherterm="gloss-irc"><acronym>IRC</acronym></glossseealso>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="glossdiv-desktop-terminology">
+ <title>Desktop Terminology</title>
+ <glossentry id="gloss-draganddrop">
+ <glossterm>Drag and Drop</glossterm>
+ <glossdef><para>This concept tries to replace many actions like copying
+ files from one place to another by a certain mouse movement, &eg;
+ clicking on an icon in a &konqueror; window, moving the mouse to another
+ window while keeping the mouse button pressed, and releasing the mouse
+ button (<quote>dropping</quote> the object) copies files.</para>
+ <glossseealso otherterm="gloss-konqueror">&konqueror;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-gui">
+ <glossterm>&GUI;</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>G</emphasis>raphical
+ <emphasis>U</emphasis>ser <emphasis>I</emphasis>nterface. Every desktop
+ environment (like &kde;) is a &GUI;. Most
+ &GUI;s feature mouse support and/or windows to manage
+ the programs.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-kde">
+ <glossterm>&kde;</glossterm>
+ <glossdef><para>Abbreviation for <quote>K Desktop Environment</quote>, a
+ leading &GUI; for &UNIX;-based systems. You can find more
+ detailled information at <ulink
+ url="http://www.kde.org">www.kde.org</ulink>.</para>
+ <glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-gnome">
+ <glossterm><acronym>GNOME</acronym></glossterm>
+ <glossdef>
+ <para><emphasis>G</emphasis>NU <emphasis>N</emphasis>etwork <emphasis>O</emphasis>bject
+ <emphasis>M</emphasis>odel <emphasis>E</emphasis>nvironment, one of the
+ leading &UNIX; &GUI;s.</para>
+ <glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-panel">
+ <glossterm>Panel</glossterm>
+ <glossdef><para>Refers to the panel (also known as
+ <quote>&kicker;</quote>) which often resides at the bottom of the
+ screen.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-kicker">&kicker;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-ripping">
+ <glossterm>ripping</glossterm>
+ <glossdef><para>The process of reading audio data from a &cdrom; and
+ storing it on the hard disk.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="kde-development">
+ <title>&kde; Development</title>
+ <glossentry id="gloss-qt">
+ <glossterm>&Qt;</glossterm>
+ <glossdef><para>The &GUI; of &kde; is built on top of
+ the &Qt; toolkit, which provides many graphical elements (so-called
+ <quote>Widgets</quote>) which are used to construct the desktop. You
+ can find more information about &Qt; at <ulink
+ url="http://www.trolltech.com">www.trolltech.com</ulink>.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
+ <glossseealso otherterm="gloss-widget">Widget</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-i18n">
+ <glossterm>i18n</glossterm>
+ <glossdef><para>Abbreviation for <quote>internationalization</quote>. &kde;
+ supports many different languages, and several i18n techniques make it
+ easy to translate the &GUI; as well as the accompanying
+ documents of &kde; into all these languages. More information about the
+ i18n process is available at <ulink
+ url="http://i18n.kde.org">i18n.kde.org</ulink>.</para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-l10n">
+ <glossterm>l10n</glossterm>
+ <glossdef><para>Abbreviation for <quote>localization</quote>, the process
+ of adapting a program to the local environment. This includes &eg; the
+ currency used for monetary values or the time format.</para>
+ <glossseealso otherterm="gloss-i18n">i18n</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-widget">
+ <glossterm>Widget</glossterm>
+ <glossdef><para>Graphical elements like scrollbars, buttons or input
+ fields which are used by &kde; to construct the &GUI;.
+ </para>
+ <glossseealso otherterm="gloss-kde">&kde;</glossseealso>
+ <glossseealso otherterm="gloss-gui">&GUI;</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-cvs">
+ <glossterm><acronym>CVS</acronym></glossterm>
+ <glossdef>
+ <para><emphasis>C</emphasis>oncurrent <emphasis>V</emphasis>ersion
+<emphasis>S</emphasis>ystem.
+ The <acronym>CVS</acronym> is a very elegant way of managing file
+versions that allow more than one developer
+ to easily work on the same project. You can find a description of how to
+get the latest (developer) version of the
+ &kde; sources via anonymous <acronym>CVS</acronym> on
+ <ulink
+url="http://www.kde.org/anoncvs.html">http://www.kde.org/anoncvs.html</ulink>.
+ More about <acronym>CVS</acronym> is available at <ulink
+url="http://www.cvshome.org">www.cvshome.org</ulink>.
+
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="glossdiv-misc">
+ <title>Miscellaneous</title>
+ <glossentry id="gloss-rfc">
+ <glossterm><acronym>RFC</acronym></glossterm>
+ <glossdef><para><emphasis>R</emphasis>equest <emphasis>F</emphasis>or
+ <emphasis>C</emphasis>omment. A common way to publish new protocol
+ ideas or procedures for evaluation of the Internet community. Though
+ <acronym>RFC</acronym>s are not mandatory, many applications try to
+ adhere to them, once they have been approved by the community. More
+ information about <acronym>RFC</acronym>s can be found at the
+ <ulink url="http://www.rfc-editor.org">RFC Homepage</ulink>.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+
+ <glossdiv id="glossdiv-protocols">
+ <title>Various protocols</title>
+ <glossentry id="gloss-smb">
+ <glossterm><acronym>SMB</acronym></glossterm>
+ <glossdef><para><emphasis>S</emphasis>erver <emphasis>M</emphasis>essage
+ <emphasis>B</emphasis>lock. A network protocol used in &Microsoft; &Windows;
+ networks to access the filesystems of other computers.</para>
+ <glossseealso otherterm="gloss-ioslave"><acronym>IO</acronym>
+Slave</glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-irc">
+ <glossterm><acronym>IRC</acronym></glossterm>
+ <glossdef><para><emphasis>I</emphasis>nternet <emphasis>R</emphasis>elay
+ <emphasis>C</emphasis>hat. A protocol defined in <acronym>RFC</acronym>
+ 1459, which handles the specification to enable real time text chat.</para>
+ <glossseealso otherterm="gloss-rfc"><acronym>RFC</acronym></glossseealso>
+ </glossdef>
+ </glossentry>
+ <glossentry id="gloss-host">
+ <glossterm>host</glossterm>
+ <glossdef><para>This can either be a name from your
+ <filename>/etc/hosts</filename> file
+ (<systemitem class="systemname">mycomputer</systemitem>),
+ an Internet name (<systemitem
+class="systemname">www.kde.org</systemitem>) or an IP-Address
+ (<systemitem>192.168.0.10</systemitem>).
+ </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+</glossary>
diff --git a/doc/glossary/kdeprintingglossary.docbook b/doc/glossary/kdeprintingglossary.docbook
new file mode 100644
index 00000000..7a9311c7
--- /dev/null
+++ b/doc/glossary/kdeprintingglossary.docbook
@@ -0,0 +1,1387 @@
+
+<!--
+<?xml version="1.0" ?>
+<!DOCTYPE glossary PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+"customization/dtd/kdex.dtd" [
+<!ENTITY % addindex "IGNORE">
+<!ENTITY % English "INCLUDE">
+<!ENTITY glossary-kdeprinting SYSTEM "kdeprintingglossary.docbook">
+
+]>
+<glossary id="glossary">
+-->
+ <glossdiv id="glossdiv-printing">
+ <title>Printing</title>
+
+
+ <glossentry id="gloss-acl">
+ <glossterm><acronym>ACLs</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>A</emphasis>ccess
+ <emphasis>C</emphasis>ontrol <emphasis>L</emphasis>ists;
+ ACLs are used to check for the access by a given
+ (authenticated) user. A first rough support for ACLs
+ for printing is available from &CUPS;; this will be refined
+ in future versions. </para>
+ <glossseealso otherterm="gloss-authentication">Authentication</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-appsocketprotocol">
+ <glossterm>AppSocket Protocol</glossterm>
+ <glossdef><para>AppSocket is a protocol for the transfer of
+ print data, also frequently called "Direct TCP/IP Printing".
+ &Hewlett-Packard; have taken AppSocket, added a few minor
+ extensions around it and been very successful in renaming
+ and marketing it under the brand "&HP; JetDirect"...</para>
+ <glossseealso otherterm="gloss-hpjetdirectprotocol">&HP; JetDirect Protocol</glossseealso>
+ <glossseealso otherterm="gloss-directtcpipprinting">Direct TCP/IP Printing</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-apsfilter">
+ <glossterm>APSfilter</glossterm>
+ <glossdef><para>APSfilter is used mainly in the context of "classical"
+ &UNIX; printing (BSD-style LPD). It is a sophisticated shell script,
+ disguised as an "all-in-one" filtering program. In reality,
+ APSfilter calls "real filters" to do the jobs needed. It sends
+ printjobs automatically through these other filters, based on an
+ initial file-type analysis of the printfile.
+ It is written and maintained by Andreas Klemm.
+<!--
+ </para>
+ <para>
+-->
+ It is
+ similar to Magicfilter and mostly uses Ghostscript for file conversions.
+ Some Linux Distributions (like &SuSE;) use APSfilter, others
+ Magicfilter (like &RedHat;), some have both for preference selection
+ (like *BSD).
+<!--
+ </para>
+ <para>
+-->
+ &CUPS; has <emphasis>no</emphasis> need for APSfilter,
+ as it runs its own file type recognition (based on &MIME; types)
+ and applies its own filtering logic.</para>
+ <glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
+ <glossseealso otherterm="gloss-magicfilter">Magicfilter</glossseealso>
+ <glossseealso otherterm="gloss-mimetypes">&MIME;-Types</glossseealso>
+ <glossseealso otherterm="gloss-printcap">printcap</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-authentication">
+ <glossterm>Authentication</glossterm>
+ <glossdef><para>Proving the identity of a certain person (maybe via username/password
+ or by means of a certificate) is often called authentication. Once you are
+ authenticated, you may or may not get access to a requested ressource,
+ possibly based on ACLs.</para>
+ <glossseealso otherterm="gloss-acl">ACLs</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-bidirectionalcommunication">
+ <glossterm>Bi-directional communication</glossterm>
+ <glossdef><para>In the context of printing, a server or a host may receive additional
+ information sent back from the printer (status messages &etc;), either
+ upon a query or unrequested. AppSocket ( = &HP; JetDirect), &CUPS; and IPP
+ support bi-directional communication, LPR/LPD and BSD-style printing
+ do not...</para>
+ <glossseealso otherterm="gloss-appsocketprotocol">AppSocket Protocol</glossseealso>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-directtcpipprinting">Direct TCP/IP Printing</glossseealso>
+ <glossseealso otherterm="gloss-hpjetdirectprotocol">&HP; JetDirect</glossseealso>
+ <glossseealso otherterm="gloss-ipp">IPP</glossseealso>
+ <glossseealso otherterm="gloss-lprlpd">LPR/LPD</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-bsdstyleprinting">
+ <glossterm>BSD-style Printing</glossterm>
+ <glossdef><para>Generic term for different variants of the traditional &UNIX;
+ printing method. Its first version appeared in the early 70s on
+ BSD &UNIX; and was formally described in <ulink url="http://www.rfc.net/rfc1179.html">RFC 1179</ulink> only as late
+ as 1990.
+<!--
+ </para>
+ <para>
+-->
+ At the time when BSD "remote" printing was first designed, printers
+ were serially or otherwise directly connected devices to a host
+ (with the Internet hardly consisting of more than 100 nodes!); printers
+ used hole-punched, continuous paper, fed through by a tractor
+ mechanism, with simple rows of ASCII text mechanically hammered on to
+ the medium, drawn from a cardboard box beneath the table. It came out
+ like a zig-zag folded paper "snake". Remote printing consisted of a
+ neighboring host in the next room sending a file
+ asking for printout.
+<!--
+ </para>
+ <para>
+-->
+ How technology has changed! Printers generally use cut-sheet media, they have
+ built-in intelligence to compute the raster images of pages after pages
+ that are sent to them using one of the powerful page description
+ languages (PDL). Many are network nodes in their own right,
+ with CPU, RAM, a hard disk and their own Operation System, and
+ are hooked to a net with potentially millions of users...
+<!--
+ </para>
+ <para>
+-->
+ It is a vast proof of the flexible &UNIX; concept for doing things,
+ that it made "Line Printing" reliably work even under these modern
+ conditions. But time has finally come now to go for something new
+ -- the IPP.
+
+ It is strong proof of the flexibility of &UNIX;; that "Line Printing" works
+ reliably, even under these modern conditions. But time has finally come now
+ to go for something new -- the IPP.
+
+ </para>
+ <glossseealso otherterm="gloss-ipp">IPP</glossseealso>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-lprlpd">LPR/LPD printing</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-cups">
+ <glossterm>&CUPS;</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>C</emphasis>ommon
+ <emphasis>U</emphasis>NIX <emphasis>P</emphasis>rinting
+ <emphasis>S</emphasis>ystem; &CUPS; is the most modern &UNIX; and Linux
+ printing system, also providing cross-platform print services
+ to &Microsoft; &Windows; and Apple &MacOS; clients. Based on IPP, it does
+ away with all the pitfalls of old-style BSD printing,
+ providing authentication, encryption and ACLs, plus many more
+ features. At the same time it is backward-compatible enough
+ to serve all legacy clients that are not yet up to IPP, via
+ LPR/LPD (BSD-style).
+<!--
+ </para>
+ <para>
+-->
+ &CUPS; is able to control any &PostScript; printer by
+ utilizing the vendor-supplied PPD (PostScript Printer
+ Description file), targeted originally for &Microsoft; Windows NT
+ printing only. &kde; Printing is most powerful if based on
+ &CUPS;.</para>
+ <glossseealso otherterm="gloss-acl">ACLs</glossseealso>
+ <glossseealso otherterm="gloss-authentication">Authentication</glossseealso>
+ <glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
+ <glossseealso otherterm="gloss-ipp">IPP</glossseealso>
+ <glossseealso otherterm="gloss-kdeprint">KDEPrint</glossseealso>
+ <glossseealso otherterm="gloss-lprlpd">LPR/LPD</glossseealso>
+ <glossseealso otherterm="gloss-ppd">PPD</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-cupsfaq">
+ <glossterm><acronym>&CUPS;-FAQ</acronym></glossterm>
+ <glossdef><para>Currently only available in German (translation is on the way),
+ the <ulink url="http://www.danka.de/printpro/faq.html">&CUPS;-FAQ</ulink>
+ is a valuable resource to answer many questions that anyone new to
+ &CUPS; printing might have at first.
+ </para>
+ <glossseealso otherterm="gloss-kdeprinthandbook">KDEPrint Handbook</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-cups-o-matic">
+ <glossterm>&CUPS;-O-Matic</glossterm>
+ <glossdef><para>&CUPS;-O-Matic was the first "Third Party" plugin for
+ the &CUPS; printing software. It is available on the <ulink
+ url="http://www.linuxprinting.org/cups-doc.html">Linuxprinting.org
+ website</ulink> to provide an online PPD-generating service.
+<!--
+ </para>
+ <para>
+-->
+
+ Together with the companion <application>cupsomatic</application> Perl-Script,
+ that needs to be installed as an additional &CUPS; backend,
+ it redirects output from the native <application>pstops</application> filter into
+ a chain of suitable Ghostscript filters. Upon completion, it
+ passes the resulting data back to a &CUPS; "backend" for sending
+ to the printer.
+<!--
+ </para>
+ <para>
+-->
+ In this way, &CUPS;-O-Matic enables support for any printer known to
+ have worked previously in a "classical" Ghostscript environment.
+ If no native &CUPS; support for that printer is in sight... &CUPS;-O-Matic
+ is now replaced by the more capable PPD-O-Matic.</para>
+ <glossseealso otherterm="gloss-cupsomatic">cupsomatic</glossseealso>
+ <glossseealso otherterm="gloss-PPD-O-Matic">PPD-O-Matic</glossseealso>
+ <glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-cupsomatic">
+ <glossterm>cupsomatic</glossterm>
+ <glossdef><para>The Perl script <application>cupsomatic</application> (plus a working Perl installation
+ on your system) is needed to make any &CUPS;-O-Matic (or PPD-O-Matic)
+ generated PPD work with &CUPS;. It was written by Grant Taylor, author of
+ the Linux Printing HOWTO and Maintainer of the <ulink
+ url="http://www.linuxprinting.org/printer_list.cgi">printer
+ database</ulink> at the Linuxprinting.org website.</para>
+ <glossseealso otherterm="gloss-cups-o-matic">&CUPS;-O-Matic</glossseealso>
+ <glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
+ <glossseealso otherterm="gloss-cupsomatic">cupsomatic</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-daemon">
+ <glossterm><acronym>Daemon</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>D</emphasis>isk
+ <emphasis>a</emphasis>nd <emphasis>e</emphasis>xecution
+ <emphasis>mon</emphasis>itor; <acronym>Daemons</acronym> are present
+ on all &UNIX; systems to perform tasks independent of user
+ intervention. Readers more familiar with &Microsoft; &Windows; might
+ want to compare daemons and the tasks they are responsible
+ with "services".
+<!--
+ </para>
+ <para>
+-->
+ One example of a daemon present on most
+ legacy &UNIX; systems is the LPD (Line Printer Daemon); &CUPS; is
+ widely seen as the successor to LPD in the &UNIX; world and
+ it also operates through a daemon. </para>
+ <glossseealso otherterm="gloss-spooling">SPOOLing</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-databaselinuxprinting">
+ <glossterm>Database, Linuxprinting.org</glossterm>
+ <glossdef><para>Already years ago, when Linux printing was still really difficult
+ (only command line printing was known to most Linux users, no device
+ specific print options were available for doing the jobs), Grant Taylor,
+ author of the "Linux Printing HOWTO", collected most of the available
+ information about printers, drivers and filters in his database.
+<!--
+ </para>
+ <para>
+-->
+ With the emerging
+ &CUPS; concept, extending the use of PPDs even to non-PostScript printers,
+ he realized the potential of this database: if one puts the different
+ datablobs (with content that could be described along the lines
+ "Which device prints with which Ghostscript or other
+ filter?", "How well?", and "What command line switches are available?") into
+ PPD-compatible files, he could have all the power of &CUPS; on top of
+ the traditional printer "drivers".
+<!--
+ </para>
+ <para>
+-->
+ This has now developed into a broader
+ concept, known as "Foomatic". Foomatic extends the capabilities
+ of spoolers other than &CUPS; (LPR/LPD, LPRng, PDQ, PPR) to a certain
+ degree ("stealing" some concepts from &CUPS;). The Linuxprinting
+ Database is not a Linux-only stop -- people running other &UNIX;
+ based OSes (like *BSD or &MacOS; X) will also find valuable information
+ and software there.
+ </para>
+ <glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
+ <glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting database</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-directtcpipprinting">
+ <glossterm>Direct TCP/IP Printing</glossterm>
+ <glossdef><para>This is a method that often uses TCP/IP port 9100 to connect
+ to the printer. It works with many modern network printers and has
+ a few advantages over LPR/LPD, as it is faster and provides some
+ "backchannel feedback data" from the printer to the host sending
+ the job.</para>
+ <glossseealso otherterm="gloss-appsocketprotocol">AppSocket Protocol</glossseealso>
+ <glossseealso otherterm="gloss-hpjetdirectprotocol">&HP; JetDirect Protocol</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-drivers">
+ <glossterm>Drivers, Printer Drivers</glossterm>
+ <glossdef><para>The term "printer drivers", used in the same sense
+ as on the &Microsoft; &Windows; platform, is not entirely applicable
+ to a Linux or &UNIX; platform. A "driver" functionality
+ is supplied on &UNIX; by different modular components working
+ together. At the core of the printer drivers are "filters". Filters convert
+ print files from a given input format to another format that is acceptable
+ to the target printer. In many cases filters may be connected to a whole
+ filter "chain", where only the result of the last conversion is sent to the
+ printer. The actual transfer of the print data to the device is performed by
+ a "backend".
+ </para>
+ <glossseealso otherterm="gloss-filter">Filter</glossseealso>
+ <glossseealso otherterm="gloss-ppd">PPDs</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-easysoftwareproducts">
+ <glossterm>Easy Software Products</glossterm>
+ <glossdef><para>Mike Sweet's company, which has contributed a few substantial
+ software products towards the Free Software community; amongst
+ them the initial version of <ulink
+ url="http://gimp-print.sf.net/">Gimp-Print,</ulink> the <ulink
+ url="http://www.easysw.com/epm/">EPM software packaging</ulink> tool
+ and <ulink url="http://www.easysw.com/htmldoc/">HTMLDOC</ulink>
+ (used by the "Linux Documentation Project" to build the PDF versions
+ of the HOWTOs) -- but most importantly: <ulink
+ url="http://www.cups.org/">&CUPS;</ulink> (the 'Common &UNIX; Printing
+ System').
+<!--
+ </para>
+ <para>
+-->
+ ESP finance themselves by selling a commercial version
+ of &CUPS;, called <ulink url="http://www.easysw.com/">ESP PrintPro,</ulink>
+ that includes some professional enhancements.
+ </para>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-espprintpro">ESP PrintPro</glossseealso>
+ <glossseealso otherterm="gloss-esp">ESP</glossseealso>
+ <glossseealso otherterm="gloss-gimpprint">Gimp-Print</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-encryption">
+ <glossterm>Encryption</glossterm>
+ <glossdef><para>Encryption of confidential data is an all-important issue if
+ you transfer it over the Internet or even within intranets.
+<!--
+ </para>
+ <para>
+-->
+ Printing
+ via traditional protocols is not encrypted at all -- it is very easy
+ to tap and eavesdrop &eg; into &PostScript; or PCL data transfered
+ over the wire.
+<!--
+ </para>
+ <para>
+-->
+ Therefore, in the design of IPP, provision was made for the easy
+ plugin of encryption mechanisms (which can be provided by the same
+ means as the encryption standards for HTTP traffic: SSL and TLS).</para>
+ <glossseealso otherterm="gloss-authentication">Authentication</glossseealso>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-ipp">IPP</glossseealso>
+ <glossseealso otherterm="gloss-ssl">SSL</glossseealso>
+ <glossseealso otherterm="gloss-tls">TLS</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-epson">
+ <glossterm><acronym>Epson</acronym></glossterm>
+ <glossdef><para>Epson inkjets are among the best supported models by Free software
+ drivers, as the company was not necessarily as secretive about their
+ devices and handed technical specification documents to developers.
+ The excellent print quality achieved by Gimp-Print on the Stylus
+ series of printers can be attributed to this openness.
+<!--
+ </para>
+ <para>
+-->
+ They have also
+ contracted Easy Software Products to maintain an enhanced version
+ of Ghostscript ("ESP GhostScript") for improved support of their
+ printer portfolio.
+ </para>
+ <glossseealso otherterm="gloss-ghostscript">ESP Ghostscript</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-escapesequence">
+ <glossterm>Escape Sequences</glossterm>
+ <glossdef><para>The first ever printers printed ASCII data only. To
+ initiate a new line, or eject a page, they included special
+ command sequences, often carrying a leading [ESC]-character.
+ &HP; evolved this concept through its series of PCL language
+ editions until today, having now developed a full-blown
+ Page Description Language (PDL) from these humble beginnings.
+ </para>
+ <glossseealso otherterm="gloss-pcl">PCL</glossseealso>
+ <glossseealso otherterm="gloss-pdl">PDL</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-escp">
+ <glossterm><acronym>ESC/P</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>E</emphasis>pson
+ <emphasis>S</emphasis>tandard <emphasis>C</emphasis>odes for
+ <emphasis>P</emphasis>rinters. Besides &PostScript; and PCL, Epson's ESC/P
+ printer language is one of the best known.</para>
+ <glossseealso otherterm="gloss-pcl">PCL</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-hpgl">hpgl</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-esp">
+ <glossterm><acronym>ESP</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>E</emphasis>asy
+ <emphasis>S</emphasis>oftware <emphasis>P</emphasis>roducts;
+ the company that developed &CUPS; (the "Common &UNIX; Printing System").
+ </para>
+ <glossseealso otherterm="gloss-easysoftwareproducts">Easy Software Products</glossseealso>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-espprintpro">ESP PrintPro</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-espghostscript">
+ <glossterm><acronym>ESP</acronym> Ghostscript</glossterm>
+ <glossdef><para>A Ghostscript version that is maintained by Easy Software
+ Products. It includes pre-compiled Gimp-Print drivers for
+ many inkjets (plus some other goodies). ESP Ghostscript
+ will produce photographic quality prints in many cases, especially
+ with the Epson Stylus model series. ESP Ghostscript is GPL-software.
+ </para>
+ <glossseealso otherterm="gloss-easysoftwareproducts">Easy Software Products</glossseealso>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-espprintpro">ESP PrintPro</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-espprintpro">
+ <glossterm><acronym>ESP</acronym> PrintPro</glossterm>
+ <glossdef><para> This professional enhancement to &CUPS; (the "Common &UNIX;
+ Printing System") is sold by the developers
+ of &CUPS; complete with more than 2,300 printer drivers for several commercial
+ &UNIX; platforms. <ulink url="http://www.easysw.com/printpro/">ESP PrintPro</ulink>
+ is supposed to work "out of the box" with little or no configuration
+ for users or admins. ESP also sell support contracts for
+ &CUPS; and PrintPro. These sales help to feed the programmers who
+ develop the Free version of &CUPS;.
+ </para>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-filter">
+ <glossterm>Filter</glossterm>
+ <glossdef><para>Filters, in general, are programs that take some input
+ data, work on it and pass it on as their output data. Filters
+ may or may not change the data.
+<!--
+ </para>
+ <para>
+-->
+ Filters in the context of printing, are programs that convert
+ a given file (destined for printing, but not suitable in the
+ format it is presently) into a printable format. Sometimes
+ whole "filter chains" have to be constructed to achieve the
+ goal, piping the output of one filter as the input to the next.
+ </para>
+ <glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
+ <glossseealso otherterm="gloss-rip">RIP</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-foomatic">
+ <glossterm>Foomatic</glossterm>
+ <glossdef><para>Foomatic started out as the wrapper name for a set of
+ different tools available from <ulink
+ url="http://www.linuxprinting.org/">Linuxprinting.org</ulink>
+ These tools aimed to make the usage of traditional
+ Ghostscript and other print filters easier for users and
+ extend the filters' capabilities by adding more command line
+ switches or explain the driver's execution data.
+<!--
+ </para>
+ <para>
+-->
+ Foomatic's different incarnations are &CUPS;-O-Matic, PPD-O-Matic,
+ PDQ-O-Matic, LPD-O-Matic, PPR-O-Matic, MF-O-Matic and
+ Direct-O-Matic. All of these allow the generation
+ of appropriate printer configuration files online, by simply
+ selection the suitable model and suggested (or alternate) driver
+ for that machine.
+<!--
+ </para>
+ <para>
+-->
+ More recently, Foomatic gravitated towards becoming a "meta-spooling"
+ system, that allows configuration of the underlying print subsystem
+ through a unified set of commands (however, this is much more
+ complicated than KDEPrint's &GUI; interface, which performs a similar
+ task with regards to different print subsystems). </para>
+ <glossseealso otherterm="gloss-cups-o-matic">&CUPS;-O-Matic</glossseealso>
+ <glossseealso otherterm="gloss-PPD-O-Matic">PPD-O-Matic</glossseealso>
+ <glossseealso otherterm="gloss-cupsomatic">cupsomatic</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-ghostscript">
+ <glossterm>Ghostscript</glossterm>
+ <glossdef><para>Ghostscript is a &PostScript; Raster Image Processor (RIP) in software, originally
+ developed by L. Peter Deutsch. There is always a <acronym>GPL</acronym> version
+ of Ghostscript available for free usage and distribution
+ (mostly 1 year old) while
+ the current version is commercially sold under another license.
+<!--
+ </para>
+ <para>
+-->
+ Ghostscript is widely used inside the Linux and &UNIX; world
+ for transforming &PostScript; into raster data suitable
+ for sending to non-&PostScript; devices.</para>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-rip">RIP</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-gimpprint">
+ <glossterm>Gimp-Print</glossterm>
+ <glossdef><para>Contrary to its name, Gimp-Print is no longer
+ just the plugin to be used for printing from the popular
+ Gimp program -- its codebase can also serve to be compiled
+ into...
+ <!--
+ </para>
+ <para>
+-->
+ *...a set of PPDs and associated filters that integrate seamlessly
+ into &CUPS;, supporting around 130 different printer models, providing
+ photographic output quality in many cases;
+<!--
+ </para>
+ <para>
+-->
+
+ *...a Ghostscript filter that can be used with any other
+ program that needs a software-RIP;
+<!--
+ </para>
+ <para>
+-->
+
+ *...a library that can be used by other software applications
+ in need of rasterization functions.
+
+
+<!--
+after 4 hours fiddling, I
+could not get those s!@*#?
+<itemizedlist> to pass
+through the meinproc checks.
+For the time being I gave up
+on it and handle it differently
+now.
+ <itemizedlist>
+ <listitem>...a set of PPDs and associated filters that integrate seamlessly
+ into &CUPS;, supporting around 130 different printer models, providing
+ photografic output quality in many cases;</listitem>
+ <listitem>...a Ghostscript filter that can be used with any other
+ program that needs a software-RIP;</listitem>
+ <listitem>...a library that can be used by other software applications
+ in need of rasterization functions.</listitem>
+ </itemizedlist>
+-->
+ </para>
+ <glossseealso otherterm="gloss-lexmark">Lexmark Drivers</glossseealso>
+ <glossseealso otherterm="gloss-rip">RIP</glossseealso>
+ <glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-hp">
+ <glossterm><acronym>&HP;</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>H</emphasis>ewlett-<emphasis>Packard</emphasis>;
+ one of the first companies to distribute their own Linux printer
+ drivers. -- More recently, the Company has released their
+ "HPIJS" package of drivers, including source code and a Free license.
+ This is the first printer manufacturer to do so. HPIJS supports most
+ current models of HP Ink- and DeskJets.
+ </para>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-hpgl">
+ <glossterm><acronym>&HP;/GL</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>&HP;</emphasis>
+ <emphasis>G</emphasis>raphical <emphasis>L</emphasis>anguage;
+ a &HP; printer language mainly used for plotters; many CAD
+ (Computer Aided Design) software programs output &HP;/GL files for
+ printing.</para>
+ <glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
+ <glossseealso otherterm="gloss-pcl">PCL</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-hpjetdirectprotocol">
+ <glossterm>&HP; JetDirect Protocol</glossterm>
+ <glossdef><para>A term branded by &HP; to describe their implementation
+ of print data transfer to the printer via an otherwise "AppSocket" or
+ "Direct TCP/IP Printing" named protocol.</para>
+ <glossseealso otherterm="gloss-appsocketprotocol">AppSocket Protocol</glossseealso>
+ <glossseealso otherterm="gloss-directtcpipprinting">Direct TCP/IP Printing</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-ietf">
+ <glossterm><acronym>IETF</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>I</emphasis>nternet
+ <emphasis>E</emphasis>ngineering <emphasis>T</emphasis>ask
+ <emphasis>F</emphasis>orce; an assembly of Internet, software
+ and hardware experts that discuss
+ new networking technologies and very often arrive at
+ conclusions that are regarded by many as standards. "TCP/IP"
+ is the most famous example.
+<!--
+ </para>
+ <para>
+-->
+
+ IETF standards, as well as
+ drafts, discussions, ideas and useful tutorials, are
+ put in writing in the famous series of "RFCs", which
+ are available to the public and included in most Linux and
+ BSD distributions.</para>
+ <glossseealso otherterm="gloss-ipp">IPP</glossseealso>
+ <glossseealso otherterm="gloss-pwg">PWG</glossseealso>
+ <glossseealso otherterm="gloss-rfc">RFC</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-ipp">
+ <glossterm><acronym>IPP</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>I</emphasis>nternet
+ <emphasis>P</emphasis>rinting <emphasis>P</emphasis>rotocol;
+ defined in a series of RFCs accepted by the IETF with
+ status "proposed standard"; was designed
+ by the PWG. -- IPP is a completely new design for network printing,
+ but it utilizes a very well-known and proven method for the
+ actual data transfer: HTTP 1.1! By not "re-inventing the wheel",
+ and basing itself on an existing and robust Internet standard,
+ IPP is able to relatively easily bolt other HTTP-compatible standard
+ mechanisms into its framework:
+<!--
+ </para>
+ <para>
+-->
+ * Basic, Digest or Certificate authentication
+ mechanisms;
+<!--
+ </para>
+ <para>
+-->
+ * SSL or TLS for encryption of transferred
+ data;
+<!--
+ </para>
+ <para>
+-->
+ * LDAP for directory services (to publish
+ data on printers, device-options, drivers, costs or
+ also to the network; or to check for passwords while
+ performing authentication).
+<!--
+ </para>
+ <para>
+-->
+
+<!--
+ </para>
+ <itemizedlist>
+ <listitem>Basic, Digest or Certificate authentication
+ mechanisms</listitem>
+ <listitem>SSL or TLS for encryption of transferred
+ data</listitem>
+ <listitem>LDAP for directory services (to publish
+ data on printers, device-options, drivers, costs or
+ elso to the network; or to check for passwords while
+ conducting authentication)</listitem>
+ </itemizedlist>
+-->
+ </para>
+
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-pwg">PWG</glossseealso>
+ <glossseealso otherterm="gloss-ietf">IETF</glossseealso>
+ <glossseealso otherterm="gloss-rfc">RFC</glossseealso>
+ <glossseealso otherterm="gloss-tls">TLS</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-kdeprint">
+ <glossterm><acronym>KDEPrint</acronym></glossterm>
+ <glossdef><para>The new printing functionality of &kde; since version 2.2
+ consists of several modules that translate the features and settings
+ of different available print subsystems (&CUPS;, BSD-style LPR/LPD, RLPR...)
+ into nice &kde; desktop &GUI; windows and dialogs to ease their
+ usage.
+<!--
+ </para>
+ <para>
+-->
+ Most important for day-to-day usage is "kprinter", the new
+ &GUI; print command. -- Note: KDEPrint does <emphasis>not</emphasis> implement its own
+ spooling mechanism or its own &PostScript; processing; for this it
+ relies on the selected <emphasis>print subsystem</emphasis>
+ -- however it does add some functionality of its own on top of this
+ foundation...
+ </para>
+ <glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-kprinter">kprinter</glossseealso>
+ <glossseealso otherterm="gloss-kdeprinthandbook">KDEPrint Handbook</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-kdeprinthandbook">
+ <glossterm><acronym>KDEPrint Handbook...</acronym></glossterm>
+ <glossdef><para>...is the name of the reference document that describes KDEPrint
+ functions to users and administrators. You can load it into Konqueror by
+ typing "help:/kdeprint" into the address field. The <ulink
+ url="http://printing.kde.org/">KDEPrint website</ulink>
+ is the resource for updates to this documentation, as well as PDF
+ versions suitable for printing it. It is authored and maintained by Kurt
+ Pfeifle.
+ </para>
+ <glossseealso otherterm="gloss-cupsfaq">&CUPS;-FAQ</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-kprinter">
+ <glossterm>kprinter</glossterm>
+ <glossdef><para><emphasis>kprinter</emphasis> is the new powerful
+ print utility that is natively used by all &kde; applications.
+<!--
+ </para>
+ <para>
+-->
+ Contrary to some common misconceptions,
+ <emphasis>kprinter</emphasis> is <emphasis>not</emphasis> a &CUPS;-only tool,
+ but supports different print subsystems. You can even switch
+ to a different print subsystem "on the fly", in between two jobs,
+ without re-configuration. Of course, due to the powerful
+ features of &CUPS;, <emphasis>kprinter</emphasis> is
+ best suited for use with a &CUPS; frontend.
+<!--
+ </para>
+ <para>
+-->
+ <emphasis>kprinter</emphasis> is the successor
+ to "qtcups", which is no longer being actively maintained. It has
+ inherited all the best features of qtcups and added several new ones.
+<!--
+ </para>
+ <para>
+-->
+
+ MOST IMPORTANT: you can use <emphasis>kprinter</emphasis>
+ with all its features in all non-&kde; applications that allow
+ a customized print command, like gv, Acrobat Reader, Netscape,
+ Mozilla, Galeon, StarOffice, OpenOffice and all GNOME programs.
+<!--
+ </para>
+ <para>
+-->
+ <emphasis>kprinter</emphasis> can act as a "standalone"
+ utility, started from an X-Terminal or a "Mini-CLI" to
+ print many different files, from different folders, with different
+ formats, in one job and simultaneously, without the need to first open the
+ files in the applications! (File formats supported this way are &PostScript;,
+ PDF, International and ASCII Text, as well as many different popular graphic
+ formats, such as PNG, TIFF, JPEG, PNM, Sun RASTER, &etc;)
+ </para>
+ <glossseealso otherterm="gloss-qtcups">QtCUPS</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-lexmark">
+ <glossterm><acronym>Lexmark</acronym></glossterm>
+ <glossdef><para>was one of the first companies to distribute their own Linux printer
+ drivers for some of their models. However, those drivers are binary only
+ (no source code available), and therefore cannot be used to integrate into
+ other Free printing software projects.
+ </para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-linuxprintingorg">
+ <glossterm>Linuxprinting.org</glossterm>
+ <glossdef><para>Linuxprinting.org = not just for Linux; all &UNIX;-like OS-es,
+ like *BSD and commercial Unices may find useful printing
+ information on this site. This web site is the home for the interesting
+ Foomatic project, that strives to develop the "Meta Print Spool and Driver
+ Configuration Toolset" (being able to configure, through one common
+ interface, different print subsystems and their required drivers) with the
+ ability to transfer all queues, printers and configuration files seamlessly
+ to another spooler without new configuration effort. -- Also, they maintain
+ the Printing Database; a collection of driver and device information that
+ enables everybody to find the most current information about printer models,
+ and also generate online the configuration files for any
+ spooler/driver/device combo known to work with one of the common Linux or
+ &UNIX; print subsystems.
+ </para>
+ <glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting database</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-linuxprintingdatabase">
+ <glossterm><acronym>Linuxprinting.org Database</acronym></glossterm>
+ <glossdef><para>....Database containing printers and drivers that are suitable
+ for them... ...a lot of information and documentation to be found... ...it
+ is now also providing some tools and utilities for easing the integration
+ of those drivers into a given system... ...the "Foomatic" family
+ of utilities; being the toolset to make use of the database
+ for most of the commonly used print subsystems, for generating "on the fly"
+ working configurations for your printer model.
+ </para>
+ <glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-lprlpd">
+ <glossterm><acronym>LPR/LPD</acronym> printing</glossterm>
+ <glossdef><para>LPR == some people translate <emphasis>L</emphasis>ine
+ <emphasis>P</emphasis>rinting <emphasis>R</emphasis>equest, others:
+ <emphasis>L</emphasis>ine <emphasis>P</emphasis>rinter
+ <emphasis>R</emphasis>emote.</para>
+ <glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-magicfilter">
+ <glossterm>Magicfilter</glossterm>
+ <glossdef><para>Similarly to the APSfilter program, Magicfilter
+ provides automatic file type recognition functions and, base
+ on that, automatic file conversion to a printable format,
+ depending on the target printer.</para>
+ <glossseealso otherterm="gloss-apsfilter">APSfilter</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-mimetypes">
+ <glossterm>&MIME;-Types</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>M</emphasis>ultipurpose (or
+ Multimedia) <emphasis>I</emphasis>nternet <emphasis>M</emphasis>ail
+ <emphasis>E</emphasis>xtensions; &MIME;-Types were first used to allow
+ the transport of binary data (like mail attachments containing
+ graphics) over mail connections that were normally only transmitting
+ ASCII characters: the data had to be encoded into an ASCII representation.
+<!--
+ </para>
+ <para>
+-->
+ Later this concept was extended to describe a data format in
+ a platform independent, but at the same time non-ambiguous, way.
+ From &Windows; everybody knows the .doc extensions for &Microsoft; Word files.
+ This is handled ambiguously on the &Windows; platform: .doc extensions are also
+ used for simple text files or for Adobe Framemaker files. And if a real
+ Word file is renamed with a different extension, it can no longer be
+ opened by the program.
+<!--
+ </para>
+ <para>
+-->
+ &MIME; typed files carry a recognition string with them, describing
+ their file format based on <emphasis>main_category/sub_category</emphasis>.
+ Inside IPP, print files are also described using the &MIME; type scheme.
+ &MIME; types are registered with the IANA (Internet Assigning Numbers
+ <emphasis>Association</emphasis>) to keep them unambiguous.
+<!--
+ </para>
+ <para>
+-->
+ &CUPS; has some &MIME; types of its own registered, like
+ <emphasis>application/vnd.cups-raster</emphasis> (for the &CUPS;-internal
+ raster image format).
+
+ </para>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-easysoftwareproducts">Easy Software Products</glossseealso>
+ <glossseealso otherterm="gloss-espprintpro">ESP PrintPro</glossseealso>
+ <glossseealso otherterm="gloss-gimpprint">Gimp-Print</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-pcl">
+ <glossterm><acronym>PCL</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>P</emphasis>rinter
+ <emphasis>C</emphasis>ontrol <emphasis>L</emphasis>anguage;
+ developed by &HP;. PCL started off in version 1 as a simple
+ command set for ASCII printing; now,
+ in its versions PCL6 and PCL-X, it is capable of printing graphics
+ and color -- but outside the &Microsoft; &Windows; realm and &HP-UX;
+ (&HP;'s own brand of &UNIX;), it is not commonly used...</para>
+ <glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
+ <glossseealso otherterm="gloss-hpgl">&HP;/GL</glossseealso>
+ <glossseealso otherterm="gloss-pdl">PDL</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-pdl">
+ <glossterm><acronym>PDL</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>P</emphasis>age
+ <emphasis>D</emphasis>escription <emphasis>L</emphasis>anguage;
+ PDLs describe, in an abstract way, the graphical representation
+ of a page. - Before it is actually transferred into
+ toner or ink laid down on to paper, a PDL needs to be
+ "interpreted" first. In &UNIX;, the most important PDL
+ is &PostScript;.
+ </para>
+ <glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
+ <glossseealso otherterm="gloss-hpgl">&HP;/GL</glossseealso>
+ <glossseealso otherterm="gloss-pcl">PCL</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-pixel">
+ <glossterm>Pixel</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>Pic</emphasis>ture
+ <emphasis>El</emphasis>ement; this term describes the smallest
+ part of a raster picture (either as printed on paper
+ or as displayed on a monitor by cathode rays or LCD elements). As
+ any graphical or image representation on those types of output
+ devices is composed of pixels, the values of "ppi" (pixel per inch)
+ and &dpi; (dots per inch) are one important parameter for the
+ overall quality and resolution of an image.</para>
+ <glossseealso otherterm="gloss-filter">Filter</glossseealso>
+ <glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-raster">Raster</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-pjl">
+ <glossterm><acronym>PJL</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>P</emphasis>rint
+ <emphasis>J</emphasis>ob <emphasis>L</emphasis>anguage;
+ developed by &HP; to control and influence default and per-job
+ settings of a printer. It may not only be used
+ for &HP;'s own (PCL-)printers; also many &PostScript;
+ and other printers understand PJL commands sent to them
+ inside a print job, or in a separate signal.</para>
+ <glossseealso otherterm="gloss-pcl">PCL</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-postscript">
+ <glossterm>&PostScript;</glossterm>
+ <glossdef><para>&PostScript; (often shortened to "PS") is the de-facto
+ standard in the &UNIX; world for printing files. It was
+ developed by Adobe and licensed to printer manufacturers
+ and software companies.
+<!--
+ </para>
+ <para>
+-->
+ As the &PostScript; specifications were
+ published by Adobe, there are also "Third Party" implementations
+ of &PostScript; generating and &PostScript; interpreting software
+ available (one of the best-known in the Free software world
+ being Ghostscript, a powerful PS-interpreter).
+ </para>
+ <glossseealso otherterm="gloss-escp">ESC/P</glossseealso>
+ <glossseealso otherterm="gloss-hpgl">&HP;/GL</glossseealso>
+ <glossseealso otherterm="gloss-pcl">PCL</glossseealso>
+ <glossseealso otherterm="gloss-ppd">PPD</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-ppd">
+ <glossterm><acronym>PPD</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>P</emphasis>ostScript
+ <emphasis>P</emphasis>rinter <emphasis>D</emphasis>escription;
+ PPDs are ASCII files storing all information about the special
+ capabilities of a printer, plus definitions of the (PostScript-
+ or PJL-) commands to call on a certain capability (like print
+ duplexing).
+<!--
+ </para>
+ <para>
+-->
+
+ As the explanation of the acronym reveals, PPDs were originally
+ only used for &PostScript; printers. &CUPS; has extended the
+ PPD concept to all types of printers.
+<!--
+ </para>
+ <para>
+-->
+
+ PPDs for &PostScript; printers are provided by the printer
+ vendors. They can be used with &CUPS; and KDEPrint to have access
+ to the full features of any &PostScript; printer. The KDEPrint Team
+ recommends using a PPD originally intended for use with
+ &Microsoft; Windows NT.
+<!--
+ </para>
+ <para>
+-->
+
+ PPDs for non-PostScript printers <emphasis>need</emphasis> a
+ companion "filter" to process the &PostScript; print files into
+ a format digestible for the non-PostScript target device. Those
+ PPD/filter combos are not (yet) available from the vendors. After
+ the initiative by the &CUPS; developers to utilize PPDs, the Free
+ Software community was creative enough to quickly come up with
+ support for most of the currently used printer models, through
+ PPDs and classical Ghostscript filters. But note: the printout
+ quality varies from "hi-quality photographic output" (using
+ Gimp-Print with most Epson inkjets) to "hardly readable" (using
+ Foomatic-enabled Ghostscript filters for models rated as
+ "paperweight" in the Linuxprinting.org database).
+ </para>
+ <glossseealso otherterm="gloss-cups">&CUPS;</glossseealso>
+ <glossseealso otherterm="gloss-linuxprintingorg">Linuxprinting.org</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-PPD-O-Matic">
+ <glossterm>PPD-O-Matic</glossterm>
+ <glossdef><para>PPD-O-Matic is a set of Perl scripts that run on the Linuxprinting.org
+ web server and can be used online to generate PPDs for any printer that is known
+ to print with Ghostscript.
+<!--
+ </para>
+ <para>
+-->
+
+ These PPDs can be hooked up to &CUPS;/KDEPrint, as well as
+ used inside PPD-aware applications like StarOffice to determine all different
+ parameters of your printjobs. It is now recommended, in most cases, to
+ use "PPD-O-Matic" instead of the older &CUPS;-O-Matic.
+<!--
+ </para>
+ <para>
+-->
+
+ To generate a PPD, go to the <ulink
+ url="http://www.linuxprinting.org/printer_list.cgi">printer
+ database</ulink>, select your printer model, follow
+ the link to show the available Ghostscript filters for that printer, select
+ one, click "generate" and finally save the file to your local system.
+ Be sure to read the instructions. Make sure that your local system
+ does indeed have Ghostscript and the filter, which you chose
+ before generating the PPD, installed.
+ </para>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-cups-o-matic">&CUPS;-O-Matic</glossseealso>
+ <glossseealso otherterm="gloss-linuxprintingorg">Linuxprinting.org</glossseealso>
+ <glossseealso otherterm="gloss-foomatic">Foomatic</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-printcap">
+ <glossterm>printcap</glossterm>
+ <glossdef><para>In BSD-style print systems, the "printcap" file holds
+ the configuration information; the printing daemon reads this file
+ to determine which printers are available, what filters are to be
+ user for each, where the spooling folder is located,
+ if there are banner pages to be used, and so on...
+ Some applications also depend on read access to the printcap
+ file, to obtain the names of available printers. </para>
+ <glossseealso otherterm="gloss-bsdstyleprinting">BSD-style printing</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-printermib">
+ <glossterm>Printer-<acronym>MIB</acronym></glossterm>
+ <glossdef><para>Abbreviation for
+ <emphasis>Printer</emphasis>-<emphasis>M</emphasis>anagement
+ <emphasis>I</emphasis>nformation <emphasis>B</emphasis>ase; the
+ Printer-MIB defines a set of parameters that are to be
+ stored inside the printer for access
+ through the network. This is useful if many (in some cases, literally
+ thousands) network printers are managed centrally
+ with the help of SNMP (Simple Network Management Protocol).</para>
+ <glossseealso otherterm="gloss-pwg">PWG</glossseealso>
+ <glossseealso otherterm="gloss-snmp">SNMP</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-pwg">
+ <glossterm><acronym>PWG</acronym></glossterm>
+ <glossdef><para>Abbreviation for
+ <emphasis>P</emphasis>rinter <emphasis>W</emphasis>orking
+ <emphasis>G</emphasis>roup; the PWG is a loose grouping of
+ representatives of the printer industry that has, in the past
+ years, developed different standards
+ in relation to network printing. These were later accepted by the
+ IETF as RFC standards, like the "Printer-MIB" and the IPP.</para>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-ipp">IPP</glossseealso>
+ <glossseealso otherterm="gloss-printermib">Printer-MIB</glossseealso>
+ <glossseealso otherterm="gloss-snmp">SNMP</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-printkioslave">
+ <glossterm>print:/ KIO Slave</glossterm>
+ <glossdef><para>You can use a syntax of "print:/..." to get quick access
+ to KDEPrint resources. Typing "print:/manager" as a Konqueror URL
+ address gives administrative access to KDEPrint. Konqueror uses &kde;'s
+ famous "KParts" technology to achieve that. </para>
+ <glossseealso otherterm="gloss-ioslave">IO Slave</glossseealso>
+ <glossseealso otherterm="gloss-kparts">KParts</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-printerdatabase">
+ <glossterm>Printer Database</glossterm>
+ <glossdef><para>.</para>
+ <glossseealso otherterm="gloss-linuxprintingdatabase">Linuxprinting Database</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-qtcups">
+ <glossterm><acronym>Qt&CUPS;</acronym></glossterm>
+ <glossdef><para>Qt&CUPS; and KUPS were the predecessors of KDEPrint; they are now
+ deprecated and no longer maintained. What was good in qtcups is all inherited
+ by "kprinter", the new KDE print dialog (which is much improved over qtcups);
+ what you liked about kups is now all in the KDEPrint Manager (accessible
+ via the KDE Control Center or via the URL "print:/manager" from Konqueror) --
+ with more functionality and less bugs... Its former developer, Michael Goffioul, is now
+ the developer of KDEPrint -- a very nice and productive guy and quick bug fixer...
+ </para>
+ <glossseealso otherterm="gloss-kprinter">kprinter</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-raster">
+ <glossterm>Raster Image</glossterm>
+ <glossdef><para>Every picture on a physical medium
+ is composed of a pattern of discrete dots in different colors and (maybe)
+ sizes. This is called a "raster image".
+<!--
+ </para>
+ <para>
+-->
+
+ This is as opposed to a "vector image"
+ where the graphic is described in terms of continuous curves, shades,
+ forms and filled areas, represented by mathematical formula. Vector images
+ normally have a smaller file size and may be scaled in size
+ without any loss of information and quality --- but they cannot be
+ output directly, but always have to be "rendered" or "rasterized"
+ first to the given resolution that the output device is capable of...
+<!--
+ </para>
+ <para>
+-->
+
+
+ The rasterization is done by a Raster Image Processor (RIP,
+ often the Ghostscript software) or some other filtering
+ instance.</para>
+ <glossseealso otherterm="gloss-pixel">Pixel</glossseealso>
+ <glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-filter">Filter</glossseealso>
+ <glossseealso otherterm="gloss-rip">RIP</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-rip">
+ <glossterm><acronym>RIP</acronym></glossterm>
+ <glossdef><para>Abbreviation for
+ <emphasis>R</emphasis>aster <emphasis>I</emphasis>mage
+ <emphasis>P</emphasis>rocess(or); if used in the context of
+ printing, "RIP" means a hardware or software
+ instance that converts &PostScript; (or other print formats
+ that are represented in one of the non-Raster PDLs) into a
+ raster image format in such a way that it is acceptable
+ for the "marking engine" of the printer.
+<!--
+ </para>
+ <para>
+-->
+
+ &PostScript; printers
+ contain their own PostScript-RIPs. A RIP may or may not be located
+ inside a printer.
+<!--
+ </para>
+ <para>
+-->
+
+ For many &UNIX; systems, Ghostscript is the package that provides
+ a "RIP in software", running on the host computer, and pre-digesting
+ the &PostScript; or other data to become ready to be sent to the
+ printing device (hence you may perceive a "grain of truth" in the
+ slogan "Ghostscript turns your printer into a &PostScript;
+ machine", which of course is not correct in the true sense of the
+ meaning).</para>
+ <glossseealso otherterm="gloss-filter">Filter</glossseealso>
+ <glossseealso otherterm="gloss-ghostscript">Ghostscript</glossseealso>
+ <glossseealso otherterm="gloss-postscript">&PostScript;</glossseealso>
+ <glossseealso otherterm="gloss-pdl">PDL</glossseealso>
+ <glossseealso otherterm="gloss-raster">Raster</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-rlpr">
+ <glossterm><acronym>RLPR</acronym> (Remote LPR)</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>R</emphasis>emote
+ <emphasis>L</emphasis>ine <emphasis>P</emphasis>rinting
+ <emphasis>R</emphasis>equest; this is a BSD-style printing system,
+ that needs no root privileges to be installed, and no "printcap" to
+ work: all parameters may be specified on the command
+ line.
+<!--
+ </para>
+ <para>
+-->
+
+ RLPR comes in handy for many laptop users who are
+ working in frequently changing environments. This is because it
+ may be installed concurrently with every other printing
+ sub system, and allows a very flexible and quick
+ way to install a printer for direct access via LPR/LPD.
+<!--
+ </para>
+ <para>
+-->
+
+ KDEPrint
+ has an "Add Printer Wizard" to make RLPR usage even easier.
+ The kprinter command allows switching to RLPR "on
+ the fly" at any time.</para>
+ <glossseealso otherterm="gloss-kdeprint">KDEPrint</glossseealso>
+ <glossseealso otherterm="gloss-kprinter">kprinter</glossseealso>
+ <glossseealso otherterm="gloss-printcap">printcap</glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-snmp">
+ <glossterm><acronym>SNMP</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>S</emphasis>imple
+ <emphasis>N</emphasis>etwork <emphasis>M</emphasis>anagement
+ <emphasis>P</emphasis>rotocol; SNMP is widely used to control
+ all types of network node (Hosts, Routers, Switches, Gateways,
+ Printers...) remotely.</para>
+ <glossseealso otherterm="gloss-pwg">PWG</glossseealso>
+ <glossseealso otherterm="gloss-printermib">Printer-MIB</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-ssl">
+ <glossterm><acronym>SSL(3)</acronym> encryption</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>S</emphasis>ecure
+ <emphasis>S</emphasis>ocket <emphasis>L</emphasis>ayer;
+ <acronym>SSL</acronym> is a proprietary encryption method for data
+ transfer over HTTP that was developed by Netscape. It is now being
+ replaced by an IETF standard named TLS.
+ </para>
+ <glossseealso otherterm="gloss-tls"><acronym>TLS</acronym></glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-spooling">
+ <glossterm><acronym>SPOOL</acronym>ing</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>S</emphasis>ynchronous
+ <emphasis>P</emphasis>eripheral <emphasis>O</emphasis>perations
+ <emphasis>O</emphasis>n<emphasis>L</emphasis>ine;
+ <acronym>SPOOL</acronym>ing enables printing applications
+ (and users) to continue their work
+ as the job is being taken care of by a system <acronym>daemon</acronym>,
+ which stores the file at a temporary location until the printer is ready
+ to print. </para>
+ <glossseealso otherterm="gloss-daemon"><acronym>Daemon</acronym></glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-tls">
+ <glossterm><acronym>TLS</acronym> encryption</glossterm>
+ <glossdef><para>Abbreviation for <emphasis>T</emphasis>ransport
+ <emphasis>L</emphasis>ayer <emphasis>S</emphasis>ecurity;
+ <acronym>TLS</acronym> is an encryption standard for
+ data transfered over HTTP 1.1; it is defined in RFC 2246;
+ although based on the former SSL development
+ (from Netscape) it is not fully compatible with it.
+ </para>
+ <glossseealso otherterm="gloss-ssl"><acronym>SSL(3)</acronym></glossseealso>
+ </glossdef>
+ </glossentry>
+
+
+ <glossentry id="gloss-systemVstyleprinting">
+ <glossterm>System V-style printing</glossterm>
+ <glossdef><para>This is the second flavor of traditional &UNIX;
+ printing (as opposed to BSD-style printing). It uses
+ a different command set (lp, lpadmin,...) to BSD,
+ but is not fundamentally different from it. However, the
+ gap between the two is big enough to make the two
+ incompatible, so that a BSD-client cannot simply print
+ to a System V style print server without additional
+ tweaking... IPP is supposed to resolve this weakness
+ and more.
+ </para>
+ <glossseealso otherterm="gloss-bsdstyleprinting"><acronym>BSD-style printing</acronym></glossseealso>
+ <glossseealso otherterm="gloss-ipp"><acronym>IPP</acronym></glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-turboprint">
+ <glossterm>TurboPrint</glossterm>
+ <glossdef><para>Shareware software providing photo quality printing for many
+ inkjet printers. It is useful if you are unable to find a driver for your
+ printer and may be hooked into either a traditional Ghostscript system
+ or a modern &CUPS; system.</para>
+ <glossseealso otherterm="gloss-gimpprint">Gimp-Print</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-xpp">
+ <glossterm><acronym>XPP</acronym></glossterm>
+ <glossdef><para>Abbreviation for <emphasis>X</emphasis>
+ <emphasis>P</emphasis>rinting <emphasis>P</emphasis>anel;
+ <acronym>XPP</acronym> was the first Free
+ graphical print command for &CUPS;, written by Till Kamppeter,
+ and in some ways a model for the "kprinter" utility in &kde;.</para>
+ </glossdef>
+ </glossentry>
+<!--
+ <glossentry id="gloss-1">
+ <glossterm>xxxx</glossterm>
+ <glossdef><para>.</para>
+ <glossseealso otherterm="gloss-1">xyz</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-3">
+ <glossterm>xxxx</glossterm>
+ <glossdef><para>.</para>
+ <glossseealso otherterm="gloss-1">xyz</glossseealso>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="gloss-4">
+ <glossterm>xxxx</glossterm>
+ <glossdef><para>.</para>
+ <glossseealso otherterm="gloss-1">xyz</glossseealso>
+ </glossdef>
+ </glossentry>
+-->
+ </glossdiv>
+
+
+<!--
+</glossary>
+-->
diff --git a/doc/kappfinder/Makefile.am b/doc/kappfinder/Makefile.am
new file mode 100644
index 00000000..3f20a1e1
--- /dev/null
+++ b/doc/kappfinder/Makefile.am
@@ -0,0 +1,5 @@
+
+KDE_LANG = en
+KDE_DOCS = AUTO
+
+KDE_MANS = AUTO
diff --git a/doc/kappfinder/man-kappfinder.1.docbook b/doc/kappfinder/man-kappfinder.1.docbook
new file mode 100644
index 00000000..1c0fdb68
--- /dev/null
+++ b/doc/kappfinder/man-kappfinder.1.docbook
@@ -0,0 +1,81 @@
+<?xml version="1.0" ?>
+<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
+<!ENTITY % English "INCLUDE">
+]>
+
+<refentry lang="&language;">
+<refentryinfo>
+<author><personname><firstname>Jan</firstname><surname>Schaumann</surname></personname>
+<email>jschauma@netmeister.org</email></author>
+<date>April 8, 2003</date>
+</refentryinfo>
+
+<refmeta>
+<refentrytitle><command>kappfinder</command></refentrytitle>
+<manvolnum>1</manvolnum>
+</refmeta>
+
+<refnamediv>
+<refname><command>kappfinder</command></refname>
+<refpurpose>An app to add installed applications to the &kde; menu.</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+<cmdsynopsis>
+<command>kappfinder</command>
+<group><option>--dir</option> <replaceable> directory</replaceable></group>
+<group><option>KDE Generic Options</option></group>
+<group><option>Qt Generic Options</option></group>
+
+</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+<title>Description</title>
+
+<para>The KDE application findern (&kappfinder;) looks for legacy and
+third party applications that are installed on your system and adds
+them to the KDE menu system. </para>
+
+</refsect1>
+
+<refsect1>
+<title>Options</title>
+
+<variablelist>
+<varlistentry>
+<term><option>--dir</option> <replaceable>directory</replaceable></term>
+<listitem>
+<para>
+Install <filename>.desktop</filename> files into directory <replaceable>directory</replaceable>
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</refsect1>
+
+<refsect1>
+<title>See Also</title>
+
+<para>More detailed user documentation is available from <ulink
+url="help:/kappfinder">help:/kappfinder</ulink> (either enter this
+<acronym>URL</acronym> into &konqueror;, or run
+<userinput><command>khelpcenter</command>
+<parameter>help:/kappfinder</parameter></userinput>).</para>
+
+</refsect1>
+
+<refsect1>
+<title>Authors</title>
+
+<para>&kappfinder; was written by &Matthias.Hoelzer-Kluepfel; &Matthias.Hoelzer-Kluepfel.mail;</para>
+
+<para>This man page was prepared by Jan Schaumann
+<email>jschauma@netmeister.org</email> for the <quote>Missing Man
+Pages Project</quote> ( <ulink
+url="http://www.netmeister.org/misc/m2p2/index.html">http://www.netmeister.org/misc/m2p2/index.html</ulink>.</para>
+
+</refsect1>
+
+</refentry>
diff --git a/doc/kate/Makefile.am b/doc/kate/Makefile.am
new file mode 100644
index 00000000..17a314c3
--- /dev/null
+++ b/doc/kate/Makefile.am
@@ -0,0 +1,3 @@
+KDE_LANG = en
+KDE_DOCS = AUTO
+KDE_MANS = AUTO
diff --git a/doc/kate/TODO b/doc/kate/TODO
new file mode 100644
index 00000000..d41ed4b8
--- /dev/null
+++ b/doc/kate/TODO
@@ -0,0 +1,6 @@
+Fill empty sections.
+Rewrite intro chapter.
+Write regexp appendix.
+Add Misc Tools chapter, ao Find in Files.
+Go over everything and make sure it reflects the practial truuth ;)
+Add links to foreign documentation.
diff --git a/doc/kate/advanced.docbook b/doc/kate/advanced.docbook
new file mode 100644
index 00000000..b9b0cda9
--- /dev/null
+++ b/doc/kate/advanced.docbook
@@ -0,0 +1,1242 @@
+<chapter id="advanced-editing-tools">
+<chapterinfo>
+<authorgroup>
+<author>&Anders.Lund; &Anders.Lund.mail;</author>
+<author>&Dominik.Haumann; &Dominik.Haumann.mail;</author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</chapterinfo>
+<title>Advanced Editing Tools</title>
+
+<sect1 id="advanced-editing-tools-comment">
+
+<title>Comment/Uncomment</title>
+
+<para>The Comment and Uncomment commands, available from the
+<guimenu>Tools</guimenu> menu allow you to add or remove comment
+markers to the selection, or the current line if no text is selected,
+if comments are supported by the format of the text you are
+editing.</para>
+
+<para>The rules for how commenting is done are defined in the syntax
+definitions, so if syntax highlighting is not used, commenting/uncommenting
+is not possible. </para>
+
+<para>Some formats define single line comment markers, some multiline
+markers and some both. If multiline markers are not available,
+commenting out a selection that does not fully include its last line
+is not possible.</para>
+
+<para>If a single line marker is available, commenting single lines is
+preferred where applicable, as this helps to avoid problems with
+nested comments.</para>
+
+<para>When removing comment markers, no uncommented text should be
+selected. When removing multiline comment markers from a selection,
+any whitespace outside the comment markers is ignored.</para>
+
+<para><indexterm><primary>comment</primary></indexterm>
+To place comment markers, use the
+<menuchoice><guimenu>Tools</guimenu><guimenuitem>Comment</guimenuitem></menuchoice>
+menu item or the related keyboard shortcut sequence, default is
+<keycombo action="simul">&Ctrl;<keycap>D</keycap></keycombo>.</para>
+
+<para><indexterm><primary>uncomment</primary></indexterm>
+To remove comment markers, use the
+<menuchoice><guimenu>Tools</guimenu><guimenuitem>Uncomment</guimenuitem></menuchoice>
+menu item or the related keyboard shortcut, default is <keycombo
+action="simul">&Ctrl;&Shift;<keycap>D</keycap></keycombo>.</para>
+
+</sect1>
+
+<sect1 id="advanced-editing-tools-commandline">
+<title>The Editor Component Command Line</title>
+
+<para>Kate's editor component has an internal command line, allowing you to
+perform various actions from a minimal GUI. The command line is a text entry
+in the bottom of the editor area, to show it select
+<menuchoice><guimenu>View</guimenu><guimenuitem>Switch to Command Line</guimenuitem></menuchoice>
+or use the shortcut (default is
+<keycombo action="simul"><keycap>F7</keycap></keycombo>). The editor provides
+a set of commands as documented below, and additional commands can be provided
+by plugins.</para>
+
+<para>To execute a command, type the comand then press the return key. The
+command line will indicate wether it succeded and possibly display a message. If
+you entered the command line by pressing <keycap>F7</keycap> it will
+automatically hide after a few seconds. To clear the message and enter a new
+command, press <keycap>F7</keycap> again.</para>
+
+<para>The command line has a built-in help system, issue the command
+<command>help</command> to get started. To see a list of all available commands
+issue <command>help list</command>, to view help for a specific command, do
+<command>help <replaceable>command</replaceable></command>.</para>
+
+<para>The command line has a built in history, so you can reuse commands already
+typed. To navigate the history, use the <keycap>Up</keycap> and
+<keycap>Down</keycap> keys. When showing historical commands, the argument part
+of the command will be selected, allowing you to easily overwrite the
+arguments.</para>
+
+<sect2 id="advanced-editing-tools-commandline-commands">
+<title>Standard Command Line Commands</title>
+
+<sect3 id="advanced-editing-tools-commandline-commands-configure">
+<title>Commands for Configuring the Editor</title>
+
+<para>These commands are provided by the editor component, and allows you to
+configure the active document and view only. This is handy if you want to use
+a setting different from the default settings, for example for indentation.
+</para>
+
+<variablelist>
+<title>Argument types</title>
+
+<varlistentry>
+<term>BOOLEAN</term>
+<listitem><para>This is used with commands that turns things on or off.
+Legal values are <userinput>on</userinput>, <userinput>off</userinput>,
+<userinput>true</userinput>, <userinput>false</userinput>,
+<userinput>1</userinput> or <userinput>0</userinput></para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>INTEGER</term>
+<listitem><para>An integer number</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>STRING</term>
+<listitem><para>A string</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+<variablelist>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-tab-width</command><arg>INTEGER width</arg></cmdsynopsis></term>
+<listitem><para>Sets the tab width to the number <userinput>width</userinput></para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-indent-width</command><arg>INTEGER width</arg></cmdsynopsis></term>
+<listitem><para>Sets the indentation width to the number
+<userinput>width</userinput>. Used only if you are indenting with
+spaces.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-word-wrap-column</command><arg>INTEGER width</arg></cmdsynopsis></term>
+<listitem><para>Sets the line width for hard wrapping to
+<userinput>width</userinput>. This is used if you are having your text wrapped
+automatically.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-icon-border</command><arg>BOOLEAN enable</arg>
+</cmdsynopsis></term>
+<listitem><para>Sets the visibility of the icon border.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-folding-markers</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>Sets the visibility of the folding markers pane.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-line-numbers</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>Sets the visibility of the line numbers pane.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-replace-tabs</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>If enabled, tabs are replaced with spaces as you type.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-remove-trailing-space</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>If enabled, trailing whitespace are removed whenever the cursor
+leaves a line.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-show-tabs</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>If enabled, TAB characters and trailing whitespace will be
+visualized by a small dot.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-indent-spaces</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>If enabled, the editor will indent with
+<option>indent-width</option> spaces for each indentation level, rather than
+with one TAB character.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-mixed-indent</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>If enabled, kate will use a mix of TAB and spaces for
+indentation. Each indentation level will be <option>indent-width</option> wide,
+and more indentation levels will be optimized to use as many TAB characters as
+possible.</para>
+<para>When executed, this command will additionally set space indentation enabled,
+and if the indent width is unspecified it will be set to half of the
+<option>tab-width</option> for the document at the time of execution.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-word-wrap</command><arg>BOOLEAN
+enable</arg></cmdsynopsis></term>
+<listitem><para>Enables dynamic word wrap according to
+<userinput>enable</userinput></para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-replace-tabs-save</command><arg>BOOLEAN enable
+</arg></cmdsynopsis></term>
+<listitem><para>When enabled, tabs will be replaced with whitespace whenever
+ the document is saved.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-remove-trailing-space-save</command><arg>BOOLEAN enable</arg></cmdsynopsis></term>
+<listitem><para>When enabled, trailing space will be removed from each line
+whenever the document is saved.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-indent-mode</command><arg>name</arg></cmdsynopsis></term>
+<listitem><para>Sets the autoindentation mode to <userinput>name</userinput>.
+If <userinput>name</userinput> is not known, the mode is set to 'none'. Valid
+modes are 'cstyle', 'csands', 'xml', 'python', 'varindent' and 'none'.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>set-highlight</command><arg>highlight</arg></cmdsynopsis></term>
+<listitem><para>Sets the syntax highlighting system for the document. The
+argument must be a valid highlight name, as seen in the
+<menuchoice><guimenu>Tools</guimenu><guisubmenu>Highlighting</guisubmenu></menuchoice>
+menu. This command provides an autocompletion list for its
+argument.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3 id="advanced-editing-tools-commandline-commands-edit">
+<title>Commands for editing</title>
+
+<para>These commands modify the current document.</para>
+
+<variablelist>
+<varlistentry>
+<term><cmdsynopsis><command>indent</command></cmdsynopsis></term>
+<listitem><para>Indents the selected lines or the current line.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>unindent</command></cmdsynopsis></term>
+<listitem><para>Unindents the selected lines or current line.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>cleanindent</command></cmdsynopsis></term>
+<listitem><para>Cleans up the indentation of the selected lines or current line
+according to the indentation settings in the document.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>comment</command></cmdsynopsis></term>
+<listitem><para>Inserts comment markers to make the selection or selected lines
+or current line a comment according to the text format as defined by the syntax
+highlight definition for the document.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>uncomment</command></cmdsynopsis></term>
+<listitem><para>Removes comment markers from the selection or selected lines
+or current line according to the text format as defined by the syntax highlight
+definition for the document.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>kill-line</command></cmdsynopsis></term>
+<listitem><para>Deletes the current line.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>replace</command><arg>pattern</arg><arg>replacement</arg></cmdsynopsis></term>
+<listitem><para>Replaces text matching <userinput>pattern</userinput> with
+<userinput>replacement</userinput>. If you want to include whitespace in the
+<userinput>pattern</userinput>, you must quote both the <userinput>pattern</userinput>
+and <userinput>replacement</userinput> with single or double quotes. If the
+arguments are unquoted, the first word is used as <userinput>pattern</userinput>
+and the rest for <userinput>replacement</userinput>. If
+<userinput>replacement</userinput> is empty, each occurrence of
+<userinput>pattern</userinput> is removed.</para>
+<para>You can set flags to configure the search by adding a colon, followed
+by one or more letters each representing a configuration, giving the form
+<userinput>replace:options pattern replacement</userinput>. Available options
+are:
+
+<variablelist>
+
+<varlistentry>
+<term><userinput>b</userinput></term>
+<listitem><para>Search backwards.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>c</userinput></term>
+<listitem><para>Search from cursor position.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>e</userinput></term>
+<listitem><para>Search in the selection only.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>r</userinput></term>
+<listitem><para>Do regular expression search. If set, you may use
+<userinput>\N</userinput> where N is a number to represent captures in the
+replacement string.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>s</userinput></term>
+<listitem><para>Do case sensitive search.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>p</userinput></term>
+<listitem><para>Prompt for permission to replace the next occurence.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>w</userinput></term>
+<listitem><para>Match whole words only.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>date</command><arg>format</arg></cmdsynopsis></term>
+<listitem><para>Inserts a date/time string as defined by the specified
+<userinput>format</userinput>, or the format <quote>yyyy-MM-dd hh:mm:ss</quote>
+if none is specified. The following translations are done when interpreting
+<userinput>format</userinput>:
+
+<informaltable>
+<tgroup cols="2">
+<tbody>
+<row><entry><literal>d</literal></entry><entry>The day as number without a leading zero (1-31).</entry></row>
+<row><entry><literal>dd</literal></entry><entry>The day as number with a leading zero (01-31).</entry></row>
+<row><entry><literal>ddd</literal></entry><entry>The abbreviated localized day name (e.g. 'Mon'..'Sun').</entry></row>
+<row><entry><literal>dddd</literal></entry><entry>The long localized day name (e.g. 'Monday'..'Sunday').</entry></row>
+<row><entry><literal>M</literal></entry><entry>The month as number without a leading zero (1-12).</entry></row>
+<row><entry><literal>MM</literal></entry><entry>The month as number with a leading zero (01-12).</entry></row>
+<row><entry><literal>MMM</literal></entry><entry>The abbreviated localized month name (e.g. 'Jan'..'Dec').</entry></row>
+<row><entry><literal>yy</literal></entry><entry>The year as two digit number
+(00-99).</entry></row>
+<row><entry><literal>yyyy</literal></entry><entry>The year as four digit number (1752-8000).</entry></row>
+<row><entry><literal>h</literal></entry><entry>The hour without a leading zero (0..23 or 1..12 if AM/PM display).</entry></row>
+<row><entry><literal>hh</literal></entry><entry>The hour with a leading zero (00..23 or 01..12 if AM/PM display).</entry></row>
+<row><entry><literal>m</literal></entry><entry>The minute without a leading zero (0..59).</entry></row>
+<row><entry><literal>mm</literal></entry><entry>The minute with a leading zero (00..59).</entry></row>
+<row><entry><literal>s</literal></entry><entry>The second without a leading zero (0..59).</entry></row>
+<row><entry><literal>ss</literal></entry><entry>The second with a leading zero (00..59).</entry></row>
+<row><entry><literal>z</literal></entry><entry>The milliseconds without leading zeroes (0..999).</entry></row>
+<row><entry><literal>zzz</literal></entry><entry>The milliseconds with leading zeroes (000..999).</entry></row>
+<row><entry><literal>AP</literal></entry><entry>Use AM/PM display. AP will be replaced by either "AM" or "PM".</entry></row>
+<row><entry><literal>ap</literal></entry><entry>Use am/pm display. ap will be replaced by either "am" or "pm".</entry></row>
+
+</tbody>
+</tgroup>
+</informaltable>
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>char</command><arg>identifier</arg></cmdsynopsis></term>
+<listitem>
+<para>This command allows you to insert literal characters by their
+numerical identifier, in decimal, octal or hexadecimal form.
+To use it launch the Editing Command dialog and type <userinput>char:
+[number]</userinput> in the entry box, then hit
+<guibutton>OK</guibutton>.</para>
+
+<example>
+<title><command>char</command> examples</title>
+
+<para>Input: <userinput>char:234</userinput></para>
+<para>Output: <computeroutput>&#234;</computeroutput></para>
+<para>Input: <userinput>char:0x1234</userinput></para>
+<para>Output: <computeroutput>&#x1234;</computeroutput></para>
+</example>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<indexterm><primary>replace, sed style</primary>
+<secondary>search, sed style</secondary></indexterm>
+<command>s///[ig]</command> <command>%s///[ig]</command></term>
+
+<listitem>
+<para>This command does a sed-like search/replace operation on the
+current line, or on the whole file (<command>%s///</command>).</para>
+
+<para>In short, the text is searched for text matching the
+<emphasis>search pattern</emphasis>, the regular expression between
+the first and the second slash, and when a match is found, the
+matching part of the text is replaced with the expression between the
+middle and last part of the string. Parentheses in the search pattern
+create <emphasis>back references</emphasis>, that is the command
+remembers which part of the match matched in the parentheses; these
+strings can be reused in the replace pattern, referred to as
+<userinput>\1</userinput> for the first set of parentheses,
+<userinput>\2</userinput> for the second and so on.</para>
+
+<para>To search for a literal <literal>(</literal> or
+<literal>)</literal>, you need to <emphasis>escape</emphasis> it using
+a backslash character: <userinput>\(\)</userinput></para>
+
+<para>If you put an <userinput>i</userinput> at the end of the
+expression, the matching will be case insensitive. If you put a
+<userinput>g</userinput> at the end, all occurrences of the pattern will be
+replaced, otherwise only the first occurrence is replaced.</para>
+
+<example>
+
+<title>Replacing text in the current line</title>
+
+<para>Your friendly compiler just stopped, telling you that the class
+<classname>myClass</classname> mentioned in line 3902 in your source file
+is not defined.</para>
+
+<para>&quot;Buckle!&quot; you think, it is of course
+<classname>MyClass</classname>. You go to line 3902, and instead of trying
+to find the word in the text, you launch the Editing Command Dialog,
+enter <userinput>s/myclass/MyClass/i</userinput>, hit the
+<guibutton>OK</guibutton> button, save the file and compile &ndash;
+successfully without the error.</para>
+
+</example>
+
+<example>
+<title>Replacing text in the whole file</title>
+
+<para>Imagine that you have a file, in which you mention a <quote>Miss
+Jensen</quote> several times, when someone comes in and tells you that
+she just got married to <quote>Mr Jones</quote>. You want, of course,
+to replace each and every occurrence of <quote>Miss Jensen</quote>
+with <quote>Ms Jones</quote>.</para>
+
+<para>Enter the command line and issue the command
+<userinput>%s/Miss Jensen/Ms Jones/</userinput> and hit return, you
+are done.</para>
+
+</example>
+
+<example>
+<title>A More Advanced Example</title>
+
+<para>This example makes use of <emphasis>back references</emphasis>
+as well as a <emphasis>character class</emphasis> (if you do not know what
+that is, please refer to the related documentation mentioned
+below).</para>
+
+<para>Suppose you have the following line:
+
+<programlisting>void MyClass::DoStringOps( String &amp;foo, String &amp;bar String *p, int &amp;a, int &amp;b )</programlisting>
+</para>
+<para>Now you realize that this is not nice code, and decide that you
+want to use the <constant>const</constant> keyword for all
+<quote>address of</quote> arguments, those characterized by the &amp;
+operator in front of the argument name. You would also like to
+simplify the white space, so that there is only 1 whitespace character
+between each word.</para>
+
+<para>Launch the Editing Command Dialog, and enter:
+<userinput>s/\s+(\w+)\s+(&amp;)/ const \1 \2/g</userinput> and hit the
+<guibutton>OK</guibutton> button. The <userinput>g</userinput> at the end of the expression makes
+the regular expression recompile for each match to save the <emphasis>backreferences</emphasis>.</para>
+
+<para>Output:
+
+<computeroutput>void MyClass::DoStringOps( const String &amp;foo, const String &amp;bar String *p, const int &amp;a, const int &amp;b )</computeroutput></para>
+
+<para>Mission completed! Now, what happened? Well, we looked for some
+white space (<literal>\s+</literal>) followed by one or more
+alphabetic characters (<literal>\w+</literal>) followed by some more
+whitespace (<literal>\s+</literal>) followed by an ampersand, and in
+the process saved the alphabetic chunk and the ampersand for reuse in
+the replace operation. Then we replaced the matching part of our line
+with one whitespace followed by <quote>const</quote> followed by one
+whitespace followed by our saved alphabetical chunk
+(<literal>\1</literal>) followed by one whitespace followed by our
+saved ampersand (<literal>\2</literal>)</para>
+
+<para>Now in some cases the alphabetical chunk was
+<quote>String</quote>, in some <quote>int</quote>, so using the
+character class <literal>\w</literal> and the <literal>+</literal>
+quantifier proved a valuable asset.</para>
+
+</example>
+
+</listitem>
+
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+<sect3 id="advanced-editing-tools-commandline-commands-navigation">
+<title>Commands for navigation</title>
+
+<variablelist>
+
+<varlistentry>
+<term><cmdsynopsis><command>goto</command><arg>INT line</arg></cmdsynopsis></term>
+<listitem><para>This command navigates to the specified line.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>find</command><arg>pattern</arg></cmdsynopsis></term>
+<listitem><para>This command navigates to the first occurrence of
+<userinput>pattern</userinput> according to the configuration. Following
+occurrences can be found using
+<menuchoice><guimenu>Edit</guimenu><guimenuitem>Find Next</guimenuitem></menuchoice>
+(the default shortcut is <keycap>F3</keycap>).</para>
+<para>The find command can be configured by appending a colon followed by one or
+more options, the form is
+<userinput>find:options pattern</userinput>. The
+following options are supported:
+
+<variablelist>
+
+<varlistentry>
+<term><userinput>b</userinput></term>
+<listitem><para>Search backwards.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>c</userinput></term>
+<listitem><para>Search from cursor position.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>e</userinput></term>
+<listitem><para>Search in the selection only.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>r</userinput></term>
+<listitem><para>Do regular expression search. If set, you may use
+<userinput>\N</userinput> where N is a number to represent captures in the
+replacement string.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>s</userinput></term>
+<listitem><para>Do case sensitive search.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>w</userinput></term>
+<listitem><para>Match whole words only.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</para>
+
+</listitem>
+
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>ifind</command><arg>pattern</arg></cmdsynopsis></term>
+<listitem><para>This command provides <quote>as-you-type</quote> searching. You
+can configure the behavior of the search by appending a colon
+followed by one or more options, like this:
+<userinput>ifind:options pattern</userinput>. Allowed options are
+
+<variablelist>
+<varlistentry>
+<term><userinput>b</userinput></term>
+<listitem><para>Search backwards.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>r</userinput></term>
+<listitem><para>Do regular expression search.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>s</userinput></term>
+<listitem><para>Do case sensitive search.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput>c</userinput></term>
+<listitem><para>Search from cursor position.</para></listitem>
+</varlistentry>
+
+</variablelist>
+</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect3>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="advanced-editing-tools-code-folding">
+<title>Using Code Folding</title>
+
+<para>Code folding allows you to hide parts of a document in the editor, making
+it easier to overview large documents. In &kate; the foldable regions are
+calculated using rules defined in the syntax highlight definitions, and
+therefore it is only available in some formats - typically program source code,
+XML markup and similar. Most highlight definitions supporting code folding
+also lets you manually define foldable regions, typically using the
+<userinput>BEGIN</userinput> and <userinput>END</userinput> keywords.</para>
+
+<para>To use the code folding feature, activate the folding markers using
+<menuchoice><guimenu>View</guimenu><guimenuitem>Show Folding
+Markers</guimenuitem></menuchoice> menu item if they are not already visible.
+The Folding Markers Pane in the left side of the screen displays a graphical
+view of the foldable regions, with +/- signs to indicate the possible operation
+on a given region: a - means that the region is expanded, clicking the - will
+collapse the region and a + will be displayed instead.</para>
+
+<para>Four commands are provided to manipulate the state of folding regions,
+see the <link linkend="view-code-folding">menu documentation</link>.
+</para>
+
+<para>If you do not want to use the code folding feature, you can disable
+the <guilabel>Show folding markers (if available)</guilabel> option in the
+<link linkend="config-dialog-editor-appearance">Appearance page of the editor
+configuration</link></para>
+
+</sect1>
+
+<sect1 id="advanced-editing-tools-scripting">
+
+<title>Scripting the editor component with Javascript</title>
+
+<sect2 id="advanced-editing-tools-scripting-introduction">
+
+<title>Introduction</title>
+
+<para>Starting with version 2.5, the &kate; editor component supports
+scripting with ECMA script, also known as JavaScript.</para>
+
+<para>Scripts can be used through <link
+linkend="advanced-editing-tools-commandline">the built in command line</link>
+only. The requirements is that the script is placed in a folder where &kate;
+can find it, along with an optional .desktop file that defines the related
+properties. The valid folder are named <filename>katepart/scripts</filename>
+in the &kde; data folders. You can find the data folders by running the command
+<command>kde-config <option>--path</option> <parameter>data</parameter></command>
+You will usually have at least a system and a personal data folder. Of course
+scripts in the system data folder are available to all users on the system,
+while those in the personal folder are available for you only.</para>
+
+<note><para>This feature is experimental and will most likely change during
+future development.</para>
+<para>We know that many of you will be disappointed because you can't add
+your scripts to the menu or assign shortcuts to them. Sorry, sometime
+in the future that will likely be possible.</para>
+<para>It is also not possible to pass any arguments to your scripts yet. Be
+patient, and that may be added in the bright future ;)</para>
+</note>
+
+</sect2>
+
+<sect2 id="advanced-editing-tools-scripting-reference">
+
+<title>The Kate JavaScript API</title>
+
+<para>Here is listed the complete set of functions and properties available
+in the <type>document</type> and <type>view</type> objects.
+In addition you can of course use all the standard objects such as
+<type>Math</type>, <type>String</type> <type>Regex</type> and so forth.</para>
+
+<para>When a script is run, the <classname>document</classname> object is the
+current document, and the <classname>view</classname> object is the current
+view.</para>
+
+<note><para>The types of arguments are of course not used in JavaScript at
+this time, they are there solely to indicate what sort of value the funcitons
+expect.</para></note>
+
+<variablelist id="advanced-editing-tools-scripting-global">
+<title>Global Functions</title>
+<varlistentry>
+<term><function>debug( <parameter><replaceable>string</replaceable></parameter>)
+[function]</function></term>
+<listitem>
+<itemizedlist>
+<title>parameters</title>
+<listitem><para><parameter>string</parameter> the string to output</para>
+</listitem>
+</itemizedlist>
+<para>Outputs the string to <acronym>STDERR</acronym> using
+<function>kdDebug()</function>. A dedicated output area is used for the output,
+which will be prefixed <computeroutput>Kate (KJS Scripts):</computeroutput>
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<variablelist id="advanced-editing-tools-scripting-document">
+<title>The <classname>document</classname> API</title>
+
+<varlistentry>
+<term><function>document.attribute( <parameter><replaceable>line</replaceable>
+</parameter>, <parameter><replaceable>column</replaceable></parameter> );
+ [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>uint line</parameter> The line of the position for which
+to find the attribute.</para></listitem>
+<listitem><para><parameter>uint column</parameter> The column of the position for
+which to find the attribute.</para></listitem>
+</itemizedlist>
+<para>Returns the numeric ID of the attribute for the document position
+[<parameter>line</parameter>,<parameter>column</parameter>]. The attribute
+represents the visual appearance or style of the text, and is also used to
+calculate the syntax highlight for a specific part of the text in mixed formats
+like HTML or PHP.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.canBreakAt( <parameter>Char c</parameter>,
+<parameter>uint attribute</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>c</parameter> The character to test</para></listitem>
+<listitem><para><parameter>attribute</parameter> The attribute at the position
+of <parameter>c</parameter>.</para></listitem>
+</itemizedlist>
+<para>Returns whether it is allowed to break the line at a character c with
+attribute attribute. The result is decided by querying the highlight owning
+attribute for which characters allow breaking the line.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.canComment( <parameter>uint start_attribute</parameter>,
+<parameter>uint end_attribute</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>start_attribute</parameter> The attribute at the
+start of the range to turn into a comment.</para></listitem>
+<listitem><para><parameter>end_attribute</parameter> The attribute at end of
+the range to turn into a comment.</para></listitem>
+</itemizedlist>
+<para>Returns whether start_attribute and end_attribute belongs to the same
+syntax highlight system. If they do, it is sane.
+</para>
+<example>
+<title>using canComment</title>
+<programlisting>
+if ( document.canComment( document.attribute(1,0), document.attribute(5,0) ) ) {
+ // 1,0 and 5,0 belongs to the same syntax highlighting system
+}
+</programlisting>
+</example>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.clear(); [function]</function></term>
+<listitem><para>Clears the document.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.commentStart( <parameter>uint attribute</parameter> );
+[function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>attribute</parameter> The attribute of the text for
+which to get the commentStart string.</para></listitem>
+</itemizedlist>
+<para>Returns the string required to start a multiline comment for a text with
+attribute, or an empty string if multiline comments are not supported for that
+text.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.commentMarker( <parameter>uint attribute</parameter> );
+[function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>attribute</parameter> The attribute of the text for
+which to get the commentMarker string</para></listitem>
+</itemizedlist>
+<para>Returns the string used to mark the rest of the line as a comment for a
+text with attribute or an empty string if single line comments are not supported
+for that text.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.commentEnd( <parameter>uint attribute</parameter> );
+[function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>attribute</parameter> The attribute of the text for
+which to get the commentEnd string</para></listitem>
+</itemizedlist>
+<para>Returns the string required to end a multiline comment for a text with
+attribute, or an empty string if multiline comments are not supported for that
+text.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.editBegin(); [function]</function></term>
+<listitem>
+<para>Start an editing group. All actions done until the call of editEnd() will
+be grouped as one undo-action.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.editEnd(); [function]</function></term>
+<listitem>
+<para>Finish an editing group.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.highlightMode; [property:read only]</function></term>
+<listitem>
+<para>The name of the document's highlight mode, such as JavaScript or C++.
+If no syntax highlight mode is set for the document, the value is None. Notice
+that you need to use the English name in cases where it differs from the
+translated one.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.indentMode; [property:read only]</function></term>
+<listitem>
+<para>The name of the document indent mode, such as
+<literal>normal</literal> or <literal>cstyle</literal>.
+Remember that if no indent mode is set, the value is <literal>none</literal>.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.indentWidth; [property:read only]</function></term>
+<listitem>
+<para>The indentation width set for the document. This is used if space
+indenting is enabled.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.insertLine( <parameter>uint line</parameter>,
+<parameter>string text</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>line</parameter> document line number</para>
+</listitem>
+<listitem><para><parameter>text</parameter> text to insert</para></listitem>
+</itemizedlist>
+<para>Inserts a new line with the text <parameter>text</parameter> at the
+line <parameter>line</parameter>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.insertText( <parameter>uint line</parameter>,
+<parameter>uint column</parameter>, <parameter>string text</parameter> );
+[function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>line</parameter> the line number</para></listitem>
+<listitem><para><parameter>column</parameter> the column</para></listitem>
+<listitem><para><parameter>text</parameter> the text which is to be
+inserted</para></listitem>
+</itemizedlist>
+<para>Inserts the text <parameter>text</parameter> in line
+<parameter>line</parameter> and column <parameter>column</parameter>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>document.length(); [function]</term>
+<listitem>
+<para>Returns the document's size in bytes.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.lines(); [function]</function></term>
+<listitem>
+<para>Returns the number of lines in the document.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>document.mixedIndent; [property:read only]</term>
+<listitem>
+<para>A boolean telling whether the mixed-indent setting is enabled for the
+document. If so, indentation is optimized to contain a mix of tab characters and
+spaces like used by the Emacs editor.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>document.removeLine( <parameter>uint line</parameter> ); [function]</term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>line</parameter> line number</para></listitem>
+</itemizedlist>
+<para>Removes the document line line.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.removeText( <parameter>uint startLine</parameter>,
+<parameter>uint startColumn</parameter>, <parameter>uint endLine</parameter>,
+<parameter>uint endColumn</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>startLine</parameter> specifies the beginning
+line</para></listitem>
+<listitem><para><parameter>startColumn</parameter> specifies the beginning
+column</para></listitem>
+<listitem><para><parameter>endLine</parameter> specifies the ending
+line</para></listitem>
+<listitem><para><parameter>endColumn</parameter> specifies the ending
+column</para></listitem>
+</itemizedlist>
+<para>Removes the text range from line <parameter>startLine</parameter> and
+column <parameter>startColumn</parameter> up to line
+<parameter>endLine</parameter> and column <parameter>endColumn</parameter>.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.setText( <parameter>string text</parameter> );
+[function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>text</parameter> document text</para></listitem>
+</itemizedlist>
+<para>Sets the entire document content to <parameter>text</parameter>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.spaceIndent; [property:read only]</function></term>
+<listitem>
+<para>A boolean telling whether space-indent is enabled for the document.
+If so, the document is indented with indentWidth spaces pr level, otherwise
+indentation is one tab character pr. level.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.textFull(); [function]</function></term>
+<listitem>
+<para>Returns the full document text. If the text spans over multiple lines the
+linefeed character is <constant>\n</constant>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.textLine( uint line ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>line</parameter> the line</para></listitem>
+</itemizedlist>
+<para>Returns the text of line <parameter>line</parameter>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>document.textRange( <parameter>uint startLine</parameter>,
+<parameter>uint startColumn</parameter>, <parameter>uint endLine</parameter>,
+<parameter>uint endColumn</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>startLine</parameter> specifies the beginning
+line</para></listitem>
+<listitem><para><parameter>startColumn</parameter> specifies the beginning
+column</para></listitem>
+<listitem><para><parameter>endLine</parameter> specifies the ending line</para>
+</listitem>
+<listitem><para><parameter>endColumn</parameter> specifies the ending
+column</para></listitem>
+</itemizedlist>
+<para>Returns the specified text range. If the range spans over multiple lines
+the linefeed character is <constant>\n</constant>.</para>
+</listitem>
+</varlistentry>
+
+</variablelist><!--/ document API -->
+
+<variablelist id="advanced-editing-tools-scripting-view">
+<title>The <classname>view</classname> API</title>
+
+<varlistentry>
+<term><function>view.clearSelection(); [function]</function></term>
+<listitem>
+<para>Deselects all text.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.cursorColumn(); [function]</function></term>
+<listitem>
+<para>Returns the current cursor column (TAB characters are expanded).</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.cursorColumnReal(); [function]</function></term>
+<listitem>
+<para>Returns the current real cursor column (TAB characters counts one).</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.cursorLine(); [function]</function></term>
+<listitem>
+<para>Returns the current cursor line.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.hasSelection(); [function]</function></term>
+<listitem>
+<para>Returns <constant>true</constant> if the view contains selected text,
+otherwise <constant>false</constant>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.removeSelectedText(); [function]</function></term>
+<listitem>
+<para>Removes the selected text, if the view has a selection.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.selectAll(); [function]</function></term>
+<listitem>
+<para>Selects all text.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.selection(); [function]</function></term>
+<listitem>
+<para>Returns the selected text. If the selection spans over multiple lines the
+linefeed character is <constant>\n</constant>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.selectionEndColumn; [property:read only]</function></term>
+<listitem>
+<para>Returns the ending column of the selection.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.selectionEndLine; [property:read only]</function></term>
+<listitem>
+<para>Returns the ending line of the selection.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.selectionStartColumn; [property:read only]</function></term>
+<listitem>
+<para>Returns the starting column of the selection.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.selectionStartLine; [property:read only]</function></term>
+<listitem>
+<para>Returns the starting line of the selection.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.setCursorPosition( <parameter>uint line</parameter>,
+<parameter>uint column</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>line</parameter> Specifies the line for the
+cursor.</para></listitem>
+<listitem><para><parameter>column</parameter> Specifies the column for the
+cursor.</para></listitem>
+</itemizedlist>
+<para>Sets the input cursor position in the view to [<parameter>line</parameter>,
+<parameter>col</parameter>]. This sets the cursor position by visual means,
+that is the a TAB character counts up to <replaceable>tabwidth</replaceable>
+depending on the position inside the line. The cursor position is made visible.
+Both line and column are zero-based.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.setCursorPositionReal( <parameter>uint line</parameter>,
+<parameter>uint column</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>line</parameter> Specifies the line for the
+cursor.</para></listitem>
+<listitem><para><parameter>column</parameter> Specifies the column for the
+cursor.</para></listitem>
+</itemizedlist>
+<para>Sets the input cursor position to [<parameter>line</parameter>,
+<parameter>col</parameter>]. This sets the string position, that is a TAB
+character counts for 1. The cursor position is made visible. Both line and
+column are zero-based.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><function>view.setSelection( <parameter>uint startLine</parameter>,
+<parameter>uint startColumn</parameter>, <parameter>uint endLine</parameter>,
+<parameter>uint endColumn</parameter> ); [function]</function></term>
+<listitem>
+<itemizedlist>
+<title>Parameters</title>
+<listitem><para><parameter>startLine</parameter> specifies the beginning line</para></listitem>
+<listitem><para><parameter>startColumn</parameter> specifies the beginning column</para></listitem>
+<listitem><para><parameter>endLine</parameter> specifies the ending line</para></listitem>
+<listitem><para><parameter>endColumn</parameter> specifies the ending column</para></listitem>
+</itemizedlist>
+<para>Sets a selection from line <parameter>startLine</parameter> and column
+<parameter>startColumn</parameter> up to line <parameter>endLine</parameter>
+and column <parameter>endColumn</parameter>.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+<example id="advanced-editing-tools-scripting-example">
+
+<title>A sample script</title>
+<para>As an example we will create a small script that uppercases the selection.
+It is obvious that we first need to check whether a selection exists, if so we
+get the text, change the case and then replace it with the new one. An
+implementation could look like this:</para>
+
+<programlisting>
+if ( view.hasSelection() )
+{
+ // uppercase selection
+ column = view.selectionStartColumn;
+ line = view.selectionStartLine;
+
+ selection = view.selection().toUpperCase();
+
+ document.editBegin();
+ view.removeSelectedText();
+ document.insertText( line, column, selection );
+ document.editEnd();
+}
+</programlisting>
+
+<para>To group this action together so that they will be reverted by a single
+activation of <guimenuitem>Undo</guimenuitem> we encapsulate the lines
+<programlisting>view.removeSelectedText()</programlisting> and
+<programlisting>document.insertText()</programlisting> with a
+<programlisting>document.editBegin()</programlisting> and
+<programlisting>document.editEnd()</programlisting>.</para>
+
+</example>
+
+<example id="advanced-editing-tools-desktop-example">
+<title>A sample <filename>.desktop</filename> file</title>
+
+<para>Here is a sample .desktop file that accompanies the above script.</para>
+
+<programlisting>
+# Example of a .desktop file
+[Desktop Entry]
+Encoding=UTF-8
+Name=Kate Part JavaScript Uppercase
+Comment=Script to uppercase the selection
+X-Kate-Command=uppercase-selection
+X-Kate-Help=&lt;p&gt;Usage: &lt;code&gt;uppercase-selection&lt;/code&gt;&lt;/p&gt;
+</programlisting>
+
+<para>As you can see you can define the Encoding, set a Name, a Comment, a help
+text using X-Kate-Help and the command line name via X-Kate-Command. The entries
+Name, Comment and X-Kate-Help are automatically translated into other languages
+by the KDE translation teams, if the files are in KDE's SVN repository.</para>
+
+</example>
+
+<sect3>
+<title>Putting it togeather</title>
+
+<para>&kate; will search the script folders (see <link
+linkend="advanced-editing-tools-scripting-introduction">above</link>) for
+<filename>*.js</filename> files. For every file it checks whether there is a
+corresponding <filename>.desktop</filename> file, like for uppercase.js it
+would look for uppercase.desktop. </para>
+<para>If a <filename>.desktop</filename> file can not be found the script will
+be registered in katepart's command line with the filename without the ending
+.js, so in our example this would be <literal>uppercase</literal>. If the
+command-name is fine and you don't need the extra features a
+<filename>.desktop</filename> file provides you do not need a
+<filename>.desktop</filename> file at all. </para>
+<para>If a <filename>.desktop</filename> file exists katepart will read the name
+under which the script will be registered from the .desktop-entry
+X-Kate-Command, for example X-Kate-Command=uppercase-selection.</para>
+
+</sect3>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/doc/kate/configdialog01.png b/doc/kate/configdialog01.png
new file mode 100644
index 00000000..75106679
--- /dev/null
+++ b/doc/kate/configdialog01.png
Binary files differ
diff --git a/doc/kate/configdialog02.png b/doc/kate/configdialog02.png
new file mode 100644
index 00000000..70a7ecae
--- /dev/null
+++ b/doc/kate/configdialog02.png
Binary files differ
diff --git a/doc/kate/configuring.docbook b/doc/kate/configuring.docbook
new file mode 100644
index 00000000..14642c74
--- /dev/null
+++ b/doc/kate/configuring.docbook
@@ -0,0 +1,1595 @@
+<chapter id="configuring-kate">
+<chapterinfo>
+<authorgroup>
+<author>&Anders.Lund; &Anders.Lund.mail;</author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</chapterinfo>
+<title>Configuring &kate;</title>
+
+<sect1 id="configuring-overview">
+<title>Overview</title>
+<para>
+<indexterm>
+<primary>configure</primary>
+<secondary>settings</secondary>
+<tertiary>preferences</tertiary></indexterm>
+<anchor id="find"/>
+<anchor id="find-again"/>
+<!-- <anchor id="print"/> -->
+<anchor id="replace"/>
+<!-- <anchor id="save"/> -->
+<anchor id="undo"/>
+<anchor id="redo"/>
+&kate; offers several means of tweaking the application to behave as desired.
+The most important ones are:
+</para>
+
+<variablelist>
+<varlistentry>
+<term id="configure">The Configuration Dialog</term>
+<listitem><para>The main configuration tool, allowing you to configure the &kate; application,
+the editor component and the usage of plugins.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term id="settings">The <guimenu>Settings</guimenu> Menu</term>
+<listitem><para>Allows you to change often used settings, and to
+launch the configuration dialogs.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>The <guimenu>View</guimenu> Menu</term>
+<listitem><para>Allows you to split the current frame, as well as to
+display the icons and line numbers pane for the currently edited
+document.</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>The embedded &konsole; is using the configuration defined in the
+&kcontrolcenter;, and may be configured by clicking the
+<mousebutton>right</mousebutton> mouse button and choosing from the
+<guimenuitem>Settings</guimenuitem> sub menu.</para>
+
+</sect1>
+
+<sect1 id="configuring-kate-configdialog">
+<title>The Main Configuration Dialog</title>
+
+<mediaobject>
+<imageobject>
+<imagedata format="PNG" fileref="configdialog01.png"/>
+</imageobject>
+</mediaobject>
+
+<para>The &kate; configuration dialog displays a tree of topics on the
+left, and a configuration page corresponding to the selected topic on
+the right.</para>
+
+<para>The configuration is divided into two groups, namely
+<itemizedlist>
+<listitem><para><link linkend="config-dialog">Application configuration</link>
+</para></listitem>
+<listitem><para><link linkend="config-dialog-editor">Editor component configuration</link></para></listitem>
+
+</itemizedlist>
+
+</para>
+
+</sect1>
+
+<sect1 id="config-dialog">
+<title>The &kate; Application Configuration</title>
+<para>This group contains pages to configure the main &kate; application</para>
+
+<sect2 id="config-dialog-general">
+<title>The General Page</title>
+<para>This section contains a few global options for &kate;</para>
+
+<variablelist>
+
+<varlistentry>
+<term><anchor id="config-dialog-general-show-full-path" />
+<guilabel>Show Full Path in Title</guilabel></term>
+<listitem><para>When enabled, Kate will display the full URL of your
+current document in the window title, rather than just the file name.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="config-general-behavior"/>
+<guilabel>Behavior</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term>
+<anchor id="config-dialog-general-sync-konsole"/>
+<guibutton>Sync Konsole with Active Document</guibutton></term>
+<listitem><para>This will cause the built-in &konsole; to
+<command>cd</command> into the directory of the active document when
+launched and when a new document gets the focus. If not enabled, you
+have to do all your navigation in the &konsole; on your own.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="config-dialog-general-warn-mod"/>
+<guilabel>Warn about files modified by foreign processes</guilabel></term>
+<listitem><para>When enabled, &kate; will notify you about files modified
+from outside the application whenever the main window receives input focus.
+You will be able to deal with several modified files at once, you
+can reload, save or discard changed files in groups.</para>
+<para>If not enabled, &kate; will prompt you for action when a externally
+modified file receives focus within the application.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</listitem>
+</varlistentry><!-- /behavior group -->
+
+<varlistentry>
+<term><anchor id="config-general-meta-data"/>
+<guilabel>Meta Data</guilabel></term>
+<listitem>
+
+<variablelist>
+<varlistentry>
+<term><anchor id="config-general-keep-meta-information"/>
+<guilabel>Keep meta-information past sessions</guilabel></term>
+<listitem><para>When enabled, &kate; will store meta data such as bookmarks
+and session configuration even when you close your documents. The data
+will be used if the document is unchanged when reopened.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="config-general-delete-meta-information-after"/>
+<guilabel>Delete unused meta information after</guilabel></term>
+<listitem><para>Set the maximum number of days to keep meta information
+for unopen files. This helps keeping the database of meta information
+reasonably sized.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</listitem>
+</varlistentry><!-- /meta data group -->
+
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-sessions">
+<title>The Sessions Page</title>
+
+<para>This section contains options related to <link
+linkend="fundamentals-using-sessions">using sessions</link>.</para>
+
+<variablelist>
+
+<varlistentry>
+<term><anchor id="config-dialog-sessions-elements"/>
+<guilabel>Elements of Sessions</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Include window configuration</guilabel></term>
+<listitem><para>If enabled, &kate; will save the window configuration
+with each session.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry><!-- /elements of sessions -->
+
+<varlistentry>
+<term><anchor id="config-dialog-sessions-startup-behavior"/>
+<guilabel>Behavior on Application Startup</guilabel></term>
+<listitem>
+<para>Select how you want &kate; to behave at startup. This setting can be
+overridden by specifying what to do on the <link
+linkend="command-line-options">command line</link>.</para>
+<variablelist>
+<varlistentry>
+<term><guilabel>Start new session</guilabel></term>
+<listitem><para>With this option, &kate; will start a new, unnamed session
+when you start it.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Load last used session</guilabel></term>
+<listitem><para>&kate; will use the most recently opened session at
+startup. This is good if you want to use the same session always or switch
+rarely.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Manually choose a session</guilabel></term>
+<listitem><para>&kate; will display a small dialog that lets you choose
+your preferred session. This is the default behavior. Nice if you use a lot of
+different sessions frequently.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry><!-- /startup behavior -->
+
+<varlistentry>
+<term><anchor id="config-dialog-sessions-exit-behavior"/>
+<guilabel>Behavior on Application Exit or Session Switch</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Do not save session</guilabel></term>
+<listitem><para>The changes to the session data (open files and if enabled,
+window configuration) will not be saved. You will of course be prompted if you
+have unsaved files. With this option, your can configure your sessions once, and
+not worry about closing extra files that you opened and do not want to see
+next time you use the session.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Save Session</guilabel></term>
+<listitem><para>&kate; will save session data, except if the session is unnamed.
+With this option, your sessions are allways restored just like you left them.
+This is the default behavior.
+</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Ask user</guilabel></term>
+<listitem><para>You will be asked if you want to save the session every time a
+named session is closed.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry><!-- /exit/switch behavior -->
+
+</variablelist>
+
+</sect2>
+
+<sect2 id="config-dialog-fileselector">
+<title>The <guilabel>Filesystem Browser</guilabel> Page</title>
+
+<variablelist>
+<varlistentry>
+<term><guilabel>Toolbar</guilabel></term>
+<listitem><para>Configure the buttons on the file system browser toolbar
+by moving the ones you want enabled to the <guilabel>Selected Actions</guilabel>
+list, and order them using the arrow buttons at the side of the list.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Auto Synchronization</guilabel></term>
+<listitem><para>You can have the filesystem browser automatically navigate to
+the directory containing the current document on certain events:
+<itemizedlist>
+<listitem><para>When a new document becomes the active one.</para></listitem>
+<listitem><para>When the filesystem browser becomes visible.</para></listitem>
+</itemizedlist>
+Even if you select not to use this feature, you can manually synchronize the
+browser with the current document by pressing the
+<guilabel>Synchronize</guilabel> toolbar button.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Remember locations</guilabel></term>
+<listitem><para>Select how long a browsing history you want. The browser does
+only remember individual locations, duplicates are removed.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Remember filters</guilabel></term>
+<listitem><para>Select how many filters you want remembered. Only individually
+distinct filters are remembered, duplicates are removed.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Session</guilabel></term>
+<listitem>
+<para>Configure wether the file system browser should remember its location and
+filter over sessions.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect2>
+
+<sect2 id="config-dialog-documentlist">
+<title>The <guilabel>Doucment List</guilabel> Page</title>
+
+<variablelist>
+<varlistentry>
+<term><guilabel>Backgound Shading</guilabel></term>
+<listitem><para>This section allows you to enable or disable the background
+shading visualization of your recent activity, and chose which colors to use if
+enabled. See the section about <link
+linkend="kate-mdi-tools-file-list">The Document List</link> for more about
+this feature.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Sort By</guilabel></term>
+<listitem><para>Set how you want the document list sorted. This can be set
+from the &RMB; menu in the document list as well.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
+<sect2 id="config-dialog-plugins">
+<title>The <guilabel>Plugins</guilabel> Page</title>
+
+<para>This page provides a list of installed plugins for the &kate;
+application. Each plug-in is represented with its name and a short description.
+You can check the checkbox with an item to enable the plug-in it represents.
+</para>
+
+<para>If a plug-in provides configuration options, a section to access those
+will appear as a child of this page.</para>
+
+</sect2>
+
+
+<sect2 id="config-dialog-externaltools">
+<title>External Tools</title>
+
+<para>In the <guimenu>Tools</guimenu> menu you will find a submenu labeled
+<guisubmenu>External Tools</guisubmenu>. These tools invokes external
+applications with data related to the current document, for example its URL,
+directory, text or selection. This page allows you to manage the menu and edit,
+remove or add new tools.</para>
+
+<para>Each external tool is a shell command which contains macros representing
+the document data. When activated, the macros are substituted with data from the
+active document.</para>
+
+<variablelist>
+<title>External Tools Properties</title>
+<varlistentry>
+<term>Label</term>
+<listitem><para>A friendly label for the External Tools menu.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Script</term>
+<listitem><para>The script to execute when the tool is activated. Before passing
+the script to the shell, the following macros are substituted:
+
+<variablelist>
+<varlistentry>
+<term>%URL</term>
+<listitem><para>The full URL of the current document, or an empty string if the
+document is unsaved.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%URLS</term>
+<listitem><para>A space seperated list of the URLs of all open documents
+(except unsaved ones).</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%directory</term>
+<listitem><para>The directory part of the current documents URL or an empty
+string if the current document is unsaved.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%filename</term>
+<listitem><para>the filename of the current document without the path, or an
+empty string if the current document is unsaved.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%line</term>
+<listitem><para>The line number of the insertion cursor is in the current
+document.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%column</term>
+<listitem><para>The column number of the insertion cursor in the current
+document.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%selection</term>
+<listitem><para>The selected text in the current document, or an empty string
+if no text is selected</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>%text</term>
+<listitem><para>The full text of the current document. Beware that this will
+potentially exceed the maximum command length allowed on your system.
+Use with care.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Executable</term>
+<listitem><para>The main executable is the script. This is mandatory, and is used
+to test if the command can be run at all. A fully qualified path is allowed
+in case the executable is not in your <envar>PATH</envar> variable.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Mimetypes</term>
+<listitem><para>A semicolon separated list of mimetypes for which this command
+should be enabled. This is currently unused.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Save</term>
+<listitem><para>You can optionally select to have the current or all documents
+saved prior to executing the script. This is handy if your script reads the file
+from disk.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Command Line Name</term>
+<listitem><para>If you fill this, the tool will be available in the
+<link linkend="advanced-editing-tools-commandline">editors command line</link> as
+<command>exttool-<replaceable>Command Line Name</replaceable></command>
+(the string you enter here prepended <quote>exttool-</quote>).</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="config-dialog-editor">
+<title>The Editor Component Configuration</title>
+<para>This group contains all pages related to the editor component of
+&kate;. Most of the settings here are defaults, they can be overridden by
+<link linkend="config-dialog-editor-filetypes">defining a filetype</link>,
+by <link linkend="config-variables">Document Variables</link> or by changing
+them pr. document during an editing session.</para>
+
+
+<sect2 id="config-dialog-editor-appearance">
+<title>Appearance</title>
+
+<variablelist>
+<varlistentry>
+<term><guilabel>Word Wrap</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry id="appearance-settings">
+<term><guilabel>Dynamic word wrap</guilabel></term>
+<listitem><para>If this option is checked, the text lines
+will be wrapped at the view border on the screen.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Dynamic word wrap indicators</guilabel></term>
+<listitem><para>Choose when the Dynamic word wrap indicators
+should be displayed.
+</para></listitem></varlistentry>
+<varlistentry>
+<term><guilabel>Vertically align dynamically wrapped lines
+to indentation depth:
+</guilabel></term>
+<listitem><para>Enables the start of dynamically wrapped
+lines to be aligned vertically to the indentation level of the first
+line. This can help to make code and markup more
+readable.</para><para>Additionally, this allows you to
+set a maximum width of the screen, as a percentage,
+after which dynamically wrapped lines will no longer be vertically aligned.
+For example, at 50%, lines whose indentation levels are deeper than 50% of the
+width of the screen will not have vertical alignment applied to subsequent
+wrapped lines.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Code Folding</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Show folding markers (if available)
+</guilabel></term>
+<listitem><para>If this option is checked, the current view will display marks
+for code folding, if code folding is available.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Borders</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Show icon border
+</guilabel></term>
+<listitem><para>If this is checked, you will see an icon border on the left
+hand side. The icon border shows bookmark signs for instance.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Show line numbers
+</guilabel></term>
+<listitem><para>If this is checked, you will see line numbers on the left
+hand side.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Show scrollbar marks
+</guilabel></term>
+<listitem><para>If this option is checked the current view
+will show marks on the vertical scrollbar. These marks will
+for instance show bookmarks.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Sort Bookmarks Menu
+</guilabel></term>
+<listitem><para>
+<variablelist>
+<varlistentry>
+<term><guilabel>By position
+</guilabel></term>
+<listitem><para>The bookmarks will be ordered by the line
+numbers they are placed at.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>By creation
+</guilabel></term>
+<listitem><para>Each new bookmark will be added to the bottom,
+independently from where it is placed in the document.</para></listitem>
+</varlistentry>
+</variablelist>
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Show identation lines
+</guilabel></term>
+<listitem><para>If this is checked, the editor wil display
+vertical lines to help identifying indent lines.</para></listitem>
+</varlistentry>
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-colors">
+<title>Fonts &amp; Colors</title>
+
+<para>This section of the dialog lets you configure all fonts and colors in
+any color scheme you have, as well creating new schemes or deleting existing
+ones. Each scheme has settings for colors, fonts and normal and highlight text
+styles.
+</para>
+
+<para>&kate; will preselect the currently active scheme for you, if you want to
+work on a different scheme start by selecting that from the
+<guilabel>Schema</guilabel> combobox.</para>
+
+<sect3 id="config-dialog-editor-colors-colors">
+<title>Colors</title>
+
+<variablelist>
+<varlistentry id="config-dialog-editor-colors-colors-text-background">
+<term><guilabel>Text Area Background</guilabel></term>
+<listitem>
+
+<variablelist>
+
+<varlistentry id="config-dialog-editor-colors-normal-text">
+<term><guilabel>Normal text</guilabel></term>
+<listitem><para>This is the default background for the editor area, it will be
+the dominant color on the editor area.</para></listitem>
+</varlistentry>
+
+<varlistentry id="config-dialog-editor-colors-selected-text">
+<term><guilabel>Selected Text</guilabel></term>
+<listitem><para>This is the background for selected text. The default is
+the global selection color, as set in your &kde; color preferences.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="config-dialog-editor-colors-current-line">
+<term><guilabel>Current Line</guilabel></term>
+<listitem><para>Set the color for the current line. Setting this a bit different
+from the Normal text background helps to keep focus on the current line.
+</para></listitem>
+</varlistentry>
+
+<varlistentry id="config-dialog-editor-colors-marks">
+<term><guilabel>Bookmark</guilabel></term>
+<listitem><para>This combo lets you set overlay colors for various mark types.
+The color is mixed into the background color of a marked line, so that a line
+with more marks or a marked line that is current has a background that is a mix
+of more colors. The mark colors are also used if you enable display of scrollbar
+marks.</para></listitem>
+</varlistentry>
+
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry id="config-dialog-editor-colors-colors-other-elements">
+<term><guilabel>Other Elements</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Left Border Background</guilabel></term>
+<listitem><para>This color is used for the marks, line numbers and folding
+marker borders in the left side of the editor view when they are displayed.
+</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Line Numbers</guilabel></term>
+<listitem><para>This color is used to draw the line numbers on the left side of
+the view when displayed.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Bracket Highlight</guilabel></term>
+<listitem><para>This color is used to draw the background of matching brackets.
+</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Word Wrap Markers</guilabel></term>
+<listitem><para>This color is used to draw a pattern to the left of dynamically
+wrapped lines when those are aligned vertically, as well as for the static word
+wrap marker.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Tab Markers</guilabel></term>
+<listitem><para>This color is used to draw white space indicators when enabled.
+</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect3>
+
+<sect3 id="config-dialog-editor-colors-fonts">
+<title>Fonts</title>
+<para>
+Here you can choose the font for the schema. You can choose from
+any font available on your system, and set a default size. A sample text
+displays at the bottom of the dialog, so you can see the effect of your choices.
+</para>
+</sect3>
+
+<sect3 id="config-dialog-editor-colors-normal-text-styles">
+<title>Normal Text Styles</title>
+<para>The normal text styles are inherited by the highlight text styles,
+allowing the editor to present text in a very consistent way, for example comment
+text is using the same style in allmost all of the text formats that kate can
+highlight.</para>
+<para>The name in the list of styles is using the style configured for
+the item, providing you with an immediate preview when configuring a style.
+</para>
+<para>Each style lets you select common attributes as well as foreground
+and background colors. To unset a background color, rightclick to use the
+context menu.</para>
+</sect3>
+
+<sect3 id="config-dialog-editor-colors-highlighting-text-styles">
+<title>Highlighting Text Styles</title>
+<para>Here you can edit the text styles used by a specific highlight definition.
+The editor preselects the highlight used by your current document. To work on a
+different highlight, select one in the <guilabel>Highlight</guilabel> combobox
+above the style list.
+</para>
+<para>The name in the list of styles is using the style configured for
+the item, providing you with an immediate preview when configuring a style.
+</para>
+<para>Each style lets you select common attributes as well as foreground
+and background colors. To unset a background color, rightclick to use the
+context menu. In addition you can see if a style is equal to the default style
+used for the item, and set it to that if not.</para>
+<para>You will notice that many highlights contain other highlights represented
+by groups in the style list. For example most highlights import the Alert
+highlight, and many source code formats imports the Doxygen highlight. Editing
+colors in those groups only affects the styles when used in the edited highlight
+format.
+</para>
+</sect3>
+
+</sect2>
+
+<sect2 id="config-dialog-editor-cursor-selection">
+<title>Cursor &amp; Selection</title>
+
+<variablelist>
+
+<varlistentry>
+<term><guilabel>Text Cursor Movement</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Smart home</guilabel></term>
+<listitem>
+<para>When selected, pressing the home key will cause the cursor to
+skip white space and go to the start of a line's text.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Wrap cursor</guilabel></term>
+<listitem>
+<para>When on, moving the insertion cursor using the <emphasis
+role="bold">Left</emphasis> and <emphasis role="bold">Right</emphasis> keys will
+go on to previous/next line at beginning/end of the line, similar to most
+editors.</para><para>When off, the insertion cursor cannot be moved left of the
+line start, but it can be moved off the line end, which can be very handy for
+programmers. When this option is chosen, moving the cursor with the arrow keys
+off the end of a line (to the right) causes it to jump down to the beginning of
+the next line. Likewise when the cursor is moved past the beginning of a line
+(to the left) it jumps up to the end of the preceding line. When this option is
+not selected, moving the cursor right past the end of a line merely causes it to
+continue horizontally in the same line and trying to move it left past the
+beginning does nothing.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Page Up/Page Down moves cursor</guilabel></term>
+<listitem>
+<para>This option changes the behavior of the cursor when the user presses
+the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> key. If unselected
+the text cursor will maintain its relative position within the visible text in
+&kate; as new text becomes visible as a result of the operation. So if the
+cursor is in the middle of the visible text when the operation occurs it will
+remain there (except when one reaches the beginning or end.) With this option
+selected, the first key press will cause the cursor to move to either the top or
+bottom of the visible text as a new page of text is displayed.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Autocenter cursor (lines):</guilabel></term>
+<listitem>
+<para>Sets the number of lines to maintain visible above and below the cursor
+when possible.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Selection Mode</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Normal</guilabel></term>
+<listitem>
+<para>Selections will be overwritten by typed text and will be lost on
+cursor movement.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Persistent</guilabel></term>
+<listitem>
+<para>Selections will stay even after cursor movement and typing.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-edit">
+<title>Editing</title>
+<variablelist>
+
+<varlistentry>
+<term><guilabel>Tabulators</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Insert spaces instead of tabulators</guilabel></term>
+<listitem>
+<para>When this is enabled the editor will insert a calculated number of spaces
+according to the position in the text and the <option>tab-width</option> setting
+when you press the <keycap>TAB</keycap> key.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Show tabulators</guilabel></term>
+<listitem>
+<para>When this is enabled &kate; will display a small dot as a visual
+representation of tabulator characters.</para>
+<note><para>This also causes dots to be drawn to indicate trailing white space.
+This will be fixed in a future version of &kate;</para></note>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term id="config-dialog-editor-tab-width">Tab Width</term> <listitem><para>If the
+<link linkend="config-dialog-editor-word-wrap"><guilabel>Replace Tabs By
+Spaces</guilabel></link>
+option is selected this entry determines the number of
+spaces with which the editor will automatically replace
+tabs.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term id="config-dialog-editor-word-wrap"><guilabel>Static Word Wrap</guilabel></term>
+<listitem><para>
+Word wrap is a feature that causes the editor to automatically start a new line
+of text and move (wrap) the cursor to the beginning of that new line. &kate;
+will automatically start a new line of text when the current line reaches the
+length specified by the <link linkend="config-dialog-editor-wrap-words-at">Wrap Words
+At:</link> option.</para>
+<variablelist>
+<varlistentry>
+<term><guilabel>Enable static word wrap</guilabel></term>
+<listitem>
+<para>Turns static word wrap on or off.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Show static word wrap markers
+(if applicable)</guilabel></term>
+<listitem>
+<para>If this option is checked, a vertical line will be drawn at the word wrap
+column as defined in the <menuchoice> <guimenu>Settings</guimenu>
+<guimenuitem>Configure Editor...</guimenuitem></menuchoice> in the Editing tab.
+Please note that the word wrap marker is only drawn if you use a fixed pitch
+font.</para>
+</listitem>
+</varlistentry>
+<varlistentry id="config-dialog-editor-wrap-words-at">
+<term><guilabel>Wrap words at:</guilabel></term>
+<listitem>
+<para>If the <link linkend="config-dialog-editor-word-wrap">Word Wrap</link> option is selected
+this entry determines the length (in characters) at which the editor will
+automatically start a new line.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Remove Trailing Spaces</guilabel></term>
+<listitem><para>&kate; will automatically eliminate extra spaces
+at the ends of lines of text.</para></listitem> </varlistentry>
+
+<varlistentry>
+<term><guilabel>Auto Brackets</guilabel></term> <listitem><para>When
+the user types a left bracket ([, (, or {) &kate; automatically enters the
+right bracket (}, ), or ]) to the right of the cursor.</para></listitem>
+</varlistentry>
+
+<varlistentry> <term>Maximum <link linkend="undo">undo</link> steps:</term>
+<listitem><para>Here the user may specify the number of steps &kate; will
+retain in memory for purposes of undoing entries and actions. This means that
+the higher the number of steps set the more memory &kate; will use for this.
+Setting this entry to 10 would mean that the user would be be able reverse the
+last ten operations, <abbrev>i.e.</abbrev> click the <guibutton>undo</guibutton>
+button 10 times and obtain results.</para></listitem> </varlistentry>
+
+<varlistentry> <term>Smart search text from:</term>
+<listitem><para>This determines where &kate; will get the search
+text from (this will be automatically entered into the Find Text
+dialog):
+<itemizedlist>
+<listitem><para><emphasis role="bold">Nowhere:</emphasis> Don't guess the search
+text.</para></listitem>
+<listitem><para><emphasis role="bold">Selection Only:</emphasis> Use
+ the current text selection, if available. </para></listitem>
+<listitem><para><emphasis role="bold">Selection, then Current Word:</emphasis>
+Use the current selection if available, otherwise use the current word.
+</para></listitem>
+<listitem><para><emphasis role="bold">Current Word
+Only:</emphasis> Use the word that the cursor is currently resting on, if
+available. </para></listitem>
+<listitem><para><emphasis role="bold">Current Word, then Selection:</emphasis>
+Use the current word if available, otherwise use the current selection.
+</para></listitem>
+</itemizedlist>
+Note that, in all the above modes, if a
+search string has not been or cannot be determined, then the Find Text Dialog
+will fall back to the last search text.
+</para></listitem>
+</varlistentry>
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-indent">
+<title>Indentation</title>
+<variablelist>
+<varlistentry>
+<term><guilabel>Automatic indentation</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Indentation mode:</guilabel></term>
+<listitem>
+<para>Select the automatic indentation mode you want to use as default. It is
+strongly recommended to use <userinput>None</userinput> or
+<userinput>Normal</userinput>here, and use filetype configurations to set other
+indentation modes for text formats like C/C++ code or &XML;.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Insert leading Doxygen "*" when typing</guilabel></term>
+<listitem>
+<para>Automatically insert a leading "*" while typing within a doxygen
+style comment. This setting is only enabled when applicable.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Indentation with Spaces</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Use spaces instead of tabs to indent</guilabel></term>
+<listitem>
+<para>This replaces tabs with the number of spaces set in <guilabel>Number of
+spaces:</guilabel> below.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Emacs style mixed mode</guilabel></term>
+<listitem>
+<para>Use a mix of tabs and space characters for indentation.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Number of spaces:</guilabel></term>
+<listitem>
+<para>Set the number of spaces you want to use for indentation when you
+check <guilabel>Use spaces instead of tabs to indent</guilabel>
+above.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Keep Indent Profile</guilabel></term>
+<listitem><para>When this is enabled, the editor will not unindent lines in a
+selection further when the line with the least indentation becomes unindented.
+If you sometimes unindent blocks of indented code, this may be helpful.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Keep Extra Spaces</guilabel></term>
+<listitem><para>Indentations of more than the selected number of spaces
+will not be shortened.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Keys to use</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Tab key indents</guilabel></term>
+<listitem>
+<para>This allows the <keycombo
+action="simul"><keycap>tab</keycap></keycombo> key to be used to indent.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Backspace key indent</guilabel></term>
+<listitem>
+<para>This allows the <keycombo
+action="simul"><keycap>backspace</keycap></keycombo> key to be used to
+indent.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Tab Key Mode if Nothing Selected</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Insert indent characters</guilabel></term>
+<listitem>
+<para>This allows the <keycombo
+action="simul"><keycap>Tab</keycap></keycombo> key insert indent
+characters.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Insert tab character</guilabel></term>
+<listitem>
+<para>This allows the <keycombo
+action="simul"><keycap>Tab</keycap></keycombo> key insert a tab.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Indent current line</guilabel></term>
+<listitem>
+<para>This allows the <keycombo
+action="simul"><keycap>Tab</keycap></keycombo> key indent the current
+line.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-open-save">
+<title>Open &amp; Save</title>
+
+<variablelist>
+
+<varlistentry>
+<term><guilabel>File Format</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Encoding:</guilabel></term>
+<listitem>
+<para>This sets the default character encoding for your files.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>End of line:</guilabel></term>
+<listitem>
+<para>Choose your prefered end of line mode for your active
+document. You have the choice between &UNIX;, DOS/&Windows; or Macintosh.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Automatic end of line detection</guilabel></term>
+<listitem>
+<para>Check this if you want the editor to autodetect the end of line
+type. The first found end of line type will be used for the whole file.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Memory Usage</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Maximum loaded blocks per file:</guilabel></term>
+<listitem>
+<para>The editor will load given number of blocks (of around 2048 lines) of
+text into memory; if the filesize is bigger than this the other blocks
+are swapped to disk and loaded transparently as-needed.</para>
+<para>This can cause little delays while navigating in the document; a
+larger block count increases the editing speed at the cost of memory.
+</para><para>For normal usage, just choose the highest possible block count:
+limit it only if you have problems with the memory usage.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Automatic Cleanups on Load/Save</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Remove trailing spaces</guilabel></term>
+<listitem>
+<para>The editor will automatically eliminate extra spaces at the ends of lines
+of text while loading/saving the file.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Folder Config File</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>Search depth for config file:</guilabel></term>
+<listitem>
+<para>The editor will search the given number of folder levels upwards
+for &kate; config file and load the settings line from it.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Backup on Save</guilabel></term>
+<listitem><para>Backing up on save will cause &kate; to copy the disk file to
+&lt;prefix&gt;&lt;filename&gt;&lt;suffix&gt;' before saving changes.
+The suffix defaults to <emphasis role="bold">~</emphasis> and prefix is empty by
+default. </para>
+<variablelist>
+<varlistentry>
+<term><guilabel>Local files</guilabel></term>
+<listitem>
+<para>Check this if you want backups of local files when
+saving.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Remote files</guilabel></term>
+<listitem>
+<para>Check this if you want backups of remote files when saving.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Prefix</guilabel></term>
+<listitem>
+<para>Enter the prefix to prepend to the backup file names.</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Suffix</guilabel></term>
+<listitem>
+<para>Enter the suffix to add to the backup file names.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-highlighting">
+<title>Highlighting</title>
+<para>This group of options is used to customize the highlighting styles for
+each programming language type. Any changes you made in other areas of this
+dialog apply only to this type.</para>
+
+<variablelist>
+<varlistentry>
+<term><guilabel>Highlight:</guilabel></term>
+<listitem><para>This is used to choose the language type to
+configure.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Informations</guilabel></term>
+<listitem>
+<para>
+View the properties of the chosen language highlighting rules:
+author name and license.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guilabel>Properties</guilabel></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><guilabel>File extensions:</guilabel></term>
+<listitem><para>This is the list of file extensions used to determine which
+files to highlight using the current syntax highlight mode.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>MIME types:</guilabel></term>
+<listitem><para>Clicking the wizard button will display a dialog with a list of
+all available mime types to choose from.</para><para>The <emphasis
+role="bold">File Extensions</emphasis> entry will automatically be edited as
+well.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Priority:</guilabel></term>
+<listitem><para>Set the priority of the highlight rule.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guibutton>Download...</guibutton></term>
+<listitem>
+<para>
+Click this button to download new or updated syntax highlight descriptions
+from the &kate; website.
+</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-filetypes">
+<title>Filetypes</title>
+<para>This page allows you to override the default configuration for documents
+of specified mimetypes. When the editor loads a document, it will try if it
+matches the file masks or mimetypes for one of the defined filetypes, and if so
+apply the variables defined. If more filetypes match, the one with the highest
+priority will be used.
+</para>
+<variablelist>
+<varlistentry>
+<term><guilabel>Filetype:</guilabel></term>
+<listitem><para>The filetype with the highest priority is the one displayed in
+the first drop down box. If more filetypes were found, they are
+also listed.</para>
+<variablelist>
+<varlistentry>
+<term><guilabel>New</guilabel></term>
+<listitem><para>This is used to create a new filetype. After
+you click on this button, the fields below get empty and you
+can fill the properties you want for the new filetype.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Delete</guilabel></term>
+<listitem><para>To remove an existing filetype, select it from the drop down
+box and press the Delete button.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem> </varlistentry>
+
+<varlistentry>
+<term><guilabel>Properties of current filetype</guilabel></term>
+<listitem><para>The filetype with the highest priority is the one displayed in
+the first drop down box. If more filetypes were found, they are also
+listed.</para>
+<variablelist>
+<varlistentry>
+<term><guilabel>Name:</guilabel></term>
+<listitem><para>The name of the filetype will be the text of the corresponding
+menu item. This name is displayed in the
+<menuchoice><guimenu>Tools</guimenu><guimenuitem>Filetypes</guimenuitem>
+</menuchoice ></para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Section:</guilabel></term>
+<listitem><para>The section name is used to organize the file types in
+menus. This is also used in the
+<menuchoice><guimenu>Tools</guimenu><guimenuitem>Filetypes</guimenuitem>
+</menuchoice> menu.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Variables:</guilabel></term>
+<listitem><para>This string allows you to configure &kate;'s settings for the
+files selected by this mimetype using &kate; variables. You can set almost any
+configuration option, such as highlight, indent-mode, encoding,
+etc.</para><para>For a full list of known variables, see the
+manual.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>File extensions:</guilabel></term>
+<listitem><para>The wildcards mask allows you to select files by filename. A
+typical mask uses an asterisk and the file extension, for example
+<filename>*.txt; *.text</filename>. The string is a semicolon-separated list of
+masks.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>MIME types:</guilabel></term>
+<listitem><para>Displays a wizard that helps you easily select
+mimetypes.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Priority:</guilabel></term>
+<listitem><para>Sets a priority for this file type. If more than one file type
+selects the same file, the one with the highest priority will be
+used.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem> </varlistentry>
+
+</variablelist>
+</sect2>
+
+<sect2 id="config-dialog-editor-shortcuts">
+<title>Shortcuts</title>
+<para>You can change here the shortcut keys configuration. Select an
+action and click on <guilabel>Custom</guilabel> if you want a different shortcut
+for this action.</para>
+<para>The search line alllows you to look for a specific action and see
+its associated shortcut.</para>
+</sect2>
+
+<sect2 id="config-dialog-editor-plugins">
+<title>Plugins</title>
+<para>This tab lists all available plugins and you can check those you
+want to use. Once a plugin is checked, the
+<guibutton>Configure</guibutton> button is enabled and you can click it
+in order to configure the highlighted plugin.</para>
+</sect2>
+
+</sect1>
+
+
+
+<sect1 id="config-variables">
+
+<title>Configuring With Document Variables</title>
+
+<para>Kate variables is kateparts implementation of document variables, similar
+to emacs and vi modelines. In katepart, the lines have the format
+
+<userinput>kate: VARIABLENAME VALUE; [ VARIABLENAME VALUE; ... ]</userinput>
+
+the lines can of course be in a comment, if the file is in a format with comments.
+Variable names are single words (no whitespace), and anything up to the next
+semicolon is the value. The semicolon is required.</para>
+
+<para>Here is an example variable line, forcing indentation settings for a C++,
+java or javascript file:
+
+<programlisting>// kate: space-indent on; indent-width 4; mixedindent off; indent-mode cstyle;</programlisting>
+</para>
+
+<note><para>Only the first and last 10 lines are searched for variable lines.</para></note>
+
+<para>There are variables to support almost all configurations in katepart, and
+aditionally plugins can use variables, in which case it should be documented in
+the plugin's documentation.</para>
+
+<sect2 id="config-variables-howto">
+<title>How kate uses variables</title>
+
+<para>When reading configuration, katepart looks in the following places
+(in that order):
+
+<itemizedlist>
+<listitem><para>The global configuration.</para></listitem>
+<listitem><para>Optional session data.</para></listitem>
+<listitem><para>The "Filetype" configuration.</para></listitem>
+<listitem><para>Document variables in the document itself.</para></listitem>
+<listitem><para>Settings made during editing from menu or command line.</para></listitem>
+</itemizedlist>
+
+As you can understand document variables has the next highest precedence.
+Whenever a document is saved, the document variables are reread, and will
+overwrite changes made using menu items or the command line.</para>
+
+<para>Any variable not listed below is stored in the document and can be queried
+by other objects such as plugins, which can use them for their own purpose.
+For example the variable indent mode uses document variables for its
+configuration.</para>
+
+<para>The variables listed here documents &kate; version 2.4. More variables
+may be added in the future. There are 3 possible types of values for variables,
+with the following valid expressions:
+<itemizedlist>
+<listitem><para>BOOL - on|off|true|false|1|0</para></listitem>
+<listitem><para>INTEGER - any integer number</para></listitem>
+<listitem><para>STRING - anything else</para></listitem>
+</itemizedlist>
+</para>
+
+<variablelist>
+<title>Available Variables</title>
+
+<varlistentry>
+<term><cmdsynopsis><command>auto-brackets</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set auto insertion of brackets on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>auto-center-lines</command><arg>INT</arg></cmdsynopsis></term>
+<listitem><para>Set the number of autocenter lines.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>auto-insert-doxygen</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Turn insertion of the leading asterisk in doxygen comments on or
+off. This has no effect unless you use the cstyle auto-indenter. </para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>background-color</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the document background color. The value must be something
+that can be evaluated to a valid color, for example "#ff0000".</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>backspace-indents</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Turn backspace indenting on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>block-selection</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Turn block selection on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>bracket-highlight-color</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the color for the bracket highlight. The value must be
+something that can be evaluated to a valid color, for example "#ff0000" </para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>current-line-color</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the color for the current line. The value must be
+something that can be evaluated to a valid color, for example "#ff0000".</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>dynamic-word-wrap</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Turns dynamic word wrap on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>eol | end-of-line</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the end of line mode. Valid settings are
+<quote>unix</quote>, <quote>mac</quote> and <quote>dos</quote></para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>encoding</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the document encoding. The value must be a valid encoding
+name, like <quote>utf-8</quote>.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>font-size</command><arg>INT</arg></cmdsynopsis></term>
+<listitem><para>Set the point size of the document font.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>font</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the font of the document. The value should be a valid font
+name, for example <quote>courier</quote>.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>icon-bar-color</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the icon bar color. The value must be something that can
+be evaluated to a valid color, for example <literal>#ff0000</literal>.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>icon-border</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set the display of the icon border on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>folding-markers</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set the display of folding markers on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>indent-mode</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the auto-indentation mode. The options <quote>none</quote>,
+<quote>normal</quote>, <quote>cstyle</quote>, <quote>csands</quote>,
+<quote>python</quote>, <quote>xml</quote> are recognized. See the section
+<xref linkend="kate-part-autoindent"/> for details.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>indent-width</command><arg>INT</arg></cmdsynopsis></term>
+<listitem><para>Set the indentation width.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>keep-extra-spaces</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set wheather to keep extra spaces when calculating indentation width.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>keep-indent-profile</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>If enabled, prevents unindenting a block if at least one line
+has no indentation.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>line-numbers</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set the display of line numbers on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>mixed-indent</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set mixed indentation ala Emacs on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>overwrite-mode</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set overwrite mode on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>persistent-selection</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set persistent selection on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>remove-trailing-space</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set dynamic end of line cleanup on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>replace-tabs-save</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set tab-&gt;space conversion on save on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>replace-tabs</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set dynamic tab-&gt;space conversion on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>replace-trailing-space-save</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set end of line cleanup on save on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>scheme</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the color scheme. The string must be the name of a color
+scheme that exists in your configuration to have any effect.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>selection-color</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the selection color. The value must be something that can
+be evaluated to a valid color, for example "#ff0000".</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>show-tabs</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set the visual TAB character on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>smart-home</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set smart home navigation on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>space-indent</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set indentation with spaces on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>tab-indents</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set the TAB key indentation on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>tab-width</command><arg>INT</arg></cmdsynopsis></term>
+<listitem><para>Set the tab display width.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>undo-steps</command><arg>INT</arg></cmdsynopsis></term>
+<listitem><para>Set the number of undo steps to remember.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>word-wrap-column</command><arg>INT</arg></cmdsynopsis></term>
+<listitem><para>Set the hard word wrap width.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>word-wrap-marker-color</command><arg>STRING</arg></cmdsynopsis></term>
+<listitem><para>Set the word wrap marker color. The value must be something
+that can be evaluated to a valid color, for example "#ff0000".</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>word-wrap</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set hard word wrapping on or off.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><cmdsynopsis><command>wrap-cursor</command><arg>BOOL</arg></cmdsynopsis></term>
+<listitem><para>Set cursor wrapping on or off.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/doc/kate/fundamentals.docbook b/doc/kate/fundamentals.docbook
new file mode 100644
index 00000000..e6beaac5
--- /dev/null
+++ b/doc/kate/fundamentals.docbook
@@ -0,0 +1,621 @@
+<chapter id="fundamentals">
+<chapterinfo>
+<authorgroup>
+<author><personname><firstname></firstname></personname></author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</chapterinfo>
+<title>The Fundamentals</title>
+
+<para>
+If you have ever used a text editor, you will have no problem using
+&kate;. In the next two sections, <link linkend="starting-kate">Starting
+&kate; </link> and in <link linkend="working-with-kate">Working with
+&kate;</link>, we'll show you everything you need to get up and running
+quickly.
+</para>
+
+<sect1 id="starting-kate">
+<title>Starting &kate;</title>
+
+<para>
+You can start &kate; from the <guimenu>K menu</guimenu> or from the
+command line.
+</para>
+
+<sect2 id="starting-from-the-menu">
+<title>From the Menu</title>
+<para>
+Open the &kde; program menu by clicking on the
+<guiicon>big K</guiicon> icon on the toolbar at the bottom left of your
+screen. This will raise the <guimenu>program menu</guimenu>. Move your
+cursor up the menu to the <menuchoice><guimenu>Utilities</guimenu>
+<guimenuitem>Editors</guimenuitem></menuchoice> menu item. A list
+of available editors will appear. Choose
+<guimenuitem>&kate;</guimenuitem>.
+</para>
+
+<para>
+Unless you configure &kate; not to, it will load the last files you
+edited. See <link linkend="configure">Configuring &kate;</link> to learn
+how to toggle this feature on and off.
+</para>
+
+</sect2>
+
+<sect2 id="starting-from-the-command-line">
+<title>From the Command Line</title>
+
+<para>
+You can start &kate; by typing its name on the command line. If you give
+it a file name, as in the example below, it will open or create that
+file.
+</para>
+
+<informalexample>
+<screen>
+<prompt>%</prompt><userinput><command>kate</command> <option><replaceable>myfile.txt</replaceable></option></userinput>
+</screen>
+</informalexample>
+
+<para>
+If you have an active connection, and permission, you can take advantage
+of &kde;'s network transparency to open files on the internet.
+</para>
+
+<informalexample>
+<screen>
+<prompt>%</prompt><userinput><command>kate</command> <option><replaceable>ftp://ftp.kde.org/pub/kde/README_FIRST</replaceable></option></userinput>
+</screen>
+</informalexample>
+
+<sect3 id="command-line-options">
+<title>Command Line Options</title>
+<para>&kate; accepts following command line options:</para>
+
+<variablelist>
+<varlistentry>
+<term><userinput><command>kate</command> <option>--help</option></userinput></term>
+<listitem>
+<para>
+This lists the most basic options available at the command line.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--help-qt</option></userinput></term>
+<listitem>
+<para>
+This lists the options available for changing the way &kate; interacts
+with &Qt;.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command> <option>--help-kde</option></userinput></term>
+<listitem>
+<para>
+This lists the options available for changing the way &kate; interacts
+with &kde;.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>-s</option> <option>--start</option> <parameter>name</parameter></userinput></term>
+<listitem>
+<para>
+Starts kate with the session <parameter>name</parameter>. The session is created
+if it does not exist already. If a &kate; instance running the specified session
+exists, the specified files are loaded in that instance. When used with the
+<option>--use</option> option, an instance running this session will be used as
+well.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>-u</option> <option>--use</option> <parameter>URL</parameter></userinput></term>
+<listitem>
+<para>
+Causes &kate; to use and existing instance if there is one. If you want all
+documents to open in one kate instance, you can add this option to the default
+command in your kde application configuration, as well as create a shell alias
+in your command intepreter if it supports that.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>-p</option> <option>--pid</option> <parameter>PID</parameter></userinput></term>
+<listitem>
+<para>
+Only reuses an instance with the specified PID (Process ID). Used with the
+<option>--use</option> option.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--encoding</option> <parameter>encoding</parameter>
+<parameter>URL</parameter></userinput></term>
+<listitem><para>Uses the specified encoding for the document.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--line</option> <parameter>line</parameter>
+<parameter>URL</parameter></userinput></term>
+<listitem><para>Navigates to the specified line after opening the document.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--column</option> <parameter>column</parameter>
+<parameter>URL</parameter></userinput></term>
+<listitem><para>Navigates to the specified column after opening the document.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--stdin</option></userinput></term>
+<listitem><para>Reads the document content from STDIN. This
+is similar to the common option <option>-</option> used in many command line
+programs, and allows you to pipe command output into &kate;.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--tempfile</option></userinput></term>
+<listitem><para>Since &kate; 2.5.1 this standard &kde; option is supported.
+When used, the specified files are treated as temporary files and
+deleted (if they are local files and you have sufficient permissions) when
+closed, unless they are modified since they were opened.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--help-all</option></userinput></term>
+<listitem>
+<para>
+This lists all of the command line options.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--author</option></userinput></term>
+<listitem>
+<para>
+Lists &kate;'s authors in the terminal window.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>-v</option> <option>--version</option></userinput></term>
+<listitem>
+<para>
+Lists version information for &Qt;, &kde;, and &kate;.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><userinput><command>kate</command>
+<option>--license</option></userinput></term>
+<listitem>
+<para>
+Shows license information.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</sect3>
+</sect2>
+
+<sect2 id="drag-and-drop">
+<title>Drag and Drop</title>
+<para>
+&kate; uses the &kde; Drag and Drop protocol. Files may be dragged and
+dropped onto &kate; from the Desktop, &konqueror; or some remote ftp
+site opened in one of &konqueror;'s windows.
+</para>
+</sect2>
+</sect1>
+
+<sect1 id="working-with-kate">
+<title>Working with &kate;</title>
+<para>
+<link linkend="quick-start">Quick Start</link> will show you how to
+toggle four simple options that will let you configure some of &kate;'s
+more powerful features right away. <link linkend="keystroke-commands">
+Shortcuts</link> lays out some of the default keystroke
+shortcuts for those who can't or don't want to use a mouse.
+</para>
+
+<sect2 id="quick-start">
+<title>Quick Start</title>
+
+<para>
+This section will describe some of the items on the
+<guimenu>Settings</guimenu> menu so that you can quickly configure
+&kate; to work the way you want it.
+</para>
+
+<para> When you start &kate; for the first time you'll see two windows
+with white backgrounds. Above the two windows is a toolbar with the
+usual labeled icons. And above that, a menubar.
+</para>
+
+<para>
+The left-hand window is a side bar. It combines the Documents
+and Filesystem Browser windows. Switch between the two by clicking on the tabs
+to the left of the window. </para>
+
+<para>
+If you've started &kate; with a file, the right-hand window will show
+the file you are editing and the Documents on the side bar will show the
+name of the file. Use the Filesystem Browser window to open files.
+</para>
+
+<para>
+You can toggle the Documents and Filesystem Browser window on and off in
+<menuchoice><guimenu>Window</guimenu><guimenu>Tool Views</guimenu></menuchoice>
+menu. This menu offers you your first glimpse into &kate;'s power and
+flexibility. In this section we'll look at three items:
+</para>
+
+<variablelist>
+
+<varlistentry>
+<term>
+<menuchoice>
+<guimenuitem>Show/Hide Documents</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+Toggles the Documents on and off. If the Documents/Filesystem Browser window is
+not open, &kate; launches the side bar as a separate, undocked,
+window. To dock the window grab the two thin parallel lines above the
+tabs by clicking on them with your &LMB; and holding the button
+down. Drag the the window into &kate;'s editing window and release the
+&LMB; when you have positioned the Documents/Filesystem Browser window as you
+prefer.
+</para>
+
+<tip>
+<para>
+If you have grabbed the two parallel lines successfully your mouse
+pointer will turn into two crossed arrows as you drag.
+</para>
+</tip>
+
+</listitem>
+</varlistentry>
+<varlistentry>
+<term><menuchoice><guimenuitem>Show/Hide
+Filesystem Browser</guimenuitem></menuchoice></term>
+<listitem>
+<para>
+Toggles the Filesystem Browser on and off. This menu item is the same as
+<guimenuitem>Show Documents</guimenuitem> with one difference. Toggling
+it on launches the window with the Filesystem Browser on top.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><guimenuitem>Show/Hide
+Terminal</guimenuitem></menuchoice></term>
+<listitem>
+<para>
+Toggles a terminal emulator on and off at the bottom of &kate;'s
+window. In other words, it gives you a command line within the
+application.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</sect2>
+
+<sect2 id="keystroke-commands">
+<title>Shortcuts</title>
+
+<para>
+Many of &kate;'s keystroke commands (shortcuts) are configurable by
+way of the <link linkend="settings">Settings</link> menu. By default
+&kate; honors the following key bindings.
+</para>
+
+<informaltable>
+<tgroup cols="2">
+<tbody>
+
+<row><entry><para><keycap>Insert</keycap></para></entry>
+<entry><para>
+Toggle between Insert and Overwrite mode. When in insert mode the editor
+will add any typed characters to the text and push any previously typed
+data to the right of the text cursor. Overwrite mode causes the entry of
+each character to eliminate the current character.</para></entry>
+</row>
+<row>
+<entry><para><keycombo><keycap>Left Arrow</keycap></keycombo></para></entry>
+<entry><para>Move the cursor one character to the left </para></entry>
+</row>
+<row>
+<entry><para><keycombo><keycap>Right Arrow</keycap></keycombo></para></entry>
+<entry><para> Move the cursor one character to the right </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Up Arrow</keycap></keycombo></para></entry>
+<entry><para> Move the cursor up one line </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Down Arrow</keycap></keycombo></para></entry>
+<entry><para> Move the cursor down one line </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Page Up</keycap></keycombo></para></entry>
+<entry><para> Move the cursor up one page </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Page Down</keycap></keycombo></para></entry>
+<entry><para>Move the cursor down one page </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Backspace</keycap></keycombo></para></entry>
+<entry><para> Delete the character to the left of the cursor </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Home</keycap></keycombo></para></entry>
+<entry><para> Move the cursor to the beginning of the line </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>End</keycap></keycombo></para></entry>
+<entry><para> Move the cursor to the end of the line </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>Delete</keycap></keycombo></para></entry>
+<entry><para>Delete the character to the right of the cursor (or any selected
+text)</para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Shift;<keycap>Left Arrow</keycap></keycombo></para></entry>
+<entry><para> Mark text one character to the left </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Shift;<keycap>Right Arrow</keycap></keycombo></para></entry>
+<entry><para> Mark text one character to the right </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>F1</keycap></keycombo></para></entry>
+<entry><para> Help</para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Shift;<keycap>F1</keycap></keycombo></para></entry>
+<entry><para><link linkend="whats-this">What's this?</link></para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo></para></entry>
+<entry><para><link linkend="find"> Find</link></para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul"><keycap>F3</keycap></keycombo></para></entry>
+<entry><para><link linkend="find-again"> Find again</link></para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>B</keycap></keycombo></para></entry>
+<entry><para>Set a Bookmark</para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>C</keycap></keycombo></para></entry>
+<entry><para> Copy the marked text to the clipboard. </para></entry>
+</row>
+
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo></para></entry>
+<entry><para> <link linkend="new">New</link> document</para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>P</keycap></keycombo></para></entry>
+<entry><para><link linkend="print">Print</link> </para></entry>
+</row>
+<row>
+
+<entry><para><keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo></para></entry>
+<entry><para>Quit - close active copy of editor </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>R</keycap></keycombo></para></entry>
+<entry><para><link linkend="replace"> Replace</link></para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>S</keycap></keycombo></para></entry>
+<entry><para>Save your file.</para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>V</keycap></keycombo></para></entry>
+<entry><para> Paste.</para></entry>
+</row>
+
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>X</keycap></keycombo></para></entry>
+<entry><para>Delete the marked text and copy it to the clipboard. </para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;<keycap>Z</keycap></keycombo></para></entry>
+<entry><para><link linkend="undo">Undo</link></para></entry>
+</row>
+<row>
+<entry><para><keycombo action="simul">&Ctrl;&Shift;<keycap>Z</keycap></keycombo></para></entry>
+<entry><para><link linkend="redo">Redo</link></para></entry>
+</row>
+</tbody>
+</tgroup>
+</informaltable>
+</sect2>
+
+</sect1>
+
+<sect1 id="fundamentals-using-sessions">
+<title>Using Sessions</title>
+
+<para>Sessions is how &kate; lets you keep more than one list of files and
+GUI configuration around. You can have as many named sessions as you want,
+and you can use unnamed or anonymous sessions for files you want to use only
+once. Currently &kate; can save the list of open files, and the general window
+configuration in the session, future versions of &kate; may add more features
+that can be saved in sessions. With the introduction of sessions, &kate; also
+allows you to open any number of instances of the application instead of just
+one as it used to do as the default behavior.</para>
+
+<para>Sessions are supported in three areas:
+
+<itemizedlist>
+<listitem><para><link linkend="command-line-options"><emphasis>Command line
+options</emphasis></link> that lets you select and start sessions when launching
+kate from the command line.</para>
+</listitem>
+<listitem><para><link linkend="sessions-menu"><emphasis>The Sessions
+menu</emphasis></link> that lets you switch, save, start and manage your
+sessions</para></listitem>
+<listitem><para><link linkend="config-dialog-sessions"><emphasis>Configuration
+options</emphasis></link> that lets you decide how sessions generally should
+behave.</para></listitem>
+</itemizedlist>
+
+</para>
+
+<para>When starting a new session, the GUI configuration of <guilabel>Default
+Session</guilabel> is loaded. To save window configuration in the default
+session, you need to enable saving window configuration in the sessions
+configuration page of the configuration dialog and then load the default
+session, set up the window as desired and save the session again.</para>
+
+<para>When a named session is loaded, &kate; will display the session name at
+the start of the window title, which then have the form
+&quot;<replaceable>Session Name</replaceable>: <replaceable>Document name or
+&URL;</replaceable> - &kate;&quot;</para>
+
+<para>When opening files on the command line with <option>--start
+<replaceable>name</replaceable></option> or if a session is selected using the
+session chooser, the specified session is loaded prior to the files specified
+on the command line. To open files from the commandline in a new, unnamed
+session, configure kate to start a new session pr default in the session page of
+the configuration dialog or use <option>--start</option> with an empty string:
+<replaceable>''</replaceable>.</para>
+
+<para>Since &kate; 2.5.1 the <acronym>PID</acronym> of the current instance is
+exported to the environment variable <envar>KATE_PID</envar>. When opening files
+from the built in terminal Kate will automatically select the current instance
+if nothing else is indicated on the command line.</para>
+
+<sect2 id="old-behavior">
+<title>Restoring old style &kate; behavior</title>
+
+<para>When you get used to using sessions you will hopefully see that they
+provide a very simple and efficient tool for working in different areas.
+However, if you prefer the old &kate; behavior (one instance opens all files),
+you can easily achieve that by following this simple strategy:
+
+<itemizedlist>
+<listitem><para>Make kate allways start with the <option>--use</option>
+parameter by adding that to the command in the application preferences,
+and additionally using a shell alias.</para></listitem>
+<listitem><para>Configure &kate; to load the last used session at startup.</para>
+</listitem>
+<listitem><para>Configure &kate; to save the file list when closing a session.
+</para></listitem>
+<listitem><para>Load the default session once</para></listitem>
+</itemizedlist>
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="fundamentals-getting-help">
+
+<title>Getting Help</title>
+
+<sect2>
+
+<title>With &kate;</title>
+<variablelist>
+
+<varlistentry>
+<term>This manual</term>
+
+<listitem>
+<para>Offers detailed documentation on all menu commands,
+configuration options, tools, dialogs, plugins &etc; as well as
+descriptions of of the &kate; window, the editor and various concepts
+used in the application.</para>
+
+<para>Press <keycap>F1</keycap> or use the
+<menuchoice><guimenu>Help</guimenu></menuchoice>
+<guisubmenu>Contents</guisubmenu> menu topic to view this
+manual.</para></listitem>
+
+</varlistentry>
+
+<varlistentry id="whats-this">
+<term>What's This Help</term>
+<listitem>
+<para>What's This help offers immediate help with single elements of
+graphical windows, such as buttons or other window areas.</para>
+
+<para>We strive to provide What's This help for any elements for which
+it makes sense. It is available throughout the configuration dialog,
+and in many other dialogs as well.</para>
+
+<para>To employ What's This help, press
+<keycombo>&Shift;<keycap>F1</keycap></keycombo> or use the
+<menuchoice><guimenu>Help</guimenu><guimenuitem>What's
+This</guimenuitem></menuchoice> menu item to enable What's This
+mode. The cursor will turn into an arrow with a question mark, and you
+can now click any element in the window to read the What's This help
+for that element, if it is available.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Help Buttons in Dialogs</term>
+<listitem>
+<para>Some dialogs have a <guibutton>Help</guibutton> Button. Pressing
+it will start the &khelpcenter; and open the relevant
+documentation.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
+<sect2>
+<title>With Your Text Files</title>
+
+<para>&kate; does not (yet!) provide any means for reading document
+related documentation. Depending on the file you are editing, you may
+find the <link linkend="kate-mdi-tools-konsole">Built in
+&konsole;</link> helpful for viewing related &UNIX; manual pages or
+info documentation, or you can use &konqueror;.</para>
+
+</sect2>
+
+</sect1>
+
+</chapter>
diff --git a/doc/kate/highlighted.png b/doc/kate/highlighted.png
new file mode 100644
index 00000000..ffb95ec4
--- /dev/null
+++ b/doc/kate/highlighted.png
Binary files differ
diff --git a/doc/kate/highlighting.docbook b/doc/kate/highlighting.docbook
new file mode 100644
index 00000000..76952d26
--- /dev/null
+++ b/doc/kate/highlighting.docbook
@@ -0,0 +1,931 @@
+<appendix id="highlight">
+<appendixinfo>
+<authorgroup>
+<author><personname><firstname></firstname></personname></author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</appendixinfo>
+<title>Working with Syntax Highlighting</title>
+
+<sect1 id="highlight-overview">
+
+<title>Overview</title>
+
+<para>Syntax Highlighting is what makes the editor automatically
+display text in different styles/colors, depending on the function of
+the string in relation to the purpose of the file. In program source
+code for example, control statements may be rendered bold, while data
+types and comments get different colors from the rest of the
+text. This greatly enhances the readability of the text, and thus
+helps the author to be more efficient and productive.</para>
+
+<mediaobject>
+<imageobject><imagedata format="PNG" fileref="highlighted.png"/></imageobject>
+<textobject><phrase>A Perl function, rendered with syntax
+highlighting.</phrase></textobject>
+<caption><para>A Perl function, rendered with syntax highlighting.</para>
+</caption>
+</mediaobject>
+
+<mediaobject>
+<imageobject><imagedata format="PNG" fileref="unhighlighted.png"/></imageobject>
+<textobject><phrase>The same Perl function, without
+highlighting.</phrase></textobject>
+<caption><para>The same Perl function, without highlighting.</para></caption>
+</mediaobject>
+
+<para>Of the two examples, which is easiest to read?</para>
+
+<para>&kate; comes with a flexible, configurable and capable system
+for doing syntax highlighting, and the standard distribution provides
+definitions for a wide range of programming, scripting and markup
+languages and other text file formats. In addition you can
+provide your own definitions in simple &XML; files.</para>
+
+<para>&kate; will automatically detect the right syntax rules when you
+open a file, based on the &MIME; Type of the file, determined by its
+extension, or, if it has none, the contents. Should you experience a
+bad choice, you can manually set the syntax to use from the
+<menuchoice><guimenu>Documents</guimenu><guisubmenu>Highlight
+Mode</guisubmenu></menuchoice> menu.</para>
+
+<para>The styles and colors used by each syntax highlight definition
+can be configured using the <link
+linkend="config-dialog-editor-appearance">Appearance</link> page of the
+<link linkend="config-dialog">Config Dialog</link>, while the &MIME; Types
+it should be used for, are handeled by the <link
+linkend="config-dialog-editor-highlighting">Highlight</link>
+page.</para>
+
+<note>
+<para>Syntax highlighting is there to enhance the readability of
+correct text, but you cannot trust it to validate your text. Marking
+text for syntax is difficult depending on the format you are using,
+and in some cases the authors of the syntax rules will be proud if 98%
+of text gets correctly rendered, though most often you need a rare
+style to see the incorrect 2%.</para>
+</note>
+
+<tip>
+<para>You can download updated or additional syntax highlight
+definitions from the &kate; website by clicking the
+<guibutton>Download</guibutton> button in the <link
+linkend="config-dialog-editor-highlighting">Highlight Page</link> of the <link
+linkend="config-dialog">Config Dialog</link>.</para>
+</tip>
+
+</sect1>
+
+<sect1 id="katehighlight-system">
+
+<title>The &kate; Syntax Highlight System</title>
+
+<para>This section will discuss the &kate; syntax highlighting
+mechanism in more detail. It is for you if you want to know about
+it, or if you want to change or create syntax definitions.</para>
+
+<sect2 id="katehighlight-howitworks">
+
+<title>How it Works</title>
+
+<para>Whenever you open a file, one of the first things the &kate;
+editor does is detect which syntax definition to use for the
+file. While reading the text of the file, and while you type away in
+it, the syntax highlighting system will analyze the text using the
+rules defined by the syntax definition and mark in it where different
+contexts and styles begin and end.</para>
+
+<para>When you type in the document, the new text is analyzed and marked on the
+fly, so that if you delete a character that is marked as the beginning or end
+of a context, the style of surrounding text changes accordingly.</para>
+
+<para>The syntax definitions used by the &kate; Syntax Highlighting System are
+&XML; files, containing
+<itemizedlist>
+<listitem><para>Rules for detecting the role of text, organized into context blocks</para></listitem>
+<listitem><para>Keyword lists</para></listitem>
+<listitem><para>Style Item definitions</para></listitem>
+</itemizedlist>
+</para>
+
+<para>When analyzing the text, the detection rules are evaluated in
+the order in which they are defined, and if the beginning of the
+current string matches a rule, the related context is used. The start
+point in the text is moved to the final point at which that rule
+matched and a new loop of the rules begins, starting in the context
+set by the matched rule.</para>
+
+</sect2>
+
+<sect2 id="highlight-system-rules">
+<title>Rules</title>
+
+<para>The detection rules are the heart of the highlighting detection
+system. A rule is a string, character or <link
+linkend="regular-expressions">regular expression</link> against which
+to match the text being analyzed. It contains information about which
+style to use for the matching part of the text. It may switch the
+working context of the system either to an explicitly mentioned
+context or to the previous context used by the text.</para>
+
+<para>Rules are organized in context groups. A context group is used
+for main text concepts within the format, for example quoted text
+strings or comment blocks in program source code. This ensures that
+the highlighting system does not need to loop through all rules when
+it is not necessary, and that some character sequences in the text can
+be treated differently depending on the current context.
+</para>
+
+<para>Contexts may be generated dynamically to allow the usage of instance
+specific data in rules.</para>
+
+</sect2>
+
+<sect2 id="highlight-context-styles-keywords">
+<title>Context Styles and Keywords</title>
+
+<para>In some programming languages, integer numbers are treated
+differently than floating point ones by the compiler (the program that
+converts the source code to a binary executable), and there may be
+characters having a special meaning within a quoted string. In such
+cases, it makes sense to render them differently from the surroundings
+so that they are easy to identify while reading the text. So even if
+they do not represent special contexts, they may be seen as such by
+the syntax highlighting system, so that they can be marked for
+different rendering.</para>
+
+<para>A syntax definition may contain as many styles as required to
+cover the concepts of the format it is used for.</para>
+
+<para>In many formats, there are lists of words that represent a
+specific concept. For example in programming languages, the control
+statements is one concept, data type names another, and built in
+functions of the language a third. The &kate; Syntax Highlighting
+System can use such lists to detect and mark words in the text to
+emphasize concepts of the text formats.</para>
+
+</sect2>
+
+<sect2 id="kate-highlight-system-default-styles">
+<title>Default Styles</title>
+
+<para>If you open a C++ source file, a &Java; source file and an
+<acronym>HTML</acronym> document in &kate;, you will see that even
+though the formats are different, and thus different words are chosen
+for special treatment, the colors used are the same. This is because
+&kate; has a predefined list of Default Styles which are employed by
+the individual syntax definitions.</para>
+
+<para>This makes it easy to recognize similar concepts in different
+text formats. For example comments are present in almost any
+programming, scripting or markup language, and when they are rendered
+using the same style in all languages, you do not have to stop and
+think to identify them within the text.</para>
+
+<tip>
+<para>All styles in a syntax definition use one of the default
+styles. A few syntax definitions use more styles that there are
+defaults, so if you use a format often, it may be worth launching the
+configuration dialog to see if some concepts are using the same
+style. For example there is only one default style for strings, but as
+the Perl programming language operates with two types of strings, you
+can enhance the highlighting by configuring those to be slightly
+different. All <link linkend="kate-highlight-default-styles">available default styles</link>
+will be explained later.</para>
+</tip>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="katehighlight-xml-format">
+<title>The Highlight Definition &XML; Format</title>
+
+<sect2>
+<title>Overview</title>
+
+<para>This section is an overview of the Highlight Definition &XML;
+format. Based on a small example it will describe the main components
+and their meaning and usage. The next section will go into detail with
+the highlight detection rules.</para>
+
+<para>The formal definition, aka the <acronym>DTD</acronym> is stored
+in the file <filename>language.dtd</filename> which should be
+installed on your system in the folder
+<filename>$<envar>KDEDIR</envar>/share/apps/katepart/syntax</filename>.
+</para>
+
+<variablelist>
+<title>Main sections of &kate; Highlight Definition files</title>
+
+<varlistentry>
+<term>A highlighting file contains a header that sets the XML version and the doctype:</term>
+<listitem>
+<programlisting>
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;!DOCTYPE language SYSTEM &quot;language.dtd&quot;&gt;
+</programlisting>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>The root of the definition file is the element <userinput>language</userinput>.
+Available attributes are:</term>
+
+<listitem>
+<para>Required attributes:</para>
+<para><userinput>name</userinput> sets the name of the language. It appears in the menus and dialogs afterwards.</para>
+<para><userinput>section</userinput> specifies the category.</para>
+<para><userinput>extensions</userinput> defines file extensions, like &quot;*.cpp;*.h&quot;</para>
+
+<para>Optional attributes:</para>
+<para><userinput>mimetype</userinput> associates files &MIME; Type based.</para>
+<para><userinput>version</userinput> specifies the current version of the definition file.</para>
+<para><userinput>kateversion</userinput> specifies the latest supported &kate; version.</para>
+<para><userinput>casesensitive</userinput> defines, whether the keywords are casesensitiv or not.</para>
+<para><userinput>priority</userinput> is necessary if another highlight definition file uses the same extensions. The higher priority will win.</para>
+<para><userinput>author</userinput> contains the name of the author and his email-address.</para>
+<para><userinput>license</userinput> contains the license, usually LGPL, Artistic, GPL and others.</para>
+<para><userinput>hidden</userinput> defines, whether the name should appear in &kate;'s menus.</para>
+<para>So the next line may look like this:</para>
+<programlisting>
+&lt;language name=&quot;C++&quot; version=&quot;1.00&quot; kateversion=&quot;2.4&quot; section=&quot;Sources&quot; extensions=&quot;*.cpp;*.h&quot; /&gt;
+</programlisting>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>Next comes the <userinput>highlighting</userinput> element, which
+contains the optional element <userinput>list</userinput> and the required
+elements <userinput>contexts</userinput> and <userinput>itemDatas</userinput>.</term>
+<listitem>
+<para><userinput>list</userinput> elements contain a list of keywords. In
+this case the keywords are <emphasis>class</emphasis> and <emphasis>const</emphasis>.
+You can add as many lists as you need.</para>
+<para>The <userinput>contexts</userinput> element contains all contexts.
+The first context is by default the start of the highlighting. There are
+two rules in the context <emphasis>Normal Text</emphasis>, which match
+the list of keywords with the name <emphasis>somename</emphasis> and a
+rule that detects a quote and switches the context to <emphasis>string</emphasis>.
+To learn more about rules read the next chapter.</para>
+<para>The third part is the <userinput>itemDatas</userinput> element. It
+contains all color and font styles needed by the contexts and rules.
+In this example, the <userinput>itemData</userinput> <emphasis>Normal Text</emphasis>,
+<emphasis>String</emphasis> and <emphasis>Keyword</emphasis> are used.
+</para>
+<programlisting>
+ &lt;highlighting&gt;
+ &lt;list name=&quot;somename&quot;&gt;
+ &lt;item&gt; class &lt;/item&gt;
+ &lt;item&gt; const &lt;/item&gt;
+ &lt;/list&gt;
+ &lt;contexts&gt;
+ &lt;context attribute=&quot;Normal Text&quot; lineEndContext=&quot;#pop&quot; name=&quot;Normal Text&quot; &gt;
+ &lt;keyword attribute=&quot;Keyword&quot; context=&quot;#stay&quot; String=&quot;somename&quot; /&gt;
+ &lt;DetectChar attribute=&quot;String&quot; context=&quot;string&quot; char=&quot;&amp;quot;&quot; /&gt;
+ &lt;/context&gt;
+ &lt;context attribute=&quot;String&quot; lineEndContext=&quot;#stay&quot; name=&quot;string&quot; &gt;
+ &lt;DetectChar attribute=&quot;String&quot; context=&quot;#pop&quot; char=&quot;&amp;quot;&quot; /&gt;
+ &lt;/context&gt;
+ &lt;/contexts&gt;
+ &lt;itemDatas&gt;
+ &lt;itemData name=&quot;Normal Text&quot; defStyleNum=&quot;dsNormal&quot; /&gt;
+ &lt;itemData name=&quot;Keyword&quot; defStyleNum=&quot;dsKeyword&quot; /&gt;
+ &lt;itemData name=&quot;String&quot; defStyleNum=&quot;dsString&quot; /&gt;
+ &lt;/itemDatas&gt;
+ &lt;/highlighting&gt;
+</programlisting>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>The last part of a highlight definition is the optional
+<userinput>general</userinput> section. It may contain information
+about keywords, code folding, comments and indentation.</term>
+
+<listitem>
+<para>The <userinput>comment</userinput> section defines with what
+string a single line comment is introduced. You also can define a
+multiline comments using <emphasis>multiLine</emphasis> with the
+additional attribute <emphasis>end</emphasis>. This is used if the
+user presses the corresponding shortcut for <emphasis>comment/uncomment</emphasis>.</para>
+<para>The <userinput>keywords</userinput> section defines whether
+keyword lists are casesensitive or not. Other attributes will be
+explained later.</para>
+<programlisting>
+ &lt;general&gt;
+ &lt;comments&gt;
+ &lt;comment name="singleLine" start="#"/&gt;
+ &lt;/comments&gt;
+ &lt;keywords casesensitive="1"/&gt;
+ &lt;/general&gt;
+&lt;/language&gt;
+</programlisting>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+
+</sect2>
+
+<sect2 id="kate-highlight-sections">
+<title>The Sections in Detail</title>
+<para>This part will describe all available attributes for contexts,
+itemDatas, keywords, comments, code folding and indentation.</para>
+
+<variablelist>
+<varlistentry>
+<term>The element <userinput>context</userinput> belongs into the group
+<userinput>contexts</userinput>. A context itself defines context specific
+rules like what should happen if the highlight system reaches the end of a
+line. Available attributes are:</term>
+
+
+<listitem>
+<para><userinput>name</userinput> the context name. Rules will use this name
+to specify the context to switch to if the rule matches.</para>
+<para><userinput>lineEndContext</userinput> defines the context the highlight
+system switches to if it reaches the end of a line. This may either be a name
+of another context, <userinput>#stay</userinput> to not switch the context
+(eg. do nothing) or <userinput>#pop</userinput> which will cause to leave this
+context. It is possible to use for example <userinput>#pop#pop#pop</userinput>
+to pop three times.</para>
+<para><userinput>lineBeginContext</userinput> defines the context if a begin
+of a line is encountered. Default: #stay.</para>
+<para><userinput>fallthrough</userinput> defines if the highlight system switches
+to the context specified in fallthroughContext if no rule matches.
+Default: <emphasis>false</emphasis>.</para>
+<para><userinput>fallthroughContext</userinput> specifies the next context
+if no rule matches.</para>
+<para><userinput>dynamic</userinput> if <emphasis>true</emphasis>, the context
+remembers strings/placeholders saved by dynamic rules. This is needed for HERE
+documents for example. Default: <emphasis>false</emphasis>.</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>The element <userinput>itemData</userinput> is in the group
+<userinput>itemDatas</userinput>. It defines the font style and colors.
+So it is possible to define your own styles and colors, however we
+recommend to stick to the default styles if possible so that the user
+will always see the same colors used in different languages. Though,
+sometimes there is no other way and it is necessary to change color
+and font attributes. The attributes name and defStyleNum are required,
+the other optional. Available attributes are:</term>
+
+<listitem>
+<para><userinput>name</userinput> sets the name of the itemData.
+Contexts and rules will use this name in their attribute
+<emphasis>attribute</emphasis> to reference an itemData.</para>
+<para><userinput>defStyleNum</userinput> defines which default style to use.
+Available default styles are explained in detail later.</para>
+<para><userinput>color</userinput> defines a color. Valid formats are
+'#rrggbb' or '#rgb'.</para>
+<para><userinput>selColor</userinput> defines the selection color.</para>
+<para><userinput>italic</userinput> if <emphasis>true</emphasis>, the text will be italic.</para>
+<para><userinput>bold</userinput> if <emphasis>true</emphasis>, the text will be bold.</para>
+<para><userinput>underline</userinput> if <emphasis>true</emphasis>, the text will be underlined.</para>
+<para><userinput>strikeout</userinput> if <emphasis>true</emphasis>, the text will be stroked out.</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>The element <userinput>keywords</userinput> in the group
+<userinput>general</userinput> defines keyword properties. Available attributes are:</term>
+
+<listitem>
+<para><userinput>casesensitive</userinput> may be <emphasis>true</emphasis>
+or <emphasis>false</emphasis>. If <emphasis>true</emphasis>, all keywords
+are matched casesensitive</para>
+<para><userinput>weakDeliminator</userinput> is a list of characters that
+do not act as word delimiters. For example the dot <userinput>'.'</userinput>
+is a word delimiter. Assume a keyword in a <userinput>list</userinput> contains
+a dot, it will only match if you specify the dot as a weak delimiter.</para>
+<para><userinput>additionalDeliminator</userinput> defines additional delimiters.</para>
+<para><userinput>wordWrapDeliminator</userinput> defines characters after which a
+line wrap may occur.</para>
+<para>Default delimiters and word wrap delimiters are the characters
+<userinput>.():!+,-&lt;=&gt;%&amp;*/;?[]^{|}~\</userinput>, space (<userinput>' '</userinput>)
+and tabulator (<userinput>'\t'</userinput>).</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>The element <userinput>comment</userinput> in the group
+<userinput>comments</userinput> defines comment properties which are used
+for <menuchoice><guimenu>Tools</guimenu><guimenuitem>Comment</guimenuitem></menuchoice> and
+<menuchoice><guimenu>Tools</guimenu><guimenuitem>Uncomment</guimenuitem></menuchoice>.
+Available attributes are:</term>
+
+<listitem>
+<para><userinput>name</userinput> is either <emphasis>singleLine</emphasis>
+or <emphasis>multiLine</emphasis>. If you choose <emphasis>multiLine</emphasis>
+the attributes <emphasis>end</emphasis> and <emphasis>region</emphasis> are
+required.</para>
+<para><userinput>start</userinput> defines the string used to start a comment.
+In C++ this would be &quot;/*&quot;.</para>
+<para><userinput>end</userinput> defines the string used to close a comment.
+In C++ this would be &quot;*/&quot;.</para>
+<para><userinput>region</userinput> should be the name of the the foldable
+multiline comment. Assume you have <emphasis>beginRegion="Comment"</emphasis>
+... <emphasis>endRegion="Comment"</emphasis> in your rules, you should use
+<emphasis>region="Comment"</emphasis>. This way uncomment works even if you
+do not select all the text of the multiline comment. The cursor only must be
+in the multiline comment.</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>The element <userinput>folding</userinput> in the group
+<userinput>general</userinput> defines code folding properties.
+Available attributes are:</term>
+
+<listitem>
+<para><userinput>indentationsensitive</userinput> if <emphasis>true</emphasis>, the code folding markers
+will be added indentation based, like in the scripting language Python. Usually you
+do not need to set it, as it defaults to <emphasis>false</emphasis>.</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>The element <userinput>indentation</userinput> in the group
+<userinput>general</userinput> defines which indenter will be used, however we strongly
+recommend to omit this element, as the indenter usually will be set by either defining
+a File Type or by adding a mode line to the text file. If you specify an indenter though,
+you will force a specific indentation on the user, which he might not like at all.
+Available attributes are:</term>
+
+<listitem>
+<para><userinput>mode</userinput> is the name of the indenter. Available indenters
+right now are: <emphasis>normal, cstyle, csands, xml, python</emphasis> and
+<emphasis>varindent</emphasis>.</para>
+</listitem>
+</varlistentry>
+
+
+</variablelist>
+
+
+</sect2>
+
+<sect2 id="kate-highlight-default-styles">
+<title>Available Default Styles</title>
+<para>Default Styles were <link linkend="kate-highlight-system-default-styles">already explained</link>,
+as a short summary: Default styles are predefined font and color styles.</para>
+<variablelist>
+<varlistentry>
+<term>So here only the list of available default styles:</term>
+<listitem>
+<para><userinput>dsNormal</userinput>, used for normal text.</para>
+<para><userinput>dsKeyword</userinput>, used for keywords.</para>
+<para><userinput>dsDataType</userinput>, used for data types.</para>
+<para><userinput>dsDecVal</userinput>, used for decimal values.</para>
+<para><userinput>dsBaseN</userinput>, used for values with a base other than 10.</para>
+<para><userinput>dsFloat</userinput>, used for float values.</para>
+<para><userinput>dsChar</userinput>, used for a character.</para>
+<para><userinput>dsString</userinput>, used for strings.</para>
+<para><userinput>dsComment</userinput>, used for comments.</para>
+<para><userinput>dsOthers</userinput>, used for 'other' things.</para>
+<para><userinput>dsAlert</userinput>, used for warning messages.</para>
+<para><userinput>dsFunction</userinput>, used for function calls.</para>
+<para><userinput>dsRegionMarker</userinput>, used for region markers.</para>
+<para><userinput>dsError</userinput>, used for error highlighting and wrong syntax.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+</sect2>
+
+</sect1>
+
+<sect1 id="kate-highlight-rules-detailled">
+<title>Highlight Detection Rules</title>
+
+<para>This section describes the syntax detection rules.</para>
+
+<para>Each rule can match zero or more characters at the beginning of
+the string they are test against. If the rule matches, the matching
+characters are assigned the style or <emphasis>attribute</emphasis>
+defined by the rule, and a rule may ask that the current context is
+switched.</para>
+
+<para>A rule looks like this:</para>
+
+<programlisting>&lt;RuleName attribute=&quot;(identifier)&quot; context=&quot;(identifier)&quot; [rule specific attributes] /&gt;</programlisting>
+
+<para>The <emphasis>attribute</emphasis> identifies the style to use
+for matched characters by name, and the <emphasis>context</emphasis>
+identifies the context to use from here.</para>
+
+<para>The <emphasis>context</emphasis> can be identified by:</para>
+
+<itemizedlist>
+<listitem>
+<para>An <emphasis>identifier</emphasis>, which is the name of the other
+context.</para>
+</listitem>
+<listitem>
+<para>An <emphasis>order</emphasis> telling the engine to stay in the
+current context (<userinput>#stay</userinput>), or to pop back to a
+previous context used in the string (<userinput>#pop</userinput>).</para>
+<para>To go back more steps, the #pop keyword can be repeated:
+<userinput>#pop#pop#pop</userinput></para>
+</listitem>
+</itemizedlist>
+
+<para>Some rules can have <emphasis>child rules</emphasis> which are
+then evaluated only if the parent rule matched. The entire matched
+string will be given the attribute defined by the parent rule. A rule
+with child rules looks like this:</para>
+
+<programlisting>
+&lt;RuleName (attributes)&gt;
+ &lt;ChildRuleName (attributes) /&gt;
+ ...
+&lt;/RuleName&gt;
+</programlisting>
+
+
+<para>Rule specific attributes varies and are described in the
+following sections.</para>
+
+
+<itemizedlist>
+<title>Common attributes</title>
+<para>All rules have the following attributes in common and are
+available whenever <userinput>(common attributes)</userinput> appears.
+<emphasis>attribute</emphasis> and <emphasis>context</emphasis>
+are required attributes, all others are optional.
+</para>
+
+<listitem>
+<para><emphasis>attribute</emphasis>: An attribute maps to a defined <emphasis>itemData</emphasis>.</para>
+</listitem>
+<listitem>
+<para><emphasis>context</emphasis>: Specify the context to which the highlighting system switches if the rule matches.</para>
+</listitem>
+<listitem>
+<para><emphasis>beginRegion</emphasis>: Start a code folding block. Default: unset.</para>
+</listitem>
+<listitem>
+<para><emphasis>endRegion</emphasis>: Close a code folding block. Default: unset.</para>
+</listitem>
+<listitem>
+<para><emphasis>lookAhead</emphasis>: If <emphasis>true</emphasis>, the
+highlighting system will not process the matches length.
+Default: <emphasis>false</emphasis>.</para>
+</listitem>
+<listitem>
+<para><emphasis>firstNonSpace</emphasis>: Match only, if the string is
+the first non-whitespace in the line. Default: <emphasis>false</emphasis>.</para>
+</listitem>
+<listitem>
+<para><emphasis>column</emphasis>: Match only, if the column matches. Default: unset.</para>
+</listitem>
+</itemizedlist>
+
+<itemizedlist>
+<title>Dynamic rules</title>
+<para>Some rules allow the optional attribute <userinput>dynamic</userinput>
+of type boolean that defaults to <emphasis>false</emphasis>. If dynamic is
+<emphasis>true</emphasis>, a rule can use placeholders representing the text
+matched by a <emphasis>regular expression</emphasis> rule that switched to the
+current context in its <userinput>string</userinput> or
+<userinput>char</userinput> attributes. In a <userinput>string</userinput>,
+the placeholder <replaceable>%N</replaceable> (where N is a number) will be
+replaced with the corresponding capture <replaceable>N</replaceable>
+from the calling regular expression. In a
+<userinput>char</userinput> the placeholer must be a number
+<replaceable>N</replaceable> and it will be replaced with the first character of
+the corresponding capture <replaceable>N</replaceable> from the calling regular
+expression. Whenever a rule allows this attribute it will contain a
+<emphasis>(dynamic)</emphasis>.</para>
+
+<listitem>
+<para><emphasis>dynamic</emphasis>: may be <emphasis>(true|false)</emphasis>.</para>
+</listitem>
+</itemizedlist>
+
+<sect2 id="highlighting-rules-in-detail">
+<title>The Rules in Detail</title>
+
+<variablelist>
+<varlistentry>
+<term>DetectChar</term>
+<listitem>
+<para>Detect a single specific character. Commonly used for example to
+find the ends of quoted strings.</para>
+<programlisting>&lt;DetectChar char=&quot;(character)&quot; (common attributes) (dynamic) /&gt;</programlisting>
+<para>The <userinput>char</userinput> attribute defines the character
+to match.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Detect2Chars</term>
+<listitem>
+<para>Detect two specific characters in a defined order.</para>
+<programlisting>&lt;Detect2Chars char=&quot;(character)&quot; char1=&quot;(character)&quot; (common attributes) (dynamic) /&gt;</programlisting>
+<para>The <userinput>char</userinput> attribute defines the first character to match,
+<userinput>char1</userinput> the second.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>AnyChar</term>
+<listitem>
+<para>Detect one character of a set of specified characters.</para>
+<programlisting>&lt;AnyChar String=&quot;(string)&quot; (common attributes) /&gt;</programlisting>
+<para>The <userinput>String</userinput> attribute defines the set of
+characters.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>StringDetect</term>
+<listitem>
+<para>Detect an exact string.</para>
+<programlisting>&lt;StringDetect String=&quot;(string)&quot; [insensitive=&quot;true|false&quot;] (common attributes) (dynamic) /&gt;</programlisting>
+<para>The <userinput>String</userinput> attribute defines the string
+to match. The <userinput>insensitive</userinput> attribute defaults to
+<emphasis>false</emphasis> and is passed to the string comparison
+function. If the value is <emphasis>true</emphasis> insensitive
+comparing is used.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>RegExpr</term>
+<listitem>
+<para>Matches against a regular expression.</para>
+<programlisting>&lt;RegExpr String=&quot;(string)&quot; [insensitive=&quot;true|false&quot;] [minimal=&quot;true|false&quot;] (common attributes) (dynamic) /&gt;</programlisting>
+<para>The <userinput>String</userinput> attribute defines the regular
+expression.</para>
+<para><userinput>insensitive</userinput> defaults to
+<emphasis>false</emphasis> and is passed to the regular expression
+engine.</para>
+<para><userinput>minimal</userinput> defaults to
+<emphasis>false</emphasis> and is passed to the regular expression
+engine.</para>
+<para>Because the rules are always matched against the beginning of
+the current string, a regular expression starting with a caret
+(<literal>^</literal>) indicates that the rule should only be
+matched against the start of a line.</para>
+<para>See <link linkend="regular-expressions">Regular Expressions</link>
+for more information on those.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>keyword</term>
+<listitem>
+<para>Detect a keyword from a specified list.</para>
+<programlisting>&lt;keyword String=&quot;(list name)&quot; (common attributes) /&gt;</programlisting>
+<para>The <userinput>String</userinput> attribute identifies the
+keyword list by name. A list with that name must exist.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Int</term>
+<listitem>
+<para>Detect an integer number.</para>
+<para><programlisting>&lt;Int (common attributes) (dynamic) /&gt;</programlisting></para>
+<para>This rule has no specific attributes. Child rules are typically
+used to detect combinations of <userinput>L</userinput> and
+<userinput>U</userinput> after the number, indicating the integer type
+in program code. Actually all rules are allowed as child rules, though,
+the <acronym>DTD</acronym> only allowes the child rule <userinput>StringDetect</userinput>.</para>
+<para>The following example matches integer numbers follows by the character 'L'.
+<programlisting>
+&lt;Int attribute="Decimal" context="#stay" &gt;
+ &lt;StringDetect attribute="Decimal" context="#stay" String="L" insensitive="true"/&gt;
+&lt;/Int&gt;
+</programlisting></para>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>Float</term>
+<listitem>
+<para>Detect a floating point number.</para>
+<para><programlisting>&lt;Float (common attributes) /&gt;</programlisting></para>
+<para>This rule has no specific attributes. <userinput>AnyChar</userinput> is
+allowed as a child rules and typically used to detect combinations, see rule
+<userinput>Int</userinput> for reference.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>HlCOct</term>
+<listitem>
+<para>Detect an octal point number representation.</para>
+<para><programlisting>&lt;HlCOct (common attributes) /&gt;</programlisting></para>
+<para>This rule has no specific attributes.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>HlCHex</term>
+<listitem>
+<para>Detect a hexadecimal number representation.</para>
+<para><programlisting>&lt;HlCHex (common attributes) /&gt;</programlisting></para>
+<para>This rule has no specific attributes.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>HlCStringChar</term>
+<listitem>
+<para>Detect an escaped character.</para>
+<para><programlisting>&lt;HlCStringChar (common attributes) /&gt;</programlisting></para>
+<para>This rule has no specific attributes.</para>
+
+<para>It matches literal representations of characters commonly used in
+program code, for example <userinput>\n</userinput>
+(newline) or <userinput>\t</userinput> (TAB).</para>
+
+<para>The following characters will match if they follow a backslash
+(<literal>\</literal>):
+<userinput>abefnrtv&quot;'?\</userinput>. Additionally, escaped
+hexadecimal numbers like for example <userinput>\xff</userinput> and
+escaped octal numbers, for example <userinput>\033</userinput> will
+match.</para>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>HlCChar</term>
+<listitem>
+<para>Detect an C character.</para>
+<para><programlisting>&lt;HlCChar (common attributes) /&gt;</programlisting></para>
+<para>This rule has no specific attributes.</para>
+
+<para>It matches C characters enclosed in a tick (Example: <userinput>'c'</userinput>).
+So in the ticks may be a simple character or an escaped character.
+See HlCStringChar for matched escaped character sequences.</para>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>RangeDetect</term>
+<listitem>
+<para>Detect a string with defined start and end characters.</para>
+<programlisting>&lt;RangeDetect char=&quot;(character)&quot; char1=&quot;(character)&quot; (common attributes) /&gt;</programlisting>
+<para><userinput>char</userinput> defines the character starting the range,
+<userinput>char1</userinput> the character ending the range.</para>
+<para>Usefull to detect for example small quoted strings and the like, but
+note that since the highlighting engine works on one line at a time, this
+will not find strings spanning over a line break.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>LineContinue</term>
+<listitem>
+<para>Matches at end of line.</para>
+<programlisting>&lt;LineContinue (common attributes) /&gt;</programlisting>
+<para>This rule has no specific attributes.</para>
+<para>This rule is useful for switching context at end of line, if the last
+character is a backslash (<userinput>'\'</userinput>). This is needed for
+example in C/C++ to continue macros or strings.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>IncludeRules</term>
+<listitem>
+<para>Include rules from another context or language/file.</para>
+<programlisting>&lt;IncludeRules context=&quot;contextlink&quot; [includeAttrib=&quot;true|false&quot;] /&gt;</programlisting>
+
+<para>The <userinput>context</userinput> attribute defines which context to include.</para>
+<para>If it a simple string it includes all defined rules into the current context, example:
+<programlisting>&lt;IncludeRules context=&quot;anotherContext&quot; /&gt;</programlisting></para>
+
+<para>
+If the string begins with <userinput>##</userinput> the highlight system
+will look for another language definition with the given name, example:
+<programlisting>&lt;IncludeRules context=&quot;##C++&quot; /&gt;</programlisting></para>
+<para>If <userinput>includeAttrib</userinput> attribute is
+<emphasis>true</emphasis>, change the destination attribute to the one of
+the source. This is required to make for example commenting work, if text
+matched by the included context is a different highlight than the host
+context.
+</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>DetectSpaces</term>
+<listitem>
+<para>Detect whitespaces.</para>
+<programlisting>&lt;DetectSpaces (common attributes) /&gt;</programlisting>
+
+<para>This rule has no specific attributes.</para>
+<para>Use this rule if you know that there can several whitespaces ahead,
+for example in the beginning of indented lines. This rule will skip all
+whitespace at once, instead of testing multiple rules and skipping one at the
+time due to no match.</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>DetectIdentifier</term>
+<listitem>
+<para>Detect identifier strings (as a regular expression: [a-zA-Z_][a-zA-Z0-9_]*).</para>
+<programlisting>&lt;DetectIdentifier (common attributes) /&gt;</programlisting>
+
+<para>This rule has no specific attributes.</para>
+<para>Use this rule to skip a string of word characters at once, rather than
+testing with multiple rules and skipping one at the time due to no match.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+</sect2>
+
+<sect2>
+<title>Tips &amp; Tricks</title>
+
+<itemizedlist>
+<para>Once you have understood how the context switching works it will be
+easy to write highlight definitions. Though you should carefully check what
+rule you choose in what situation. Regular expressions are very mighty, but
+they are slow compared to the other rules. So you may consider the following
+tips.
+</para>
+
+<listitem>
+<para>If you only match two characters use <userinput>Detect2Chars</userinput>
+instead of <userinput>StringDetect</userinput>. The same applies to
+<userinput>DetectChar</userinput>.</para>
+</listitem>
+<listitem>
+<para>Regular expressions are easy to use but often there is another much
+faster way to achieve the same result. Consider you only want to match
+the character <userinput>'#'</userinput> if it is the first character in the
+line. A regular expression based solution would look like this:
+<programlisting>&lt;RegExpr attribute=&quot;Macro&quot; context=&quot;macro&quot; String=&quot;^\s*#&quot; /&gt;</programlisting>
+You can achieve the same much faster in using:
+<programlisting>&lt;DetectChar attribute=&quot;Macro&quot; context=&quot;macro&quot; char=&quot;#&quot; firstNonSpace=&quot;true&quot; /&gt;</programlisting>
+If you want to match the regular expression <userinput>'^#'</userinput> you
+can still use <userinput>DetectChar</userinput> with the attribute <userinput>column=&quot;0&quot;</userinput>.
+The attribute <userinput>column</userinput> counts character based, so a tabulator still is only one character.
+</para>
+</listitem>
+<listitem>
+<para>You can switch contexts without processing characters. Assume that you
+want to switch context when you meet the string <userinput>*/</userinput>, but
+need to process that string in the next context. The below rule will match, and
+the <userinput>lookAhead</userinput> attribute will cause the highlighter to
+keep the matched string for the next context.
+<programlisting>&lt;Detect2Chars attribute=&quot;Comment&quot; context=&quot;#pop&quot; char=&quot;*&quot; char1=&quot;/&quot; lookAhead=&quot;true&quot; /&gt;</programlisting>
+</para>
+</listitem>
+<listitem>
+<para>Use <userinput>DetectSpaces</userinput> if you know that many whitespaces occur.</para>
+</listitem>
+<listitem>
+<para>Use <userinput>DetectIdentifier</userinput> instead of the regular expression <userinput>'[a-zA-Z_]\w*'</userinput>.</para>
+</listitem>
+<listitem>
+<para>Use default styles whenever you can. This way the user will find a familiar environment.</para>
+</listitem>
+<listitem>
+<para>Look into other XML-files to see how other people implement tricky rules.</para>
+</listitem>
+<listitem>
+<para>You can validate every XML file by using the command
+<command>xmllint --dtdvalid language.dtd mySyntax.xml</command>.</para>
+</listitem>
+<listitem>
+<para>If you repeat complex regular expression very often you can use
+<emphasis>ENTITIES</emphasis>. Example:</para>
+<programlisting>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!DOCTYPE language SYSTEM "language.dtd"
+[
+ &lt;!ENTITY myref "[A-Za-z_:][\w.:_-]*"&gt;
+]&gt;
+</programlisting>
+<para>Now you can use <emphasis>&amp;myref;</emphasis> instead of the regular
+expression.</para>
+</listitem>
+</itemizedlist>
+</sect2>
+
+</sect1>
+
+</appendix>
diff --git a/doc/kate/index.docbook b/doc/kate/index.docbook
new file mode 100644
index 00000000..fe409a83
--- /dev/null
+++ b/doc/kate/index.docbook
@@ -0,0 +1,293 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
+"dtd/kdex.dtd" [
+ <!ENTITY kappname "&kate;">
+ <!ENTITY package "kdebase">
+ <!ENTITY configuring-chapter SYSTEM "configuring.docbook">
+ <!ENTITY highlighting-appendix SYSTEM "highlighting.docbook">
+ <!ENTITY advanced-chapter SYSTEM "advanced.docbook">
+ <!ENTITY fundamentals-chapter SYSTEM "fundamentals.docbook">
+ <!ENTITY mdi-chapter SYSTEM "mdi.docbook">
+ <!ENTITY menu-chapter SYSTEM "menus.docbook">
+ <!ENTITY part-chapter SYSTEM "part.docbook">
+ <!ENTITY plugins-chapter SYSTEM "plugins.docbook">
+ <!ENTITY regexp-appendix SYSTEM "regular-expressions.docbook">
+ <!ENTITY % addindex "IGNORE">
+ <!ENTITY % English "INCLUDE"><!-- change language only here -->
+]>
+
+<book lang="&language;">
+<title>The &kate; Handbook</title>
+
+<bookinfo>
+<authorgroup>
+<author>&Anders.Lund; &Anders.Lund.mail;</author>
+<author>&Seth.Rothberg; &Seth.Rothberg.mail;</author>
+<author>&Dominik.Haumann; &Dominik.Haumann.mail;</author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+
+<copyright>
+<year>2000</year>
+<year>2001</year>
+<holder>&Seth.Rothberg;</holder>
+</copyright>
+<copyright>
+<year>2002</year><year>2003</year><year>2005</year>
+<holder>&Anders.Lund;</holder>
+</copyright>
+<copyright>
+<year>2005</year>
+<holder>&Dominik.Haumann;</holder>
+</copyright>
+
+<legalnotice>&FDLNotice;</legalnotice>
+
+<date>2005-12-29</date>
+<releaseinfo>2.5.0</releaseinfo>
+
+<abstract>
+<para>&kate; is a programmer's text editor for &kde; 2.2 and above.</para>
+
+<para>This handbook documents &kate; Version 2.5.0</para>
+</abstract>
+
+<keywordset>
+<keyword>KDE</keyword>
+<keyword>kdebase</keyword>
+<keyword>Kate</keyword>
+<keyword>text</keyword>
+<keyword>editor</keyword>
+<keyword>programmer</keyword>
+<keyword>programming</keyword>
+<keyword>projects</keyword>
+<keyword>MDI</keyword>
+<keyword>Multi</keyword>
+<keyword>Document</keyword>
+<keyword>Interface</keyword>
+<keyword>terminal</keyword>
+<keyword>console</keyword>
+</keywordset>
+
+</bookinfo>
+
+<chapter id="introduction">
+<title>Introduction</title>
+
+<para>
+Welcome to &kate;, a programmer's text editor for &kde; version 2.2 and
+above. Some of &kate;'s many features include configurable syntax
+highlighting for languages ranging from C and C++ to
+<acronym>HTML</acronym> to bash scripts, the ability to create and
+maintain projects, a multiple document interface
+(<acronym>MDI</acronym>), and a self-contained terminal emulator.
+</para>
+
+<para>
+But &kate; is more than a programmer's editor. Its ability to open
+several files at once makes it ideal for editing &UNIX;'s many
+configuration files. This document was written in &kate;.
+</para>
+
+<para>
+<mediaobject>
+<imageobject><imagedata format="PNG" fileref="kate.png"/></imageobject>
+<caption><para>Editing this manual...</para></caption>
+</mediaobject>
+</para>
+
+</chapter>
+
+&fundamentals-chapter;
+
+&mdi-chapter;
+
+&part-chapter;
+
+&plugins-chapter;
+
+&advanced-chapter;
+
+&menu-chapter;
+
+&configuring-chapter;
+
+<chapter id="credits">
+
+<title>Credits and License</title>
+
+<para>
+&kate;. Program copyright 2000, 2001, 2002 - 2005 by the &kate; developer team.
+</para>
+
+<variablelist>
+<title>The &kate; team:</title>
+<varlistentry>
+<term>&Christoph.Cullmann; &Christoph.Cullmann.mail;</term>
+<listitem><para>Project Manager &amp; Core Developer</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Anders.Lund; &Anders.Lund.mail;</term>
+<listitem><para>Core Developer, Perl syntax highlighting,
+documentation</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Joseph.Wenninger; &Joseph.Wenninger.mail;</term>
+<listitem><para>Core Developer, syntax highlighting</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Michael Bartl <email>michael.bartl1@chello.at</email></term>
+<listitem><para>Core Developer</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Phlip <email>phlip_cpp@my-deja.com</email></term>
+<listitem><para>The project compiler</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Waldo.Bastian; &Waldo.Bastian.mail;</term>
+<listitem><para>The cool buffer system</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Matt Newell <email>newellm@proaxis.com</email></term>
+<listitem><para>Testing...</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Michael McCallum <email>gholam@xtra.co.nz</email></term>
+<listitem><para>Core Developer</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Jochen Wilhemly <email>digisnap@cs.tu-berlin.de</email></term>
+<listitem><para>KWrite Author</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Michael.Koch; &Michael.Koch.mail;</term>
+<listitem><para>KWrite port to KParts</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Christian Gebauer <email>gebauer@bigfoot.com</email></term>
+<listitem><para>Unspecified</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Simon.Hausmann; &Simon.Hausmann.mail;</term>
+<listitem><para>Unspecified</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Glen Parker <email>glenebob@nwlink.com</email></term>
+<listitem><para>KWrite Undo History, KSpell integration</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Scott Manson <email>sdmanson@alltel.net</email></term>
+<listitem><para>KWrite XML syntax highlighting support</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&John.Firebaugh; &John.Firebaugh.mail;</term>
+<listitem><para>Various Patches</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Dominik.Haumann; &Dominik.Haumann.mail;</term>
+<listitem><para>Developer, Highlight wizard</para></listitem>
+</varlistentry>
+</variablelist>
+
+<variablelist>
+<title>Many other people have contributed:</title>
+<varlistentry>
+<term>Matteo Merli <email>merlim@libero.it</email></term>
+<listitem><para>Highlighting for RPM Spec-Files, Diff and more</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Rocky Scaletta <email>rocky@purdue.edu</email></term>
+<listitem><para>Highlighting for VHDL</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Yury Lebedev </term>
+<listitem><para>Highlighting for SQL</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Chris Ross</term>
+<listitem><para>Highlighting for Ferite</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Nick Roux</term>
+<listitem><para>Highlighting for ILERPG</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>John Firebaugh</term>
+<listitem><para>Highlighting for Java, and much more</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Carsten Niehaus</term>
+<listitem><para>Highlighting for LaTeX</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Per Wigren</term>
+<listitem><para>Highlighting for Makefiles, Python</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>Jan Fritz</term>
+<listitem><para>Highlighting for Python</para></listitem>
+</varlistentry>
+<varlistentry>
+<term>&Daniel.Naber;</term>
+<listitem><para>Small bugfixes, XML plugin</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>Documentation copyright 2000,2001 &Seth.Rothberg;
+&Seth.Rothberg.mail;</para>
+
+<para>Documentation copyright 2002, 2003, 2005 &Anders.Lund;
+&Anders.Lund.mail;</para>
+
+<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
+
+&underFDL; <!-- FDL: do not remove -->
+&underGPL; <!-- GPL License -->
+
+</chapter>
+
+&highlighting-appendix;
+
+&regexp-appendix;
+
+<appendix id="installation">
+<title>Installation</title>
+
+&install.intro.documentation;
+
+&install.compile.documentation;
+
+</appendix>
+
+&documentation.index;
+
+<!--
+Index Word List:
+menu - context - syntax - markup - shortcuts - highlighting
+embedded terminal - editing - search - replace - regexp -> Regular Expression
+split window - selection - insert overwrite - selection -
+configure/customize/preferences - insert/overwrite - non-printing characters
+font - unicode - wordwrap/linewrap - project - bookmarks - docks - plugins
+block selection / rectangles - view - indenting - editor - word processor
+copy - paste - find - spelling - language (both kinds) - encoding -
+pretty printing - formatting - line numbers - icon border -
+folding - insert time - sed
+
+done
+comment / uncomment
+configure / settings / preferences
+
+-->
+
+</book>
+
+<!--
+Local Variables:
+mode: sgml
+sgml-namecase-general: t
+sgml-namecase-entity: nil
+sgml-general-insert-case: lower
+sgml-minimize-attributes: nil
+sgml-omittag: nil
+End:
+-->
diff --git a/doc/kate/kate.png b/doc/kate/kate.png
new file mode 100644
index 00000000..dc1ee4c4
--- /dev/null
+++ b/doc/kate/kate.png
Binary files differ
diff --git a/doc/kate/man-kate.1.docbook b/doc/kate/man-kate.1.docbook
new file mode 100644
index 00000000..80899a4f
--- /dev/null
+++ b/doc/kate/man-kate.1.docbook
@@ -0,0 +1,165 @@
+<?xml version="1.0" ?>
+<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
+<!ENTITY % English "INCLUDE">
+]>
+
+<refentry lang="&language;">
+<refentryinfo>
+<title>KDE User's Manual</title>
+<author>&Lauri.Watts; &Lauri.Watts.mail;</author>
+<date>June 07, 2005</date>
+<productname>K Desktop Environment</productname>
+</refentryinfo>
+
+<refmeta>
+<refentrytitle><command>kate</command></refentrytitle>
+<manvolnum>1</manvolnum>
+</refmeta>
+
+<refnamediv>
+<refname><command>kate</command></refname>
+<refpurpose>Advanced text editor for &kde;</refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+<cmdsynopsis>
+<command>kate</command>
+<group choice="opt"><option>-s, --start</option> <replaceable>
+name</replaceable> </group>
+<group choice="opt"><option>-u, --use</option></group>
+<group choice="opt"><option>-p, --pid</option><replaceable>
+pid</replaceable></group>
+<group choice="opt"><option>-e, --encoding</option> <replaceable>
+name</replaceable></group>
+<group choice="opt"><option>-l, --line</option> <replaceable>
+line</replaceable></group>
+<group choice="opt"><option>-c, --column</option>
+<replaceable> column</replaceable></group>
+<group choice="opt"><option>-i, --stdin</option></group>
+<arg choice="opt">KDE Generic Options</arg>
+<arg choice="opt">Qt Generic Options</arg>
+</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+<title>Description</title>
+<para>&kate; is the &kde; Advanced Text Editor. </para>
+<para>&kate; also provides the editor part for various applications, under
+the name &kwrite;.</para>
+<para>Some of &kate;'s many features include configurable syntax
+highlighting for languages ranging from C and C++ to
+<acronym>HTML</acronym> to bash scripts, the ability to create and
+maintain projects, a multiple document interface
+(<acronym>MDI</acronym>), and a self-contained terminal emulator.
+</para>
+
+<para>
+But &kate; is more than a programmer's editor. Its ability to open
+several files at once makes it ideal for editing &UNIX;'s many
+configuration files. This document was written in &kate;.
+</para>
+
+
+</refsect1>
+
+<refsect1>
+<title>Options</title>
+
+<variablelist>
+<varlistentry>
+<term><option>-s</option>, <option>--start</option> <replaceable>name</replaceable></term>
+
+<listitem><para>Start &kate; with a given session.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><option>-u, --use</option></term>
+<listitem><para>Use an already running &kate;</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><option>-p, --pid</option> <replaceable>
+pid</replaceable></term>
+<listitem><para>Only try to reuse kate instance with this
+<replaceable>pid</replaceable></para></listitem>
+</varlistentry>
+<varlistentry>
+<term><option>-e, --encoding</option> <replaceable>
+name</replaceable></term>
+<listitem><para>Set encoding for the file to open</para><para>You can use
+this to force a file opened in utf-8 format, for instance. (The command
+<command>iconv -l</command> provides a list of encodings, which may be
+helpful to you.)</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><option>-l, --line</option> <replaceable> line</replaceable></term>
+<listitem><para>Navigate to this line</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><option>-c, --column</option> <replaceable>
+column</replaceable></term>
+<listitem><para>Navigate to this column</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><option>-i, --stdin</option></term>
+<listitem><para>Read the contents of
+<filename>stdin</filename></para></listitem>
+</varlistentry>
+</variablelist>
+
+</refsect1>
+
+<refsect1>
+<title>See Also</title>
+
+<para>kwrite(1)</para>
+
+<para>More detailed user documentation is available from <ulink
+url="help:/kate">help:/kate</ulink>
+(either enter this <acronym>URL</acronym> into &konqueror;, or run
+<userinput><command>khelpcenter</command>
+<parameter>help:/kate</parameter></userinput>).</para>
+
+<para>There is also further information available at <ulink
+url="http://kate.kde.org/">the &kate; website</ulink>.</para>
+</refsect1>
+
+<refsect1>
+<title>Examples</title>
+
+<para>To open a file named <filename>source.cpp</filename> at column 15,
+line 25, in an existing &kate; window, you could use:</para>
+<screen><userinput><command>kate</command> <option>-c 15</option> <option>-l
+25</option> <option>-u</option> <filename>source.cpp</filename></userinput> </screen>
+
+<para>If you have an active internet connection, you can take advantage of
+&kde;'s network transparency to open a file from an ftp site. If you do not
+have write permission on the remote server, the file will be opened read
+only and you will be prompted for a local filename to save to if you make
+changes. If you do have write permission, changes will be saved
+transparently over the network.</para>
+<screen><userinput><command>kate</command> <option><replaceable>ftp://ftp.kde.org/pub/kde/README_FIRST</replaceable></option></userinput></screen>
+
+<!-- FIXME: Some more useful examples would be cool, how about this snagged -->
+<!-- from a mail of anders (slightly edited /line/l to remove the double -->
+<!-- dashes:
+
+> /some/file/path/file.name:lineno
+> it would rock if Kate could understand that and not only open up file.name,
+> but jump to lineno after the file is opened.
+
+How bad is it to have to convert that into
+-l lineno /some/file/path/file.name
+
+sed s,([^:]*):(\d+),-l \2 \1,
+
+will do that, for example.-->
+
+</refsect1>
+
+<refsect1>
+<title>Authors</title>
+<para>The maintainer of &kate; is &Christoph.Cullmann;
+&Christoph.Cullmann.mail;. A comprehensive list of authors and contributors
+is available in the complete user manual mentioned above.</para>
+</refsect1>
+
+</refentry>
diff --git a/doc/kate/mdi.docbook b/doc/kate/mdi.docbook
new file mode 100644
index 00000000..a6c6854d
--- /dev/null
+++ b/doc/kate/mdi.docbook
@@ -0,0 +1,266 @@
+<chapter id="kate-mdi">
+<chapterinfo>
+<authorgroup>
+<author>&Anders.Lund; &Anders.Lund.mail;</author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</chapterinfo>
+<title>Working With the &kate; <acronym>MDI</acronym></title>
+
+<sect1 id="kate-mdi-overview">
+<title>Overview</title>
+
+<para>Window, View, Document, Frame, Editor... What are they all in
+the terminology of &kate;, and how do you get the most out of it? This
+chapter will explain all of that, and even more.</para>
+
+<sect2 id="kate-mdi-overview-mainwindow">
+
+<title>The Main Window</title>
+
+<para><indexterm><primary>Main window</primary></indexterm>
+The &kate; Main Window is a standard &kde; application window,
+with the addition of side bars containing tool views. It has a
+Menubar with all the common menus, and some more, and a toolbar
+providing access to commonly used commands.</para>
+
+<para>The most important part of the window is the Editing Area, by
+default displaying a single text editor component, in which you can
+work with your documents.</para>
+
+<para>The docking capabilities of the window is used for the tool
+windows:</para>
+
+<itemizedlist>
+<listitem><para><link linkend="kate-mdi-tools-file-list">The File List</link></para></listitem>
+<listitem><para><link linkend="kate-mdi-tools-file-selector">The Filesystem
+Browser</link></para></listitem>
+<listitem><para><link linkend="kate-mdi-tools-konsole">The Built in Terminal Emulator</link></para></listitem>
+</itemizedlist>
+
+<para>And possibly other tool views, for example provided by
+plugins.</para>
+
+<para>Tool views can be positioned in any sidebar, to move a tool right click
+its sidebar button and select from the &RMB; menu</para>
+
+<para>A tool view can be marked as <emphasis>persistent</emphasis> in the &RMB;
+menu for its sidebar button. The sidebar can contain
+more tools at one time so that when a tool is persistant other tools can be
+shown simultaneously.</para>
+
+</sect2>
+
+
+</sect1>
+
+<sect1 id="kate-mdi-editor">
+
+<title>The Editor area</title>
+
+<para><indexterm><primary>Editing Area</primary></indexterm>
+&kate; is capable of having more than one document open at the
+same time, and also of splitting the editing area into any number of
+frames, similar to how for example &konqueror; or the popular
+<application>emacs</application> text editor works. This way you can
+view several documents at the same time, or more instances of the same
+document, handy for example if your document contains definitions in
+the top that you want to see often for reference. Or you could view a
+program source header in one frame, while editing the implementation
+file in another.</para>
+
+<para>When a document is available in more than one editor, changes
+made in one editor will immediately be reflected in the others as
+well. This includes changing the text as well as selecting
+text. Search operations or cursor movement is only reflected in the
+current editor.</para>
+
+<para>It is currently not possible to have more instances of the same
+document open in the sense that one instance will be edited while the
+other will not.</para>
+
+<para>When splitting an editor into two frames, it is divided into two
+equally sized frames, both displaying the current document of that
+editor. The new frame will be at the bottom (in the case of a
+horizontal split) or at the right (for a vertical split). The new
+frame gets the focus, which is visualized by a small green led in the
+focused frame.</para>
+
+</sect1>
+
+<sect1 id="kate-mdi-tools-file-list">
+<title>The Document List</title>
+
+<para><indexterm><primary>File list</primary></indexterm>
+The file list displays a list of all documents currently open in
+&kate;. Modified files will have a small <guiicon>floppy
+disk</guiicon> icon on their left to indicate that state.</para>
+
+<para>If two or more files with the same name (located in different
+folders) are open, the names of the second will be prepended
+<quote>&lt;2&gt;</quote> and so on. The tool-tip for the file will
+display its full name including the path, allowing you to choose the
+desired one.</para> <para>To display a document in the currently
+active frame, click the document name in the list.</para>
+
+<para>You can sort the list in a few different ways by rightclicking the
+list and selecting from the <guisubmenu>Sort By</guisubmenu> menu.
+
+The options are
+<variablelist>
+
+<varlistentry>
+<term><guimenuitem>Opening Order</guimenuitem></term>
+<listitem><para>Lists the documents in the order of opening</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guimenuitem>Document Name</guimenuitem></term>
+<listitem><para>Lists the documents alphabetically by their name.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guimenuitem>URL</guimenuitem></term>
+<listitem><para>Lists the documents alphabetically by URL.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</para>
+
+<para>The document list will pr default visualize your history by shading the
+entries for the most recent documents with a background color. If the document
+was edited, an extra color is blended in. The most recent document has the
+strongest color, so that you can easily find the documents you are working on.
+This feature can be disabled in
+<link linkend="config-dialog-documentlist">The Document List Page</link>
+of the configuration dialog.</para>
+
+<para>The default location in the &kate; window is to the left of the
+editing area.</para>
+</sect1>
+
+<sect1 id="kate-mdi-tools-file-selector">
+<title>The Filesystem Browser</title>
+
+<para><indexterm><primary>Filesystem Browser</primary></indexterm>
+The Filesystem Browser is a folder viewer, allowing you to open
+files from a displayed folder in the current frame.</para>
+
+<para>From top down, the Filesystem Browser consist of the following
+elements:</para>
+
+<variablelist>
+<varlistentry>
+<term>A Toolbar</term>
+<listitem>
+<para>This contains standard navigations tool buttons:</para>
+<variablelist>
+<varlistentry>
+<term><guibutton>Home</guibutton></term>
+<listitem><para>Pressing it will cause the folder view to <command>cd</command> to your home folder.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Up</guibutton></term>
+<listitem><para>This will cause the folder view to <command>cd</command> to the immediate parent of the currently displayed
+folder if possible.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Back</guibutton></term>
+<listitem><para>Causes the folder view to <command>cd</command> to the previously displayed folder in the history.
+This button is disabled, if there is no previous item.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Forward</guibutton></term>
+<listitem><para>Causes the folder view to <command>cd</command> to the next folder in the history.
+This button is disabled, if there is no next folder.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Sync</guibutton></term>
+<listitem><para>This button will cause the folder view to
+<command>cd</command> to the folder of the currently active
+document if possible. This button is disabled, if the active document
+is a new, unsaved file, or the folder in which it resides can not
+be decided.</para></listitem>
+</varlistentry>
+</variablelist>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>A &URL; entry</term>
+<listitem>
+<para>Here you can type the path of a folder to browse. The &URL;
+entry maintains a list of previously typed paths. To choose one use
+the arrow button to the right of the entry.</para>
+<tip><para>The &URL; entry has folder auto-completion. The completion
+method can be set using the &RMB; menu of the text
+entry.</para></tip>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>A Folder View</term>
+<listitem><para>This is a standard &kde; folder view.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>A Filter Entry</term>
+<listitem>
+<para>The Filter entry allows you to enter a filter for the files
+displayed in the folder view. The filter uses standard globs; patterns
+must be separated by white space. Example: <userinput>*.cpp *.h
+*.moc</userinput></para>
+<para>To display all files, enter a single asterisk
+<userinput>*</userinput>.</para>
+<para>The filter entry saves the last 10 filters entered between
+sessions, to use one, press the arrow button on the right of the entry
+and select the desired filter string.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+
+<sect1 id="kate-mdi-tools-konsole">
+<title>The Built in Terminal Emulator</title>
+
+<para><indexterm><primary>Terminal emulator</primary></indexterm>
+The built in Terminal Emulator is a copy of the &kde; &konsole;
+terminal application, for your convenience. It is available from the
+<menuchoice><guimenu>Settings</guimenu><guimenuitem>Show Terminal
+Emulator</guimenuitem></menuchoice> menu item or by pressing the <keycombo
+action="simul"><keycap>F7</keycap></keycombo> key, and will get the focus
+whenever displayed. Additionally, if the <link
+linkend="config-dialog-general-sync-konsole">Sync &konsole; with
+active document</link> option is enabled, it will
+change into the directory of the current document if
+possible when it is displayed, or when the current document
+changes.</para>
+
+<para>The default location in the &kate; window is at the bottom,
+below the editing area.</para>
+
+<para>You can configure the &konsole; using its &RMB; menu, for more
+information, see the &konsole; manual.</para>
+
+</sect1>
+
+<sect1 id="kate-mdi-tools-externaltools">
+<title>External Tools</title>
+
+<para>In the <guimenu>Tools</guimenu> menu you will find a submenu labeled
+<guisubmenu>External Tools</guisubmenu>. These tools invokes external
+applications with data related to the current document, for example its URL,
+directory, text or selection.</para>
+
+<para>External tools are user defined, you can add, edit or remove tools using
+the <link linkend="config-dialog-externaltools">External Tools configuration panel</link>.
+</para>
+
+</sect1>
+
+</chapter>
diff --git a/doc/kate/menus.docbook b/doc/kate/menus.docbook
new file mode 100644
index 00000000..26ae7551
--- /dev/null
+++ b/doc/kate/menus.docbook
@@ -0,0 +1,1438 @@
+<chapter id="menu-entries">
+<chapterinfo>
+<authorgroup>
+<author><personname><firstname></firstname></personname></author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</chapterinfo>
+<title>Menu Entries</title>
+
+<sect1 id="file-menu">
+<title>The <guimenu>File</guimenu> Menu</title>
+
+<variablelist>
+<varlistentry>
+<term>
+<anchor id="new"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>New</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This command <action>starts a new document</action> in the editing
+window. In the <guibutton>Documents</guibutton> list on the left the new file
+is named <emphasis>Untitled</emphasis>.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="open"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Open...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Launches &kde;'s open file dialog box to let you open one or more files.
+</para>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="open-recent"/>
+<menuchoice>
+<guimenu>File</guimenu>
+<guimenuitem>Open Recent</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This command allows you to <action>open a file</action> from a submenu
+that contains a list of recently edited files.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="open-with"/>
+<menuchoice>
+<guimenu>File</guimenu>
+<guimenuitem>Open With</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This submenu presents a list of applications known to handle the mime type
+of your current document. Activating an entry will open the current document
+with that application.</para>
+<para>In addition, a entry <guimenuitem>Other...</guimenuitem> command launches
+the open with dialog box that allows you to <action>select another application
+to open the active file</action>. Your file will still be open in &kate;.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="save"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>S</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Save</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This command <action>saves your file</action>. Use it often. If the file is
+<emphasis>Untitled</emphasis> then
+<guimenuitem>Save</guimenuitem> becomes
+<guimenuitem>Save As</guimenuitem>.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="save-as"/>
+<menuchoice>
+<guimenu>File</guimenu>
+<guimenuitem>Save As...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+<action>Name and rename files</action> with this command.
+It launches the save file dialog box. This dialog works just as
+the open file dialog box does. You can use it to navigate through
+your file system, preview existing files, or filter your file
+view with file masks.
+</para>
+
+<para>
+Type the name you want to give the file you are saving in the
+Location combo box and press the
+<guibutton>OK</guibutton> button.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="save-all"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>L</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Save All</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This command <action>saves all modified open files</action>.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="reload"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul"><keycap>F5</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Reload</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+<action>Reloads the active file</action>. This command is
+useful if another program or process has changed the file while you have
+it open in &kate;
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="print"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>P</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Print...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+<action>Print the active file</action>.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term id="export-as-html">
+<menuchoice>
+<guimenu>File</guimenu>
+<guimenuitem>Export as HTML...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+Export your file in HTML format so your document can be viewed as a
+web page.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term id="mail">
+<menuchoice>
+<guimenu>File</guimenu>
+<guimenuitem>Mail...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+Open your mail client and attach the file in the mail.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="close"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>W</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Close</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+<action>Close the active file</action> with this command. If you
+have made unsaved changes, you will be prompted to save
+the file before &kate; closes it.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="close-all"/>
+<menuchoice>
+<guimenu>File</guimenu>
+<guimenuitem>Close All</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This command <action>closes all the files you have open</action>
+in &kate;.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="quit"/>
+<menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
+</shortcut>
+<guimenu>File</guimenu>
+<guimenuitem>Quit</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+This command <action>closes &kate;</action> and any files you were
+editing. If you have made unsaved changes to any of the files you were
+editing, you will be prompted to save them.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</sect1>
+
+<sect1 id="edit-menu">
+<title>The <guimenu>Edit</guimenu> Menu</title>
+<para>The <guimenu>Edit</guimenu> menu contains a host of commands,
+all to work with the currently active document.</para>
+
+<variablelist>
+<title>Menu Entries</title>
+<varlistentry>
+<term>
+<anchor id="edit-undo"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>Z</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Undo</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Undo the last editing command (typing, copying, cutting etc.)</para>
+<note><para>If grouped undo is enabled, this may undo several editing commands of the same type, like typing in characters.</para></note>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-redo"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;&Shift;<keycap>Z</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Redo</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Redo the last undo step.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-cut"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>X</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Cut</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Removes selected text if any, and places a copy of the removed text in the clipboard.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-copy"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>C</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Copy</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Copies selected text, if any, to the clipboard.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-copy-as-html"/>
+<menuchoice>
+<guimenu>Edit</guimenu>
+<guimenuitem>Copy as HTML</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Copies selected text with the syntax highlight as HTML text.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-paste" />
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>V</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Paste</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Copies the first item in the clipboard into the editor at cursor position.</para>
+<note><para>If Overwrite Selection is enabled, the pasted text will overwrite the selection, if any.</para></note>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-select-all"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>A</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Select All</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Selects all text in the editor.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-deselect"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;&Shift;<keycap>A</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Deselect</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Deselects the selected text in the editor if any.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-toggle-block-selection"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>Shift</keycap>
+<keycap>B</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Block Selection Mode</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Toggles Selection Mode. When the Selection Mode is <quote>BLOCK</quote>, you can make vertical selections,
+ie select column 5 to 10 in lines 9 to 15.</para>
+<para>The status bar shows the current state of the Selection Mode, either <quote>NORM</quote> or <quote>BLK</quote>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-find"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Find...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Launch the Find Dialog to allow you to search for text in the edited document.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-find-next"/>
+<menuchoice>
+<shortcut><keycombo action="simul"><keycap>F3</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Find Next</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Go to the nearest downwards match of the last text or regular expression searched for, starting from cursor position</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-find-previous"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Shift;<keycap>F3</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Find Previous</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Go to the nearest upwards match of the last text or regular expression searched for, starting from cursor position</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-replace"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>R</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Replace...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Launch the Replace Dialog to replace one or more instances of a defined text with something else.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="edit-go-to-line"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>G</keycap></keycombo></shortcut>
+<guimenu>Edit</guimenu>
+<guimenuitem>Go to line...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Launches the Go To Line Dialog, allowing you to enter the number of a line to find in
+the document</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="document-menu">
+<title>The <guimenu>Document</guimenu> Menu</title>
+<para>The Document menu provides a menu entry for each open document.
+Clicking one of these will bring the requested document to focus. If you have
+multiple frames, an editor for that document will be displayed in the currently
+active frame.</para>
+<para>In addition, commands to browse your open documents are provided:
+<variablelist>
+<title>Menu items</title>
+
+<varlistentry>
+<term>
+<anchor id="document-back"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Alt;<keycap>Left</keycap></keycombo></shortcut>
+<guimenu>Document</guimenu>
+<guimenuitem>Back</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>This will bring the previous document in the stack in focus. If you have
+multiple frames, an editor for the document will be displayed in the currently
+active frame.</para> <para>The order is the order in which documents were
+opened, rather than a logical history. This behavior may change in future
+versions of &kate;.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="document-forward"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Alt;<keycap>Right</keycap></keycombo></shortcut>
+<guimenu>Document</guimenu>
+<guimenuitem>Forward</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>This will bring the next document in the stack in focus. If you have
+multiple frames, an editor for the document will be displayed in the currently
+active frame.</para>
+<para>The order is the order in which the documents were opened,
+rather than a logical history. This behavior may change in future versions of
+&kate;.</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</para>
+</sect1>
+
+<sect1 id="view-menu">
+<title>The <guimenu>View</guimenu> menu</title>
+
+<para>The <guimenu>View</guimenu> menu allows you to manage settings
+specific to the active editor, and to manage frames.</para>
+
+<variablelist>
+<title>Menu Items</title>
+
+<varlistentry>
+<term><menuchoice><shortcut><keycap>F7</keycap></shortcut>
+<guimenu>View</guimenu><guimenuitem>Switch to Command Line</guimenuitem>
+</menuchoice></term>
+<listitem><para>This command will toggle the display of the
+<link linkend="advanced-editing-tools-commandline">built in command line</link>.
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><guimenu>View</guimenu><guisubmenu>Schema</guisubmenu>
+</menuchoice></term>
+<listitem><para>This menu lists the available schemas. You can change the schema
+for the current view here, to change the default schema you need to
+use the <link linkend="config-dialog-editor-colors">config dialog</link></para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><shortcut><keycombo action="simul"><keycap>F10</keycap>
+</keycombo></shortcut>
+<guimenu>View</guimenu><guimenuitem>Dynamic Word Wrap</guimenuitem></menuchoice>
+</term>
+<listitem><para>Toggles dynamic word wrap in the current view. Dynamic word
+wrap makes all the text in a view visible without the need for horizontal
+scrolling by rendering one actual line on more visual lines as needed.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><guimenu>View</guimenu><guimenuitem>Show/Hide Static Word
+Wrap Marker</guimenuitem></menuchoice></term>
+<listitem><para>Toggles the display of a vertical line indicating the position
+of the wrap width as configured in the <link
+linkend="config-dialog-editor-wrap-words-at">config dialog</link>. This
+feature requires that you use a true fixed-width font.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="view-show-icon-border"/>
+<menuchoice>
+<shortcut><keycombo action="simul"><keycap>F6</keycap></keycombo></shortcut>
+<guimenu>View</guimenu>
+<guimenuitem>Show/Hide Icon Border</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>This is a toggle item. Setting it on checked will make the Icon Border
+visible in the left side of the active editor, and vice versa.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="view-show-line-numbers"/>
+<menuchoice>
+<shortcut><keycombo action="simul"><keycap>F11</keycap></keycombo></shortcut>
+<guimenu>View</guimenu>
+<guimenuitem>Show/Hide Line Numbers</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>This is a toggle Item. Setting it on checked will make a pane displaying
+the line numbers of the document visible in the left border of the active editor,
+and vice versa.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><guimenu>View</guimenu><guimenuitem>Show/Hide Scrollbar
+Marks</guimenuitem></menuchoice></term>
+<listitem><para>Toggles the visualization of bookmarks (and other marks) on the
+vertical scrollbar. When enabled, marks are represented by a thin line in the
+mark color at the scrollbar, middleclicking on the lines will scroll the view
+to a position near the mark.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><shortcut><keycombo action="simul"><keycap>F9</keycap>
+</keycombo></shortcut>
+<guimenu>View</guimenu><guimenuitem>Show/Hide Folding Markers</guimenuitem>
+</menuchoice></term>
+<listitem><para>Toggles the display of the folding marker pane in the left
+side of the view. See <link linkend="advanced-editing-tools-code-folding">Using
+Code Folding</link>.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="view-code-folding"/>
+<menuchoice>
+<guimenuitem>Code Folding</guimenuitem>
+</menuchoice>
+</term>
+
+<listitem>
+<variablelist>
+<varlistentry>
+<term><menuchoice><shortcut><keycombo action="simul">&Ctrl;
+<keycap>Shift</keycap><keycap>-</keycap></keycombo></shortcut>
+<guimenuitem>Collapse Toplevel</guimenuitem></menuchoice>
+</term>
+<listitem><para>Collapse all toplevel regions in the document.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><menuchoice><shortcut><keycombo action="simul">&Ctrl;
+<keycap>Shift</keycap><keycap>+</keycap></keycombo></shortcut>
+<guimenuitem>Expand Toplevel</guimenuitem></menuchoice>
+</term>
+<listitem><para>Expand all toplevel regions in the document.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><menuchoice><shortcut><keycombo action="simul">&Ctrl;
+<keycap>-</keycap></keycombo></shortcut>
+<guimenuitem>Collapse One Local Level</guimenuitem></menuchoice>
+</term>
+<listitem><para>Collapse the region closest to the cursor.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><menuchoice><shortcut><keycombo action="simul">&Ctrl;
+<keycap>+</keycap></keycombo></shortcut>
+<guimenuitem>Expand One Local Level</guimenuitem></menuchoice>
+</term>
+<listitem><para>Expand the region closest to the cursor.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="bookmarks-menu">
+<title>The <guimenu>Bookmarks</guimenu> Menu</title>
+
+<para>The <guimenu>Bookmarks</guimenu> menu allows you to work with
+the bookmarks in the currently active document.</para>
+
+<para>Below the entries described here, one entry for each bookmark in
+the active document will be available. The text will be the first few
+words of the marked line. Choose an item to move the cursor to the
+start of that line. The editor will scroll as necessary to make that
+line visible.</para>
+
+<variablelist>
+
+<title>Menu Items</title>
+
+<varlistentry>
+<term>
+<anchor id="bookmarks-toggle-bookmark"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;<keycap>B</keycap></keycombo></shortcut>
+<guimenu>Bookmarks</guimenu>
+<guimenuitem>Set/Clear Bookmark</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Sets or removes a bookmark in the current line of the active document.
+(If it's there, it is removed, otherwise one is set.)</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="bookmarks-clear-bookmarks"/>
+<menuchoice>
+<guimenu>Bookmarks</guimenu>
+<guimenuitem>Clear All Bookmarks</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Clears (removes) all bookmarks in the active document.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry id="bookmarks-previous">
+<term><menuchoice><shortcut><keycombo action="simul">&Alt;
+<keycap>Page Up</keycap></keycombo></shortcut>
+<guimenu>Bookmarks</guimenu><guimenuitem>Previous</guimenuitem></menuchoice>
+</term>
+<listitem><para>This will move the cursor to beginning of the first above line
+with a bookmark. The menuitem text will include the line number and the first
+piece of text on the line. This item is only available when there is a bookmark
+in a line above the cursor.</para></listitem>
+</varlistentry>
+
+<varlistentry id="bookmarks-next">
+<term><menuchoice><shortcut><keycombo action="simul">&Alt;
+<keycap>Page Down</keycap></keycombo></shortcut>
+<guimenu>Bookmarks</guimenu><guimenuitem>Next</guimenuitem></menuchoice></term>
+<listitem><para>This will move the cursor to beginning of the next line with a
+bookmark. The menuitem text will include the line number and the first piece of
+text on the line. This item is only available when there is a bookmark in a line
+below the cursor.</para></listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="tools-menu">
+
+<title>The <guimenu>Tools</guimenu> Menu</title>
+
+<variablelist>
+
+<varlistentry>
+<term><menuchoice><guimenu>Tools</guimenu><guimenuitem>Pipe to
+Console</guimenuitem></menuchoice></term>
+<listitem><para>Feed the currently selected text ito the built in terminal
+emulator. No newline is added after the text.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><guimenu>Tools</guimenu><guisubmenu>External
+Tools</guisubmenu></menuchoice></term>
+<listitem><para>This submenu contains all the <link
+linkend="kate-mdi-tools-externaltools">external tools</link>you have
+configured.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-read-only"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Read Only Mode</guimenuitem></menuchoice></term>
+<listitem>
+<para>Set the current document to Read Only mode. This prevents any text
+addition and any changes in the document formatting.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-filetype"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Filletype</guimenuitem></menuchoice></term>
+<listitem>
+<para>Choose the filetype scheme you prefer for the active document. This
+overwrites the global <link linkend="config-dialog-editor-filetypes">filetype</link>
+mode set in <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure
+Editor...</guimenuitem></menuchoice> in the Filetypes tab for your current
+document only.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-highlighting"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Highlighting</guimenuitem></menuchoice></term>
+ <listitem>
+<para>Choose the Highlighting scheme you prefer for the active document. This
+overwrites the global highlighting mode set in <menuchoice>
+<guimenu>Settings</guimenu> <guimenuitem>Configure Editor...</guimenuitem>
+</menuchoice> for your current document only.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-indentation"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Indentation</guimenuitem></menuchoice></term>
+<listitem>
+<para>Choose the <link linkend="kate-part-autoindent">style of
+indentation</link> you want for your active document.
+This overwrites the global indentation mode set in <menuchoice>
+<guimenu>Settings</guimenu> <guimenuitem>Configure Editor...</guimenuitem>
+</menuchoice> for your current document only.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-encoding"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Encoding</guimenuitem></menuchoice></term>
+<listitem>
+<para>You can overwrite the default encoding set in <menuchoice>
+<guimenu>Settings</guimenu>
+<guimenuitem>Configure
+Editor...</guimenuitem></menuchoice> in the <guilabel>Open/Save</guilabel> tab
+to set a different encoding for your current document. The encoding you
+set here will be only valid for your current document.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-end-of-line"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>End of Line</guimenuitem></menuchoice></term>
+<listitem>
+<para>Choose your prefered end of line mode for your active
+document. This overwrites the global end of line mode set in <menuchoice>
+<guimenu>Settings</guimenu> <guimenuitem>Configure Editor...</guimenuitem>
+</menuchoice> for your current document only.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-spelling"/><menuchoice>
+<guimenu>Tools</guimenu><guimenuitem>Spelling...</guimenuitem></menuchoice>
+</term>
+
+<listitem><para><action>This initiates the spellchecking program - a program
+designed to help the user catch and correct any spelling errors.</action>
+Clicking on this entry will start the checker and bring up the speller dialog
+box through which the user can control the process. There are four settings
+lined up vertically in the center of the dialog with their corresponding labels
+just to the left. Starting at the top they are:</para>
+
+<variablelist>
+<varlistentry>
+<term><guilabel>Unknown word:</guilabel></term>
+<listitem><para>Here, the spellchecker indicates the word currently under
+consideration. This happens when the checker encounters a word not in its
+dictionary - a file containing a list of correctly spelled words against which
+it compares each word in the editor.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Replace with:</guilabel></term>
+<listitem><para> If the checker has any similar words in its dictionary the
+first one will be listed here. The user can accept the suggestion, type in his
+or her own correction, or choose a different suggestion from the next
+box.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Suggested Words:</guilabel></term>
+<listitem><para> The checker may list here a number of possible replacements for
+the word under consideration. Clicking on any one of the suggestions will cause
+that word to be entered in the <guilabel>Replacement:</guilabel> box,
+above.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guilabel>Language:</guilabel></term>
+<listitem><para> If you have installed multiple dictionaries, here you can
+select which dictionary/language should be used.</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>On the right side of the dialog box are 5 buttons that allow the user to
+control the spellcheck process. They are:</para>
+
+<variablelist>
+<varlistentry>
+<term><guibutton>Add to Dictionary</guibutton></term>
+<listitem><para>Pressing this button adds the word in the <guilabel>Misspelled
+Word:</guilabel> box to the checker's dictionary. This means that in the future
+the checker will always consider this word to be correctly
+spelled.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Replace</guibutton></term>
+<listitem><para> This button has the checker replace the word under
+consideration in the document with the word in the
+<guilabel>Replacement:</guilabel> box.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Replace All</guibutton></term>
+<listitem><para> This button causes the checker to replace not only the current
+<guilabel>Unknown word:</guilabel> but to automatically make the same
+substitution for any other occurrences of this <guilabel>Misspelled
+Word:</guilabel> in the document.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Ignore</guibutton></term>
+<listitem><para>Activating this button will have the checker move on without
+making any changes.</para></listitem>
+</varlistentry>
+<varlistentry>
+<term><guibutton>Ignore All</guibutton></term>
+<listitem><para> This button tells the checker to do nothing with the current
+<guilabel>Unknown word:</guilabel> and to pass over any other instances of
+the same word.</para> <note><para>This only applies to the current spellcheck
+run. If the checker is run again later it will stop on this same
+word.</para></note></listitem>
+</varlistentry>
+</variablelist>
+
+<para>Three more buttons are located horizontally along the bottom of the
+spellcheck dialog. They are:</para>
+
+<variablelist>
+<varlistentry>
+<term><guibutton>Help</guibutton></term>
+<listitem><para> This invokes the &kde; help system starting at the &kate; help
+pages (this document).</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guibutton>Finished</guibutton></term>
+<listitem><para> This button ends the spellcheck process, and returns to the
+document.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><guibutton>Cancel</guibutton></term>
+<listitem><para> This button cancels the spellcheck process, all modifications
+are reverted, and you will return to your document.</para></listitem>
+</varlistentry>
+</variablelist>
+</listitem>
+</varlistentry>
+</variablelist>
+
+<variablelist>
+<varlistentry>
+<term><anchor id="tools-spelling-from-cursor"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Spelling (from cursor)...</guimenuitem></menuchoice></term>
+ <listitem>
+<para>This initiates the spellchecking program but it starts where your cursor
+is instead of at the beginning of the document.</para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-spellcheck-selection"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Spellcheck Selection...</guimenuitem></menuchoice></term>
+ <listitem>
+<para>Spellchecks the current selection.</para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="indent"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>I</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu><guimenuitem>Indent</guimenuitem></menuchoice></term>
+<listitem>
+<para>This increases the paragraph's indentation by one step. The size of the
+step depends on the <link linkend="config-dialog-editor-indent">indentation
+settings</link>.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-unindent"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;&Shift;<keycap>I</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu><guimenuitem>Unindent</guimenuitem></menuchoice></term>
+
+<listitem>
+<para>This reduces the paragraph's indentation by one step. The size of the step
+
+depends on the <link linkend="config-dialog-editor-indent">indentation settings</link>.</para>
+
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-cleanindent"/><menuchoice>
+<guimenu>Tools</guimenu><guimenuitem>Clean
+Indentation</guimenuitem></menuchoice></term> <listitem>
+<para>This cleans the indentation for the current selection or for the
+line the cursor is currently in. Cleaning the indentation ensures that
+all your selected text follows the indentation mode you choose.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-align"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Align</guimenuitem>
+</menuchoice></term>
+<listitem>
+<para>Causes a realign of the current line or selected lines using the
+indentation mode and indentation settings in the doucment.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-comment"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>D</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu>
+<guimenuitem>Comment</guimenuitem>
+</menuchoice></term>
+<listitem><para>This adds one space to the beginning of the line
+where the text cursor is located or to the beginning of any
+selected lines.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-uncomment"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;&Shift;<keycap>D</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu>
+<guimenuitem>Uncomment</guimenuitem>
+</menuchoice></term>
+<listitem><para>This removes one space (if any exist) from the beginning of the
+line where the text cursor is located or from the beginning of any
+selected lines.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-uppercase"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>U</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu>
+<guimenuitem>Uppercase</guimenuitem>
+</menuchoice></term>
+<listitem><para>Put the selected text or the letter after the cursor in
+uppercase.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-lowercase"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;&Shift;<keycap>U</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu>
+<guimenuitem>Lowercase</guimenuitem>
+</menuchoice></term>
+<listitem><para>Put the selected text or the letter after the cursor in
+lowercase.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-capitalize"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Alt;&Ctrl;<keycap>U</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu>
+<guimenuitem>Capitalize</guimenuitem>
+</menuchoice></term>
+<listitem><para>Capitalize the selected text or the current
+word.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-join-lines"/><menuchoice>
+<shortcut>
+<keycombo action="simul">&Ctrl;<keycap>J</keycap></keycombo>
+</shortcut>
+<guimenu>Tools</guimenu>
+<guimenuitem>Join Lines</guimenuitem>
+</menuchoice></term>
+<listitem><para>Joins the selected lines, or the current line and the line below
+with one white space character as a separator. Leading/trailing white space on
+joined lines is removed in the affected ends.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><anchor id="tools-word-wrap-document"/><menuchoice>
+<guimenu>Tools</guimenu>
+<guimenuitem>Word Wrap Document</guimenuitem>
+</menuchoice></term>
+<listitem><para>Apply static word wrapping on all the document. That means that
+a new line of text will automatically start when the current
+line exceeds the length specified by the Wrap words at: option
+in the Editing tab in <menuchoice>
+<guimenu>Settings</guimenu><guimenuitem>Configure
+Editor...</guimenuitem></menuchoice></para></listitem>
+</varlistentry>
+
+</variablelist>
+
+
+</sect1>
+
+<sect1 id="sessions-menu">
+<title>The <guimenu>Sessions</guimenu> Menu</title>
+
+<para>This menu contains entries for using and managing &kate; sessions.
+For more information, read <link
+linkend="fundamentals-using-sessions">Using Sessions</link>.</para>
+
+<variablelist>
+
+<varlistentry id="sessions-new">
+<term><menuchoice><guimenu>Sessions</guimenu>
+<guimenuitem>New</guimenuitem></menuchoice></term>
+<listitem><para>Creates a new empty session. All currently open files will
+be closed.</para></listitem>
+
+</varlistentry>
+
+<varlistentry id="sessions-open">
+<term><menuchoice><guimenu>Sessions</guimenu><guimenuitem>Open...</guimenuitem>
+</menuchoice></term>
+<listitem><para>Open an existing session. The Session Chooser dialog is
+displayed to let you choose one.</para></listitem>
+</varlistentry>
+
+<varlistentry id="sessions-quick-open">
+<term><menuchoice><guimenu>Sessions</guimenu><guisubmenu>Quick Open</guisubmenu>
+</menuchoice></term>
+<listitem><para>This submenu lets you open an existing session.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry id="sessions-save">
+<term><menuchoice><guimenu>Sessions</guimenu><guimenuitem>Save</guimenuitem>
+</menuchoice></term>
+<listitem><para>Save the current session. If the session is anonymous, you will
+be prompted for a session name.</para></listitem>
+</varlistentry>
+
+<varlistentry id="sessions-save-as">
+<term><menuchoice><guimenu>Sessions</guimenu><guimenuitem>Save
+As...</guimenuitem></menuchoice></term>
+<listitem><para>Save the current session under a new name. You are prompted for
+a name to use.</para></listitem>
+</varlistentry>
+
+<varlistentry id="sessions-manage">
+<term><menuchoice><guimenu>Sessions</guimenu><guimenuitem>Manage...</guimenuitem>
+</menuchoice></term>
+<listitem><para>Displays the Session Manager dialog which allows you to rename
+and delete sessions.</para></listitem>
+</varlistentry>
+
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="settings-menu">
+
+<title>The <guimenu>Settings</guimenu> Menu</title>
+
+<para>The <guimenu>Settings</guimenu> menu allows you to change the properties
+of the main window, such as showing/hiding toolbars, and provides
+access to the configuration dialogs.</para>
+
+<variablelist>
+
+<varlistentry>
+<term>
+<anchor id="settings-toolbars"/>
+<menuchoice>
+<guimenu>Settings</guimenu>
+<guisubmenu>Toolbars</guisubmenu>
+</menuchoice>
+</term>
+<listitem>
+<para>This submenu lists the available toolbars, each item toggles the display
+of the associated toolbar.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry id="settings-fullscreen">
+<term><menuchoice><guimenu>Settings</guimenu><guimenuitem>Full Screen
+Mode</guimenuitem></menuchoice></term>
+<listitem><para>Toggles full screen display.</para>
+<note><para>This commmand will be moved to the Window menu in a future
+version of &kate;</para></note>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="settings-configure-shortcuts"/>
+<menuchoice>
+<guimenu>Settings</guimenu>
+<guimenuitem>Configure Shortcuts...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Display the familiar &kde; Keyboard Shortcut Configuration
+Dialog.</para>
+</listitem>
+</varlistentry>
+
+
+<varlistentry>
+<term>
+<anchor id="settings-configure-toolbars"/>
+<menuchoice>
+<guimenu>Settings</guimenu>
+<guimenuitem>Configure Toolbars...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Display the familiar &kde; Toolbar Configuration Dialog.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="settings-configure-kate"/>
+<menuchoice>
+<guimenu>Settings</guimenu>
+<guimenuitem>Configure &kate;...</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Launch the <link linkend="config-dialog">Main Configuration Dialog</link></para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="window-menu">
+<title>the <guimenu>Window</guimenu> Menu</title>
+
+<variablelist>
+<varlistentry>
+<term>
+<anchor id="window-new"/>
+<menuchoice>
+<guimenu>Window</guimenu>
+<guimenuitem>New Window</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>
+<action>Opens another instance of &kate;</action>.
+The new instance will be identical to your previous instance.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-split-vertical"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;&Shift;<keycap>L</keycap></keycombo></shortcut>
+<guimenu>Window</guimenu>
+<guimenuitem>Split Vertical</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>This will split the frame (which may be the main editing area) in two equally sized frames,
+the new one to the left of the current one. The new frame gets the focus, and will display the
+same document as the old one.</para>
+<para>See also <link linkend="kate-mdi">Working with the &kate; MDI</link></para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-split-horizontal"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;&Shift;<keycap>T</keycap></keycombo></shortcut>
+<guimenu>Window</guimenu>
+<guimenuitem>Split Horizontal</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Splits the current frame (which may be the main editing area) in two equally sized frames,
+the new one at the bottom half. The new frame gets the focus, and displays the same document as
+the old one.</para>
+<para>See also <link linkend="kate-mdi">Working with the &kate; MDI</link></para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-close-current"/>
+<menuchoice>
+<shortcut><keycombo action="simul">&Ctrl;&Shift;<keycap>R</keycap></keycombo></shortcut>
+<guimenu>Window</guimenu>
+<guimenuitem>Close Current</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Closes the active frame. This is disabled, if there is only one frame
+(the main editing area).</para> <para>No documents get closed by closing a
+frame &ndash; they will still be available in the <link
+linkend="document-menu"><guimenu>Documents</guimenu> Menu</link> as well as in
+the File List.</para> <para>See also <link linkend="kate-mdi">Working with the
+&kate; MDI</link></para>
+</listitem>
+</varlistentry>
+
+<varlistentry id="window-next-view">
+<term><menuchoice><shortcut><keycombo action="simul"><keycap>F8</keycap>
+</keycombo></shortcut><guimenu>Window</guimenu><guimenuitem>Next
+View</guimenuitem></menuchoice></term>
+<listitem><para>Focus the next document view, if you have split the editor area
+in more views.</para></listitem>
+</varlistentry>
+
+<varlistentry id="window-previous-view">
+<term><menuchoice><shortcut><keycombo action="simul">&Shift;<keycap>F8</keycap>
+</keycombo></shortcut><guimenu>Window</guimenu><guimenuitem>Previous
+View</guimenuitem></menuchoice></term>
+<listitem><para>Focus the previous document view, if you have split the editor
+area in more views.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term><menuchoice><guimenu>Window</guimenu><guisubmenu>Tool Views</guisubmenu>
+</menuchoice></term>
+<listitem>
+<variablelist>
+<varlistentry>
+<term><anchor id="window-toolviews-show-sidebars"/>
+<menuchoice><guimenu>Window</guimenu><guisubmenu>Tool Views</guisubmenu>
+<guimenuitem>Show/Hide Sidebars</guimenuitem></menuchoice></term>
+<listitem><para>Toggles the display of the sidebar button rows. This command
+does not affect the display of the sidebar content widgets, any sidebar that
+is visible will stay visible, and if you assigned shortcuts to the below
+commands those will of course continue to work.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-toolviews-show-filelist"/>
+<menuchoice>
+<guimenu>Window</guimenu><guisubmenu>Tool Views</guisubmenu>
+<guimenuitem>Show Documents</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Toggle the display of &kate;'s Documents list</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-toolviews-show-fileselector"/>
+<menuchoice>
+<guimenu>Window</guimenu><guisubmenu>Tool Views</guisubmenu>
+<guimenuitem>Show/Hide Filesystem Browser</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Toggle the display of &kate;'s Filesystem Browser</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-toolviews-greptool"/>
+<menuchoice>
+<guimenu>Window</guimenu><guisubmenu>Tool Views</guisubmenu>
+<guimenuitem>Show/Hide Find in Files</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Toggle the display of &kate;'s <guilabel>Find in Files</guilabel> tool.
+</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>
+<anchor id="window-toolviews-show-konsole"/>
+<menuchoice>
+<guimenu>Window</guimenu><guisubmenu>Tool Views</guisubmenu>
+<guimenuitem>Show/Hide Terminal</guimenuitem>
+</menuchoice>
+</term>
+<listitem>
+<para>Toggles the display of the built in terminal emulator.</para>
+<para>When activated the first time, the terminal will be created.</para>
+<para>When the terminal emulator is displayed, it will get the focus, so that
+you can start typing in commands immediately. If the <link
+linkend="config-dialog-general-sync-konsole">Sync Konsole with Active
+Document</link> option is enabled in the <link
+linkend="config-dialog-general">General Page</link> of the <link
+linkend="config-dialog">Main configuration dialog</link> the shell session will
+change to the directory of the active document, if it is a local file.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+</sect1>
+
+<sect1 id="help-menu">
+
+<title>The <guimenu>Help</guimenu> Menu</title>
+
+<para>Apart from standard &kde; <guimenu>Help</guimenu> menu items
+described below you will have menu entries to show the
+Plugins User Manuals for installed plugins.</para>
+
+&help.menu.documentation;
+
+</sect1>
+
+</chapter>
diff --git a/doc/kate/mimetypechooser.png b/doc/kate/mimetypechooser.png
new file mode 100644
index 00000000..45220f8a
--- /dev/null
+++ b/doc/kate/mimetypechooser.png
Binary files differ
diff --git a/doc/kate/part.docbook b/doc/kate/part.docbook
new file mode 100644
index 00000000..e09725b3
--- /dev/null
+++ b/doc/kate/part.docbook
@@ -0,0 +1,671 @@
+<chapter id="kate-part">
+<chapterinfo>
+<authorgroup>
+<author>&Anders.Lund; &Anders.Lund.mail;</author>
+<!-- TRANS:ROLES_OF_TRANSLATORS -->
+</authorgroup>
+</chapterinfo>
+<title>Working with the &kate; editor</title>
+
+<sect1 id="kate-part-overview">
+
+<title>Overview</title>
+
+<para>The &kate; editor is the editing area of the &kate; window. This
+editor is also used by &kwrite;, and it can be used in &konqueror; for
+displaying text files from your local computer, or from the
+network.</para>
+
+<para>The editor is composed of the following components:</para>
+
+<variablelist>
+
+<varlistentry>
+<term>The editing area</term>
+<listitem><para>This is where the text of your document is located.</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>The Scroll bars</term>
+<listitem>
+<para>The scroll bars indicate the position of the visible part of
+the document text, and can be used to move around the
+document. Dragging the scrollbars will not cause the insertion cursor
+to be moved.</para>
+<para>The scroll bars are displayed and hidden as required.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>The Icon Border</term>
+<listitem>
+<para>The icon border is a small pane on the left side of the editor,
+displaying a small icon next to marked lines.</para>
+<para>You can set or remove a <link
+linkend="kate-part-bookmarks">bookmark</link> in a visible line by
+clicking the &LMB; in the icon border next to that line.</para>
+<para>The display of the icon border can be toggled using the
+<menuchoice><guimenu>View</guimenu> <guimenuitem>Show Icon
+Border</guimenuitem></menuchoice> menu item.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>The Line Numbers Pane</term>
+<listitem>
+<para>The Line numbers pane shows the line numbers of all visible
+lines in the document.</para>
+<para>The display of the Line Numbers Pane can be toggled using the
+<menuchoice><guimenu>View</guimenu> <guimenuitem>Show Line
+Numbers</guimenuitem></menuchoice> menu item.</para>
+</listitem>
+</varlistentry>
+
+<varlistentry>
+<term>The Folding Pane</term>
+<listitem>
+<para>The folding pane allows you to collapse or expand foldable blocks
+of lines. The calculation of the foldable regions are done according to
+rules in the syntax highlight definition for the document.</para>
+</listitem>
+</varlistentry>
+
+</variablelist>
+
+<itemizedlist>
+<title>Also in this Chapter:</title>
+<listitem><para><link linkend="kate-part-navigation">Navigating in the
+Text</link> </para></listitem>
+<listitem><para><link linkend="kate-part-selection">Working with the
+Selection</link></para></listitem>
+<listitem><para><link linkend="kate-part-copy-and-paste">Copying and
+Pasting Text</link></para></listitem>
+<listitem><para><link linkend="kate-part-find-replace">Finding and
+Replacing Text</link></para></listitem>
+<listitem><para><link linkend="kate-part-bookmarks">Using
+Bookmarks</link></para></listitem>
+<listitem><para><link linkend="kate-part-auto-wrap">Automatically
+Wrapping Text</link></para></listitem>
+<listitem><para><link linkend="kate-part-autoindent">Using automatic indenting</link></para></listitem>
+</itemizedlist>
+
+</sect1>
+
+<sect1 id="kate-part-navigation">
+<title>Navigating in the Text</title>
+
+<para>Moving around in the text in &kate; is like in most graphical text
+editors. You move the cursor using the arrow keys and the
+<keycap>Page Up</keycap>, <keycap>Page Down</keycap>, <keycap>Home</keycap> and
+<keycap>End</keycap> keys in combination with the <keycap>Ctrl</keycap> and
+<keycap>Shift</keycap> modifiers. The <keycap>Shift</keycap> key is always used
+to generate a selection, while the <keycap>Ctrl</keycap> key have different
+effects on different keys:
+<itemizedlist>
+<listitem><para>For the <keycap>Up</keycap> and <keycap>Down</keycap> keys it