From: Karl Williamson Date: Thu, 25 Feb 2010 19:36:53 +0000 (-0700) Subject: Note that \N{U+...} forces character semantics X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=195e542a7ae4c1d9d4590b90e4b3949219cb0b9f;p=p5sagit%2Fp5-mst-13.2.git Note that \N{U+...} forces character semantics --- diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 6ede1a4..ae13a33 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -146,14 +146,15 @@ If you use a Unicode editor to edit your program, Unicode characters may occur directly within the literal strings in UTF-8 encoding, or UTF-16. (The former requires a BOM or C, the latter requires a BOM.) -Unicode characters can also be added to a string by using the C<\x{...} or C<\N{U+...}> -notations. The Unicode code for the desired character, in hexadecimal, -should be placed in the braces. For instance, a smiley face is +Unicode characters can also be added to a string by using the C<\N{U+...}> +notation. The Unicode code for the desired character, in hexadecimal, +should be placed in the braces, after the C. For instance, a smiley face is C<\N{U+263A}>. -For characters below 0x100 you may get byte semantics instead of +Alternatively, you can use the C<\x{...}> notation for characters 0x100 and +above. For characters below 0x100 you may get byte semantics instead of character semantics; see L. On EBCDIC machines there is -the additional problem with the C\x{...} form in that the value for such characters gives the EBCDIC +the additional problem that the value for such characters gives the EBCDIC character rather than the Unicode one. Additionally, if you