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.


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).

All this only affects *generation* of vXXX and only the pre-MIME-DIR mode.

Except that the fully transparent folding mechanism in MIME-DIR will now also 
prefer folding multi-values after a value separator if possible (but this is 
merely cosmetic, as it makes generated iCalendar with EXDATEs more 
human-readable).


_______________________________________________
os-libsynthesis mailing list
os-libsynthesis@synthesis.ch
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis

Reply via email to