| Summary | Horde-SyncML encodes XML-Tags |
| Queue | Synchronization |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | q0107 (at) cuba (dot) ionum (dot) ch |
| Created | 06/15/2011 (5259 days ago) |
| Due | |
| Updated | 06/20/2011 (5254 days ago) |
| Assigned | 06/15/2011 (5259 days ago) |
| Resolved | 06/20/2011 (5254 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
xml-entities), even the syncml output who has content-type
"application/vnd.syncml+xml". i browsed through horde-syncml source
code and found nothing. the bug may be elsewhere ...
i'm programming a syncml-client-framework in perl and it worked with
horde 3. since i upgraded to horde 4 my xml-parser throws an error.
Priority ⇒ 1. Low
State ⇒ Feedback
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Horde-SyncML encodes XML-Tags
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Example:
-- snip ---
END:VEVENT
END:VCALENDAR
]]></Data>
</Item>
</Add>
</Sync>
<Status><CmdID>265</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>7</CmdRef>
<Cmd>Alert</Cmd>
<TargetRef>card</TargetRef>
<SourceRef>card</SourceRef>
<Data>200</Data>
it should look like this:
END:VEVENT
END:VCALENDAR
]]></Data>
</Item>
</Add>
</Sync>
<Status><CmdID>265</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>7</CmdRef>
<Cmd>Alert</Cmd>
<TargetRef>card</TargetRef>
<SourceRef>card</SourceRef>
<Data>200</Data>