From: Karl Williamson Date: Mon, 24 May 2010 14:08:51 +0000 (-0600) Subject: PATCH: correct misstatement, formats in perlunicode X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=d5cd9e7bba185db6dc6b1e6fa215978a38ae9ea8;p=p5sagit%2Fp5-mst-13.2.git PATCH: correct misstatement, formats in perlunicode This is suitable for 5.12.2, but not many people use this feature. --- diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 6d50e83..1b4c249 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -876,13 +876,13 @@ would be intersecting with nothing (resulting in an empty set). =head2 User-Defined Case Mappings -You can also define your own mappings to be used in the lc(), -lcfirst(), uc(), and ucfirst() (or their string-inlined versions). +You can also define your own mappings to be used in C, +C, C, and C (or their string-inlined versions, +C<\L>, C<\l>, C<\U>, and C<\u>). The principle is similar to that of user-defined character properties: to define subroutines -with names like C (for lc() and lcfirst()), C (for -the first character in ucfirst()), and C (for uc(), and the -rest of the characters in ucfirst()). +with names C (for C and C); C (for +C); and C (for C). The string returned by the subroutines needs to be two hexadecimal numbers separated by two tabulators: the two numbers being, respectively, the source @@ -894,17 +894,18 @@ code point and the destination code point. For example: END } -defines an uc() mapping that causes only the character "a" +defines a mapping for C (and C<\U>) that causes only the character "a" to be mapped to "A"; all other characters will remain unchanged. (For serious hackers only) The above means you have to furnish a complete mapping; you can't just override a couple of characters and leave the rest unchanged. You can find all the mappings in the directory -C<$Config{privlib}>/F. The mapping data is returned as the -here-document, and the C are special exception mappings -derived from <$Config{privlib}>/F. The "Digit" and +C<$Config{privlib}>F. The mapping data is returned as the +here-document. The C> hashes in those files are special +exception mappings derived from +C<$Config{privlib}>F. The "Digit" and "Fold" mappings that one can see in the directory are not directly -user-accessible, one can use either the C module, or just match +user-accessible, one can use either the L module, or just match case-insensitively (that's when the "Fold" mapping is used). The mappings will only take effect on scalars that have been marked as having