| -rw-r--r-- | bin/Migration-HowTo.txt | 17 | ||||
| -rw-r--r-- | bin/ReadMe_Zaurus.txt | 11 | ||||
| -rw-r--r-- | bin/kdepim/WhatsNew.txt | 9 |
3 files changed, 26 insertions, 11 deletions
diff --git a/bin/Migration-HowTo.txt b/bin/Migration-HowTo.txt index 2212004..f9e8123 100644 --- a/bin/Migration-HowTo.txt +++ b/bin/Migration-HowTo.txt @@ -1,320 +1,315 @@ Migration HowTo Outlook 200X -> KDE -Version 1.0.4 +Version 1.0.5 The latest version of this file can be downloaded from http://sourceforge.net/projects/kdepimpi/ Please choose there package/project/file: general Files for KDE/Pim MigrationHowTo_OL2KDE MigrationHowTo_OL2KDE.txt.zip This HowTo describes the process of migrating data ( contact and calendar data ) from Outlook 98/200X (TM) to the PIM programs of the KDE-Desktop-Environment. We will call Outlook as OL in this document. The PIM programs are KAdddressbook and KOrganizer, which may be used embedded in the Kontact PIM management framework. This HowTo describes version 1.9.5b of the migration tools. The migration tools are the platform independent versions of KAdddressbook and KOrganizer: KAdddressbook/Pi and KOrganizer/Pi. If you want to migrate emails, you can do that via an IMAP server. A Kolab server is an IMAP server. A HowTo how to migrate emails and contact and calendar data to a Kolab server using the Toltec (TM) Outlook(TM) plugin is available as well. You can found it on http://sourceforge.net/projects/kdepimpi/ Please choose there package/project/file: general Files for KDE/Pim MigrationHowTo_OL2KDE MigrationHowTo_OL2Kolab.txt.zip Content: 1) How to start 2) How to import pst files in Outlook 3) Where to get the migration tools 4) How to install the migration tools 5) How to get the contact data out of Outlook200X 6) How to get the calendar data out of Outlook200X 7) How to import your contact data into Kontact 8) How to import your calendar data into Kontact APPENDIX A) Problems and solutions when reading contact data APPENDIX B) Problems and solutions when reading calendar data **************************************** 1) How to start **************************************** For the migration we need the actual Outlook 200X data, which Outlook stores in *.pst files. Then we need an installed version of Outlook 200X to access these *.pst files. When we have an Outllook 200X running with all data accessable, we need the migration tools. If you have no Outlook200X installed please install the Outlook version, you need to a import your *.pst files. If you have an Outlook200X installed with no contact/calendar data available, and you have some *.pst files please continue with: 2) How to import pst files in Outlook. If you have a running Outlook200X already with contact/calendar data available, please continue with: 3) Where to get the migration tools. **************************************** 2) How to import pst files in Outlook **************************************** To open a local *.pst file in Outlook2003, choose menu: File - Open - Outlook Data File ... Now the data included in this file is shown as folders of a newly added root folder in the Outlook folder view. This root folder is probably not accessable from the migration tools via OLE. To access data stored in one of the subfolders, copy this subfolder to a root folder, which can be accessed from the migration tools via OLE. (To know, which folder can be accessed, just perform 5.) or 6.) until you get the Oulook import dialog!) To copy it, right click on that subfolder and choose Copy "<subfoldername>"... in the popup menu. **************************************** 3) Where to get the migration tools **************************************** The data migration is is performed with the Windows versions of KAdddressbook/Pi and KOrganizer/Pi. Pi stands for platform-independend - platform-independend because the same program is available for different platforms, like Windows, Linux desktop and Sharp-Zaurus PDA. Note: The Linux desktop versions of KOrganizer/Pi and KOrganizer/KDE-desktop are two different programs! You cannot use KOrganizer/Pi together with, or embedded in, the KDE-desktop environment. The same is valid for KAdddressbook/Pi. The programs you need for the migration are: a) KAdddressbook/Pi executeable + 2dlls + icons b) KOrganizer/Pi executeable + icons c) The Qt3 library qt-mt331.dll and the MSVC library msvcr71.dll and the MSVC library mfc71u.dll You can download all of them at: http://sourceforge.net/projects/kdepimpi/ Download of a) and b) Please choose there package/project with name KDE/Pim (Direct link: http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 ) Choose there the topmost latest version and the files -kapixxx-exe.zip -kopixxx-exe.zip -The latest version is currently ( 2004-09-15 ) 1.9.5b. -Such that the files to download are -kapi195b-exe.zip -kopi195b-exe.zip +kdepim_X.X.X_for_Windows.zip +Such that the files to download is +kdepim_X.X.X_for_Windows.zip To download c) Please choose there package/project/file: general Files for KDE/Pim Needed Windows Dlls kdepimdll.zip (Direct link: http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=122438&release_id=256700 ) Choose there the file: kdepimdll.zip Now you have downloaded the files -kapi195b-exe.zip -kopi195b-exe.zip +kdepim_X.X.X_for_Windows.zip kdepimdll.zip and we can continue to install the files, which is simply unzipping them. **************************************** 4) How to install the migration tools **************************************** You have downloaded the files -kapi195b-exe.zip -kopi195b-exe.zip +kdepim_X.X.X_for_Windows.zip kdepimdll.zip Unzip these files. Now choose an arbitrary installation directory, where to copy all the needed files together. You should have now the following files and the directory "kdepim" in the same directory: kopi.exe kapi.exe microkabc_dir.dll microkabc_file.dll msvcr71.dll mfc71u.dll qt-mt331.dll ReadMich.txt kdepim (directory) The directory "kdepim" should contain subdirectories kaddressbook korganizer which itself contain some subdirectories with icons and help text. Now the migration tools are ready for use. NOTE AND HINT for performing migration on many workstations: Just burn the content of the installation dir on a CD. Then you can put the CD in every workstation and execute the migration tools from that CD directly. ************************************************************* 5) How to get the contact data out of Outlook200X ************************************************************* Note: When accessing Outlook to read the data, it should not be possible, that there is any data lost in Outlook, because the progam accesses Outlook only Read-Only. You have the file kapi.exe and the other needed files accessable on your workstation. Getting the contact data Please start kapi.exe. Choose menu: File - Import - Import from Outlook... You will get a dialog which shows all "Personal Folders" of Outlook. Choose the Contact Folder(s) you want to import and select them with a hook. (All other folder but the contact containing folders are shown, but disabled). (If the data you want to import is not stored in one of the shown folders, please read step 2.) and click on "close" ). Click the "import" button. Now Outlook asks you to allow access to the contact data. Select "Allow access" amd click "Yes" in this dialog. Now the importing is performed and KA/Pi will show a progress bar. After importing, KA/Pi shows a dialog, how much contacts are imported. If you press a second time "import" , already imported contacts are not imported again. After importing you can choose another "Contact Folder" to import or close the import dialog. Please close the import dialog. Now you see the imported contacts in KA/Pi on the left in the list view. Please verify, that the import was correct. About problems of mapping particular Outlook-data-fields to KAdressbook-data-fields see Appendix A). Choose menu: File - Save and close KA/Pi. Now you should have the contact data in the file std.vcf in your home directory in the path (YOURHOMEDIR)\kdepim\apps\kabc\std.vcf Copy that file to a moveable disk or memory stick or just copy it via network to the destination. Import that file into KAddressbook/Kontact via Import - Import vcard. Details about importing you can read at: 7) How to import your contact data into Kontact Now you have your Outlook200X contact data on the KDE desktop available and you are done with the migration of contacts. ************************************************************* 6) How to get the calendar data out of Outlook200X ************************************************************* Note: When accessing Outlook to read the data, it should not be possible, that there is any data lost in Outlook, because the progam accesses Outlook only Read-Only. You have the file kopi.exe and the other needed files accessable on your workstation. Getting the calendar data NOTE: Before extracting the calendar data, it is recommended to extract the contact data first. If you extract the contact data first, the identity (UID) of attendees of a meeting can be mapped correctly in the newly created appointments, such that you can access the attendee contact data later directly from KOrganizer. Please start kopi.exe. You will see a dialog, that you started KO/Pi for the first time and that the timezone configuration will be shown now. Confirm with "Ok". Now you will see the configuration dialog of KO/Pi. Please choose your timezone and adjust the daylight saving settings. The dialog shows defaults for CET (Central European Time), such that users located in central Europe simply can press "OK" in that dialog. (Note: Don't forget to set the timezone in KDE KOrganizer before importing data there. The timezone in KDE KOrganizer is set per default to UTC (GMT), that is -1h of CET). Now you will see the KO/Pi main window. Choose menu: File - Import from OL You will get a dialog which shows all "Personal Folders" of Outlook. Choose the Calendar Folder(s) you want to import and select them with a hook. (All other folder but the calendar data containing folders are shown, but disabled). (If the data you want to import is not stored in one of the shown folders, please read step 2.) and click on "close" ). Click the "import" button. Now Outllok asks you to allow access to the contact data. Select "Allow access" amd click "Yes" in this dialog. Now the importing is performed and KO/Pi will show a progress bar. After importing, KO/Pi shows a dialog, how much calendar items are imported. If you press a second time "import" , already imported calendar items are not imported again. After importing you can choose another "Calendar Folder" to import or close the import dialog. Please close the import dialog. Now you see the imported calendar items in KO/Pi. Please verify, that the import was correct. About problems of mapping particular Outlook-data-fields to KOrganizer-data-fields see Appendix B). Close KO/Pi - data will be saved automatically. Now you should have the calendar data in the file mycalendar.ics in your home directory in the path (YOURHOMEDIR)\kdepim\apps\korganizer\mycalendar.ics Copy that file to a moveable disk or memory stick or just copy it via network to the destination. Import that file into KOrganizer/Kontact. Details about importing your calendar data you can read at: 8) How to import your calendar data into Kontact. (Warning again: Don't forget to set the timezone in KDE KOrganizer before importing data there. The timezone in KDE KOrganizer is set per default to UTC (GMT), that is -1h of CET). Now you have your Outlook200X calendar data on the KDE desktop available and you are done with the migration. Hint: If you want to use KO/Pi and KA/Pi on your windows desktop, you should read all the help information available in the KO/Pi Help menu. One Highlight of KO/Pi is the easy syncing with another *.ics file. (Information about syncing available in the KO/Pi help menu). Another hint: KO/Pi + KA/Pi ( = KDE-Pim/Pi ) are available for the Sharp Zaurus PDA. Syncing data works for KO/Pi ( version 1.9.3) but not yet for KA/Pi. ************************************************************* 7) How to import your contact data into Kontact ************************************************************* We want to import and upload our contacts to a Kolab server. You should have access to a properly configured Kolab client. This Kolab client is Kontact in KDE. Make sure, you have the needed IMAP resources configured in KAddressbook. To configure IMAP resources, you should do: Open KDE control center, choose there KDE Components - KDE Resource Configuration Choose there: Resources: contact and then: Add... IMAP Now start Kontact and select the Contacts icon on the left side. Choose menu: File... - Import - Import VCard... Select the imap resource as destination of the import and choose the file to import. Now the contacts should be imported and you are done. Don't forget to sync the IMAP account to upload to contacts to the server. ************************************************************* 8) How to import your calendar data into Kontact ************************************************************* We want to import and upload our calendar data to a Kolab server. You should have access to a properly configured Kolab client. This Kolab client is Kontact in KDE. Make sure, you have the needed IMAP resources configured in KOrganizer. To configure IMAP resources, you should do: Open KDE control center, choose there KDE Components - KDE Resource Configuration Choose there: Resources: calendar and then: Add... Calendar on IMAP-server via KMail Now start Kontact and select the Calendar icon on the left side. Choose menu: File... - Import - Merge Calendar... Select the imap resource as destination of the import and choose the file to import. Now the calendar data should be imported and you are done. Don't forget to sync the IMAP account to upload the calendar data to the server. ************************************************************* APPENDIX A) Problems and solutions when reading contact data ************************************************************* diff --git a/bin/ReadMe_Zaurus.txt b/bin/ReadMe_Zaurus.txt index 2cac8cd..e91fb0e 100644 --- a/bin/ReadMe_Zaurus.txt +++ b/bin/ReadMe_Zaurus.txt @@ -1,148 +1,159 @@ This is the Zaurus version of KO/Pi and KA/Pi (www.pi-sync.net), the platform independent PIM programs based on the PIM programs (KOrganizer and KAddressbook) of KDE (www.kdeorg). KO/Pi or KA/Pi are licensed under the GPL. Please read the file kdepim/licence.txt This ReadMe is included in two different packages. Depending if the filename of the package, please read section 2) or 3) ***************************************************** 2) Zaurus Sharp ROM, gcc 2.95 compiled ***************************************************** Filename: kdepim_X.X.X_for_SharpROM.ipk.zip Package contains: kaddressbook_X.X.X_arm.ipk korganizer-alarm_X.X.X_arm.ipk kmicrokdelibs_X.X.X_arm.ipk kmobilephoneaccess_X.X.X_arm.ipk ksharpPIM-DTMaccess_X.X.X_arm.ipk kopiemail_X.X.X_arm.ipk pimTABicon_X.X.X_arm.ipk korganizer_X.X.X_arm.ipk pwmanager_X.X.X_arm.ipk This package is for users of the Sharp ROM and clones. Users of old OpenZaurus releases, which are gcc2.95 compiled can use it as well. CONTENT: File kmicrokdelibs_X.X.X_arm.ipk: The libs in this file are needed to run any of the included programs. Install it. File kaddressbook_X.X.X_arm.ipk: Contains KA/Pi addressbook program and needed additional libs. File korganizer-alarm_X.X.X_arm.ipk: Contains KO/Pi calendar program and needed additional libs. File kopiemail_X.X.X_arm.ipk: Contains OM/Pi email program and needed additional libs. File pwmanager_X.X.X_arm.ipk: Contains PwM/Pi password manager program. File ksharpPIM-DTMaccess_X.X.X_arm.ipk: Contains needed program/lib to sync KA/Pi and KO/Pi with the Sharp PIM applications on the Zaurus, which use the new Sharp DMT Pim format. File korganizer-alarm_X.X.X_arm.ipk: Provides an alarm applet to get informed about alarms. The Zaurus will wake up from suspend if an event triggers an alarm. File kmobilephoneaccess_X.X.X_arm.ipk: Contains a command line tool for accessing mobile phones. It is used from Kx/Pi to sync with / export to mobile phones. It is not working very well, please do not expect too much. File pimTABicon_X.X.X_arm.ipk: If you insatll a program of the package, you may get a new TAB wchich is called Pim. If you did not have had this TAB on your Z, that TAB will not display an icon. Install this small package to assihn an icon to the new Pim TAB. Unzip package and install the apps in the usual way. +To get the character conversion in OM/Pi working, please download +at the sourceforge project site the package +sr-character-conversion_SharpROM_arm.ipk.zip +from the section "general files for KDE/Pim" +Instructions how to install this package are in a ReadMe in this file. + ***************************************************** 3) OpenZaurus ROM, gcc 3.xx compiled ***************************************************** Filename: kdepim_X.X.X_for_OZ-gcc3xx.ipk.zip Package contains: kaddressbook_OZ-gcc3xx_X.X.X_arm.ipk kmicrokdelibs_OZ-gcc3xx_X.X.X_arm.ipk kopiemail_OZ-gcc3xx_X.X.X_arm.ipk korganizer-alarm_OZ-gcc3xx_X.X.X_arm.ipk korganizer_OZ-gcc3xx_X.X.X_arm.ipk kmobilephoneaccess_OZ-gcc3xx_X.X.X_arm.ipk pimTABicon_OZ-gcc3xx_X.X.X_arm.ipk pwmanager_OZ-gcc3xx_X.X.X_arm.ipk This package is for users of the Open Zaurus ROM 3.3.6, compiled by coredump (aka known as Hentges-Rom). The programs may run on the new Open Zaurus Release 3.5.1 as well, but they cannot be installed there properly, because the package manager of OZ needs more information in the ipk files to install them properly. If you have Open Zaurus 3.5.1, you should use the packages of the OZ 3.5.1 feed, compiled and maintained by Hrw. Do not ask the OZ people about problems with these packages, they cannot help you. CONTENT: By the way, I cannot help you as well, because I am not using OZ. File kmicrokdelibs_OZ-gcc3xx_X.X.X_arm.ipk: The libs in this file are needed to run any of the included programs. Install it. File kaddressbook_OZ-gcc3xx_X.X.X_arm.ipk: Contains KA/Pi addressbook program and needed additional libs. File korganizer-alarm_OZ-gcc3xx_X.X.X_arm.ipk: Contains KO/Pi calendar program and needed additional libs. File kopiemail_OZ-gcc3xx_X.X.X_arm.ipk: Contains OM/Pi email program and needed additional libs. File pwmanager_OZ-gcc3xx_X.X.X_arm.ipk: Contains PwM/Pi password manager program. File korganizer-alarm_OZ-gcc3xx_X.X.X_arm.ipk: Provides an alarm applet to get informed about alarms. The Zaurus will wake up from suspend if an event triggers an alarm. File kmobilephoneaccess_OZ-gcc3xx_X.X.X_arm.ipk: Contains a command line tool for accessing mobile phones. It is used from Kx/Pi to sync with / export to mobile phones. It is not working very well, please do not expect too much. File pimTABicon_OZ-gcc3xx_X.X.X_arm.ipk: If you insatll a program of the package, you may get a new TAB wchich is called Pim. If you did not have had this TAB on your Z, that TAB will not display an icon. Install this small package to assihn an icon to the new Pim TAB. Unzip package and install the apps in the usual way. +To get the character conversion in OM/Pi working, please download +at the sourceforge project site the package +oz-character-conversion_OZ-gcc3xx_arm.ipk.zip +from the section "general files for KDE/Pim" +Instructions how to install this package are in a ReadMe in this file.
\ No newline at end of file diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 76f08cc..4905631 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt @@ -1,203 +1,212 @@ Info about the changes in new versions of KDE-Pim/Pi ********** VERSION 1.9.13 ************ Fixed nasty PwM/Pi file reading bug, when the used hash algo of file is different then the global hash algo. Added KA/Pi support for opie mailit mailapplication. Fixed some bugs in OM/Pi. +Now character conversion tables are available for the Zaurus +to make OM/Pi working properly. +To get the character conversion in OM/Pi working, please download +at the sourceforge project site the package +sr-character-conversion_SharpROM_arm.ipk.zip +(or oz-character-conversion_OZ-gcc3xx_arm.ipk.zip for OZ roms) +from the section "general files for KDE/Pim" +Instructions how to install this package are in a ReadMe in this file. + Fixed the orientation change problem in KA/Pi when switching portrait/landscape mode. French translation available for KA/Pi and OM/Pi. Fixed some problems with categories in KO/Pi in DTM sync. Added selection dialog for export to phone in KA/Pi. If in KO/Pi is an attendee selected to add to a meeting and this attendee is already in the list of attendees, this person is not added again. Some menu cleanup in KA/Pi. ********** VERSION 1.9.12 ************ Fix for the bug in KO/Pi What's Next view of version 1.9.11. Bugfix: Licence file is now shown again. OM/Pi now supports Unicode (utf8 charset). Fixed some bugs in OM/Pi. KA/Pi has more German translation. ********** VERSION 1.9.11 ************ Fixed several problems in PWM/Pi, like asking the user, if unsaved changed are pending when closing the app. And PwM/Pi handles now different texts for the fields Description, Username, Password, configurable per category. Fixed a crash in KO/Pi , when importing/loading vcs files which have an entry with an attendee with state: NEEDS ACTION Fixed some problems in the German translation of OM/Pi, which makes some dialogs not fitting on the screen of the Z 5500. Fixed Qtopia crash, when disabling/deinstalling KO/Pi alarm applet. Implemented direct KDE<->KA/Pi sync for KA/Pi running on Linux desktop. Added feature "remove sync info" to sync menu. Tweaked the KO/Pi What's next view a bit, added setting to hide events that are done. Disabled "beam receive enabled" on startup to avoid problems if Fastload is enabled. Please set "beam receive enabled", if you want to receive data via IR. Fixed bug in direct KDE<->KO/Pi sync for KO/Pi running on Linux desktop. Made in KA/Pi scrolling possible, if details view is selected. (The keyboard focus is set automatically to the search line) Fixed a bug in DMT sync, that a new entry in DTM was added on every sync to Kx/Pi. Fixed missing writing of KA/Pi categories to DMT entries when syncing. Fixed a bug in DMT sync with todos created in KO/Pi containing non-latin1 characters. Rearranged package contents of Sharp-ipks and made all packages installable on SD again. Fixed the writing of addressbook data in DTM sync. Empty fields in KA/Pi were not removed. Added better category handling in KA/Pi: Added item Edit Categories and Manage new categories to the settings menu. Possible to configure a view to display categories. Added detailed "KDE Sync Howto" and "Multi Sync Howto" to Help menu. Fixed displaying of "free" days and time in KO Monthview and Agendaview. ... and many other bugfixes. ********** VERSION 1.9.10 ************ Many internal small bugfixes. And fix of the "big" bug in KO/Pi, that after Syncing the appointments had an offset by several hours. That was a problem with the internal timezone setting, introduced by the changed timezone configuration settings. German translation for OM/Pi is now available. ********** VERSION 1.9.9 ************ KDE-Pim/Pi has a new Member! It is called PWM/Pi (Passwordmanager/platform-independent) and it is available for the Zaurus. It is planned, that it will be available later for Windows. (And for Linux, of course). It is a port of the Passwordmanager of KDE. It will need the MicroKDElibs to run. Made loading of addressbooks in KA/Pi up to 7 times faster! The bigger your addressbook file, the more starting speed will you gain. (relatively) The Qtopia addressbook connector is now platform independend as well and should work on any platform for importing/exporting Qtopia and Opie XML files. Added a +30min feature to the timezone settings to make KDE-Pim/Pi useable in Australia and other parts on the world with strange timezones ;-) German "Umlaute" should now be sorted correctly on the Z in KA/Pi. It is now possible to disable the "receive data via infrared" feature, such that syncing with Outlook is now possible again with Kx/Pi runing. Please disable it, before syncing Sharp DTM with Outlook. For your convenience, the "receive data via infrared" feature is disabled automatically, if you sync Kx/Pi with DTM. You have to enable it again manually after syncing. Enabling this feature makes it impossible to start the Sharp DTM apps. If this feature is enabled, you will only get the alarm notification from KO/Pi and not from the Sharp calendar. This is very useful if you sync KO/Pi with Sharp DTM, because after syncing you usually would get notified about an alarm by KO/Pi and the Sharp Calendar. Together with the Linux desktop version of KO/Pi it is now possible to sync KO/Pi on the Zaurus with the complete KDE-desktop (3.3 or later) calendar data easily. That makes it possible to sync the Z with one click of a mouse with the KDE-Desktop. This feature it available for all Zaurus platforms KO/Pi is running on. The only thing needed is a running KO/Pi on Linux and a compiled version of the small KDE-Pim/Pi<->KDE-Desktop access command line program, which is in the KDE-Pim/Pi sources available. The "KDE-desktop" syncing feature for KA/Pi will follow in the next releases. Fixed the vcard export bug, which had the version 1.9.8. Added missing GERMAN translation to KO/Pi. Hi PsionX, could you add the missing french translation?Thx! Translation files for KA/Pi are available as well. GERMAN translation will be available in the next release. PsionX ( yres, you again ;-) ), could you start translating KA/Pi? Thx! You can download the version 1.9.9 at http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 Note: To run the mail program OM/Pi you need libopenssl. A link to a download loaction is available at ZSI at www.killefiz.de ********** VERSION 1.9.8 ************ Fixed character decoding in OM/Pi. (e.g. German "Umlaute" were not displayed properly.) Made is possible to reparent todos in KO/Pi. Use contextmenu or keys (look at Help-Keys + Colors) for that. Added the missing Sync-Howto and WhatsNew to the packages. KO/Pi on Linux desktop can now sync with KDE desktop. That means: When using KO/Pi on Linux desktop for syncing with KDE desktop and the Zaurus, the Zaurus can be synced now with all KDE-Calendar resources, not only with one local file. |