From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-25 b6b47AF: Properly encode/decode base64Binary data in SOAP Date: Mon, 14 Mar 2016 19:55:52 +0200 Message-ID: <83io0pc5av.fsf@gnu.org> References: <20160106200404.17375.71733@vcs.savannah.gnu.org> <87oaalxvi7.fsf@linux-m68k.org> <87k2l9xg19.fsf@linux-m68k.org> <87d1r1x84z.fsf@linux-m68k.org> <83lh5mfjsn.fsf@gnu.org> <83oaaidydx.fsf@gnu.org> <83io0qdtb0.fsf@gnu.org> <8760wpxz9z.fsf@gmx.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1457978231 25725 80.91.229.3 (14 Mar 2016 17:57:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Mar 2016 17:57:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 14 18:57:04 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1afWjf-0005vA-LA for ged-emacs-devel@m.gmane.org; Mon, 14 Mar 2016 18:56:55 +0100 Original-Received: from localhost ([::1]:43035 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afWjf-0006HP-4n for ged-emacs-devel@m.gmane.org; Mon, 14 Mar 2016 13:56:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60010) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afWjA-0006Cn-Gd for emacs-devel@gnu.org; Mon, 14 Mar 2016 13:56:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1afWj7-0005ff-B1 for emacs-devel@gnu.org; Mon, 14 Mar 2016 13:56:24 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35914) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1afWj7-0005fb-8A; Mon, 14 Mar 2016 13:56:21 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2622 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1afWj6-000540-5S; Mon, 14 Mar 2016 13:56:20 -0400 In-reply-to: (message from Stefan Monnier on Mon, 14 Mar 2016 08:39:06 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:201724 Archived-At: > From: Stefan Monnier > Date: Mon, 14 Mar 2016 08:39:06 -0400 > > > On the server side, debbugs.gnu.org, a perl script using SOAP::Lite is > > responsible for encoding the attributes. IIUC, the internal package > > SOAP::Serializer decides depending on the contents of a string, whether > > it shall be xsd:base64Binary, or not. See: > > > $self->typelookup({ > > 'base64Binary' => > > [10, sub {$_[0] =~ /[^\x09\x0a\x0d\x20-\x7f]/ }, 'as_base64Binary'], > > ... > > So on the receiving side, debbugs.el should similarly check > multibyteness of the string to decide what to do with it, I think. ??? The multibyteness of a string is an illusion created by Emacs, as you well know. There's nothing in the byte stream that is inherently multibyte or unibyte. The only thing that the multibyteness of the string could tell us is what kind of processing did soap-client.el do to produce the string, that's all. So I'm unsure what you had in mind when you wrote this. I'm probably missing something, but what?