Yesterday we had our first instance of Chandler sending a character
not supported by XML to Cosmo, in this case an 0x0c (page break).
Cosmo rightly rejected the data as it was not legal XML. But the
question remains, what do we do about this situation? It comes down to:
1) Strip such characters before sending them in XML
2) Abort a sync if the data has such a character
3) Chandler+Cosmo agree on an encoding mechanism
#3 feels like the right thing to do. One suggestion is to encode all
non-allowed by XML characters using %XX where the XX are hex digits.
Should we take that route?
Also, what does Cosmo do when a CalDAV client sends an ICS body that
has a character like 0x0c in it?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
