updated NEWS for 0.9 and bumped version to 0.9

1 files changed, 46 insertions, 42 deletions

diff --git a/NEWS b/NEWS
index 0bd19a5c..701eeaf3 100644
--- a/NEWS
+++ b/NEWS
@@ -2,19 +2,19 @@ SyncEvolution 0.8.1 -> 0.9, 12.08.2009
 --------------------------------------
 Synthesis SyncML Engine version: see src/synthesis/ChangeLog
 
-A major new release and the first step towards further improvements:
-from this release onwards, the Synthesis SyncML engine is used as the
+This is a major new release, with first steps towards further improvements.
+From this release on, the Synthesis SyncML engine will be the
 underlying SyncML and data conversion engine.
 
 A native GTK GUI is now included. The "sync-ui" program depends on a
 backend D-Bus service ("synevo-dbus-server") and several auxiliary
-files. Therefore it only runs without hacks after installation in 
-/usr (possible with .deb, .rpm and binary .tar.gz archives and
-with "sudo make install" after compiling from source). The
+files. Therefore, it only runs without hacks after installation in 
+/usr (possible with .deb, .rpm and binary .tar.gz archives, and
+with "sudo make install", after compiling from source). The
 normal command line tool still works without being installed.
 
-This release switches from an "all items are sent verbatim to the
-SyncML server" to a "parse and convert" data handling model. The
+In this release, the data handling model was changed from "all items
+are sent verbatim to the SyncML server" to "parse and convert". The
 argument for the former approach was that the SyncML server should be
 the only entity in the system which does data conversion. The previous
 releases already had to deviate from this approach to accommodate for
@@ -30,21 +30,21 @@ synchronize events and tasks with a wider variety of servers.
 It is still true that properties not supported by a server cannot
 be synchronized to other devices, so using a server with full
 iCalendar 2.0 support is recommended. But in contrast to 0.8.1,
-information that can only be stored locally is no longer lost when
-receiving an incomplete update from the SyncML server thanks to
-intelligent merging provided by the Synthesis engine. This depends on
+information that can be stored only locally is no longer lost when
+receiving an incomplete update from the SyncML server, thanks to
+intelligent merging, provided by the Synthesis engine. This depends on
 an accurate description of the server's capabilities, which might not
-be provided by all of them - still needs to be tested in more detail.
+be provided by all of them. This still needs to be tested in more detail.
 
 Interoperability with servers tested extensively in this release.
 The following servers are now supported:
 
-* ScheduleWorld. Very complete support for Evolution data, the only
-  known issues are around resuming from an interrupted sync.
+* ScheduleWorld. There is very complete support for Evolution data. The
+  only known issues are around resuming from an interrupted sync.
 
 * Google contact sync.
 
-  Google follows the vCard 2.1 specification and thus does not support
+  Google follows the vCard 2.1 specification, and thus does not support
   some of the vCard 3.0 additions, nor some of the common extensions. As
   a result, several properties are not synchronized (nickname, birthday,
   spouse/manager, URLs, ...). Only one top-level organization seems to
@@ -56,7 +56,7 @@ The following servers are now supported:
   adding such a contact again, the server discards the data sent by the
   client and recreates the contact with the data that it remembered.
 
-  Because SSL certificate checking for Google only works with libsoup
+  Because SSL certificate checking for Google works only with libsoup
   if the platform has a patched libsoup
   (http://bugzilla.gnome.org/show_bug.cgi?id=589323) or libsoup >=
   2.28, certificate checking remains turned off by default for
@@ -77,10 +77,10 @@ The following servers are now supported:
 
   Interoperability with the Funambol server was improved by adding
   support for some vCard extensions (X-MANAGER/ASSISTANT/SPOUSE/ANNIVERSARY,
-  #2418). Lost ACTION property is worked around (#2422).
+  #2418). Lost ACTION property has a work around (#2422).
 
-  To enabled that support in an existing configuration so that
-  exchanges items as iCalendar 2.0, use:
+  To enable that support in an existing configuration so that it
+  exchanges items in the more suitable iCalendar 2.0 format, use:
 
   syncevolution --configure --source-type sync=two-way \
                 funambol calendar todo
@@ -89,13 +89,17 @@ The following servers are now supported:
   syncevolution --configure --source-type type='todo:text/calendar!' \
                 funambol todo
 
+  Without the exclamation mark, format auto-negotiation would pick the
+  less capable vCalendar 1.0 format because that is marked as preferred
+  by the server.
 
-*** WARNING ***: after switching from a previous release to the
-current one or vice versa, do a "syncevolution --sync
+
+*** WARNING ***: After switching from a previous release to the
+current one, or vice versa, do a "syncevolution --sync
 refresh-from-server" or "--sync refresh-from-client" (depending on
-which side has the authoritative copy of the data) once to get client
+which side has the authoritative copy of the data) once, to get client
 and server into a consistent state. Not doing so can result in
