Hi,

In message "Re: \u escapes in string literals: proof of concept     implementation"
    on Tue, 6 Nov 2007 14:58:24 +0900, Martin Duerst <duerst / it.aoyama.ac.jp> writes:

|>Rather, "\x{4366 4544} \x{3f2d 3159}" for both of Shift_JIS and
|>EUC-JP
|
|Can you explain how you got these numbers?

Perhaps JIS 0208 KU for higher byte, and TEN for lower byte, in other
words, EUC-JP code point with each byte MSB masked.

Anyway I have no plan to use \u nor \x{} for string representation.
It's only for literals, not backwards.

Your proposal of using hexadecimal instead of octal in
[ruby-core:13026] sounds interesting.

I'd like to merge \u patch (with option c in [ruby-core:12769]).  Who
is going to be in charge?  David? or Nobu?

							matz.