Jussi Kukkonen wrote:
Yes, seems to work well now. Everything I could think of adding on the
phone ends up on the server -- and this is with no showctcapproperties
tricks.
So it seems you may be correct about the X-* types being the problem.
Patrick informed me that I can copy the default 01vcard-profile.xml into
~/.config/syncevolution-xml/datatypes/ and modify there: After a quick
test it seems that some extras are allowed but some will disable the
whole property.
As an example, this is the default TEL property:
<property name="TEL">
<value field="TEL"/>
<position field="TEL" repeat="array" increment="1" minshow="1"/>
<parameter name="TYPE" default="yes" positional="no" show="yes">
<value field="TEL_FLAGS" conversion="multimix" combine=",">
<enum name="HOME" value="B0"/>
<enum name="WORK" value="B1"/>
<enum mode="ignore" value="B2"/> <!-- OTHER -->
<enum name="VOICE" value="B3"/>
<enum name="CELL" value="B4"/>
<enum name="FAX" value="B5"/>
<enum name="PAGER" value="B6"/>
<enum name="PREF" value="B7"/>
<enum name="CAR" value="B8"/>
<enum name="X-EVOLUTION-CALLBACK" value="B9"/>
<enum name="X-EVOLUTION-RADIO" value="B10"/>
<enum name="X-EVOLUTION-TELEX" value="B11"/>
<enum name="X-EVOLUTION-TTYTDD" value="B12"/>
<enum mode="prefix" name="X-CustomLabel-" value="1.L"/>
<enum mode="prefix" name="X-Synthesis-Ref" value="2.L"/>
</value>
</parameter>
<parameter name="X-EVOLUTION-UI-SLOT" positional="no" show="yes">
<value field="TEL_SLOT"/>
</parameter>
</property>
Removing the parameter X-EVOLUTION_UI-SLOT is enough to get the phone to
send TEL data: the extra enums don't seem to bother it.
-Jussi
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
