On Wed, 2012-05-30 at 15:35 +0300, Andris Pavenis wrote:
> I have already earlier tried to use Android Funambol client with 
> libsynthesis based server.

I also tried with Android Funambol client + SyncEvolution +
libsynthesis, but although I made some progress I did not quite succeed.

Make sure that you have the following commit in your code:

commit 9b7164cfb0328c89aada0a3ee195493f31f561b7
Author: Patrick Ohly <[email protected]>
Date:   Fri Mar 2 17:04:05 2012 +0100

    SyncML TK: support (hexa-)decimal character entities in XML
    
    The Funambol Android client uses XML instead of WBXML and encodes
    some characters, like the at sign, with decimal character
    entities: &#64;
    
    This was not handled by the SyncML TK, which only supports some named
    entities and #43 as a special decimal entity, thus resulting in
    a 0x200b = SML_ERR_XLT_INVAL_SYNCML_DOC error.
    
    Fixed by fully supporting all decimal and hexadecimal character
    entities by converting the string value into integer and, with sanity
    checks, into a char. xmlHTMLEntity() now has to return a computed
    value and therefore its signature had to be changed away from
    returning a pointer to the result. Works because it never returned
    anything other than a char anyway.

It's in the master branch of
http://meego.gitorious.org/meego-middleware/libsynthesis

Not sure whether that is the issue that you are seeing. I don't remember
what issues I still had when I gave up.

Speaking of that master branch: Lukas, there are some other bug fixes
that you might want to merge back.

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

Reply via email to