From: Christopher S. <ope...@ch...> - 2006-08-21 13:26:30
|
Hi, sorry for this late answer. Some of your reports are already reported but there are still a few issues which have no ticket. Am Samstag, 29. Juli 2006 21:06 schrieb Achim Spangler: > Hi, > > I reported some weeks ago on still existing problems with German > Umlauts, Resetting mobile phone and bad sync conflicts. http://www.opensync.org/ticket/288 ? > [...] > At first I was a irritated, as my mobile was STILL resetted with the > new merged irmc-sync plugin. But some evaluation revealed, that the > sync-group CACHE had some VERY VERY BAD DATA CACHED in my > $HOME/.opensync/ SO THAT MY MOBILE PHONE WAS CRASHED BY SOME RUBBISH > FROM OLDER TRIES!!!! ==> > 1) The OpenSync programs shouldn't cause problems, when the current > version of both sides don't contain any reference to broken cached > entries (in my case it was probably a event at date, where neiter > my mobile phone nor KDEPIM listed an event!!) > 2) there should be a call parameter option to multisync to clear any > cached data for a sync group. > At least I had to create a complete new group, to get a fresh > start. Please create a ticket, thanks! > OK - after I had created a new syncgroup, had cleared the complete > mobile phone contact list (after backing it up) and had initially > filtered everything but contacts OUT, I got my first successfull > sync!!! Yippie > > I was also able to successfully sync later with all parts including > notes, calendar .. > > Here some comments which I fill with debug information in the > anonymized attachement. > 1) It would be very fine, when debug messages on broken utf8 encoding > would list also the affected words (or line), so that I have a chance > to search KDEPIM and my mobile for those illegal data. > EVEN BETTER: > msynctool would immediately stop at thos positions, and would > allow the user to define a corrected text The problem is that your phone exports some data as ISO-8859-1. This cause the broken characters. I hope that we can fix this in the devel-branch. http://www.opensync.org/ticket/288 > 2) There are still several <tag> types for events and contacts, which > are differing between KDEPIM and irmc-sync/K750i, so that the user > gets lots of erroneous conflict reports. > I attache several conflict reports, where I replaced all personal > data I was aware of Please create a ticket. > > PLEASE PLEASE DEAR developers check the attachement and derive > decision plans to let opensync ignore in future those differences. Thanks again for your feedback. We'll do our best :) Best regards Christopher |