On Wed, 2010-09-08 at 16:40 +0100, Lukas Zeller wrote: > On Sep 8, 2010, at 16:25 , Lukas Zeller wrote: > > > I'm now in the process of merging some updates on our side and will > > push them onto luz in the next hour or so (but leave master at its > > current position for now). > > Done, and tagged as libsynthesis_3.4.0.16 in our git in the luz branch. > > Two notes regarding these changes (the rest should be fully > transparent for the apps using libsynthesis): > > > 1) 0e139ee311 (engine 3.4.0.10: separate changelogs, pendingmaps and > pendingitem for each profile to allow for different syncsets in > profiles (as needed by SyncML PRO iOS)): > > This change is transparent as long as the app using libsynthesis does > not mess with the *.bfi files directly, especially make assumptions > about their names. It is possible to stay with the old unified > changelog for applications not using more than one profile (by > explicitly turning off the new separate changelogs in the config), but > I would recommend to use the new way because the old way is deprecated > and might be removed entirely later.
SyncEvolution has already worked the new way by using separate bin directories for each peer. The commit message says that transition to the new format is done automatically. Doesn't this prevent downgrading? While is not always possible, we try to support that in SyncEvolution as often as possible. Is there a way to avoid the automatic conversion and continue writing in the old format? > 2) 4275e77001 (engine: refined folding for pre-MIME-DIR and MIME-DIR - > new "foldbetween" <property> attribute.): > > This changes the way folding occurs in pre-MIME-DIR formats (vCard > 2.1, vCalendar 1.0), as it no longer inserts extra spaces to break > long multi-value properties with no spaces in the values, but instead > uses QP (as it already did for single-value properties with no spaces > in the value). However, as the new (correct) behaviour probably causes > more troubles for poor implementation with multi-values like EXDATE, > there's now a new property-level config option to allow inserting a > space between value and value separator when needed to wrap long > lines. With this, EXDATE is rendered similar as before (before the > spaces were inserted AFTER the separator, which caused a extra LEADING > space, while now it will be an extra TRAILING space). > > So the recommendation is to add foldbetween="yes" in the config for > EXDATE (and possibly other semantically similar properties). What are such other properties? Anything which has a separator in the value? Here are some that I can think of right away: ORG, CATEGORY -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
