Ruby Draft Specification

Thanks for your helpful comments.

Rex Jaeschke wrote:

As chair of ISO/IEC JTC 1/SC 22, where the mainstream languages support 10646 and where some WGs have had not-so-good experiences with national dialects of 646 (which don't have []{}| characters), I think you will get opposition for not supporting 10646. At the very least, you should provide rationale as to why you don't.

The reason why we don't support ISO/IEC 10646 in the draft is that ISO/IEC 10646 is not supported well in Ruby 1.8, which is our primary reference.

We therefore would like to refer to ISO/IEC 646 IRV, which has []{}| characters, instead of ISO/IEC 10646 (please see #56).
What do you think of it?

Referring to 646 IRV is fine with me, but be ready to deal with questions from some SC 22 NBs about your not supporting 10646. If you have a cover letter/rationale document that will accompany the final Fast Track submission, that would be a good place to explain your current choice, and, perhaps, your long-term plan about full 10646 support.

Rex Jaeschke wrote:

Referring to 646 IRV is fine with me, but be ready to deal with questions from some SC 22 NBs about your not supporting 10646. If you have a cover letter/rationale document that will accompany the final Fast Track submission, that would be a good place to explain your current choice, and, perhaps, your long-term plan about full 10646 support.

We will prepare such a document. Thank you.