From: Gregory Brown <gregory.t.brown@...>
Date: 2009-08-13T20:40:31+09:00
Subject: Re: 1.9 String and M17N documentation

On Thu, Aug 13, 2009 at 5:14 AM, Brian Candler<b.candler@pobox.com> wrote:

> That could actually be useful in helping to combine strings from
> different sources. All the compatibility rules would vanish, and rather
> than raising exceptions, ruby would just "do the right thing".
> Transcoding to BINARY/ASCII-8BIT would be a null operation, so building
> a binary string would be safe too.
>
> This isn't a total U-turn, but it would be quite a major shift and I
> suspect too big for 1.9.x.

Yeah, this is also a reasonable behavior, IMO.  However, I think Matz
has some reservation about (potentially lossy) transcoding, which is
the reason for the M17N system in the first place.  Special casing
form ASCII-8BIT might be more conservative.

-greg