From 2796c109dc2c56e2241410992d78bd8e0cccd71f Mon Sep 17 00:00:00 2001 From: Jarkko Hietaniemi Date: Wed, 4 Jul 2001 01:32:11 +0000 Subject: Support preferentially the Unicode 'scripts' definition in the \p{In...} notation since according to Unicode the scripts concept is more natural for matching than using the somewhat artificial block names. The block names are still available, though, and if there's a name conflict, the scripts one wins and the blocks one has to do with 'Block' appended to its name. For more information see http://www.unicode.org/unicode/reports/tr24/ p4raw-id: //depot/perl@11132 --- pod/perltodo.pod | 11 ----------- 1 file changed, 11 deletions(-) (limited to 'pod/perltodo.pod') diff --git a/pod/perltodo.pod b/pod/perltodo.pod index f96c7704e1..3c7243254e 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -87,17 +87,6 @@ class subtraction. http://www.unicode.org/unicode/reports/tr18/ -=head2 Unicode Scripts support - -Currently the C<\p{In...}> supports only the Blocks database, like -C<\p{BasicLatin}>, C<\p{InGreek}>, C<\p{InThai}>, but there's also the -Scripts database, which has members like C, C, -C, C. It is desireable that also the script names -could be used for the C<\p{In...}> construct. Note: needs to be -researched whether this is possible, that is, are there conflicts -between the Blocks and the Scripts, is the Blocks Greek the same as -the Scripts Greek? - =head2 use Thread for iThreads Artur Bergman's C module is a start on this, but needs to -- cgit v1.2.1