[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-25 b6b47AF: Properly encode/decode base64Binary data in SOAP

From: Thomas Fitzsimmons
Subject: Re: emacs-25 b6b47AF: Properly encode/decode base64Binary data in SOAP
Date: Mon, 14 Mar 2016 10:58:44 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Michael Albinus <address@hidden> writes:

> Stefan Monnier <address@hidden> writes:
>>> Well, if debbugs.el would get an indication from soap-client.el, whether
>>> a string was encoded as xsd:string or xsd:base64Binary, it could decode
>>> the latter values itself.
>> The multibyteness of the string should be exactly that indication.
> It isn't, at least in its current implementation. Let's take our example
> (debbugs-get-status 22285). The debbugs server returns (beside other
> data)
> <severity xsi:type="xsd:string">normal</severity>
> <originator 
> xsi:type="xsd:base64Binary">Q2zDqW1lbnQgUGl0LS1DbGF1ZGVsIDxjbGVtZW50LnBpdGNsYXVkZWxAbGl2ZS5jb20+</originator>
> Testing multibyteness returns
> (multibyte-string-p (cdr (assq 'severity (car (debbugs-get-status 22285)))))
> t
> (multibyte-string-p (cdr (assq 'originator (car (debbugs-get-status 22285)))))
> t

Yes, that's because of Andreas's soap-client patch
(b6b47af82f6c7d960388ec46dd8ab371c2e34de4), the patch under discussion
that I'd like to revert.  Without that patch, the originator check would
return nil.

Andreas has pointed me to the issue he applied it to fix:


My plan is to replicate that without the soap-client patch, and try to
fix it a different way, in Debbugs.  From that thread, I think this will
show it:

(async-get (async-start
            `(lambda ()
               (load ,(locate-library "debbugs"))
               (debbugs-get-status 22285))))

I'll work on this hopefully this evening unless you beat me to it.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]