summaryrefslogtreecommitdiff
path: root/pod/perlunicode.pod
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2011-12-03 21:37:48 -0700
committerKarl Williamson <public@khwilliamson.com>2011-12-20 22:02:42 -0700
commit0bd4278638caf33618355e433372cb94a2853626 (patch)
tree840a0ca31b59e6a775a4de80790627856a4b7523 /pod/perlunicode.pod
parent95cf23680e00af63884a0f886d7434eb1b930377 (diff)
downloadperl-0bd4278638caf33618355e433372cb94a2853626.tar.gz
pod nits
Diffstat (limited to 'pod/perlunicode.pod')
-rw-r--r--pod/perlunicode.pod3
1 files changed, 2 insertions, 1 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 0d8bd1ab9f..2529c97523 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -155,7 +155,8 @@ 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</The "Unicode Bug">. On EBCDIC machines there is
the additional problem that the value for such characters gives the EBCDIC
-character rather than the Unicode one.
+character rather than the Unicode one, thus it is more portable to use
+C<\N{U+...}> instead.
Additionally, if you