author | zautrix <zautrix> | 2005-07-26 13:38:06 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2005-07-26 13:38:06 (UTC) |
commit | b37d71f782540851846613a70a60daf86816f7ec (patch) (unidiff) | |
tree | cd69f9e9a57903a2d463f9f30d376631b705f279 /bin/kdepim | |
parent | 346437d384dd780a1f7b75dd9caa3770525edfda (diff) | |
download | kdepimpi-b37d71f782540851846613a70a60daf86816f7ec.zip kdepimpi-b37d71f782540851846613a70a60daf86816f7ec.tar.gz kdepimpi-b37d71f782540851846613a70a60daf86816f7ec.tar.bz2 |
fixxx
-rw-r--r-- | bin/kdepim/WhatsNew.txt | 5 | ||||
-rw-r--r-- | bin/kdepim/korganizer/germantranslation.txt | 2 |
2 files changed, 5 insertions, 2 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 368f379..2032420 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt | |||
@@ -1,101 +1,104 @@ | |||
1 | Info about the changes in new versions of KDE-Pim/Pi | 1 | Info about the changes in new versions of KDE-Pim/Pi |
2 | 2 | ||
3 | ********** VERSION 2.1.17 ************ | 3 | ********** VERSION 2.1.17 ************ |
4 | 4 | ||
5 | 5 | KO/Pi: | |
6 | Added option to display times in What's Next View on two lines. | ||
7 | Removed "Allday" for allday events of one day duration in What's Next View. | ||
8 | Added date range for allday events of more than one day duration in What's Next View. | ||
6 | 9 | ||
7 | ********** VERSION 2.1.16 ************ | 10 | ********** VERSION 2.1.16 ************ |
8 | 11 | ||
9 | Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus. | 12 | Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus. |
10 | Added columns for datetime in todo view: Last modified, created and last modified subtodo | 13 | Added columns for datetime in todo view: Last modified, created and last modified subtodo |
11 | Fixed a bug in agenda view displaying recurring multiday events which are longer than two days. | 14 | Fixed a bug in agenda view displaying recurring multiday events which are longer than two days. |
12 | Made conflict detection up to 4 times faster. | 15 | Made conflict detection up to 4 times faster. |
13 | 16 | ||
14 | ********** VERSION 2.1.15 ************ | 17 | ********** VERSION 2.1.15 ************ |
15 | 18 | ||
16 | Fixed two layout problems on the Z: | 19 | Fixed two layout problems on the Z: |
17 | Made the with of the newly added buttons on the Quick-Todo smaller. | 20 | Made the with of the newly added buttons on the Quick-Todo smaller. |
18 | Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. | 21 | Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible. |
19 | 22 | ||
20 | 23 | ||
21 | ********** VERSION 2.1.14 ************ | 24 | ********** VERSION 2.1.14 ************ |
22 | 25 | ||
23 | Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done. | 26 | Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done. |
24 | Added a button to add a subtodo quickly. | 27 | Added a button to add a subtodo quickly. |
25 | 28 | ||
26 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). | 29 | Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ). |
27 | Added an option to change the layout of the list week to column mode. | 30 | Added an option to change the layout of the list week to column mode. |
28 | 31 | ||
29 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. | 32 | Fixed some usability problems in pi-sync mode by adding some progress information about file transfer. |
30 | 33 | ||
31 | Fixed pi-sync problems with the new multi calendar feature. | 34 | Fixed pi-sync problems with the new multi calendar feature. |
32 | Now pi-sync behaviour should be: | 35 | Now pi-sync behaviour should be: |
33 | 1) Local sends file request ( as usual ) | 36 | 1) Local sends file request ( as usual ) |
34 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. | 37 | 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars. |
35 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). | 38 | 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ). |
36 | If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar. | 39 | If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar. |
37 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. | 40 | 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote. |
38 | If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar. | 41 | If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar. |
39 | 42 | ||
40 | Summary: | 43 | Summary: |
41 | No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner. | 44 | No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner. |
42 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. | 45 | If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour. |
43 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. | 46 | Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. |
44 | 47 | ||
45 | ********** VERSION 2.1.13 ************ | 48 | ********** VERSION 2.1.13 ************ |
46 | 49 | ||
47 | Fixed a problem in KA/Pi search. | 50 | Fixed a problem in KA/Pi search. |
48 | Fixed some minor problems in KO/Pi. | 51 | Fixed some minor problems in KO/Pi. |
49 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. | 52 | Added calendar selection possibility to the todo view popup and to the event/todo/journal editor. |
50 | 53 | ||
51 | Fixed memory usage problems in KA/Pi: | 54 | Fixed memory usage problems in KA/Pi: |
52 | When loading data KA/Pi did load the file data twice. | 55 | When loading data KA/Pi did load the file data twice. |
53 | Example: | 56 | Example: |
54 | A 600k file did consume 1200k memory during loading process. | 57 | A 600k file did consume 1200k memory during loading process. |
55 | This is fixed, it does now consume only 600k during loading process. | 58 | This is fixed, it does now consume only 600k during loading process. |
56 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. | 59 | When saving data KA/Pi did consume a lot of memory for the data parsing during the save process. |
57 | This is fixed. | 60 | This is fixed. |
58 | Example: | 61 | Example: |
59 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. | 62 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. |
60 | When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system. | 63 | When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system. |
61 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. | 64 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. |
62 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 65 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
63 | The saving of data may be a bit slower now. | 66 | The saving of data may be a bit slower now. |
64 | 67 | ||
65 | Fixed memory usage problems in KO/Pi: | 68 | Fixed memory usage problems in KO/Pi: |
66 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 69 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
67 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 70 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
68 | This is fixed. | 71 | This is fixed. |
69 | Example: | 72 | Example: |
70 | When saving a 400k file KO/Pi do now use 400k less memory now. | 73 | When saving a 400k file KO/Pi do now use 400k less memory now. |
71 | 74 | ||
72 | Optimized memory usage in KO/Pi Agenda view: | 75 | Optimized memory usage in KO/Pi Agenda view: |
73 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. | 76 | KO/Pi is storing some paint information in extra buffers for faster repainting of the agenda view. |
74 | These buffers were not made smaller (i.e. downsized) because of performance reasons. | 77 | These buffers were not made smaller (i.e. downsized) because of performance reasons. |
75 | The handling of these buffers are now much smarter: | 78 | The handling of these buffers are now much smarter: |
76 | Two (of six) buffers are removed completely. | 79 | Two (of six) buffers are removed completely. |
77 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. | 80 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. |
78 | Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi. | 81 | Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi. |
79 | 82 | ||
80 | Worst case example ( for a maximum size agenda content): | 83 | Worst case example ( for a maximum size agenda content): |
81 | When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem. | 84 | When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem. |
82 | 85 | ||
83 | When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower. | 86 | When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower. |
84 | 87 | ||
85 | Summary: | 88 | Summary: |
86 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. | 89 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. |
87 | 90 | ||
88 | ********** VERSION 2.1.12 ************ | 91 | ********** VERSION 2.1.12 ************ |
89 | 92 | ||
90 | KO/Pi: | 93 | KO/Pi: |
91 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. | 94 | Many small usability fixes, e.g. rearranged the popup menus such that they are better to use on the Zaurus. |
92 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. | 95 | Fixed a problem with the month view when file was saved but KO/Pi was not the active window. |
93 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). | 96 | Fixed some problems in the resource config dialog (e.g. added a warning if you set all calendars to read-only). |
94 | Fixed some other small problems. | 97 | Fixed some other small problems. |
95 | 98 | ||
96 | ********** VERSION 2.1.11 ************ | 99 | ********** VERSION 2.1.11 ************ |
97 | 100 | ||
98 | KO/Pi: | 101 | KO/Pi: |
99 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. | 102 | Because we can have many calendars now in KO/Pi we can have more than one journal entry per day. |
100 | Added features to handle (and add ) more than one journal entry per day. | 103 | Added features to handle (and add ) more than one journal entry per day. |
101 | Added option for a journal title. | 104 | Added option for a journal title. |
diff --git a/bin/kdepim/korganizer/germantranslation.txt b/bin/kdepim/korganizer/germantranslation.txt index 0b928ef..e699fe9 100644 --- a/bin/kdepim/korganizer/germantranslation.txt +++ b/bin/kdepim/korganizer/germantranslation.txt | |||
@@ -1436,108 +1436,108 @@ | |||
1436 | { "Assistant","Assistent" }, | 1436 | { "Assistant","Assistent" }, |
1437 | { "Manager","Manager" }, | 1437 | { "Manager","Manager" }, |
1438 | { "Secrecy","Sichtbar" }, | 1438 | { "Secrecy","Sichtbar" }, |
1439 | { "male","männlich" }, | 1439 | { "male","männlich" }, |
1440 | { "female","weiblich" }, | 1440 | { "female","weiblich" }, |
1441 | { "Hide!","Verbergen!" }, | 1441 | { "Hide!","Verbergen!" }, |
1442 | { "Show!","Anzeigen!" }, | 1442 | { "Show!","Anzeigen!" }, |
1443 | { "Details","Details" }, | 1443 | { "Details","Details" }, |
1444 | { "Profession","Beruf" }, | 1444 | { "Profession","Beruf" }, |
1445 | { "Children","Kinder" }, | 1445 | { "Children","Kinder" }, |
1446 | { "Department","Abteilung" }, | 1446 | { "Department","Abteilung" }, |
1447 | { "Backup cancelled","Backup abgebrochen" }, | 1447 | { "Backup cancelled","Backup abgebrochen" }, |
1448 | { "Backup globally disabled","Backup global abgeschaltet" }, | 1448 | { "Backup globally disabled","Backup global abgeschaltet" }, |
1449 | { "Backup succesfully finished","Backup erfolgreich beendet" }, | 1449 | { "Backup succesfully finished","Backup erfolgreich beendet" }, |
1450 | { "(Hint: You can enable automatic backup in the global settings!)","(Hinweis: Sie können ein automatisches Backup in den globalen Einstellungen konfigurieren!)" }, | 1450 | { "(Hint: You can enable automatic backup in the global settings!)","(Hinweis: Sie können ein automatisches Backup in den globalen Einstellungen konfigurieren!)" }, |
1451 | { "This will <b>backup all calendar files</b> to the directory %1 %2","Das schreibt ein <b>Backup aller Kalenderdateien</b> in das Verzeichnis %1 %2" }, | 1451 | { "This will <b>backup all calendar files</b> to the directory %1 %2","Das schreibt ein <b>Backup aller Kalenderdateien</b> in das Verzeichnis %1 %2" }, |
1452 | { "Birthdays","Geburtstage" }, | 1452 | { "Birthdays","Geburtstage" }, |
1453 | { "KO/Pi import information!","KO/Pi Import Information!" }, | 1453 | { "KO/Pi import information!","KO/Pi Import Information!" }, |
1454 | { "Start this todo\nand stop all running","Starte dieses Todo\nund stoppe alle Laufenden" }, | 1454 | { "Start this todo\nand stop all running","Starte dieses Todo\nund stoppe alle Laufenden" }, |
1455 | { "Cancel - do not start"," Abbrechen - Todo nicht starten" }, | 1455 | { "Cancel - do not start"," Abbrechen - Todo nicht starten" }, |
1456 | { "The timezone has changed!\nShould the calendar be reloaded\nto shift the time of the events?\nPlease read Menu: Help->FAQ:\n"How do I change the timezone?"\nas well!","Die Zeitzone wurde geändert!\nSollen die Kalender neu geladen\nwerden num die Zeiten\nder Termine zu ändern?\nBitte lesen Sie auch\nMenu: Help->FAQ:\n"How do I change the timezone?"" }, | 1456 | { "The timezone has changed!\nShould the calendar be reloaded\nto shift the time of the events?\nPlease read Menu: Help->FAQ:\n"How do I change the timezone?"\nas well!","Die Zeitzone wurde geändert!\nSollen die Kalender neu geladen\nwerden num die Zeiten\nder Termine zu ändern?\nBitte lesen Sie auch\nMenu: Help->FAQ:\n"How do I change the timezone?"" }, |
1457 | { "Reload","Neu laden" }, | 1457 | { "Reload","Neu laden" }, |
1458 | { "Timezone settings","Zeitzoneneinstellung" }, | 1458 | { "Timezone settings","Zeitzoneneinstellung" }, |
1459 | { "Title: ","Titel: " }, | 1459 | { "Title: ","Titel: " }, |
1460 | { "Journal from: ","Journal vom: " }, | 1460 | { "Journal from: ","Journal vom: " }, |
1461 | { "Journal: %1 from ","Journal: %1 vom " }, | 1461 | { "Journal: %1 from ","Journal: %1 vom " }, |
1462 | { "<b>Click here to edit categories: </b>","<b>Klicke hier um Kategorien zu ändern: </b>" }, | 1462 | { "<b>Click here to edit categories: </b>","<b>Klicke hier um Kategorien zu ändern: </b>" }, |
1463 | { "Selected Item","Ausgewähltes Item" }, | 1463 | { "Selected Item","Ausgewähltes Item" }, |
1464 | { "Select Date...","Wähle Datum..." }, | 1464 | { "Select Date...","Wähle Datum..." }, |
1465 | { "After importing/loading/syncing there may be new categories in events or todos which are not added automatically to the category list. Please choose what to do <b>now</b>:","Nach dem Importieren/Laden/Syncen kann es neue Kategorien in den Terminen oder Todos geben, die nicht automatisch der Kategorieliste hinzugefügt werden. Bitte wählen Sie, was <b>jetzt</b> passieren soll:" }, | 1465 | { "After importing/loading/syncing there may be new categories in events or todos which are not added automatically to the category list. Please choose what to do <b>now</b>:","Nach dem Importieren/Laden/Syncen kann es neue Kategorien in den Terminen oder Todos geben, die nicht automatisch der Kategorieliste hinzugefügt werden. Bitte wählen Sie, was <b>jetzt</b> passieren soll:" }, |
1466 | { "Change category list now!","Ändere Kategorieliste jetzt!" }, | 1466 | { "Change category list now!","Ändere Kategorieliste jetzt!" }, |
1467 | { "Edit category list...","Ändere Kategorieliste..." }, | 1467 | { "Edit category list...","Ändere Kategorieliste..." }, |
1468 | { "Toolbar changes needs a restart!","Neustart benötigt für Toolbaränderungen!" }, | 1468 | { "Toolbar changes needs a restart!","Neustart benötigt für Toolbaränderungen!" }, |
1469 | { "Filepath: ","Dateipfad: " }, | 1469 | { "Filepath: ","Dateipfad: " }, |
1470 | { "You can try to reload the calendar in the Resource View!","In der Resourcenansicht können Sie erneut versuchen den Kalender zu laden!" }, | 1470 | { "You can try to reload the calendar in the Resource View!","In der Resourcenansicht können Sie erneut versuchen den Kalender zu laden!" }, |
1471 | { "<b>WARNING:</b> There is a pending suspended alarm!","<b>WARNUNG:</b> Es gibt einen laufenden Suspendalarm!" }, | 1471 | { "<b>WARNING:</b> There is a pending suspended alarm!","<b>WARNUNG:</b> Es gibt einen laufenden Suspendalarm!" }, |
1472 | { "Pending Suspend Alarm","Laufender Suspend Alarm" }, | 1472 | { "Pending Suspend Alarm","Laufender Suspend Alarm" }, |
1473 | { "Error loading calendar %1","Fehler beim Laden von Kalender %1" }, | 1473 | { "Error loading calendar %1","Fehler beim Laden von Kalender %1" }, |
1474 | { "Calendar(s) not loaded:","Nicht geladene(r) Kalender:" }, | 1474 | { "Calendar(s) not loaded:","Nicht geladene(r) Kalender:" }, |
1475 | { "Loding of calendar(s) failed","Laden von Kalendern fehlgeschlagen" }, | 1475 | { "Loding of calendar(s) failed","Laden von Kalendern fehlgeschlagen" }, |
1476 | { "Alarm Options","Alarm Einstellungen" }, | 1476 | { "Alarm Options","Alarm Einstellungen" }, |
1477 | { "Delete selected...","Lösche Ausgewählte..." }, | 1477 | { "Delete selected...","Lösche Ausgewählte..." }, |
1478 | { "None","Nichts" }, | 1478 | { "None","Nichts" }, |
1479 | { "Selection","Auswahl" }, | 1479 | { "Selection","Auswahl" }, |
1480 | { "Set categories","Setze Kategorien" }, | 1480 | { "Set categories","Setze Kategorien" }, |
1481 | { "This adds the selected\nitems to the calendar\n%1\nand removes them from\ntheir current calendar!","Das fügt die ausgewählten\nEinträge dem Kalender\n%1\nhinzu und entfernt sie von\nihrem aktuellen Kalender!" }, | 1481 | { "This adds the selected\nitems to the calendar\n%1\nand removes them from\ntheir current calendar!","Das fügt die ausgewählten\nEinträge dem Kalender\n%1\nhinzu und entfernt sie von\nihrem aktuellen Kalender!" }, |
1482 | { "Reset","Neu setzen" }, | 1482 | { "Reset","Neu setzen" }, |
1483 | { "Do you want to <b>add</b> categories to the selected items or <b>reset</b> the list (i.e. remove current categories)?","Möchten Sie Kategorien zu den ausgewählten Einträgen <b>hinzufügen</b> oder die Liste <b>neu setzen</b> (d.h. vorhandene Kategorien löschen)?" }, | 1483 | { "Do you want to <b>add</b> categories to the selected items or <b>reset</b> the list (i.e. remove current categories)?","Möchten Sie Kategorien zu den ausgewählten Einträgen <b>hinzufügen</b> oder die Liste <b>neu setzen</b> (d.h. vorhandene Kategorien löschen)?" }, |
1484 | { "The file\n%1\ndoes not exist!\nShall I create it for you?","Die Datei\n%1\nexistiert nicht!\nSoll sie neu angelegt werden?" }, | 1484 | { "The file\n%1\ndoes not exist!\nShall I create it for you?","Die Datei\n%1\nexistiert nicht!\nSoll sie neu angelegt werden?" }, |
1485 | { "Sorry, cannot create the file\n%1!\nNo calendar added!","Kann leider die Datei\n%1\nnicht anlegen!\nKein Kalender hinzugefügt!" }, | 1485 | { "Sorry, cannot create the file\n%1!\nNo calendar added!","Kann leider die Datei\n%1\nnicht anlegen!\nKein Kalender hinzugefügt!" }, |
1486 | { "\nNO\n WRITEABLE\n CALENDAR\n FOUND!\n\nPlease fix your calendar settings!\n","\nKEIN\n SCHREIBBARER\n KALENDER\n GEFUNDEN!\n\nBitte korrigieren Sie\nihre Kalendereinstellungen!\n" }, | 1486 | { "\nNO\n WRITEABLE\n CALENDAR\n FOUND!\n\nPlease fix your calendar settings!\n","\nKEIN\n SCHREIBBARER\n KALENDER\n GEFUNDEN!\n\nBitte korrigieren Sie\nihre Kalendereinstellungen!\n" }, |
1487 | { "\nThe file\n%1\non disk has changed!\nFile size: %2 bytes.\nLast modified: %3\nDo you want to:\n\n - Save and overwrite file?\n - Sync with file, then save?\n - Cancel without saving? \n","\nDie Datei\n%1\nwurde verändert!\nDatei Grösse: %2 Bytes.\nZuletzt geändert: %3\nMöchten Sie:\n\n - Speichern und die Datei überschreiben?\n - Mit Datei Synchronisieren, dann speichern?\n - Abbrechen ohne zu speichern? \n" }, | 1487 | { "\nThe file\n%1\non disk has changed!\nFile size: %2 bytes.\nLast modified: %3\nDo you want to:\n\n - Save and overwrite file?\n - Sync with file, then save?\n - Cancel without saving? \n","\nDie Datei\n%1\nwurde verändert!\nDatei Grösse: %2 Bytes.\nZuletzt geändert: %3\nMöchten Sie:\n\n - Speichern und die Datei überschreiben?\n - Mit Datei Synchronisieren, dann speichern?\n - Abbrechen ohne zu speichern? \n" }, |
1488 | { "Edit","Edit" }, | 1488 | { "Edit","Edit" }, |
1489 | { "Last Modified","Zuletzt geändert" }, | 1489 | { "Last Modified","Zuletzt geändert" }, |
1490 | { "Journal viewer","Journal Anzeige" }, | 1490 | { "Journal viewer","Journal Anzeige" }, |
1491 | { "Configure Calendar Files...","Konfiguriere Kalenderdateien..." }, | 1491 | { "Configure Calendar Files...","Konfiguriere Kalenderdateien..." }, |
1492 | { "You can use and display <b>more than one</b> calendar file in KO/Pi. A calendar file is called a <b>resource</b>. To add a calendar or change calendar settings please use menu: <b>View -> Toggle Resource View</b>.","Sie können <b>mehr als eine</b> Kalenderdatei in KO/Pi darstellen und benutzen. Eine Kalenderdatei wird <b>Resource</b> genannt. Um einen Kalender hinzuzufügen oder die Kalendereinstellungen zu ändern benutzen Sie bitte das Menu: <b>Ansicht -> Resourcenansicht umschalten</b>." }, | 1492 | { "You can use and display <b>more than one</b> calendar file in KO/Pi. A calendar file is called a <b>resource</b>. To add a calendar or change calendar settings please use menu: <b>View -> Toggle Resource View</b>.","Sie können <b>mehr als eine</b> Kalenderdatei in KO/Pi darstellen und benutzen. Eine Kalenderdatei wird <b>Resource</b> genannt. Um einen Kalender hinzuzufügen oder die Kalendereinstellungen zu ändern benutzen Sie bitte das Menu: <b>Ansicht -> Resourcenansicht umschalten</b>." }, |
1493 | { "Hide Completed","Verstecke erledigte Todos" }, | 1493 | { "Hide Completed","Verstecke erledigte Todos" }, |
1494 | { "Show not Running","Zeige nicht Laufende" }, | 1494 | { "Show not Running","Zeige nicht Laufende" }, |
1495 | { "Click to add new Todo","Klick für neues Todo!" }, | 1495 | { "Click to add new Todo","Klick für neues Todo!" }, |
1496 | { "Show next conflict for","Zeige nächsten Konflikt für" }, | 1496 | { "Show next conflict for","Zeige nächsten Konflikt für" }, |
1497 | { "All events","Alle Termine" }, | 1497 | { "All events","Alle Termine" }, |
1498 | { "Allday events","Ganztagestermine" }, | 1498 | { "Allday events","Ganztagestermine" }, |
1499 | { "Events with time","Termine mit Zeit" }, | 1499 | { "Events with time","Termine mit Zeit" }, |
1500 | { "No conflict found","Kein Konflikt gefunden" }, | 1500 | { "No conflict found","Kein Konflikt gefunden" }, |
1501 | { "Conflict %1 <-> %2","Konflikt %1 <-> %2" }, | 1501 | { "Conflict %1 <-> %2","Konflikt %1 <-> %2" }, |
1502 | { "<p><b>Q</b>: Show next date with conflicting events\n ","<p><b>Q</b>: Zeige nächstes Datum mit Terminen im Konflikt\n " }, | 1502 | { "<p><b>Q</b>: Show next date with conflicting events\n ","<p><b>Q</b>: Zeige nächstes Datum mit Terminen im Konflikt\n " }, |
1503 | { "Week view mode uses row layout","Wochenansicht Modus nutzt Reihenlayout" }, | 1503 | { "Week view mode uses row layout","Wochenansicht Modus nutzt Reihenlayout" }, |
1504 | { "The event\n%1\nconflicts with event\n%2\nat date\n%3.\n","Der Termin\n%1\nist im Konflikt mit Termin\n%2\nam Datum\n%3.\n" }, | 1504 | { "The event\n%1\nconflicts with event\n%2\nat date\n%3.\n","Der Termin\n%1\nist im Konflikt mit Termin\n%2\nam Datum\n%3.\n" }, |
1505 | { "KO/Pi Conflict delected","KO/Pi Konflikt erkannt" }, | 1505 | { "KO/Pi Conflict delected","KO/Pi Konflikt erkannt" }, |
1506 | { "Show date","Zeige Datum" }, | 1506 | { "Show date","Zeige Datum" }, |
1507 | { "No problem!","Null Problemo!" }, | 1507 | { "No problem!","Null Problemo!" }, |
1508 | { "Automatically sync with KDE-Desktop\nwhen receiving sync request","Synce automatisch mit KDE-Desktop\nwenn eine Sync-Anforderung kommt" }, | 1508 | { "Automatically sync with KDE-Desktop\nwhen receiving sync request","Synce automatisch mit KDE-Desktop\nwenn eine Sync-Anforderung kommt" }, |
1509 | { "Pi-Sync Port Error","Pi-Sync Port Fehler" }, | 1509 | { "Pi-Sync Port Error","Pi-Sync Port Fehler" }, |
1510 | { "<b>Enabling Pi-Sync failed!</b> Failed to bind or listen to the port %1! Is another instance already listening to that port?","<b>Anschalten von Pi-Sync fehlgeschlagen!</b> Fehler beim Ansprechen des Ports %1! Ist bereits eine andere Anwendung dabei diesen Port zu nutzen?" }, | 1510 | { "<b>Enabling Pi-Sync failed!</b> Failed to bind or listen to the port %1! Is another instance already listening to that port?","<b>Anschalten von Pi-Sync fehlgeschlagen!</b> Fehler beim Ansprechen des Ports %1! Ist bereits eine andere Anwendung dabei diesen Port zu nutzen?" }, |
1511 | { "No valid port number:\n%1","Keine gültige Port Nummer:\n%1" }, | 1511 | { "No valid port number:\n%1","Keine gültige Port Nummer:\n%1" }, |
1512 | { "Port number (Default: %1)\nValid range from 1 to 65535","Port Nummer (Standard: %1)\nGültiger Bereich von 1 bis 65535" }, | 1512 | { "Port number (Default: %1)\nValid range from 1 to 65535","Port Nummer (Standard: %1)\nGültiger Bereich von 1 bis 65535" }, |
1513 | { "Pi-Sync Error","Pi-Sync Fehler" }, | 1513 | { "Pi-Sync Error","Pi-Sync Fehler" }, |
1514 | { "Got send file request\nwith invalid password","Erhielt "sende Datei" Anfrage\nmit ungültigem Passwort" }, | 1514 | { "Got send file request\nwith invalid password","Erhielt "sende Datei" Anfrage\nmit ungültigem Passwort" }, |
1515 | { "Got receive file request\nwith invalid password","Erhielt "empfange Datei" Anfrage\nmit ungültigem Passwort" }, | 1515 | { "Got receive file request\nwith invalid password","Erhielt "empfange Datei" Anfrage\nmit ungültigem Passwort" }, |
1516 | { "Wrong password: Receiving remote file failed.","Falsches Passwort: Empfangen von entfernter Datei fehlgeschlagen." }, | 1516 | { "Wrong password: Receiving remote file failed.","Falsches Passwort: Empfangen von entfernter Datei fehlgeschlagen." }, |
1517 | { "Please close error dialog on remote.","Bitte schließe Fehler-Dialog am entfernten Rechner" }, | 1517 | { "Please close error dialog on remote.","Bitte schließe Fehler-Dialog am entfernten Rechner" }, |
1518 | { "Unknown error on remote.","Unbekannter Fehler am entfernten Rechner" }, | 1518 | { "Unknown error on remote.","Unbekannter Fehler am entfernten Rechner" }, |
1519 | { "Pi-Sync: Connected!","Pi-Sync: Verbunden!" }, | 1519 | { "Pi-Sync: Connected!","Pi-Sync: Verbunden!" }, |
1520 | { "Receiving file from remote...","Empfange entfernte Datei..." }, | 1520 | { "Receiving file from remote...","Empfange entfernte Datei..." }, |
1521 | { "Sending back synced file...","Sende synchronisierte Datei zurück..." }, | 1521 | { "Sending back synced file...","Sende synchronisierte Datei zurück..." }, |
1522 | { "Do you want to\nclear all sync info\nof all profiles?","Möchten Sie wirklich\ndie Sync-Info\nfür alle Profile\nlöschen?" }, | 1522 | { "Do you want to\nclear all sync info\nof all profiles?","Möchten Sie wirklich\ndie Sync-Info\nfür alle Profile\nlöschen?" }, |
1523 | { "Do you want to\nclear the sync\ninfo of profile\n%1?\n","Möchten Sie wirklich\ndie Sync-Info für Profil\n%1?\nlöschen" }, | 1523 | { "Do you want to\nclear the sync\ninfo of profile\n%1?\n","Möchten Sie wirklich\ndie Sync-Info für Profil\n%1?\nlöschen" }, |
1524 | { "Sorry, no valid port.Syncing cancelled.","Sorry, kein gültiger Port. Syncing abgebrochen." }, | 1524 | { "Sorry, no valid port.Syncing cancelled.","Sorry, kein gültiger Port. Syncing abgebrochen." }, |
1525 | { "Remote port number:\n(May be: 1 - 65535)","Ferne Port Nummer:\n(Darf sein: 1 - 65535)" }, | 1525 | { "Remote port number:\n(May be: 1 - 65535)","Ferne Port Nummer:\n(Darf sein: 1 - 65535)" }, |
1526 | { "Writing back file ...","Schreibe Datei zurück..." }, | 1526 | { "Writing back file ...","Schreibe Datei zurück..." }, |
1527 | { "Sending back file ...","Sende Datei zurück..." }, | 1527 | { "Sending back file ...","Sende Datei zurück..." }, |
1528 | { "Eeek, there I am ticklish!","Hihi, da bin ich kitzlig!" }, | 1528 | { "Eeek, there I am ticklish!","Hihi, da bin ich kitzlig!" }, |
1529 | { "Created","Angelegt" }, | 1529 | { "Created","Angelegt" }, |
1530 | { "Last Modified Sub","Zuletzt geändertes Sub" }, | 1530 | { "Last Modified Sub","Zuletzt geändertes Sub" }, |
1531 | { "Checking conflicts ... please wait","Überprüfe Konflikte ... bitte warten" }, | 1531 | { "Checking conflicts ... please wait","Überprüfe Konflikte ... bitte warten" }, |
1532 | { "","" }, | 1532 | { "Show times on two lines","Zeige Zeiten auf zwei Zeilen" }, |
1533 | { "","" }, | 1533 | { "","" }, |
1534 | { "","" }, | 1534 | { "","" }, |
1535 | { "","" }, | 1535 | { "","" }, |
1536 | { "","" }, | 1536 | { "","" }, |
1537 | { "","" }, | 1537 | { "","" }, |
1538 | { "","" }, | 1538 | { "","" }, |
1539 | { "","" }, | 1539 | { "","" }, |
1540 | { "","" }, | 1540 | { "","" }, |
1541 | { "","" }, | 1541 | { "","" }, |
1542 | { "","" }, | 1542 | { "","" }, |
1543 | { "","" }, | 1543 | { "","" }, |