-applying the same changes to the server multiple times and thus
+applying the same changes to the server multiple times, and thus
 duplicates.
 
 Other changes in detail:
@@ -105,27 +109,27 @@ Other changes in detail:
 * Both libcurl and libsoup can be selected at compile time as HTTP(S)
   transport mechanism.
 
-* SF #2101015: Expect: 100-continue header results in 417 Error with proxy
+* SF #2101015: Expect: 100-continue header results in 417 Error with proxy.
   Should no longer occur with the HTTP transports in this release.
 
-* SF #1874805: Syncing with Funambol results in loosing all-day property
+* SF #1874805: Syncing with Funambol results in loosing all-day property.
   This now works thanks to the Synthesis data conversion rules.
 
 * SF #2586600: Synchronisation with mobical.net fails in 0.8.1.
   Works now, but there are some known issues (Bugzilla #3009)
   and therefore mobical.net is not officially supported yet.
 
-* SF #2542968: separator for categories should not be escaped
+* SF #2542968: Separator for categories should not be escaped.
   Done correctly by the Synthesis vcard conversion.
 
 * bug fix: Evolution notes with only a summary and no description were
-  not sent correctly to the server: an empty text was sent instead of
-  sending the summary
+  not sent correctly to the server. Instead of sending the summary,
+  an empty text was sent. 
 
 * CTRL-C no longer kills SyncEvolution right away. Instead it
   asks the server to suspend the session. If that takes too
   long, then pressing CTRL-C twice quickly will abort the sync
-  without waiting for the server (warning, this may lead to a
+  without waiting for the server (Warning, this may lead to a
   slow sync in the next session).
 
 * WBXML is enabled by default now, except for Funambol (#2415).
@@ -134,25 +138,25 @@ Other changes in detail:
 
 * New configuration templates can be added to
   /etc/default/applications/syncevolution. These templates may contain
-  icons which are used by the GUI (no icons shipped right now).
+  icons, which are used by the GUI (no icons shipped right now).
 
 * Information about previous synchronization sessions is now stored in a
-  machine-readable format and can be accessed via the new
+  machine-readable format and can be accessed using the new
   --print-sessions options. The output of this information is more
-  complete and nicer formatted.
+  complete and more nicely formatted.
 
-* --status now not only shows data changes since the last sync, but also
-  the item changes (see README for the difference between the two).
+* --status now shows not only data changes since the last sync, but also
+  item changes (see README for the difference between the two).
 
 * The new --restore option allows restoring local data to the state as
   it was before or after a sync. For this to work, "logdir" must be set
   (done by default for new configurations). The format of database dumps
-  was changed to implement this feature: instead of in a flat file,
+  was changed to implement this feature. Instead of in a flat file,
   items are now saved as individual files in a directory. To get the
   previous format back (for example, to import as one .vcf or .ics file
   manually) concatenate these files.
 
-* With --remove one can remove configurations. It leaves data files and
+* With –-remove, one can remove configurations. It leaves data files and
   the local databases untouched.
 
 
@@ -163,17 +167,17 @@ Known issues:
   (#5185), which is a bit misleading. This is a result of #3314,
   which introduced changes not "received" from the server.
 
-* When a network error occurs in such a way that the client
-  never notices that the connection to the server got lost, then
-  it will hang forever waiting for the serer's reply (#3427).
+* When a network error occurs and the client
+  never notices that the connection to the server was lost, 
+  it will hang forever, waiting for the server's reply (#3427).
 
-* The file backend now only works for data formats understood
+* The file backend now works only for data formats understood
   by SyncEvolution and the Synthesis engine. Items are parsed
-  when exchanging them between backend, engine, and server,
-  in contrast to 0.8.1 where item content was not touched
+  when exchanging them among the backend, engine, and server,
+  in contrast to 0.8.1, where item content was not touched
   locally (#5046).
 
-* The ZYB.com server sends conflicting sync anchors, therefore
+* The ZYB.com server sends conflicting sync anchors, so
   most syncs don't work as expected (#2424).