Hello!
What's the intended behavior of suppressempty for arrays?
"suppressempty": This optional boolean value. can be set to true if
this property must
never be sent empty (without values). This is the case for most
vCalendar fields, for example.
The default seems to be suppressempty=no (judging from the "can be set
to true"). When I have arrays with empty entries, will those be
generated?
Example:
- 35 : string RELATEDNAMES [ 0, 0, 0] : <array with 3
elements>
-- element 0 : <empty>
-- element 1 : <empty>
-- element 2 : <empty>
...
- 83 : string LABEL [ 0, 0, 0] : <array with 3 elements>
-- element 0 : "Spouse"
-- element 1 : "Manager"
-- element 2 : "Assistant"
<property name="X-ABRELATEDNAMES" groupfield="GROUP_TAG">
<value field="RELATEDNAMES"/>
<position field="RELATEDNAMES" repeat="array" increment="1"
minshow="0"/>
<parameter name="X-ABLabel" rule="HAVE-ABLABEL-PARAMETER"
sharedfield="yes">
<value field="LABEL"/>
</parameter>
</property>
...
<property name="X-ABLabel" suppressempty="yes" groupfield="GROUP_TAG"
rule="HAVE-ABLABEL-PROPERTY">
<value field="LABEL" repeat="array" increment="1" minshow="0"/>
<position field="LABEL" repeat="array" increment="1" minshow="1"/>
</property>
This leads to:
BEGIN:VCARD
VERSION:3.0
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.47//EN
REV:20140512T093706Z
UID:syuid384197.212266690650521
N:parserbug=;;;;
FN:parserbug=
X-EVOLUTION-FILE-AS:parserbug=
NICKNAME:user17
NOTE:triggers parser bug in Funambol 3.0: trailing = is mistaken for soft l
ine break=
item3.X-ABLabel:Spouse
item2.X-ABLabel:Manager
item1.X-ABLabel:Assistant
END:VCARD
The X-ABRELATEDNAMES properties were not generated. The labels should be
redundant, but some peers get confused. Google preserves them as
stand-alone X-ABLabel without tag. DAViCal preserves them with tag,
which then happened to confuse SyncEvolution's conversion code (separate
issue).
--
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
