[#10193] String.ord — David Flanagan <david@...>

Hi,

41 messages 2007/02/05
[#10197] Re: String.ord — Yukihiro Matsumoto <matz@...> 2007/02/06

Hi,

[#10198] Re: String.ord — David Flanagan <david@...> 2007/02/06

Yukihiro Matsumoto wrote:

[#10199] Re: String.ord — Daniel Berger <djberg96@...> 2007/02/06

David Flanagan wrote:

[#10200] Re: String.ord — David Flanagan <david@...> 2007/02/06

Daniel Berger wrote:

[#10208] Re: String.ord — "Nikolai Weibull" <now@...> 2007/02/06

On 2/6/07, David Flanagan <david@davidflanagan.com> wrote:

[#10213] Re: String.ord — David Flanagan <david@...> 2007/02/06

Nikolai Weibull wrote:

[#10215] Re: String.ord — "Nikolai Weibull" <now@...> 2007/02/06

On 2/6/07, David Flanagan <david@davidflanagan.com> wrote:

[#10216] Re: String.ord — David Flanagan <david@...> 2007/02/07

Nikolai Weibull wrote:

[#10288] Socket library should support abstract unix sockets — <noreply@...>

Bugs item #8597, was opened at 2007-02-13 16:10

12 messages 2007/02/13

[#10321] File.basename fails on Windows root paths — <noreply@...>

Bugs item #8676, was opened at 2007-02-15 10:09

11 messages 2007/02/15

[#10323] Trouble with xmlrpc — James Edward Gray II <james@...>

Some of the Ruby code used by TextMate makes use of xmlrpc/

31 messages 2007/02/15
[#10324] Re: Trouble with xmlrpc — "Berger, Daniel" <Daniel.Berger@...> 2007/02/15

> -----Original Message-----

[#10326] Re: Trouble with xmlrpc — James Edward Gray II <james@...> 2007/02/15

On Feb 15, 2007, at 1:29 PM, Berger, Daniel wrote:

[#10342] Re: Trouble with xmlrpc — James Edward Gray II <james@...> 2007/02/16

While I am complaining about xmlrpc, we have another issue. It's

[#10343] Re: Trouble with xmlrpc — Alex Young <alex@...> 2007/02/16

James Edward Gray II wrote:

[#10344] Re: Trouble with xmlrpc — James Edward Gray II <james@...> 2007/02/16

On Feb 16, 2007, at 12:08 PM, Alex Young wrote:

Re: MIME decoding confused by non-MIME characters

From: Sam Roberts <sroberts@...>
Date: 2007-02-28 19:02:32 UTC
List: ruby-core #10455
On Wed, Feb 28, 2007 at 09:18:06PM +0900, Urabe Shyouhei wrote:
> Brian Candler wrote:
> > That is, non-printable characters (here a UTF8-encoded BOM) are causing MIME
> > unpack to return garbage.
> >   
> Fixed.  Thanks reporting.

base64 decoding has same problem, doesn't it?

  > bom = "\xEF\xBB\xBF"
  => "\357\273\277"
  > b64 = ["hello"].pack('m*')
  => "aGVsbG8=\n"
  > (bom + b64).unpack('m*')
  => ["$\000\032\031[\e\e"]


Also:

     Any characters outside of the base64 alphabet are to be ignored in
	 base64-encoded data.
		- RFC2045, section 6.8

Instread, Ruby truncates input:

	> ["a"*40+"b"*20].pack('m*').sub("\n", " \n").unpack('m*')
	=> ["aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbb"]

It is common for extra whitespace, at ends of line for example, to be
present in base64.

Sam


In This Thread