emphasized the need to chose the right uri/type combination, in particular with ScheduleWorld
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@179 15ad00c4-1369-45f4-8270-35d70d36bdcd
This commit is contained in:
parent
78acb31a56
commit
335f13515b
10
README
10
README
|
@ -254,7 +254,8 @@ Configuration with ScheduleWorld
|
|||
--------------------------------
|
||||
|
||||
It is recommended to sync against the new vCard 3.0 URI (card3) and
|
||||
iCalendar 2.0 URI (cal2, task2). These are the native formats of
|
||||
iCalendar 2.0 URIs (cal2, task2), using the "text/vcard", "text/calendar"
|
||||
and "text/x-todo" type setting respectively. These are the native formats of
|
||||
Evolution and a lot of effort went into ensuring that they store as
|
||||
much Evolution data as possible. SyncEvolution is primarily tested
|
||||
against ScheduleWorld. The "scheduleworld_1" example configuration is
|
||||
|
@ -516,6 +517,13 @@ Be sure to always include the following information:
|
|||
what you expect to see,
|
||||
what you get instead
|
||||
|
||||
*Warning*: logs may expose user/password if the basic authentication
|
||||
mechanism is used. Before posting such logs search for
|
||||
<Type>syncml:auth-basic</Type>
|
||||
and overwrite the <Data> directly afterwards. It might look like this
|
||||
and occur multiple times in the log:
|
||||
<Data>MGKlldQ2MZnJha3RhbA==</Data>
|
||||
|
||||
|
||||
Compiling from Source
|
||||
---------------------
|
||||
|
|
|
@ -18,13 +18,20 @@ sync = two-way
|
|||
syncModes = slow,two-way,refresh-client,refresh-server
|
||||
|
||||
# specifies the format of the data
|
||||
#
|
||||
# text/calendar = Evolution calender data (in iCalendar 2.0 format)
|
||||
# text/x-todo = Evolution task data (iCalendar 2.0)
|
||||
# text/x-vcard = Evolution contact data in vCard 2.1 format
|
||||
# (works with most servers)
|
||||
# test/vcard = Evolution contact data in vCard 3.0 (RFC 2425) format
|
||||
# (internal format of Evolution, preferred with servers
|
||||
# that support it)
|
||||
# that support it and thus recommended for ScheduleWorld
|
||||
# together with the "card3" uri)
|
||||
#
|
||||
# Sending and receiving items in the same format as used by the server for
|
||||
# the uri selected below is essential. Errors while parsing and/or storing
|
||||
# items one either client or server can be caused by a mismatch between
|
||||
# type and uri.
|
||||
type = text/x-vcard
|
||||
|
||||
|
||||
|
|
Loading…
Reference in a new issue