Kontact for Windows
-------------------
(20091216 Ludwig Reiter, Intevation GmbH)

WARNING:
This is a beta software release which targets experienced users 
who want to help with testing and developing of KDE Kontact enterprise4
(a native Kolab Client). It is _not_ recommended for production use!
Keep a backup of your precious data!

KDE Kontact is Free Software under various copyrights and licenses,
for details see the files coming with the distributions and the sources.
Note that if you distribute the binaries, you MUST also (be ready to) 
distribute the corresponding sources with it.

For updated information, check www.kolab.org, corresponding mailinglists, 
http://www.kolab-konsortium.de/en/index.html and
http://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug)

  Kontact-Installer_20091204-3.exe

Version number (please use in reports):
Kontact Version 1.3 (enterprise4 0.20091204.1058385) Windows

Instructions:

 1. Download it, check its integrity and run the installer as administrator.
    (The installer is optimized for size, so it will need about
    1 Gigabytes of space unpackaged.)

 2. Crypto will need the additional software package Gpg4win2 (tested with
    gpg4win-2.0.1, but newer versions should also work).
    There are known problems with Gpg4win versions, 
    so please read the corresponding README-en.txt!
    Get the installer from www.gpg4win.org.
    After installing gpg4win you need to remove the following files from the
    Kontact program directory:

    kontact\bin\libgpg-error-0.dll
    kontact\bin\libgpgme++.dll
    kontact\bin\libgpgme-qt-11.dll
    kontact\bin\libgpgme-11.dll
    kontact\bin\libgpgme++-qt.dll
    kontact\bin\kleopatra.exe
    kontact\lib\kde4\kcm_kleopatra.dll

    and set the following pathes:

    KDEDIRS should contain the gpg4win install directory before the kontact path.
    PATH should contain the gpg4win install directory before the kontact path.

 3. Use the menu to start the Kolabwizard or Kontact directly.
    Configuration of Kontact can be done via Kolabwizard or manually.
    (You sometimes need to delete surplus identities and file-resources
    manually from within Kontact.) 
    After configuration with Kolabwizard you need to run Kontact and configure
    the server account passwords and the freebusy password.

 4. If you desire to use Kontact in the English language:
    To change the application language of Kontact from German to English 
    please use a text editor and change the locale settings 
    in the file 'kdeglobals' to:
      Country=en
      Language=en_US
    Restart all KDE processes (esp. logout, login) and start and close
    Kontact once.
    You will find this file usually in the install directory
    in 'Kontact\share\config'
    (e.g. c:\Program Files\Kontact\share\config\kdeglobals).

Possible known problems:

 5. You have to stop Kontact after the initial sync after configuration
    and restart it, so that the groupware folders, like the calendar 
    or contacts folder, are recognized.  (kolab/issue3169 (No writable 
    resource found if kontact is started the first time after a kolabwizard 
    configuration) 

 6. Rarely a sync stops, because of an unexpected finish of the kio-slave
    for imaps. Just sync again, which should work.
    (See: kolab/issue3379)

 7. During some test setups the native file dialog of Windows 
    can lead to an error message, which can be ignored.
    (See: kolab/issue3158 (Opening windows native file dialog 
    raises ignorable error messsage.) Please report to us, 
    if this happens to you.

 8. We expect, that other Kolab clients can have problems with some 
    groupware objects, especially with tasks.
    This version of Kontact works nicely with its own objects, except tasks.
    (See: kolab/issue3173 (Broken objects with  ISO time written, e.g. 
    creation-time)
    Other clients might show events and tasks at the wrong time.

 9. Sometimes kontact pauses for about 10-60 seconds, e.g. if an alarm
    pops up. This happens just once each session and for some
    dbus usage patterns.

10. The kwallet request dialogs sometimes appear in the background. If these 
    dialogs are overlooked, Kontact seems frozen, but it is not. Just look
    at the taskbar and answer kwallet first.

11. In earlier versions of Kontact the index of the cache could get into a
    broken state. This should be fixed in this version, so please report
    to us, if an index corruption still happens.
    If the index is broken, rebuilding of the cache
    (_NOT_ rebuilding of the index) should help.
    The sympthoms of a broken index are: some objects in the folders are
    doubled, other things don't work, like events.

12. After a single folder sync and in some other cases the configuration 
    dialogs needs a long time to pop up. So you need to wait for minutes.
    After a restart these dialogs should appear in short time again. 
    I advise to configure kontact only after a restart.

13. The configuration files (.kde) have moved to a different folder.
    So after an update from an earlier version you have to reconfigure Kontact.

14. At an initial start of kontact it needs some minutes to appear.