Movatterモバイル変換

[Moved to DR at the May, 2015 meeting.]

Proposed resolution (April, 2015):

Change 5.2 [lex.phases] paragraph 1 number 1 as follows:

...(An implementation may use any internal encoding, so long asan actual extended character encountered in the source file, andthe same extended character expressed in the source file as auniversal-character-name (i.e.e.g., usingthe\uXXXX notation), are handled equivalently exceptwhere this replacement is reverted in a raw string literal.)

According to 5.2 [lex.phases] paragraph 1, first phase,

Any source file character not in the basic source characterset (5.3.1 [lex.charset]) is replaced by theuniversal-character-name that designates that character. (Animplementation may use any internal encoding, so long as anactual extended character encountered in the source file,and the same extended character expressed in the source fileas a universal-character-name (i.e., usingthe\uXXXX notation), are handled equivalentlyexcept where this replacement is reverted in a raw stringliteral.)

This wording is obviously not intended to exclude the use ofcharacters with code points larger than0xffff, butthe reference to “the\uXXXX notation” mightsuggest that the\Uxxxxxxxx form is not allowed.