[sync] Bug #157: convertCharset

[Karsten Fourmont]

> Great! I will soon spend some time on the SyncML stuff too, so we 
> should sync *SCNR* our efforts. 
:-)))

> I will concentrate on Sync4j clients  and Kronolith first.

Sounds good. VCARD parsing definetly needs improvment. Recurring events
are not implemented yet.
I use Sync4j for testing and it more or less works. However there are 
charset issues (bug 157). I'll do a seperate post on these.

I don't have any plany to work on vcard etc. support for the moment. 
With the only exception of bug 157 (charset stuff). So feel free to work 
on it.

> Shouldn't conflict resolution happen on the client side?

The client may do so but normally does not: Chapter 2.4. of the spec
(http://www.syncml.org/docs/syncml_sync_protocol_v11_20020215.pdf) says:

"Conflicts, which happen because of modifications on the same items on
the server and the client databases, are in general resolved by a sync
engine SW on the server device."


> Great. We probably should keep the todo list in framework/SyncML 
> uptodate also with who is working on what.

Right. Do you think it makes sense to create a seperate SyncML  queue on
bugs.horde.org? I would start putting the bugs reported on the list there.

BTW, my "karsten" account is not permitted to write wiki entries. Can 
somebody with admin rights on wiki.horde.org change this? thanks.


Cheers,
  Karsten