5 no warnings 'surrogate'; # surrogates can be inputs to this
12 our @ISA = qw(Exporter);
14 our @EXPORT_OK = qw(charinfo
16 charblocks charscripts
18 general_categories bidi_types
20 casefold all_casefolds casespec
34 Unicode::UCD - Unicode character database
38 use Unicode::UCD 'charinfo';
39 my $charinfo = charinfo($codepoint);
41 use Unicode::UCD 'casefold';
42 my $casefold = casefold(0xFB00);
44 use Unicode::UCD 'all_casefolds';
45 my $all_casefolds_ref = all_casefolds();
47 use Unicode::UCD 'casespec';
48 my $casespec = casespec(0xFB00);
50 use Unicode::UCD 'charblock';
51 my $charblock = charblock($codepoint);
53 use Unicode::UCD 'charscript';
54 my $charscript = charscript($codepoint);
56 use Unicode::UCD 'charblocks';
57 my $charblocks = charblocks();
59 use Unicode::UCD 'charscripts';
60 my $charscripts = charscripts();
62 use Unicode::UCD qw(charscript charinrange);
63 my $range = charscript($script);
64 print "looks like $script\n" if charinrange($range, $codepoint);
66 use Unicode::UCD qw(general_categories bidi_types);
67 my $categories = general_categories();
68 my $types = bidi_types();
70 use Unicode::UCD 'prop_aliases';
71 my @space_names = prop_aliases("space");
73 use Unicode::UCD 'prop_value_aliases';
74 my @gc_punct_names = prop_value_aliases("Gc", "Punct");
76 use Unicode::UCD 'prop_invlist';
77 my @puncts = prop_invlist("gc=punctuation");
79 use Unicode::UCD 'prop_invmap';
80 my ($list_ref, $map_ref, $format, $missing)
81 = prop_invmap("General Category");
83 use Unicode::UCD 'compexcl';
84 my $compexcl = compexcl($codepoint);
86 use Unicode::UCD 'namedseq';
87 my $namedseq = namedseq($named_sequence_name);
89 my $unicode_version = Unicode::UCD::UnicodeVersion();
91 my $convert_to_numeric =
92 Unicode::UCD::num("\N{RUMI DIGIT ONE}\N{RUMI DIGIT TWO}");
96 The Unicode::UCD module offers a series of functions that
97 provide a simple interface to the Unicode
100 =head2 code point argument
102 Some of the functions are called with a I<code point argument>, which is either
103 a decimal or a hexadecimal scalar designating a Unicode code point, or C<U+>
104 followed by hexadecimals designating a Unicode code point. In other words, if
105 you want a code point to be interpreted as a hexadecimal number, you must
106 prefix it with either C<0x> or C<U+>, because a string like e.g. C<123> will be
107 interpreted as a decimal code point. Note that the largest code point in
117 my $v_unicode_version; # v-string.
120 my ($rfh, @path) = @_;
122 unless (defined $$rfh) {
125 $f = File::Spec->catfile($d, "unicore", @path);
126 last if open($$rfh, $f);
129 croak __PACKAGE__, ": failed to find ",
130 File::Spec->catfile(@path), " in @INC"
136 sub _dclone ($) { # Use Storable::dclone if available; otherwise emulate it.
138 use if defined &DynaLoader::boot_DynaLoader, Storable => qw(dclone);
140 return dclone(shift) if defined &dclone;
144 return $arg unless $type; # No deep cloning needed for scalars
146 if ($type eq 'ARRAY') {
148 foreach my $element (@$arg) {
149 push @return, &_dclone($element);
153 elsif ($type eq 'HASH') {
155 foreach my $key (keys %$arg) {
156 $return{$key} = &_dclone($arg->{$key});
161 croak "_dclone can't handle " . $type;
167 use Unicode::UCD 'charinfo';
169 my $charinfo = charinfo(0x41);
171 This returns information about the input L</code point argument>
172 as a reference to a hash of fields as defined by the Unicode
173 standard. If the L</code point argument> is not assigned in the standard
174 (i.e., has the general category C<Cn> meaning C<Unassigned>)
175 or is a non-character (meaning it is guaranteed to never be assigned in
177 C<undef> is returned.
179 Fields that aren't applicable to the particular code point argument exist in the
180 returned hash, and are empty.
182 The keys in the hash with the meanings of their values are:
188 the input L</code point argument> expressed in hexadecimal, with leading zeros
189 added if necessary to make it contain at least four hexdigits
193 name of I<code>, all IN UPPER CASE.
194 Some control-type code points do not have names.
195 This field will be empty for C<Surrogate> and C<Private Use> code points,
196 and for the others without a name,
197 it will contain a description enclosed in angle brackets, like
198 C<E<lt>controlE<gt>>.
203 The short name of the general category of I<code>.
204 This will match one of the keys in the hash returned by L</general_categories()>.
206 The L</prop_value_aliases()> function can be used to get all the synonyms
207 of the category name.
211 the combining class number for I<code> used in the Canonical Ordering Algorithm.
212 For Unicode 5.1, this is described in Section 3.11 C<Canonical Ordering Behavior>
214 L<http://www.unicode.org/versions/Unicode5.1.0/>
216 The L</prop_value_aliases()> function can be used to get all the synonyms
217 of the combining class number.
221 bidirectional type of I<code>.
222 This will match one of the keys in the hash returned by L</bidi_types()>.
224 The L</prop_value_aliases()> function can be used to get all the synonyms
225 of the bidi type name.
227 =item B<decomposition>
229 is empty if I<code> has no decomposition; or is one or more codes
230 (separated by spaces) that, taken in order, represent a decomposition for
231 I<code>. Each has at least four hexdigits.
232 The codes may be preceded by a word enclosed in angle brackets then a space,
233 like C<E<lt>compatE<gt> >, giving the type of decomposition
235 This decomposition may be an intermediate one whose components are also
236 decomposable. Use L<Unicode::Normalize> to get the final decomposition.
240 if I<code> is a decimal digit this is its integer numeric value
244 if I<code> represents some other digit-like number, this is its integer
249 if I<code> represents a whole or rational number, this is its numeric value.
250 Rational values are expressed as a string like C<1/4>.
254 C<Y> or C<N> designating if I<code> is mirrored in bidirectional text
258 name of I<code> in the Unicode 1.0 standard if one
259 existed for this code point and is different from the current name
263 As of Unicode 6.0, this is always empty.
267 is empty if there is no single code point uppercase mapping for I<code>
268 (its uppercase mapping is itself);
269 otherwise it is that mapping expressed as at least four hexdigits.
270 (L</casespec()> should be used in addition to B<charinfo()>
271 for case mappings when the calling program can cope with multiple code point
276 is empty if there is no single code point lowercase mapping for I<code>
277 (its lowercase mapping is itself);
278 otherwise it is that mapping expressed as at least four hexdigits.
279 (L</casespec()> should be used in addition to B<charinfo()>
280 for case mappings when the calling program can cope with multiple code point
285 is empty if there is no single code point titlecase mapping for I<code>
286 (its titlecase mapping is itself);
287 otherwise it is that mapping expressed as at least four hexdigits.
288 (L</casespec()> should be used in addition to B<charinfo()>
289 for case mappings when the calling program can cope with multiple code point
294 the block I<code> belongs to (used in C<\p{Blk=...}>).
295 See L</Blocks versus Scripts>.
300 the script I<code> belongs to.
301 See L</Blocks versus Scripts>.
305 Note that you cannot do (de)composition and casing based solely on the
306 I<decomposition>, I<combining>, I<lower>, I<upper>, and I<title> fields;
307 you will need also the L</compexcl()>, and L</casespec()> functions.
311 # NB: This function is nearly duplicated in charnames.pm
315 if ($arg =~ /^[1-9]\d*$/) {
317 } elsif ($arg =~ /^(?:[Uu]\+|0[xX])?([[:xdigit:]]+)$/) {
324 # Populated by _num. Converts real number back to input rational
325 my %real_to_rational;
327 # To store the contents of files found on disk.
340 # This function has traditionally mimicked what is in UnicodeData.txt,
341 # warts and all. This is a re-write that avoids UnicodeData.txt so that
342 # it can be removed to save disk space. Instead, this assembles
343 # information gotten by other methods that get data from various other
344 # files. It uses charnames to get the character name; and various
347 use feature 'unicode_strings';
349 # Will fail if called under minitest
350 use if defined &DynaLoader::boot_DynaLoader, "Unicode::Normalize" => qw(getCombinClass NFD);
353 my $code = _getcode($arg);
354 croak __PACKAGE__, "::charinfo: unknown code '$arg'" unless defined $code;
356 # Non-unicode implies undef.
357 return if $code > 0x10FFFF;
360 my $char = chr($code);
362 @CATEGORIES =_read_table("To/Gc.pl") unless @CATEGORIES;
363 $prop{'category'} = _search(\@CATEGORIES, 0, $#CATEGORIES, $code)
364 // $utf8::SwashInfo{'ToGc'}{'missing'};
366 return if $prop{'category'} eq 'Cn'; # Unassigned code points are undef
368 $prop{'code'} = sprintf "%04X", $code;
369 $prop{'name'} = ($char =~ /\p{Cntrl}/) ? '<control>'
370 : (charnames::viacode($code) // "");
372 $prop{'combining'} = getCombinClass($code);
374 @BIDIS =_read_table("To/Bc.pl") unless @BIDIS;
375 $prop{'bidi'} = _search(\@BIDIS, 0, $#BIDIS, $code)
376 // $utf8::SwashInfo{'ToBc'}{'missing'};
378 # For most code points, we can just read in "unicore/Decomposition.pl", as
379 # its contents are exactly what should be output. But that file doesn't
380 # contain the data for the Hangul syllable decompositions, which can be
381 # algorithmically computed, and NFD() does that, so we call NFD() for
382 # those. We can't use NFD() for everything, as it does a complete
383 # recursive decomposition, and what this function has always done is to
384 # return what's in UnicodeData.txt which doesn't show that recursiveness.
385 # Fortunately, the NFD() of the Hanguls doesn't have any recursion
387 # Having no decomposition implies an empty field; otherwise, all but
388 # "Canonical" imply a compatible decomposition, and the type is prefixed
389 # to that, as it is in UnicodeData.txt
390 UnicodeVersion() unless defined $v_unicode_version;
391 if ($v_unicode_version ge v2.0.0 && $char =~ /\p{Block=Hangul_Syllables}/) {
392 # The code points of the decomposition are output in standard Unicode
393 # hex format, separated by blanks.
394 $prop{'decomposition'} = join " ", map { sprintf("%04X", $_)}
395 unpack "U*", NFD($char);
398 @DECOMPOSITIONS = _read_table("Decomposition.pl")
399 unless @DECOMPOSITIONS;
400 $prop{'decomposition'} = _search(\@DECOMPOSITIONS, 0, $#DECOMPOSITIONS,
404 # Can use num() to get the numeric values, if any.
405 if (! defined (my $value = num($char))) {
406 $prop{'decimal'} = $prop{'digit'} = $prop{'numeric'} = "";
410 $prop{'decimal'} = $prop{'digit'} = $prop{'numeric'} = $value;
414 # For non-decimal-digits, we have to read in the Numeric type
415 # to distinguish them. It is not just a matter of integer vs.
416 # rational, as some whole number values are not considered digits,
417 # e.g., TAMIL NUMBER TEN.
418 $prop{'decimal'} = "";
420 @NUMERIC_TYPES =_read_table("To/Nt.pl") unless @NUMERIC_TYPES;
421 if ((_search(\@NUMERIC_TYPES, 0, $#NUMERIC_TYPES, $code) // "")
424 $prop{'digit'} = $prop{'numeric'} = $value;
428 $prop{'numeric'} = $real_to_rational{$value} // $value;
433 $prop{'mirrored'} = ($char =~ /\p{Bidi_Mirrored}/) ? 'Y' : 'N';
435 %UNICODE_1_NAMES =_read_table("To/Na1.pl", "use_hash") unless %UNICODE_1_NAMES;
436 $prop{'unicode10'} = $UNICODE_1_NAMES{$code} // "";
438 UnicodeVersion() unless defined $v_unicode_version;
439 if ($v_unicode_version ge v6.0.0) {
440 $prop{'comment'} = "";
443 %ISO_COMMENT = _read_table("To/Isc.pl", "use_hash") unless %ISO_COMMENT;
444 $prop{'comment'} = (defined $ISO_COMMENT{$code})
445 ? $ISO_COMMENT{$code}
449 %SIMPLE_UPPER = _read_table("To/Uc.pl", "use_hash") unless %SIMPLE_UPPER;
450 $prop{'upper'} = (defined $SIMPLE_UPPER{$code})
451 ? sprintf("%04X", $SIMPLE_UPPER{$code})
454 %SIMPLE_LOWER = _read_table("To/Lc.pl", "use_hash") unless %SIMPLE_LOWER;
455 $prop{'lower'} = (defined $SIMPLE_LOWER{$code})
456 ? sprintf("%04X", $SIMPLE_LOWER{$code})
459 %SIMPLE_TITLE = _read_table("To/Tc.pl", "use_hash") unless %SIMPLE_TITLE;
460 $prop{'title'} = (defined $SIMPLE_TITLE{$code})
461 ? sprintf("%04X", $SIMPLE_TITLE{$code})
464 $prop{block} = charblock($code);
465 $prop{script} = charscript($code);
469 sub _search { # Binary search in a [[lo,hi,prop],[...],...] table.
470 my ($table, $lo, $hi, $code) = @_;
474 my $mid = int(($lo+$hi) / 2);
476 if ($table->[$mid]->[0] < $code) {
477 if ($table->[$mid]->[1] >= $code) {
478 return $table->[$mid]->[2];
480 _search($table, $mid + 1, $hi, $code);
482 } elsif ($table->[$mid]->[0] > $code) {
483 _search($table, $lo, $mid - 1, $code);
485 return $table->[$mid]->[2];
489 sub _read_table ($;$) {
491 # Returns the contents of the mktables generated table file located at $1
492 # in the form of either an array of arrays or a hash, depending on if the
493 # optional second parameter is true (for hash return) or not. In the case
494 # of a hash return, each key is a code point, and its corresponding value
495 # is what the table gives as the code point's corresponding value. In the
496 # case of an array return, each outer array denotes a range with [0] the
497 # start point of that range; [1] the end point; and [2] the value that
498 # every code point in the range has. The hash return is useful for fast
499 # lookup when the table contains only single code point ranges. The array
500 # return takes much less memory when there are large ranges.
502 # This function has the side effect of setting
503 # $utf8::SwashInfo{$property}{'format'} to be the mktables format of the
505 # $utf8::SwashInfo{$property}{'missing'} to be the value for all entries
506 # not listed in the table.
507 # where $property is the Unicode property name, preceded by 'To' for map
508 # properties., e.g., 'ToSc'.
510 # Table entries look like one of:
511 # 0000 0040 Common # [65]
515 my $return_hash = shift;
516 $return_hash = 0 unless defined $return_hash;
520 my $list = do "unicore/$table";
522 # Look up if this property requires adjustments, which we do below if it
524 require "unicore/Heavy.pl";
525 my $property = $table =~ s/\.pl//r;
526 $property = $utf8::file_to_swash_name{$property};
527 my $to_adjust = defined $property
528 && $utf8::SwashInfo{$property}{'format'} eq 'a';
530 for (split /^/m, $list) {
531 my ($start, $end, $value) = / ^ (.+?) \t (.*?) \t (.+?)
532 \s* ( \# .* )? # Optional comment
534 my $decimal_start = hex $start;
535 my $decimal_end = ($end eq "") ? $decimal_start : hex $end;
537 foreach my $i ($decimal_start .. $decimal_end) {
538 $return{$i} = ($to_adjust)
539 ? $value + $i - $decimal_start
545 && $return[-1][1] == $decimal_start - 1
546 && $return[-1][2] eq $value)
548 # If this is merely extending the previous range, do just that.
549 $return[-1]->[1] = $decimal_end;
552 push @return, [ $decimal_start, $decimal_end, $value ];
555 return ($return_hash) ? %return : @return;
559 my ($range, $arg) = @_;
560 my $code = _getcode($arg);
561 croak __PACKAGE__, "::charinrange: unknown code '$arg'"
562 unless defined $code;
563 _search($range, 0, $#$range, $code);
566 =head2 B<charblock()>
568 use Unicode::UCD 'charblock';
570 my $charblock = charblock(0x41);
571 my $charblock = charblock(1234);
572 my $charblock = charblock(0x263a);
573 my $charblock = charblock("U+263a");
575 my $range = charblock('Armenian');
577 With a L</code point argument> charblock() returns the I<block> the code point
578 belongs to, e.g. C<Basic Latin>. The old-style block name is returned (see
579 L</Old-style versus new-style block names>).
580 If the code point is unassigned, this returns the block it would belong to if
581 it were assigned. (If the Unicode version being used is so early as to not
582 have blocks, all code points are considered to be in C<No_Block>.)
584 See also L</Blocks versus Scripts>.
586 If supplied with an argument that can't be a code point, charblock() tries to
587 do the opposite and interpret the argument as an old-style block name. The
589 is a I<range set> with one range: an anonymous list with a single element that
590 consists of another anonymous list whose first element is the first code point
591 in the block, and whose second (and final) element is the final code point in
592 the block. (The extra list consisting of just one element is so that the same
593 program logic can be used to handle both this return, and the return from
594 L</charscript()> which can have multiple ranges.) You can test whether a code
595 point is in a range using the L</charinrange()> function. If the argument is
596 not a known block, C<undef> is returned.
605 # Can't read from the mktables table because it loses the hyphens in the
608 UnicodeVersion() unless defined $v_unicode_version;
609 if ($v_unicode_version lt v2.0.0) {
610 my $subrange = [ 0, 0x10FFFF, 'No_Block' ];
611 push @BLOCKS, $subrange;
612 push @{$BLOCKS{$3}}, $subrange;
614 elsif (openunicode(\$BLOCKSFH, "Blocks.txt")) {
617 while (<$BLOCKSFH>) {
618 if (/^([0-9A-F]+)\.\.([0-9A-F]+);\s+(.+)/) {
619 my ($lo, $hi) = (hex($1), hex($2));
620 my $subrange = [ $lo, $hi, $3 ];
621 push @BLOCKS, $subrange;
622 push @{$BLOCKS{$3}}, $subrange;
633 _charblocks() unless @BLOCKS;
635 my $code = _getcode($arg);
638 my $result = _search(\@BLOCKS, 0, $#BLOCKS, $code);
639 return $result if defined $result;
642 elsif (exists $BLOCKS{$arg}) {
643 return _dclone $BLOCKS{$arg};
647 =head2 B<charscript()>
649 use Unicode::UCD 'charscript';
651 my $charscript = charscript(0x41);
652 my $charscript = charscript(1234);
653 my $charscript = charscript("U+263a");
655 my $range = charscript('Thai');
657 With a L</code point argument> charscript() returns the I<script> the
658 code point belongs to, e.g. C<Latin>, C<Greek>, C<Han>.
659 If the code point is unassigned or the Unicode version being used is so early
660 that it doesn't have scripts, this function returns C<"Unknown">.
662 If supplied with an argument that can't be a code point, charscript() tries
663 to do the opposite and interpret the argument as a script name. The
664 return value is a I<range set>: an anonymous list of lists that contain
665 I<start-of-range>, I<end-of-range> code point pairs. You can test whether a
666 code point is in a range set using the L</charinrange()> function. If the
667 argument is not a known script, C<undef> is returned.
669 See also L</Blocks versus Scripts>.
678 UnicodeVersion() unless defined $v_unicode_version;
679 if ($v_unicode_version lt v3.1.0) {
680 push @SCRIPTS, [ 0, 0x10FFFF, 'Unknown' ];
683 @SCRIPTS =_read_table("To/Sc.pl");
686 foreach my $entry (@SCRIPTS) {
687 $entry->[2] =~ s/(_\w)/\L$1/g; # Preserve old-style casing
688 push @{$SCRIPTS{$entry->[2]}}, $entry;
695 _charscripts() unless @SCRIPTS;
697 my $code = _getcode($arg);
700 my $result = _search(\@SCRIPTS, 0, $#SCRIPTS, $code);
701 return $result if defined $result;
702 return $utf8::SwashInfo{'ToSc'}{'missing'};
703 } elsif (exists $SCRIPTS{$arg}) {
704 return _dclone $SCRIPTS{$arg};
710 =head2 B<charblocks()>
712 use Unicode::UCD 'charblocks';
714 my $charblocks = charblocks();
716 charblocks() returns a reference to a hash with the known block names
717 as the keys, and the code point ranges (see L</charblock()>) as the values.
719 The names are in the old-style (see L</Old-style versus new-style block
722 L<prop_invmap("block")|/prop_invmap()> can be used to get this same data in a
723 different type of data structure.
725 See also L</Blocks versus Scripts>.
730 _charblocks() unless %BLOCKS;
731 return _dclone \%BLOCKS;
734 =head2 B<charscripts()>
736 use Unicode::UCD 'charscripts';
738 my $charscripts = charscripts();
740 charscripts() returns a reference to a hash with the known script
741 names as the keys, and the code point ranges (see L</charscript()>) as
744 L<prop_invmap("script")|/prop_invmap()> can be used to get this same data in a
745 different type of data structure.
747 See also L</Blocks versus Scripts>.
752 _charscripts() unless %SCRIPTS;
753 return _dclone \%SCRIPTS;
756 =head2 B<charinrange()>
758 In addition to using the C<\p{Blk=...}> and C<\P{Blk=...}> constructs, you
759 can also test whether a code point is in the I<range> as returned by
760 L</charblock()> and L</charscript()> or as the values of the hash returned
761 by L</charblocks()> and L</charscripts()> by using charinrange():
763 use Unicode::UCD qw(charscript charinrange);
765 $range = charscript('Hiragana');
766 print "looks like hiragana\n" if charinrange($range, $codepoint);
770 my %GENERAL_CATEGORIES =
773 'LC' => 'CasedLetter',
774 'Lu' => 'UppercaseLetter',
775 'Ll' => 'LowercaseLetter',
776 'Lt' => 'TitlecaseLetter',
777 'Lm' => 'ModifierLetter',
778 'Lo' => 'OtherLetter',
780 'Mn' => 'NonspacingMark',
781 'Mc' => 'SpacingMark',
782 'Me' => 'EnclosingMark',
784 'Nd' => 'DecimalNumber',
785 'Nl' => 'LetterNumber',
786 'No' => 'OtherNumber',
787 'P' => 'Punctuation',
788 'Pc' => 'ConnectorPunctuation',
789 'Pd' => 'DashPunctuation',
790 'Ps' => 'OpenPunctuation',
791 'Pe' => 'ClosePunctuation',
792 'Pi' => 'InitialPunctuation',
793 'Pf' => 'FinalPunctuation',
794 'Po' => 'OtherPunctuation',
796 'Sm' => 'MathSymbol',
797 'Sc' => 'CurrencySymbol',
798 'Sk' => 'ModifierSymbol',
799 'So' => 'OtherSymbol',
801 'Zs' => 'SpaceSeparator',
802 'Zl' => 'LineSeparator',
803 'Zp' => 'ParagraphSeparator',
808 'Co' => 'PrivateUse',
809 'Cn' => 'Unassigned',
812 sub general_categories {
813 return _dclone \%GENERAL_CATEGORIES;
816 =head2 B<general_categories()>
818 use Unicode::UCD 'general_categories';
820 my $categories = general_categories();
822 This returns a reference to a hash which has short
823 general category names (such as C<Lu>, C<Nd>, C<Zs>, C<S>) as keys and long
824 names (such as C<UppercaseLetter>, C<DecimalNumber>, C<SpaceSeparator>,
825 C<Symbol>) as values. The hash is reversible in case you need to go
826 from the long names to the short names. The general category is the
828 L</charinfo()> under the C<category> key.
830 The L</prop_value_aliases()> function can be used to get all the synonyms of
837 'L' => 'Left-to-Right',
838 'LRE' => 'Left-to-Right Embedding',
839 'LRO' => 'Left-to-Right Override',
840 'R' => 'Right-to-Left',
841 'AL' => 'Right-to-Left Arabic',
842 'RLE' => 'Right-to-Left Embedding',
843 'RLO' => 'Right-to-Left Override',
844 'PDF' => 'Pop Directional Format',
845 'EN' => 'European Number',
846 'ES' => 'European Number Separator',
847 'ET' => 'European Number Terminator',
848 'AN' => 'Arabic Number',
849 'CS' => 'Common Number Separator',
850 'NSM' => 'Non-Spacing Mark',
851 'BN' => 'Boundary Neutral',
852 'B' => 'Paragraph Separator',
853 'S' => 'Segment Separator',
854 'WS' => 'Whitespace',
855 'ON' => 'Other Neutrals',
858 =head2 B<bidi_types()>
860 use Unicode::UCD 'bidi_types';
862 my $categories = bidi_types();
864 This returns a reference to a hash which has the short
865 bidi (bidirectional) type names (such as C<L>, C<R>) as keys and long
866 names (such as C<Left-to-Right>, C<Right-to-Left>) as values. The
867 hash is reversible in case you need to go from the long names to the
868 short names. The bidi type is the one returned from
870 under the C<bidi> key. For the exact meaning of the various bidi classes
871 the Unicode TR9 is recommended reading:
872 L<http://www.unicode.org/reports/tr9/>
873 (as of Unicode 5.0.0)
875 The L</prop_value_aliases()> function can be used to get all the synonyms of
881 return _dclone \%BIDI_TYPES;
886 use Unicode::UCD 'compexcl';
888 my $compexcl = compexcl(0x09dc);
890 This routine returns C<undef> if the Unicode version being used is so early
891 that it doesn't have this property. It is included for backwards
892 compatibility, but as of Perl 5.12 and more modern Unicode versions, for
893 most purposes it is probably more convenient to use one of the following
896 my $compexcl = chr(0x09dc) =~ /\p{Comp_Ex};
897 my $compexcl = chr(0x09dc) =~ /\p{Full_Composition_Exclusion};
901 my $compexcl = chr(0x09dc) =~ /\p{CE};
902 my $compexcl = chr(0x09dc) =~ /\p{Composition_Exclusion};
904 The first two forms return B<true> if the L</code point argument> should not
905 be produced by composition normalization. For the final two forms to return
906 B<true>, it is additionally required that this fact not otherwise be
907 determinable from the Unicode data base.
909 This routine behaves identically to the final two forms. That is,
910 it does not return B<true> if the code point has a decomposition
911 consisting of another single code point, nor if its decomposition starts
912 with a code point whose combining class is non-zero. Code points that meet
913 either of these conditions should also not be produced by composition
914 normalization, which is probably why you should use the
915 C<Full_Composition_Exclusion> property instead, as shown above.
917 The routine returns B<false> otherwise.
923 my $code = _getcode($arg);
924 croak __PACKAGE__, "::compexcl: unknown code '$arg'"
925 unless defined $code;
927 UnicodeVersion() unless defined $v_unicode_version;
928 return if $v_unicode_version lt v3.0.0;
930 no warnings "non_unicode"; # So works on non-Unicode code points
931 return chr($code) =~ /\p{Composition_Exclusion}/;
936 use Unicode::UCD 'casefold';
938 my $casefold = casefold(0xDF);
939 if (defined $casefold) {
940 my @full_fold_hex = split / /, $casefold->{'full'};
941 my $full_fold_string =
942 join "", map {chr(hex($_))} @full_fold_hex;
943 my @turkic_fold_hex =
944 split / /, ($casefold->{'turkic'} ne "")
945 ? $casefold->{'turkic'}
946 : $casefold->{'full'};
947 my $turkic_fold_string =
948 join "", map {chr(hex($_))} @turkic_fold_hex;
950 if (defined $casefold && $casefold->{'simple'} ne "") {
951 my $simple_fold_hex = $casefold->{'simple'};
952 my $simple_fold_string = chr(hex($simple_fold_hex));
955 This returns the (almost) locale-independent case folding of the
956 character specified by the L</code point argument>. (Starting in Perl v5.16,
957 the core function C<fc()> returns the C<full> mapping (described below)
958 faster than this does, and for entire strings.)
960 If there is no case folding for the input code point, C<undef> is returned.
962 If there is a case folding for that code point, a reference to a hash
963 with the following fields is returned:
969 the input L</code point argument> expressed in hexadecimal, with leading zeros
970 added if necessary to make it contain at least four hexdigits
974 one or more codes (separated by spaces) that, taken in order, give the
975 code points for the case folding for I<code>.
976 Each has at least four hexdigits.
980 is empty, or is exactly one code with at least four hexdigits which can be used
981 as an alternative case folding when the calling program cannot cope with the
982 fold being a sequence of multiple code points. If I<full> is just one code
983 point, then I<simple> equals I<full>. If there is no single code point folding
984 defined for I<code>, then I<simple> is the empty string. Otherwise, it is an
985 inferior, but still better-than-nothing alternative folding to I<full>.
989 is the same as I<simple> if I<simple> is not empty, and it is the same as I<full>
990 otherwise. It can be considered to be the simplest possible folding for
991 I<code>. It is defined primarily for backwards compatibility.
995 is C<C> (for C<common>) if the best possible fold is a single code point
996 (I<simple> equals I<full> equals I<mapping>). It is C<S> if there are distinct
997 folds, I<simple> and I<full> (I<mapping> equals I<simple>). And it is C<F> if
998 there is only a I<full> fold (I<mapping> equals I<full>; I<simple> is empty).
1000 describes the contents of I<mapping>. It is defined primarily for backwards
1003 For Unicode versions between 3.1 and 3.1.1 inclusive, I<status> can also be
1004 C<I> which is the same as C<C> but is a special case for dotted uppercase I and
1005 dotless lowercase i:
1009 =item B<*> If you use this C<I> mapping
1011 the result is case-insensitive,
1012 but dotless and dotted I's are not distinguished
1014 =item B<*> If you exclude this C<I> mapping
1016 the result is not fully case-insensitive, but
1017 dotless and dotted I's are distinguished
1023 contains any special folding for Turkic languages. For versions of Unicode
1024 starting with 3.2, this field is empty unless I<code> has a different folding
1025 in Turkic languages, in which case it is one or more codes (separated by
1026 spaces) that, taken in order, give the code points for the case folding for
1027 I<code> in those languages.
1028 Each code has at least four hexdigits.
1029 Note that this folding does not maintain canonical equivalence without
1030 additional processing.
1032 For Unicode versions between 3.1 and 3.1.1 inclusive, this field is empty unless
1034 special folding for Turkic languages, in which case I<status> is C<I>, and
1035 I<mapping>, I<full>, I<simple>, and I<turkic> are all equal.
1039 Programs that want complete generality and the best folding results should use
1040 the folding contained in the I<full> field. But note that the fold for some
1041 code points will be a sequence of multiple code points.
1043 Programs that can't cope with the fold mapping being multiple code points can
1044 use the folding contained in the I<simple> field, with the loss of some
1045 generality. In Unicode 5.1, about 7% of the defined foldings have no single
1048 The I<mapping> and I<status> fields are provided for backwards compatibility for
1049 existing programs. They contain the same values as in previous versions of
1052 Locale is not completely independent. The I<turkic> field contains results to
1053 use when the locale is a Turkic language.
1055 For more information about case mappings see
1056 L<http://www.unicode.org/unicode/reports/tr21>
1063 unless (%CASEFOLD) { # Populate the hash
1064 my ($full_invlist_ref, $full_invmap_ref, undef, $default)
1065 = prop_invmap('Case_Folding');
1067 # Use the recipe given in the prop_invmap() pod to convert the
1068 # inversion map into the hash.
1069 for my $i (0 .. @$full_invlist_ref - 1 - 1) {
1070 next if $full_invmap_ref->[$i] == $default;
1072 for my $j ($full_invlist_ref->[$i] .. $full_invlist_ref->[$i+1] -1) {
1074 if (! ref $full_invmap_ref->[$i]) {
1076 # This is a single character mapping
1077 $CASEFOLD{$j}{'status'} = 'C';
1078 $CASEFOLD{$j}{'simple'}
1079 = $CASEFOLD{$j}{'full'}
1080 = $CASEFOLD{$j}{'mapping'}
1081 = sprintf("%04X", $full_invmap_ref->[$i] + $adjust);
1082 $CASEFOLD{$j}{'code'} = sprintf("%04X", $j);
1083 $CASEFOLD{$j}{'turkic'} = "";
1085 else { # prop_invmap ensures that $adjust is 0 for a ref
1086 $CASEFOLD{$j}{'status'} = 'F';
1087 $CASEFOLD{$j}{'full'}
1088 = $CASEFOLD{$j}{'mapping'}
1089 = join " ", map { sprintf "%04X", $_ }
1090 @{$full_invmap_ref->[$i]};
1091 $CASEFOLD{$j}{'simple'} = "";
1092 $CASEFOLD{$j}{'code'} = sprintf("%04X", $j);
1093 $CASEFOLD{$j}{'turkic'} = "";
1098 # We have filled in the full mappings above, assuming there were no
1099 # simple ones for the ones with multi-character maps. Now, we find
1100 # and fix the cases where that assumption was false.
1101 (my ($simple_invlist_ref, $simple_invmap_ref, undef), $default)
1102 = prop_invmap('Simple_Case_Folding');
1103 for my $i (0 .. @$simple_invlist_ref - 1 - 1) {
1104 next if $simple_invmap_ref->[$i] == $default;
1106 for my $j ($simple_invlist_ref->[$i]
1107 .. $simple_invlist_ref->[$i+1] -1)
1110 next if $CASEFOLD{$j}{'status'} eq 'C';
1111 $CASEFOLD{$j}{'status'} = 'S';
1112 $CASEFOLD{$j}{'simple'}
1113 = $CASEFOLD{$j}{'mapping'}
1114 = sprintf("%04X", $simple_invmap_ref->[$i] + $adjust);
1115 $CASEFOLD{$j}{'code'} = sprintf("%04X", $j);
1116 $CASEFOLD{$j}{'turkic'} = "";
1120 # We hard-code in the turkish rules
1121 UnicodeVersion() unless defined $v_unicode_version;
1122 if ($v_unicode_version ge v3.2.0) {
1124 # These two code points should already have regular entries, so
1125 # just fill in the turkish fields
1126 $CASEFOLD{ord('I')}{'turkic'} = '0131';
1127 $CASEFOLD{0x130}{'turkic'} = sprintf "%04X", ord('i');
1129 elsif ($v_unicode_version ge v3.1.0) {
1131 # These two code points don't have entries otherwise.
1132 $CASEFOLD{0x130}{'code'} = '0130';
1133 $CASEFOLD{0x131}{'code'} = '0131';
1134 $CASEFOLD{0x130}{'status'} = $CASEFOLD{0x131}{'status'} = 'I';
1135 $CASEFOLD{0x130}{'turkic'}
1136 = $CASEFOLD{0x130}{'mapping'}
1137 = $CASEFOLD{0x130}{'full'}
1138 = $CASEFOLD{0x130}{'simple'}
1139 = $CASEFOLD{0x131}{'turkic'}
1140 = $CASEFOLD{0x131}{'mapping'}
1141 = $CASEFOLD{0x131}{'full'}
1142 = $CASEFOLD{0x131}{'simple'}
1143 = sprintf "%04X", ord('i');
1150 my $code = _getcode($arg);
1151 croak __PACKAGE__, "::casefold: unknown code '$arg'"
1152 unless defined $code;
1154 _casefold() unless %CASEFOLD;
1156 return $CASEFOLD{$code};
1159 =head2 B<all_casefolds()>
1162 use Unicode::UCD 'all_casefolds';
1164 my $all_folds_ref = all_casefolds();
1165 foreach my $char_with_casefold (sort { $a <=> $b }
1166 keys %$all_folds_ref)
1168 printf "%04X:", $char_with_casefold;
1169 my $casefold = $all_folds_ref->{$char_with_casefold};
1171 # Get folds for $char_with_casefold
1173 my @full_fold_hex = split / /, $casefold->{'full'};
1174 my $full_fold_string =
1175 join "", map {chr(hex($_))} @full_fold_hex;
1176 print " full=", join " ", @full_fold_hex;
1177 my @turkic_fold_hex =
1178 split / /, ($casefold->{'turkic'} ne "")
1179 ? $casefold->{'turkic'}
1180 : $casefold->{'full'};
1181 my $turkic_fold_string =
1182 join "", map {chr(hex($_))} @turkic_fold_hex;
1183 print "; turkic=", join " ", @turkic_fold_hex;
1184 if (defined $casefold && $casefold->{'simple'} ne "") {
1185 my $simple_fold_hex = $casefold->{'simple'};
1186 my $simple_fold_string = chr(hex($simple_fold_hex));
1187 print "; simple=$simple_fold_hex";
1192 This returns all the case foldings in the current version of Unicode in the
1193 form of a reference to a hash. Each key to the hash is the decimal
1194 representation of a Unicode character that has a casefold to other than
1195 itself. The casefold of a semi-colon is itself, so it isn't in the hash;
1196 likewise for a lowercase "a", but there is an entry for a capital "A". The
1197 hash value for each key is another hash, identical to what is returned by
1198 L</casefold()> if called with that code point as its argument. So the value
1199 C<< all_casefolds()->{ord("A")}' >> is equivalent to C<casefold(ord("A"))>;
1203 sub all_casefolds () {
1204 _casefold() unless %CASEFOLD;
1205 return _dclone \%CASEFOLD;
1208 =head2 B<casespec()>
1210 use Unicode::UCD 'casespec';
1212 my $casespec = casespec(0xFB00);
1214 This returns the potentially locale-dependent case mappings of the L</code point
1215 argument>. The mappings may be longer than a single code point (which the basic
1216 Unicode case mappings as returned by L</charinfo()> never are).
1218 If there are no case mappings for the L</code point argument>, or if all three
1219 possible mappings (I<lower>, I<title> and I<upper>) result in single code
1220 points and are locale independent and unconditional, C<undef> is returned
1221 (which means that the case mappings, if any, for the code point are those
1222 returned by L</charinfo()>).
1224 Otherwise, a reference to a hash giving the mappings (or a reference to a hash
1225 of such hashes, explained below) is returned with the following keys and their
1228 The keys in the bottom layer hash with the meanings of their values are:
1234 the input L</code point argument> expressed in hexadecimal, with leading zeros
1235 added if necessary to make it contain at least four hexdigits
1239 one or more codes (separated by spaces) that, taken in order, give the
1240 code points for the lower case of I<code>.
1241 Each has at least four hexdigits.
1245 one or more codes (separated by spaces) that, taken in order, give the
1246 code points for the title case of I<code>.
1247 Each has at least four hexdigits.
1251 one or more codes (separated by spaces) that, taken in order, give the
1252 code points for the upper case of I<code>.
1253 Each has at least four hexdigits.
1257 the conditions for the mappings to be valid.
1258 If C<undef>, the mappings are always valid.
1259 When defined, this field is a list of conditions,
1260 all of which must be true for the mappings to be valid.
1261 The list consists of one or more
1262 I<locales> (see below)
1263 and/or I<contexts> (explained in the next paragraph),
1264 separated by spaces.
1265 (Other than as used to separate elements, spaces are to be ignored.)
1266 Case distinctions in the condition list are not significant.
1267 Conditions preceded by "NON_" represent the negation of the condition.
1269 A I<context> is one of those defined in the Unicode standard.
1270 For Unicode 5.1, they are defined in Section 3.13 C<Default Case Operations>
1272 L<http://www.unicode.org/versions/Unicode5.1.0/>.
1273 These are for context-sensitive casing.
1277 The hash described above is returned for locale-independent casing, where
1278 at least one of the mappings has length longer than one. If C<undef> is
1279 returned, the code point may have mappings, but if so, all are length one,
1280 and are returned by L</charinfo()>.
1281 Note that when this function does return a value, it will be for the complete
1282 set of mappings for a code point, even those whose length is one.
1284 If there are additional casing rules that apply only in certain locales,
1285 an additional key for each will be defined in the returned hash. Each such key
1286 will be its locale name, defined as a 2-letter ISO 3166 country code, possibly
1287 followed by a "_" and a 2-letter ISO language code (possibly followed by a "_"
1288 and a variant code). You can find the lists of all possible locales, see
1289 L<Locale::Country> and L<Locale::Language>.
1290 (In Unicode 6.0, the only locales returned by this function
1291 are C<lt>, C<tr>, and C<az>.)
1293 Each locale key is a reference to a hash that has the form above, and gives
1294 the casing rules for that particular locale, which take precedence over the
1295 locale-independent ones when in that locale.
1297 If the only casing for a code point is locale-dependent, then the returned
1298 hash will not have any of the base keys, like C<code>, C<upper>, etc., but
1299 will contain only locale keys.
1301 For more information about case mappings see
1302 L<http://www.unicode.org/unicode/reports/tr21/>
1309 unless (%CASESPEC) {
1310 UnicodeVersion() unless defined $v_unicode_version;
1311 if ($v_unicode_version lt v2.1.8) {
1314 elsif (openunicode(\$CASESPECFH, "SpecialCasing.txt")) {
1317 while (<$CASESPECFH>) {
1318 if (/^([0-9A-F]+); ([0-9A-F]+(?: [0-9A-F]+)*)?; ([0-9A-F]+(?: [0-9A-F]+)*)?; ([0-9A-F]+(?: [0-9A-F]+)*)?; (\w+(?: \w+)*)?/) {
1320 my ($hexcode, $lower, $title, $upper, $condition) =
1321 ($1, $2, $3, $4, $5);
1322 my $code = hex($hexcode);
1324 # In 2.1.8, there were duplicate entries; ignore all but
1325 # the first one -- there were no conditions in the file
1327 if (exists $CASESPEC{$code} && $v_unicode_version ne v2.1.8)
1329 if (exists $CASESPEC{$code}->{code}) {
1334 @{$CASESPEC{$code}}{qw(lower
1338 if (defined $oldcondition) {
1340 ($oldcondition =~ /^([a-z][a-z](?:_\S+)?)/);
1341 delete $CASESPEC{$code};
1342 $CASESPEC{$code}->{$oldlocale} =
1347 condition => $oldcondition };
1351 ($condition =~ /^([a-z][a-z](?:_\S+)?)/);
1352 $CASESPEC{$code}->{$locale} =
1357 condition => $condition };
1364 condition => $condition };
1375 my $code = _getcode($arg);
1376 croak __PACKAGE__, "::casespec: unknown code '$arg'"
1377 unless defined $code;
1379 _casespec() unless %CASESPEC;
1381 return ref $CASESPEC{$code} ? _dclone $CASESPEC{$code} : $CASESPEC{$code};
1384 =head2 B<namedseq()>
1386 use Unicode::UCD 'namedseq';
1388 my $namedseq = namedseq("KATAKANA LETTER AINU P");
1389 my @namedseq = namedseq("KATAKANA LETTER AINU P");
1390 my %namedseq = namedseq();
1392 If used with a single argument in a scalar context, returns the string
1393 consisting of the code points of the named sequence, or C<undef> if no
1394 named sequence by that name exists. If used with a single argument in
1395 a list context, it returns the list of the ordinals of the code points. If used
1397 arguments in a list context, returns a hash with the names of the
1398 named sequences as the keys and the named sequences as strings as
1399 the values. Otherwise, it returns C<undef> or an empty list depending
1402 This function only operates on officially approved (not provisional) named
1405 Note that as of Perl 5.14, C<\N{KATAKANA LETTER AINU P}> will insert the named
1406 sequence into double-quoted strings, and C<charnames::string_vianame("KATAKANA
1407 LETTER AINU P")> will return the same string this function does, but will also
1408 operate on character names that aren't named sequences, without you having to
1409 know which are which. See L<charnames>.
1416 unless (%NAMEDSEQ) {
1417 if (openunicode(\$NAMEDSEQFH, "Name.pl")) {
1420 while (<$NAMEDSEQFH>) {
1421 if (/^ [0-9A-F]+ \ /x) {
1423 my ($sequence, $name) = split /\t/;
1424 my @s = map { chr(hex($_)) } split(' ', $sequence);
1425 $NAMEDSEQ{$name} = join("", @s);
1435 # Use charnames::string_vianame() which now returns this information,
1436 # unless the caller wants the hash returned, in which case we read it in,
1437 # and thereafter use it instead of calling charnames, as it is faster.
1439 my $wantarray = wantarray();
1440 if (defined $wantarray) {
1443 _namedseq() unless %NAMEDSEQ;
1448 $s = $NAMEDSEQ{ $_[0] };
1451 $s = charnames::string_vianame($_[0]);
1453 return defined $s ? map { ord($_) } split('', $s) : ();
1456 return $NAMEDSEQ{ $_[0] } if %NAMEDSEQ;
1457 return charnames::string_vianame($_[0]);
1466 my @numbers = _read_table("To/Nv.pl");
1467 foreach my $entry (@numbers) {
1468 my ($start, $end, $value) = @$entry;
1470 # If value contains a slash, convert to decimal, add a reverse hash
1472 if ((my @rational = split /\//, $value) == 2) {
1473 my $real = $rational[0] / $rational[1];
1474 $real_to_rational{$real} = $value;
1477 # Should only be single element, but just in case...
1478 for my $i ($start .. $end) {
1479 $NUMERIC{$i} = $value;
1483 # The values require adjusting, as is in 'a' format
1484 for my $i ($start .. $end) {
1485 $NUMERIC{$i} = $value + $i - $start;
1490 # Decided unsafe to use these that aren't officially part of the Unicode
1493 #my $pi = acos(-1.0);
1494 #$NUMERIC{0x03C0} = $pi;
1496 # Euler's constant, not to be confused with Euler's number
1497 #$NUMERIC{0x2107} = 0.57721566490153286060651209008240243104215933593992;
1500 #$NUMERIC{0x212F} = 2.7182818284590452353602874713526624977572;
1509 use Unicode::UCD 'num';
1511 my $val = num("123");
1512 my $one_quarter = num("\N{VULGAR FRACTION 1/4}");
1514 C<num> returns the numeric value of the input Unicode string; or C<undef> if it
1515 doesn't think the entire string has a completely valid, safe numeric value.
1517 If the string is just one character in length, the Unicode numeric value
1518 is returned if it has one, or C<undef> otherwise. Note that this need
1519 not be a whole number. C<num("\N{TIBETAN DIGIT HALF ZERO}")>, for
1520 example returns -0.5.
1524 #A few characters to which Unicode doesn't officially
1525 #assign a numeric value are considered numeric by C<num>.
1528 # EULER CONSTANT 0.5772... (this is NOT Euler's number)
1529 # SCRIPT SMALL E 2.71828... (this IS Euler's number)
1530 # GREEK SMALL LETTER PI 3.14159...
1534 If the string is more than one character, C<undef> is returned unless
1535 all its characters are decimal digits (that is, they would match C<\d+>),
1536 from the same script. For example if you have an ASCII '0' and a Bengali
1537 '3', mixed together, they aren't considered a valid number, and C<undef>
1538 is returned. A further restriction is that the digits all have to be of
1539 the same form. A half-width digit mixed with a full-width one will
1540 return C<undef>. The Arabic script has two sets of digits; C<num> will
1541 return C<undef> unless all the digits in the string come from the same
1544 C<num> errs on the side of safety, and there may be valid strings of
1545 decimal digits that it doesn't recognize. Note that Unicode defines
1546 a number of "digit" characters that aren't "decimal digit" characters.
1547 "Decimal digits" have the property that they have a positional value, i.e.,
1548 there is a units position, a 10's position, a 100's, etc, AND they are
1549 arranged in Unicode in blocks of 10 contiguous code points. The Chinese
1550 digits, for example, are not in such a contiguous block, and so Unicode
1551 doesn't view them as decimal digits, but merely digits, and so C<\d> will not
1552 match them. A single-character string containing one of these digits will
1553 have its decimal value returned by C<num>, but any longer string containing
1554 only these digits will return C<undef>.
1556 Strings of multiple sub- and superscripts are not recognized as numbers. You
1557 can use either of the compatibility decompositions in Unicode::Normalize to
1558 change these into digits, and then call C<num> on the result.
1562 # To handle sub, superscripts, this could if called in list context,
1563 # consider those, and return the <decomposition> type in the second
1569 _numeric unless %NUMERIC;
1571 my $length = length($string);
1572 return $NUMERIC{ord($string)} if $length == 1;
1573 return if $string =~ /\D/;
1574 my $first_ord = ord(substr($string, 0, 1));
1575 my $value = $NUMERIC{$first_ord};
1577 # To be a valid decimal number, it should be in a block of 10 consecutive
1578 # characters, whose values are 0, 1, 2, ... 9. Therefore this digit's
1579 # value is its offset in that block from the character that means zero.
1580 my $zero_ord = $first_ord - $value;
1582 # Unicode 6.0 instituted the rule that only digits in a consecutive
1583 # block of 10 would be considered decimal digits. If this is an earlier
1584 # release, we verify that this first character is a member of such a
1585 # block. That is, that the block of characters surrounding this one
1586 # consists of all \d characters whose numeric values are the expected
1588 UnicodeVersion() unless defined $v_unicode_version;
1589 if ($v_unicode_version lt v6.0.0) {
1590 for my $i (0 .. 9) {
1591 my $ord = $zero_ord + $i;
1592 return unless chr($ord) =~ /\d/;
1593 my $numeric = $NUMERIC{$ord};
1594 return unless defined $numeric;
1595 return unless $numeric == $i;
1599 for my $i (1 .. $length -1) {
1601 # Here we know either by verifying, or by fact of the first character
1602 # being a \d in Unicode 6.0 or later, that any character between the
1603 # character that means 0, and 9 positions above it must be \d, and
1604 # must have its value correspond to its offset from the zero. Any
1605 # characters outside these 10 do not form a legal number for this
1607 my $ord = ord(substr($string, $i, 1));
1608 my $digit = $ord - $zero_ord;
1609 return unless $digit >= 0 && $digit <= 9;
1610 $value = $value * 10 + $digit;
1618 =head2 B<prop_aliases()>
1620 use Unicode::UCD 'prop_aliases';
1622 my ($short_name, $full_name, @other_names) = prop_aliases("space");
1623 my $same_full_name = prop_aliases("Space"); # Scalar context
1624 my ($same_short_name) = prop_aliases("Space"); # gets 0th element
1625 print "The full name is $full_name\n";
1626 print "The short name is $short_name\n";
1627 print "The other aliases are: ", join(", ", @other_names), "\n";
1630 The full name is White_Space
1631 The short name is WSpace
1632 The other aliases are: Space
1634 Most Unicode properties have several synonymous names. Typically, there is at
1635 least a short name, convenient to type, and a long name that more fully
1636 describes the property, and hence is more easily understood.
1638 If you know one name for a Unicode property, you can use C<prop_aliases> to find
1639 either the long name (when called in scalar context), or a list of all of the
1640 names, somewhat ordered so that the short name is in the 0th element, the long
1641 name in the next element, and any other synonyms are in the remaining
1642 elements, in no particular order.
1644 The long name is returned in a form nicely capitalized, suitable for printing.
1646 The input parameter name is loosely matched, which means that white space,
1647 hyphens, and underscores are ignored (except for the trailing underscore in
1648 the old_form grandfathered-in C<"L_">, which is better written as C<"LC">, and
1649 both of which mean C<General_Category=Cased Letter>).
1651 If the name is unknown, C<undef> is returned (or an empty list in list
1652 context). Note that Perl typically recognizes property names in regular
1653 expressions with an optional C<"Is_>" (with or without the underscore)
1654 prefixed to them, such as C<\p{isgc=punct}>. This function does not recognize
1655 those in the input, returning C<undef>. Nor are they included in the output
1656 as possible synonyms.
1658 C<prop_aliases> does know about the Perl extensions to Unicode properties,
1659 such as C<Any> and C<XPosixAlpha>, and the single form equivalents to Unicode
1660 properties such as C<XDigit>, C<Greek>, C<In_Greek>, and C<Is_Greek>. The
1661 final example demonstrates that the C<"Is_"> prefix is recognized for these
1662 extensions; it is needed to resolve ambiguities. For example,
1663 C<prop_aliases('lc')> returns the list C<(lc, Lowercase_Mapping)>, but
1664 C<prop_aliases('islc')> returns C<(Is_LC, Cased_Letter)>. This is
1665 because C<islc> is a Perl extension which is short for
1666 C<General_Category=Cased Letter>. The lists returned for the Perl extensions
1667 will not include the C<"Is_"> prefix (whether or not the input had it) unless
1668 needed to resolve ambiguities, as shown in the C<"islc"> example, where the
1669 returned list had one element containing C<"Is_">, and the other without.
1671 It is also possible for the reverse to happen: C<prop_aliases('isc')> returns
1672 the list C<(isc, ISO_Comment)>; whereas C<prop_aliases('c')> returns
1673 C<(C, Other)> (the latter being a Perl extension meaning
1674 C<General_Category=Other>.
1675 L<perluniprops/Properties accessible through Unicode::UCD> lists the available
1676 forms, including which ones are discouraged from use.
1678 Those discouraged forms are accepted as input to C<prop_aliases>, but are not
1679 returned in the lists. C<prop_aliases('isL&')> and C<prop_aliases('isL_')>,
1680 which are old synonyms for C<"Is_LC"> and should not be used in new code, are
1681 examples of this. These both return C<(Is_LC, Cased_Letter)>. Thus this
1682 function allows you to take a discourarged form, and find its acceptable
1683 alternatives. The same goes with single-form Block property equivalences.
1684 Only the forms that begin with C<"In_"> are not discouraged; if you pass
1685 C<prop_aliases> a discouraged form, you will get back the equivalent ones that
1686 begin with C<"In_">. It will otherwise look like a new-style block name (see.
1687 L</Old-style versus new-style block names>).
1689 C<prop_aliases> does not know about any user-defined properties, and will
1690 return C<undef> if called with one of those. Likewise for Perl internal
1691 properties, with the exception of "Perl_Decimal_Digit" which it does know
1692 about (and which is documented below in L</prop_invmap()>).
1696 # It may be that there are use cases where the discouraged forms should be
1697 # returned. If that comes up, an optional boolean second parameter to the
1698 # function could be created, for example.
1700 # These are created by mktables for this routine and stored in unicore/UCD.pl
1701 # where their structures are described.
1702 our %string_property_loose_to_name;
1703 our %ambiguous_names;
1704 our %loose_perlprop_to_name;
1707 sub prop_aliases ($) {
1709 return unless defined $prop;
1711 require "unicore/UCD.pl";
1712 require "unicore/Heavy.pl";
1713 require "utf8_heavy.pl";
1715 # The property name may be loosely or strictly matched; we don't know yet.
1716 # But both types use lower-case.
1719 # It is loosely matched if its lower case isn't known to be strict.
1721 if (! exists $utf8::stricter_to_file_of{$prop}) {
1722 my $loose = utf8::_loose_name($prop);
1724 # There is a hash that converts from any loose name to its standard
1725 # form, mapping all synonyms for a name to one name that can be used
1726 # as a key into another hash. The whole concept is for memory
1727 # savings, as the second hash doesn't have to have all the
1728 # combinations. Actually, there are two hashes that do the
1729 # converstion. One is used in utf8_heavy.pl (stored in Heavy.pl) for
1730 # looking up properties matchable in regexes. This function needs to
1731 # access string properties, which aren't available in regexes, so a
1732 # second conversion hash is made for them (stored in UCD.pl). Look in
1733 # the string one now, as the rest can have an optional 'is' prefix,
1734 # which these don't.
1735 if (exists $string_property_loose_to_name{$loose}) {
1737 # Convert to its standard loose name.
1738 $prop = $string_property_loose_to_name{$loose};
1741 my $retrying = 0; # bool. ? Has an initial 'is' been stripped
1743 if (exists $utf8::loose_property_name_of{$loose}
1745 || ! exists $ambiguous_names{$loose}))
1747 # Found an entry giving the standard form. We don't get here
1748 # (in the test above) when we've stripped off an
1749 # 'is' and the result is an ambiguous name. That is because
1750 # these are official Unicode properties (though Perl can have
1751 # an optional 'is' prefix meaning the official property), and
1752 # all ambiguous cases involve a Perl single-form extension
1753 # for the gc, script, or block properties, and the stripped
1754 # 'is' means that they mean one of those, and not one of
1756 $prop = $utf8::loose_property_name_of{$loose};
1758 elsif (exists $loose_perlprop_to_name{$loose}) {
1760 # This hash is specifically for this function to list Perl
1761 # extensions that aren't in the earlier hashes. If there is
1762 # only one element, the short and long names are identical.
1763 # Otherwise the form is already in the same form as
1764 # %prop_aliases, which is handled at the end of the function.
1765 $list_ref = $loose_perlprop_to_name{$loose};
1766 if (@$list_ref == 1) {
1767 my @list = ($list_ref->[0], $list_ref->[0]);
1771 elsif (! exists $utf8::loose_to_file_of{$loose}) {
1773 # loose_to_file_of is a complete list of loose names. If not
1774 # there, the input is unknown.
1779 # Here we found the name but not its aliases, so it has to
1780 # exist. This means it must be one of the Perl single-form
1781 # extensions. First see if it is for a property-value
1782 # combination in one of the following properties.
1784 foreach my $property ("gc", "script") {
1785 @list = prop_value_aliases($property, $loose);
1790 # Here, it is one of those property-value combination
1791 # single-form synonyms. There are ambiguities with some
1792 # of these. Check against the list for these, and adjust
1794 for my $i (0 .. @list -1) {
1795 if (exists $ambiguous_names
1796 {utf8::_loose_name(lc $list[$i])})
1798 # The ambiguity is resolved by toggling whether or
1799 # not it has an 'is' prefix
1800 $list[$i] =~ s/^Is_// or $list[$i] =~ s/^/Is_/;
1806 # Here, it wasn't one of the gc or script single-form
1807 # extensions. It could be a block property single-form
1808 # extension. An 'in' prefix definitely means that, and should
1809 # be looked up without the prefix. However, starting in
1810 # Unicode 6.1, we have to special case 'indic...', as there
1811 # is a property that begins with that name. We shouldn't
1812 # strip the 'in' from that. I'm (khw) generalizing this to
1813 # 'indic' instead of the single property, because I suspect
1814 # that others of this class may come along in the future.
1815 # However, this could backfire and a block created whose name
1816 # begins with 'dic...', and we would want to strip the 'in'.
1817 # At which point this would have to be tweaked.
1818 my $began_with_in = $loose =~ s/^in(?!dic)//;
1819 @list = prop_value_aliases("block", $loose);
1821 map { $_ =~ s/^/In_/ } @list;
1825 # Here still haven't found it. The last opportunity for it
1826 # being valid is only if it began with 'is'. We retry without
1827 # the 'is', setting a flag to that effect so that we don't
1828 # accept things that begin with 'isis...'
1829 if (! $retrying && ! $began_with_in && $loose =~ s/^is//) {
1834 # Here, didn't find it. Since it was in %loose_to_file_of, we
1835 # should have been able to find it.
1836 carp __PACKAGE__, "::prop_aliases: Unexpectedly could not find '$prop'. Send bug report to perlbug\@perl.org";
1843 # Here, we have set $prop to a standard form name of the input. Look
1844 # it up in the structure created by mktables for this purpose, which
1845 # contains both strict and loosely matched properties. Avoid
1847 $list_ref = $prop_aliases{$prop} if exists $prop_aliases{$prop};
1848 return unless $list_ref;
1851 # The full name is in element 1.
1852 return $list_ref->[1] unless wantarray;
1854 return @{_dclone $list_ref};
1859 =head2 B<prop_value_aliases()>
1861 use Unicode::UCD 'prop_value_aliases';
1863 my ($short_name, $full_name, @other_names)
1864 = prop_value_aliases("Gc", "Punct");
1865 my $same_full_name = prop_value_aliases("Gc", "P"); # Scalar cntxt
1866 my ($same_short_name) = prop_value_aliases("Gc", "P"); # gets 0th
1868 print "The full name is $full_name\n";
1869 print "The short name is $short_name\n";
1870 print "The other aliases are: ", join(", ", @other_names), "\n";
1873 The full name is Punctuation
1875 The other aliases are: Punct
1877 Some Unicode properties have a restricted set of legal values. For example,
1878 all binary properties are restricted to just C<true> or C<false>; and there
1879 are only a few dozen possible General Categories.
1881 For such properties, there are usually several synonyms for each possible
1882 value. For example, in binary properties, I<truth> can be represented by any of
1883 the strings "Y", "Yes", "T", or "True"; and the General Category
1884 "Punctuation" by that string, or "Punct", or simply "P".
1886 Like property names, there is typically at least a short name for each such
1887 property-value, and a long name. If you know any name of the property-value,
1888 you can use C<prop_value_aliases>() to get the long name (when called in
1889 scalar context), or a list of all the names, with the short name in the 0th
1890 element, the long name in the next element, and any other synonyms in the
1891 remaining elements, in no particular order, except that any all-numeric
1892 synonyms will be last.
1894 The long name is returned in a form nicely capitalized, suitable for printing.
1896 Case, white space, hyphens, and underscores are ignored in the input parameters
1897 (except for the trailing underscore in the old-form grandfathered-in general
1898 category property value C<"L_">, which is better written as C<"LC">).
1900 If either name is unknown, C<undef> is returned. Note that Perl typically
1901 recognizes property names in regular expressions with an optional C<"Is_>"
1902 (with or without the underscore) prefixed to them, such as C<\p{isgc=punct}>.
1903 This function does not recognize those in the property parameter, returning
1906 If called with a property that doesn't have synonyms for its values, it
1907 returns the input value, possibly normalized with capitalization and
1910 For the block property, new-style block names are returned (see
1911 L</Old-style versus new-style block names>).
1913 To find the synonyms for single-forms, such as C<\p{Any}>, use
1914 L</prop_aliases()> instead.
1916 C<prop_value_aliases> does not know about any user-defined properties, and
1917 will return C<undef> if called with one of those.
1921 # These are created by mktables for this routine and stored in unicore/UCD.pl
1922 # where their structures are described.
1923 our %loose_to_standard_value;
1924 our %prop_value_aliases;
1926 sub prop_value_aliases ($$) {
1927 my ($prop, $value) = @_;
1928 return unless defined $prop && defined $value;
1930 require "unicore/UCD.pl";
1931 require "utf8_heavy.pl";
1933 # Find the property name synonym that's used as the key in other hashes,
1934 # which is element 0 in the returned list.
1935 ($prop) = prop_aliases($prop);
1937 $prop = utf8::_loose_name(lc $prop);
1939 # Here is a legal property, but the hash below (created by mktables for
1940 # this purpose) only knows about the properties that have a very finite
1941 # number of potential values, that is not ones whose value could be
1942 # anything, like most (if not all) string properties. These don't have
1943 # synonyms anyway. Simply return the input. For example, there is no
1944 # synonym for ('Uppercase_Mapping', A').
1945 return $value if ! exists $prop_value_aliases{$prop};
1947 # The value name may be loosely or strictly matched; we don't know yet.
1948 # But both types use lower-case.
1951 # If the name isn't found under loose matching, it certainly won't be
1952 # found under strict
1953 my $loose_value = utf8::_loose_name($value);
1954 return unless exists $loose_to_standard_value{"$prop=$loose_value"};
1956 # Similarly if the combination under loose matching doesn't exist, it
1957 # won't exist under strict.
1958 my $standard_value = $loose_to_standard_value{"$prop=$loose_value"};
1959 return unless exists $prop_value_aliases{$prop}{$standard_value};
1961 # Here we did find a combination under loose matching rules. But it could
1962 # be that is a strict property match that shouldn't have matched.
1963 # %prop_value_aliases is set up so that the strict matches will appear as
1964 # if they were in loose form. Thus, if the non-loose version is legal,
1965 # we're ok, can skip the further check.
1966 if (! exists $utf8::stricter_to_file_of{"$prop=$value"}
1968 # We're also ok and skip the further check if value loosely matches.
1969 # mktables has verified that no strict name under loose rules maps to
1970 # an existing loose name. This code relies on the very limited
1971 # circumstances that strict names can be here. Strict name matching
1972 # happens under two conditions:
1973 # 1) when the name begins with an underscore. But this function
1974 # doesn't accept those, and %prop_value_aliases doesn't have
1976 # 2) When the values are numeric, in which case we need to look
1977 # further, but their squeezed-out loose values will be in
1978 # %stricter_to_file_of
1979 && exists $utf8::stricter_to_file_of{"$prop=$loose_value"})
1981 # The only thing that's legal loosely under strict is that can have an
1982 # underscore between digit pairs XXX
1983 while ($value =~ s/(\d)_(\d)/$1$2/g) {}
1984 return unless exists $utf8::stricter_to_file_of{"$prop=$value"};
1987 # Here, we know that the combination exists. Return it.
1988 my $list_ref = $prop_value_aliases{$prop}{$standard_value};
1989 if (@$list_ref > 1) {
1990 # The full name is in element 1.
1991 return $list_ref->[1] unless wantarray;
1993 return @{_dclone $list_ref};
1996 return $list_ref->[0] unless wantarray;
1998 # Only 1 element means that it repeats
1999 return ( $list_ref->[0], $list_ref->[0] );
2002 # All 1 bits is the largest possible UV.
2003 $Unicode::UCD::MAX_CP = ~0;
2007 =head2 B<prop_invlist()>
2009 C<prop_invlist> returns an inversion list (described below) that defines all the
2010 code points for the binary Unicode property (or "property=value" pair) given
2011 by the input parameter string:
2014 use Unicode::UCD 'prop_invlist';
2015 say join ", ", prop_invlist("Any");
2020 If the input is unknown C<undef> is returned in scalar context; an empty-list
2021 in list context. If the input is known, the number of elements in
2022 the list is returned if called in scalar context.
2024 L<perluniprops|perluniprops/Properties accessible through \p{} and \P{}> gives
2025 the list of properties that this function accepts, as well as all the possible
2026 forms for them (including with the optional "Is_" prefixes). (Except this
2027 function doesn't accept any Perl-internal properties, some of which are listed
2028 there.) This function uses the same loose or tighter matching rules for
2029 resolving the input property's name as is done for regular expressions. These
2030 are also specified in L<perluniprops|perluniprops/Properties accessible
2031 through \p{} and \P{}>. Examples of using the "property=value" form are:
2033 say join ", ", prop_invlist("Script=Shavian");
2038 say join ", ", prop_invlist("ASCII_Hex_Digit=No");
2041 0, 48, 58, 65, 71, 97, 103
2043 say join ", ", prop_invlist("ASCII_Hex_Digit=Yes");
2046 48, 58, 65, 71, 97, 103
2048 Inversion lists are a compact way of specifying Unicode property-value
2049 definitions. The 0th item in the list is the lowest code point that has the
2050 property-value. The next item (item [1]) is the lowest code point beyond that
2051 one that does NOT have the property-value. And the next item beyond that
2052 ([2]) is the lowest code point beyond that one that does have the
2053 property-value, and so on. Put another way, each element in the list gives
2054 the beginning of a range that has the property-value (for even numbered
2055 elements), or doesn't have the property-value (for odd numbered elements).
2056 The name for this data structure stems from the fact that each element in the
2057 list toggles (or inverts) whether the corresponding range is or isn't on the
2060 In the final example above, the first ASCII Hex digit is code point 48, the
2061 character "0", and all code points from it through 57 (a "9") are ASCII hex
2062 digits. Code points 58 through 64 aren't, but 65 (an "A") through 70 (an "F")
2063 are, as are 97 ("a") through 102 ("f"). 103 starts a range of code points
2064 that aren't ASCII hex digits. That range extends to infinity, which on your
2065 computer can be found in the variable C<$Unicode::UCD::MAX_CP>. (This
2066 variable is as close to infinity as Perl can get on your platform, and may be
2067 too high for some operations to work; you may wish to use a smaller number for
2070 Note that the inversion lists returned by this function can possibly include
2071 non-Unicode code points, that is anything above 0x10FFFF. This is in
2072 contrast to Perl regular expression matches on those code points, in which a
2073 non-Unicode code point always fails to match. For example, both of these have
2076 chr(0x110000) =~ \p{ASCII_Hex_Digit=True} # Fails.
2077 chr(0x110000) =~ \p{ASCII_Hex_Digit=False} # Fails!
2079 And both raise a warning that a Unicode property is being used on a
2080 non-Unicode code point. It is arguable as to which is the correct thing to do
2081 here. This function has chosen the way opposite to the Perl regular
2082 expression behavior. This allows you to easily flip to to the Perl regular
2083 expression way (for you to go in the other direction would be far harder).
2084 Simply add 0x110000 at the end of the non-empty returned list if it isn't
2085 already that value; and pop that value if it is; like:
2087 my @list = prop_invlist("foo");
2089 if ($list[-1] == 0x110000) {
2090 pop @list; # Defeat the turning on for above Unicode
2093 push @list, 0x110000; # Turn off for above Unicode
2097 It is a simple matter to expand out an inversion list to a full list of all
2098 code points that have the property-value:
2100 my @invlist = prop_invlist($property_name);
2101 die "empty" unless @invlist;
2103 for (my $i = 0; $i < @invlist; $i += 2) {
2104 my $upper = ($i + 1) < @invlist
2105 ? $invlist[$i+1] - 1 # In range
2106 : $Unicode::UCD::MAX_CP; # To infinity. You may want
2107 # to stop much much earlier;
2108 # going this high may expose
2109 # perl deficiencies with very
2111 for my $j ($invlist[$i] .. $upper) {
2112 push @full_list, $j;
2116 C<prop_invlist> does not know about any user-defined nor Perl internal-only
2117 properties, and will return C<undef> if called with one of those.
2121 # User-defined properties could be handled with some changes to utf8_heavy.pl;
2122 # and implementing here of dealing with EXTRAS. If done, consideration should
2123 # be given to the fact that the user subroutine could return different results
2124 # with each call; security issues need to be thought about.
2126 # These are created by mktables for this routine and stored in unicore/UCD.pl
2127 # where their structures are described.
2128 our %loose_defaults;
2129 our $MAX_UNICODE_CODEPOINT;
2131 sub prop_invlist ($;$) {
2134 # Undocumented way to get at Perl internal properties
2135 my $internal_ok = defined $_[1] && $_[1] eq '_perl_core_internal_ok';
2137 return if ! defined $prop;
2139 require "utf8_heavy.pl";
2141 # Warnings for these are only for regexes, so not applicable to us
2142 no warnings 'deprecated';
2144 # Get the swash definition of the property-value.
2145 my $swash = utf8::SWASHNEW(__PACKAGE__, $prop, undef, 1, 0);
2147 # Fail if not found, or isn't a boolean property-value, or is a
2148 # user-defined property, or is internal-only.
2151 || $swash->{'BITS'} != 1
2152 || $swash->{'USER_DEFINED'}
2153 || (! $internal_ok && $prop =~ /^\s*_/);
2155 if ($swash->{'EXTRAS'}) {
2156 carp __PACKAGE__, "::prop_invlist: swash returned for $prop unexpectedly has EXTRAS magic";
2159 if ($swash->{'SPECIALS'}) {
2160 carp __PACKAGE__, "::prop_invlist: swash returned for $prop unexpectedly has SPECIALS magic";
2166 # The input lines look like:
2170 # Split into lines, stripped of trailing comments
2171 foreach my $range (split "\n",
2172 $swash->{'LIST'} =~ s/ \s* (?: \# .* )? $ //xmgr)
2174 # And find the beginning and end of the range on the line
2175 my ($hex_begin, $hex_end) = split "\t", $range;
2176 my $begin = hex $hex_begin;
2178 # If the new range merely extends the old, we remove the marker
2179 # created the last time through the loop for the old's end, which
2180 # causes the new one's end to be used instead.
2181 if (@invlist && $begin == $invlist[-1]) {
2185 # Add the beginning of the range
2186 push @invlist, $begin;
2189 if (defined $hex_end) { # The next item starts with the code point 1
2190 # beyond the end of the range.
2191 push @invlist, hex($hex_end) + 1;
2193 else { # No end of range, is a single code point.
2194 push @invlist, $begin + 1;
2198 require "unicore/UCD.pl";
2199 my $FIRST_NON_UNICODE = $MAX_UNICODE_CODEPOINT + 1;
2201 # Could need to be inverted: add or subtract a 0 at the beginning of the
2202 # list. And to keep it from matching non-Unicode, add or subtract the
2203 # first non-unicode code point.
2204 if ($swash->{'INVERT_IT'}) {
2205 if (@invlist && $invlist[0] == 0) {
2209 unshift @invlist, 0;
2211 if (@invlist && $invlist[-1] == $FIRST_NON_UNICODE) {
2215 push @invlist, $FIRST_NON_UNICODE;
2219 # Here, the list is set up to include only Unicode code points. But, if
2220 # the table is the default one for the property, it should contain all
2221 # non-Unicode code points. First calculate the loose name for the
2222 # property. This is done even for strict-name properties, as the data
2223 # structure that mktables generates for us is set up so that we don't have
2224 # to worry about that. The property-value needs to be split if compound,
2225 # as the loose rules need to be independently calculated on each part. We
2226 # know that it is syntactically valid, or SWASHNEW would have failed.
2229 my ($prop_only, $table) = split /\s*[:=]\s*/, $prop;
2232 # May have optional prefixed 'is'
2233 $prop = utf8::_loose_name($prop_only) =~ s/^is//r;
2234 $prop = $utf8::loose_property_name_of{$prop};
2235 $prop .= "=" . utf8::_loose_name($table);
2238 $prop = utf8::_loose_name($prop);
2240 if (exists $loose_defaults{$prop}) {
2242 # Here, is the default table. If a range ended with 10ffff, instead
2243 # continue that range to infinity, by popping the 110000; otherwise,
2244 # add the range from 11000 to infinity
2245 if (! @invlist || $invlist[-1] != $FIRST_NON_UNICODE) {
2246 push @invlist, $FIRST_NON_UNICODE;
2256 sub _search_invlist {
2257 # Find the range in the inversion list which contains a code point; that
2258 # is, find i such that l[i] <= code_point < l[i+1]
2260 # If this is ever made public, could use to speed up .t specials. Would
2261 # need to use code point argument, as in other functions in this pm
2263 my $list_ref = shift;
2264 my $code_point = shift;
2265 # Verify non-neg numeric XXX
2267 my $max_element = @$list_ref - 1;
2268 return if ! $max_element < 0; # Undef if list is empty.
2270 # Short cut something at the far-end of the table. This also allows us to
2271 # refer to element [$i+1] without fear of being out-of-bounds in the loop
2273 return $max_element if $code_point >= $list_ref->[$max_element];
2275 use integer; # want integer division
2277 my $i = $max_element / 2;
2280 my $upper = $max_element;
2283 if ($code_point >= $list_ref->[$i]) {
2285 # Here we have met the lower constraint. We can quit if we
2286 # also meet the upper one.
2287 last if $code_point < $list_ref->[$i+1];
2289 $lower = $i; # Still too low.
2294 # Here, $code_point < $list_ref[$i], so look lower down.
2298 # Split search domain in half to try again.
2299 my $temp = ($upper + $lower) / 2;
2301 # No point in continuing unless $i changes for next time
2303 return $i if $temp == $i;
2305 } # End of while loop
2307 # Here we have found the offset
2313 =head2 B<prop_invmap()>
2315 use Unicode::UCD 'prop_invmap';
2316 my ($list_ref, $map_ref, $format, $missing)
2317 = prop_invmap("General Category");
2319 C<prop_invmap> is used to get the complete mapping definition for a property,
2320 in the form of an inversion map. An inversion map consists of two parallel
2321 arrays. One is an ordered list of code points that mark range beginnings, and
2322 the other gives the value (or mapping) that all code points in the
2323 corresponding range have.
2325 C<prop_invmap> is called with the name of the desired property. The name is
2326 loosely matched, meaning that differences in case, white-space, hyphens, and
2327 underscores are not meaningful (except for the trailing underscore in the
2328 old-form grandfathered-in property C<"L_">, which is better written as C<"LC">,
2329 or even better, C<"Gc=LC">).
2331 Many Unicode properties have more than one name (or alias). C<prop_invmap>
2332 understands all of these, including Perl extensions to them. Ambiguities are
2333 resolved as described above for L</prop_aliases()>. The Perl internal
2334 property "Perl_Decimal_Digit, described below, is also accepted. C<undef> is
2335 returned if the property name is unknown.
2336 See L<perluniprops/Properties accessible through Unicode::UCD> for the
2337 properties acceptable as inputs to this function.
2339 It is a fatal error to call this function except in list context.
2341 In addition to the the two arrays that form the inversion map, C<prop_invmap>
2342 returns two other values; one is a scalar that gives some details as to the
2343 format of the entries of the map array; the other is used for specialized
2344 purposes, described at the end of this section.
2346 This means that C<prop_invmap> returns a 4 element list. For example,
2348 my ($blocks_ranges_ref, $blocks_maps_ref, $format, $default)
2349 = prop_invmap("Block");
2351 In this call, the two arrays will be populated as shown below (for Unicode
2354 Index @blocks_ranges @blocks_maps
2355 0 0x0000 Basic Latin
2356 1 0x0080 Latin-1 Supplement
2357 2 0x0100 Latin Extended-A
2358 3 0x0180 Latin Extended-B
2359 4 0x0250 IPA Extensions
2360 5 0x02B0 Spacing Modifier Letters
2361 6 0x0300 Combining Diacritical Marks
2362 7 0x0370 Greek and Coptic
2365 233 0x2B820 No_Block
2366 234 0x2F800 CJK Compatibility Ideographs Supplement
2367 235 0x2FA20 No_Block
2369 237 0xE0080 No_Block
2370 238 0xE0100 Variation Selectors Supplement
2371 239 0xE01F0 No_Block
2372 240 0xF0000 Supplementary Private Use Area-A
2373 241 0x100000 Supplementary Private Use Area-B
2374 242 0x110000 No_Block
2376 The first line (with Index [0]) means that the value for code point 0 is "Basic
2377 Latin". The entry "0x0080" in the @blocks_ranges column in the second line
2378 means that the value from the first line, "Basic Latin", extends to all code
2379 points in the range from 0 up to but not including 0x0080, that is, through
2380 127. In other words, the code points from 0 to 127 are all in the "Basic
2381 Latin" block. Similarly, all code points in the range from 0x0080 up to (but
2382 not including) 0x0100 are in the block named "Latin-1 Supplement", etc.
2383 (Notice that the return is the old-style block names; see L</Old-style versus
2384 new-style block names>).
2386 The final line (with Index [242]) means that the value for all code points above
2387 the legal Unicode maximum code point have the value "No_Block", which is the
2388 term Unicode uses for a non-existing block.
2390 The arrays completely specify the mappings for all possible code points.
2391 The final element in an inversion map returned by this function will always be
2392 for the range that consists of all the code points that aren't legal Unicode,
2393 but that are expressible on the platform. (That is, it starts with code point
2394 0x110000, the first code point above the legal Unicode maximum, and extends to
2395 infinity.) The value for that range will be the same that any typical
2396 unassigned code point has for the specified property. (Certain unassigned
2397 code points are not "typical"; for example the non-character code points, or
2398 those in blocks that are to be written right-to-left. The above-Unicode
2399 range's value is not based on these atypical code points.) It could be argued
2400 that, instead of treating these as unassigned Unicode code points, the value
2401 for this range should be C<undef>. If you wish, you can change the returned
2404 The maps are almost always simple scalars that should be interpreted as-is.
2405 These values are those given in the Unicode-supplied data files, which may be
2406 inconsistent as to capitalization and as to which synonym for a property-value
2407 is given. The results may be normalized by using the L</prop_value_aliases()>
2410 There are exceptions to the simple scalar maps. Some properties have some
2411 elements in their map list that are themselves lists of scalars; and some
2412 special strings are returned that are not to be interpreted as-is. Element
2413 [2] (placed into C<$format> in the example above) of the returned four element
2414 list tells you if the map has any of these special elements or not, as follows:
2420 means all the elements of the map array are simple scalars, with no special
2421 elements. Almost all properties are like this, like the C<block> example
2426 means that some of the map array elements have the form given by C<"s">, and
2427 the rest are lists of scalars. For example, here is a portion of the output
2428 of calling C<prop_invmap>() with the "Script Extensions" property:
2430 @scripts_ranges @scripts_maps
2433 0x0964 [ Bengali, Devanagari, Gurumukhi, Oriya ]
2437 Here, the code points 0x964 and 0x965 are both used in Bengali,
2438 Devanagari, Gurmukhi, and Oriya, but no other scripts.
2440 The Name_Alias property is also of this form. But each scalar consists of two
2441 components: 1) the name, and 2) the type of alias this is. They are
2442 separated by a colon and a space. In Unicode 6.1, there are several alias types:
2448 indicates that the name is a corrected form for the
2449 original name (which remains valid) for the same code point.
2453 adds a new name for a control character.
2457 is an alternate name for a character
2461 is a name for a character that has been documented but was never in any
2464 =item C<abbreviation>
2466 is a common abbreviation for a character
2470 The lists are ordered (roughly) so the most preferred names come before less
2475 @aliases_ranges @alias_maps
2477 0x009E [ 'PRIVACY MESSAGE: control', 'PM: abbreviation' ]
2478 0x009F [ 'APPLICATION PROGRAM COMMAND: control',
2481 0x00A0 'NBSP: abbreviation'
2483 0x00AD 'SHY: abbreviation'
2485 0x01A2 'LATIN CAPITAL LETTER GHA: correction'
2486 0x01A3 'LATIN SMALL LETTER GHA: correction'
2490 A map to the empty string means that there is no alias defined for the code
2495 is like C<"s"> in that all the map array elements are scalars, but here they are
2496 restricted to all being integers, and some have to be adjusted (hence the name
2497 C<"a">) to get the correct result. For example, in:
2499 my ($uppers_ranges_ref, $uppers_maps_ref, $format)
2500 = prop_invmap("Simple_Uppercase_Mapping");
2502 the returned arrays look like this:
2504 @$uppers_ranges_ref @$uppers_maps_ref Note
2506 97 65 'a' maps to 'A', b => B ...
2508 181 924 MICRO SIGN => Greek Cap MU
2512 Let's start with the second line. It says that the uppercase of code point 97
2513 is 65; or C<uc("a")> == "A". But the line is for the entire range of code
2514 points 97 through 122. To get the mapping for any code point in a range, you
2515 take the offset it has from the beginning code point of the range, and add
2516 that to the mapping for that first code point. So, the mapping for 122 ("z")
2517 is derived by taking the offset of 122 from 97 (=25) and adding that to 65,
2518 yielding 90 ("z"). Likewise for everything in between.
2520 The first line works the same way. The first map in a range is always the
2521 correct value for its code point (because the adjustment is 0). Thus the
2522 C<uc(chr(0))> is just itself. Also, C<uc(chr(1))> is also itself, as the
2523 adjustment is 0+1-0 .. C<uc(chr(96))> is 96.
2525 Requiring this simple adjustment allows the returned arrays to be
2526 significantly smaller than otherwise, up to a factor of 10, speeding up
2527 searching through them.
2531 means that some of the map array elements have the form given by C<"a">, and
2532 the rest are ordered lists of code points.
2535 my ($uppers_ranges_ref, $uppers_maps_ref, $format)
2536 = prop_invmap("Uppercase_Mapping");
2538 the returned arrays look like this:
2540 @$uppers_ranges_ref @$uppers_maps_ref
2547 0x0149 [ 0x02BC 0x004E ]
2552 This is the full Uppercase_Mapping property (as opposed to the
2553 Simple_Uppercase_Mapping given in the example for format C<"a">). The only
2554 difference between the two in the ranges shown is that the code point at
2555 0x0149 (LATIN SMALL LETTER N PRECEDED BY APOSTROPHE) maps to a string of two
2556 characters, 0x02BC (MODIFIER LETTER APOSTROPHE) followed by 0x004E (LATIN
2559 No adjustments are needed to entries that are references to arrays; each such
2560 entry will have exactly one element in its range, so the offset is always 0.
2564 This is like C<"a">, but some elements are the empty string, and should not be
2566 The one internal Perl property accessible by C<prop_invmap> is of this type:
2567 "Perl_Decimal_Digit" returns an inversion map which gives the numeric values
2568 that are represented by the Unicode decimal digit characters. Characters that
2569 don't represent decimal digits map to the empty string, like so:
2584 This means that the code points from 0 to 0x2F do not represent decimal digits;
2585 the code point 0x30 (DIGIT ZERO) represents 0; code point 0x31, (DIGIT ONE),
2586 represents 0+1-0 = 1; ... code point 0x39, (DIGIT NINE), represents 0+9-0 = 9;
2587 ... code points 0x3A through 0x65F do not represent decimal digits; 0x660
2588 (ARABIC-INDIC DIGIT ZERO), represents 0; ... 0x07C1 (NKO DIGIT ONE),
2589 represents 0+1-0 = 1 ...
2593 is a combination of the C<"al"> type and the C<"ae"> type. Some of
2594 the map array elements have the forms given by C<"al">, and
2595 the rest are the empty string. The property C<NFKC_Casefold> has this form.
2596 An example slice is:
2598 @$ranges_ref @$maps_ref Note
2600 0x00AA 97 FEMININE ORDINAL INDICATOR => 'a'
2602 0x00AD SOFT HYPHEN => ""
2604 0x00AF [ 0x0020, 0x0304 ] MACRON => SPACE . COMBINING MACRON
2610 means that all the elements of the map array are either rational numbers or
2611 the string C<"NaN">, meaning "Not a Number". A rational number is either an
2612 integer, or two integers separated by a solidus (C<"/">). The second integer
2613 represents the denominator of the division implied by the solidus, and is
2614 actually always positive, so it is guaranteed not to be 0 and to not be
2615 signed. When the element is a plain integer (without the
2616 solidus), it may need to be adjusted to get the correct value by adding the
2617 offset, just as other C<"a"> properties. No adjustment is needed for
2618 fractions, as the range is guaranteed to have just a single element, and so
2619 the offset is always 0.
2621 If you want to convert the returned map to entirely scalar numbers, you
2622 can use something like this:
2624 my ($invlist_ref, $invmap_ref, $format) = prop_invmap($property);
2625 if ($format && $format eq "ar") {
2626 map { $_ = eval $_ if $_ ne 'NaN' } @$map_ref;
2629 Here's some entries from the output of the property "Nv", which has format
2632 @numerics_ranges @numerics_maps Note
2634 0x30 0 DIGIT 0 .. DIGIT 9
2636 0xB2 2 SUPERSCRIPTs 2 and 3
2638 0xB9 1 SUPERSCRIPT 1
2640 0xBC 1/4 VULGAR FRACTION 1/4
2641 0xBD 1/2 VULGAR FRACTION 1/2
2642 0xBE 3/4 VULGAR FRACTION 3/4
2644 0x660 0 ARABIC-INDIC DIGIT ZERO .. NINE
2649 means the Name property. All the elements of the map array are simple
2650 scalars, but some of them contain special strings that require more work to
2651 get the actual name.
2655 CJK UNIFIED IDEOGRAPH-<code point>
2657 mean that the name for the code point is "CJK UNIFIED IDEOGRAPH-"
2658 with the code point (expressed in hexadecimal) appended to it, like "CJK
2659 UNIFIED IDEOGRAPH-3403" (similarly for S<C<CJK COMPATIBILITY IDEOGRAPH-E<lt>code
2666 means that the name is algorithmically calculated. This is easily done by
2667 the function L<charnames/charnames::viacode(code)>.
2669 Note that for control characters (C<Gc=cc>), Unicode's data files have the
2670 string "C<E<lt>controlE<gt>>", but the real name of each of these characters is the empty
2671 string. This function returns that real name, the empty string. (There are
2672 names for these characters, but they are considered aliases, not the Name
2673 property name, and are contained in the C<Name_Alias> property.)
2677 means the Decomposition_Mapping property. This property is like C<"al">
2678 properties, except that one of the scalar elements is of the form:
2682 This signifies that this entry should be replaced by the decompositions for
2683 all the code points whose decomposition is algorithmically calculated. (All
2684 of them are currently in one range and no others outisde the range are likely
2685 to ever be added to Unicode; the C<"n"> format
2686 has this same entry.) These can be generated via the function
2687 L<Unicode::Normalize::NFD()|Unicode::Normalize>.
2689 Note that the mapping is the one that is specified in the Unicode data files,
2690 and to get the final decomposition, it may need to be applied recursively.
2694 Note that a format begins with the letter "a" if and only the property it is
2695 for requires adjustments by adding the offsets in multi-element ranges. For
2696 all these properties, an entry should be adjusted only if the map is a scalar
2697 which is an integer. That is, it must match the regular expression:
2701 Further, the first element in a range never needs adjustment, as the
2702 adjustment would be just adding 0.
2704 A binary search can be used to quickly find a code point in the inversion
2705 list, and hence its corresponding mapping.
2707 The final element (index [3], assigned to C<$default> in the "block" example) in
2708 the four element list returned by this function may be useful for applications
2709 that wish to convert the returned inversion map data structure into some
2710 other, such as a hash. It gives the mapping that most code points map to
2711 under the property. If you establish the convention that any code point not
2712 explicitly listed in your data structure maps to this value, you can
2713 potentially make your data structure much smaller. As you construct your data
2714 structure from the one returned by this function, simply ignore those ranges
2715 that map to this value, generally called the "default" value. For example, to
2716 convert to the data structure searchable by L</charinrange()>, you can follow
2717 this recipe for properties that don't require adjustments:
2719 my ($list_ref, $map_ref, $format, $missing) = prop_invmap($property);
2722 # Look at each element in the list, but the -2 is needed because we
2723 # look at $i+1 in the loop, and the final element is guaranteed to map
2724 # to $missing by prop_invmap(), so we would skip it anyway.
2725 for my $i (0 .. @$list_ref - 2) {
2726 next if $map_ref->[$i] eq $missing;
2727 push @range_list, [ $list_ref->[$i],
2733 print charinrange(\@range_list, $code_point), "\n";
2735 With this, C<charinrange()> will return C<undef> if its input code point maps
2736 to C<$missing>. You can avoid this by omitting the C<next> statement, and adding
2737 a line after the loop to handle the final element of the inversion map.
2739 Similarly, this recipe can be used for properties that do require adjustments:
2741 for my $i (0 .. @$list_ref - 2) {
2742 next if $map_ref->[$i] eq $missing;
2744 # prop_invmap() guarantees that if the mapping is to an array, the
2745 # range has just one element, so no need to worry about adjustments.
2746 if (ref $map_ref->[$i]) {
2748 [ $list_ref->[$i], $list_ref->[$i], $map_ref->[$i] ];
2750 else { # Otherwise each element is actually mapped to a separate
2751 # value, so the range has to be split into single code point
2756 # For each code point that gets mapped to something...
2757 for my $j ($list_ref->[$i] .. $list_ref->[$i+1] -1 ) {
2759 # ... add a range consisting of just it mapping to the
2760 # original plus the adjustment, which is incremented for the
2761 # next time through the loop, as the offset increases by 1
2762 # for each element in the range
2764 [ $j, $j, $map_ref->[$i] + $adjustment++ ];
2769 Note that the inversion maps returned for the C<Case_Folding> and
2770 C<Simple_Case_Folding> properties do not include the Turkic-locale mappings.
2771 Use L</casefold()> for these.
2773 C<prop_invmap> does not know about any user-defined properties, and will
2774 return C<undef> if called with one of those.
2778 # User-defined properties could be handled with some changes to utf8_heavy.pl;
2779 # if done, consideration should be given to the fact that the user subroutine
2780 # could return different results with each call, which could lead to some
2783 # One could store things in memory so they don't have to be recalculated, but
2784 # it is unlikely this will be called often, and some properties would take up
2785 # significant memory.
2787 # These are created by mktables for this routine and stored in unicore/UCD.pl
2788 # where their structures are described.
2789 our @algorithmic_named_code_points;
2793 sub prop_invmap ($) {
2795 croak __PACKAGE__, "::prop_invmap: must be called in list context" unless wantarray;
2798 return unless defined $prop;
2800 # Fail internal properties
2801 return if $prop =~ /^_/;
2803 # The values returned by this function.
2804 my (@invlist, @invmap, $format, $missing);
2806 # The swash has two components we look at, the base list, and a hash,
2807 # named 'SPECIALS', containing any additional members whose mappings don't
2808 # fit into the the base list scheme of things. These generally 'override'
2809 # any value in the base list for the same code point.
2812 require "utf8_heavy.pl";
2813 require "unicore/UCD.pl";
2817 # If there are multiple entries for a single code point
2818 my $has_multiples = 0;
2820 # Try to get the map swash for the property. They have 'To' prepended to
2821 # the property name, and 32 means we will accept 32 bit return values.
2822 # The 0 means we aren't calling this from tr///.
2823 my $swash = utf8::SWASHNEW(__PACKAGE__, "To$prop", undef, 32, 0);
2825 # If didn't find it, could be because needs a proxy. And if was the
2826 # 'Block' or 'Name' property, use a proxy even if did find it. Finding it
2827 # in these cases would be the result of the installation changing mktables
2828 # to output the Block or Name tables. The Block table gives block names
2829 # in the new-style, and this routine is supposed to return old-style block
2830 # names. The Name table is valid, but we need to execute the special code
2831 # below to add in the algorithmic-defined name entries.
2832 # And NFKCCF needs conversion, so handle that here too.
2833 if (ref $swash eq ""
2834 || $swash->{'TYPE'} =~ / ^ To (?: Blk | Na | NFKCCF ) $ /x)
2837 # Get the short name of the input property, in standard form
2838 my ($second_try) = prop_aliases($prop);
2839 return unless $second_try;
2840 $second_try = utf8::_loose_name(lc $second_try);
2842 if ($second_try eq "in") {
2844 # This property is identical to age for inversion map purposes
2848 elsif ($second_try =~ / ^ s ( cf | fc | [ltu] c ) $ /x) {
2850 # These properties use just the LIST part of the full mapping,
2851 # which includes the simple maps that are otherwise overridden by
2852 # the SPECIALS. So all we need do is to not look at the SPECIALS;
2853 # set $overrides to indicate that
2856 # The full name is the simple name stripped of its initial 's'
2859 # .. except for this case
2860 $prop = 'cf' if $prop eq 'fc';
2864 elsif ($second_try eq "blk") {
2866 # We use the old block names. Just create a fake swash from its
2870 $blocks{'LIST'} = "";
2871 $blocks{'TYPE'} = "ToBlk";
2872 $utf8::SwashInfo{ToBlk}{'missing'} = "No_Block";
2873 $utf8::SwashInfo{ToBlk}{'format'} = "s";
2875 foreach my $block (@BLOCKS) {
2876 $blocks{'LIST'} .= sprintf "%x\t%x\t%s\n",
2883 elsif ($second_try eq "na") {
2885 # Use the combo file that has all the Name-type properties in it,
2886 # extracting just the ones that are for the actual 'Name'
2887 # property. And create a fake swash from it.
2889 $names{'LIST'} = "";
2890 my $original = do "unicore/Name.pl";
2891 my $algorithm_names = \@algorithmic_named_code_points;
2893 # We need to remove the names from it that are aliases. For that
2894 # we need to also read in that table. Create a hash with the keys
2895 # being the code points, and the values being a list of the
2896 # aliases for the code point key.
2897 my ($aliases_code_points, $aliases_maps, undef, undef) =
2898 &prop_invmap('Name_Alias');
2900 for (my $i = 0; $i < @$aliases_code_points; $i++) {
2901 my $code_point = $aliases_code_points->[$i];
2902 $aliases{$code_point} = $aliases_maps->[$i];
2904 # If not already a list, make it into one, so that later we
2905 # can treat things uniformly
2906 if (! ref $aliases{$code_point}) {
2907 $aliases{$code_point} = [ $aliases{$code_point} ];
2910 # Remove the alias type from the entry, retaining just the
2912 map { s/:.*// } @{$aliases{$code_point}};
2916 foreach my $line (split "\n", $original) {
2917 my ($hex_code_point, $name) = split "\t", $line;
2919 # Weeds out all comments, blank lines, and named sequences
2920 next if $hex_code_point =~ /[^[:xdigit:]]/a;
2922 my $code_point = hex $hex_code_point;
2924 # The name of all controls is the default: the empty string.
2925 # The set of controls is immutable, so these hard-coded
2927 next if $code_point <= 0x9F
2928 && ($code_point <= 0x1F || $code_point >= 0x7F);
2930 # If this is a name_alias, it isn't a name
2931 next if grep { $_ eq $name } @{$aliases{$code_point}};
2933 # If we are beyond where one of the special lines needs to
2935 while ($i < @$algorithm_names
2936 && $code_point > $algorithm_names->[$i]->{'low'})
2939 # ... then insert it, ahead of what we were about to
2941 $names{'LIST'} .= sprintf "%x\t%x\t%s\n",
2942 $algorithm_names->[$i]->{'low'},
2943 $algorithm_names->[$i]->{'high'},
2944 $algorithm_names->[$i]->{'name'};
2946 # Done with this range.
2949 # We loop until all special lines that precede the next
2950 # regular one are output.
2953 # Here, is a normal name.
2954 $names{'LIST'} .= sprintf "%x\t\t%s\n", $code_point, $name;
2955 } # End of loop through all the names
2957 $names{'TYPE'} = "ToNa";
2958 $utf8::SwashInfo{ToNa}{'missing'} = "";
2959 $utf8::SwashInfo{ToNa}{'format'} = "n";
2962 elsif ($second_try =~ / ^ ( d [mt] ) $ /x) {
2964 # The file is a combination of dt and dm properties. Create a
2965 # fake swash from the portion that we want.
2966 my $original = do "unicore/Decomposition.pl";
2969 if ($second_try eq 'dt') {
2970 $decomps{'TYPE'} = "ToDt";
2971 $utf8::SwashInfo{'ToDt'}{'missing'} = "None";
2972 $utf8::SwashInfo{'ToDt'}{'format'} = "s";
2973 } # 'dm' is handled below, with 'nfkccf'
2975 $decomps{'LIST'} = "";
2977 # This property has one special range not in the file: for the
2978 # hangul syllables. But not in Unicode version 1.
2979 UnicodeVersion() unless defined $v_unicode_version;
2980 my $done_hangul = ($v_unicode_version lt v2.0.0)
2982 : 0; # Have we done the hangul range ?
2983 foreach my $line (split "\n", $original) {
2984 my ($hex_lower, $hex_upper, $type_and_map) = split "\t", $line;
2985 my $code_point = hex $hex_lower;
2989 # The type, enclosed in <...>, precedes the mapping separated
2991 if ($type_and_map =~ / ^ < ( .* ) > \s+ (.*) $ /x) {
2992 $value = ($second_try eq 'dt') ? $1 : $2
2994 else { # If there is no type specified, it's canonical
2995 $value = ($second_try eq 'dt')
3000 # Insert the hangul range at the appropriate spot.
3001 if (! $done_hangul && $code_point > $HANGUL_BEGIN) {
3004 sprintf "%x\t%x\t%s\n",
3006 $HANGUL_BEGIN + $HANGUL_COUNT - 1,
3007 ($second_try eq 'dt')
3009 : "<hangul syllable>";
3012 if ($value =~ / / && $hex_upper ne "" && $hex_upper ne $hex_lower) {
3013 $line = sprintf("%04X\t%s\t%s", hex($hex_lower) + 1, $hex_upper, $value);
3018 # And append this to our constructed LIST.
3019 $decomps{'LIST'} .= "$hex_lower\t$hex_upper\t$value\n";
3025 elsif ($second_try ne 'nfkccf') { # Don't know this property. Fail.
3029 if ($second_try eq 'nfkccf' || $second_try eq 'dm') {
3031 # The 'nfkccf' property is stored in the old format for backwards
3032 # compatibility for any applications that has read its file
3033 # directly before prop_invmap() existed.
3034 # And the code above has extracted the 'dm' property from its file
3035 # yielding the same format. So here we convert them to adjusted
3036 # format for compatibility with the other properties similar to
3040 # We construct a new converted list.
3043 my @ranges = split "\n", $swash->{'LIST'};
3044 for (my $i = 0; $i < @ranges; $i++) {
3045 my ($hex_begin, $hex_end, $map) = split "\t", $ranges[$i];
3047 # The dm property has maps that are space separated sequences
3048 # of code points, as well as the special entry "<hangul
3049 # syllable>, which also contains a blank.
3050 my @map = split " ", $map;
3053 # If it's just the special entry, append as-is.
3054 if ($map eq '<hangul syllable>') {
3055 $list .= "$ranges[$i]\n";
3059 # These should all be single-element ranges.
3060 croak __PACKAGE__, "::prop_invmap: Not expecting a mapping with multiple code points in a multi-element range, $ranges[$i]" if $hex_end ne "" && $hex_end ne $hex_begin;
3062 # Convert them to decimal, as that's what's expected.
3063 $list .= "$hex_begin\t\t"
3064 . join(" ", map { hex } @map)
3070 # Here, the mapping doesn't have a blank, is for a single code
3072 my $begin = hex $hex_begin;
3073 my $end = (defined $hex_end && $hex_end ne "")
3077 # Again, the output is to be in decimal.
3078 my $decimal_map = hex $map;
3080 # We know that multi-element ranges with the same mapping
3081 # should not be adjusted, as after the adjustment
3082 # multi-element ranges are for consecutive increasing code
3083 # points. Further, the final element in the list won't be
3084 # adjusted, as there is nothing after it to include in the
3086 if ($begin != $end || $i == @ranges -1) {
3088 # So just convert these to single-element ranges
3089 foreach my $code_point ($begin .. $end) {
3090 $list .= sprintf("%04X\t\t%d\n",
3091 $code_point, $decimal_map);
3096 # Here, we have a candidate for adjusting. What we do is
3097 # look through the subsequent adjacent elements in the
3098 # input. If the map to the next one differs by 1 from the
3099 # one before, then we combine into a larger range with the
3100 # initial map. Loop doing this until we find one that
3101 # can't be combined.
3103 my $offset = 0; # How far away are we from the initial
3105 my $squished = 0; # ? Did we squish at least two
3106 # elements together into one range
3107 for ( ; $i < @ranges; $i++) {
3108 my ($next_hex_begin, $next_hex_end, $next_map)
3109 = split "\t", $ranges[$i+1];
3111 # In the case of 'dm', the map may be a sequence of
3112 # multiple code points, which are never combined with
3114 last if $next_map =~ / /;
3117 my $next_decimal_map = hex $next_map;
3119 # If the next map is not next in sequence, it
3120 # shouldn't be combined.
3121 last if $next_decimal_map != $decimal_map + $offset;
3123 my $next_begin = hex $next_hex_begin;
3125 # Likewise, if the next element isn't adjacent to the
3126 # previous one, it shouldn't be combined.
3127 last if $next_begin != $begin + $offset;
3129 my $next_end = (defined $next_hex_end
3130 && $next_hex_end ne "")
3134 # And finally, if the next element is a multi-element
3135 # range, it shouldn't be combined.
3136 last if $next_end != $next_begin;
3138 # Here, we will combine. Loop to see if we should
3139 # combine the next element too.
3145 # Here, 'i' is the element number of the last element to
3146 # be combined, and the range is single-element, or we
3147 # wouldn't be combining. Get it's code point.
3148 my ($hex_end, undef, undef) = split "\t", $ranges[$i];
3149 $list .= "$hex_begin\t$hex_end\t$decimal_map\n";
3152 # Here, no combining done. Just appen the initial
3153 # (and current) values.
3154 $list .= "$hex_begin\t\t$decimal_map\n";
3157 } # End of loop constructing the converted list
3159 # Finish up the data structure for our converted swash
3160 my $type = ($second_try eq 'nfkccf') ? 'ToNFKCCF' : 'ToDm';
3161 $revised_swash{'LIST'} = $list;
3162 $revised_swash{'TYPE'} = $type;
3163 $revised_swash{'SPECIALS'} = $swash->{'SPECIALS'};
3164 $swash = \%revised_swash;
3166 $utf8::SwashInfo{$type}{'missing'} = 0;
3167 $utf8::SwashInfo{$type}{'format'} = 'a';
3171 if ($swash->{'EXTRAS'}) {
3172 carp __PACKAGE__, "::prop_invmap: swash returned for $prop unexpectedly has EXTRAS magic";
3176 # Here, have a valid swash return. Examine it.
3177 my $returned_prop = $swash->{'TYPE'};
3179 # All properties but binary ones should have 'missing' and 'format'
3181 $missing = $utf8::SwashInfo{$returned_prop}{'missing'};
3182 $missing = 'N' unless defined $missing;
3184 $format = $utf8::SwashInfo{$returned_prop}{'format'};
3185 $format = 'b' unless defined $format;
3187 my $requires_adjustment = $format =~ /^a/;
3189 # The LIST input lines look like:
3192 # 0375\t0377\tGreek # [3]
3193 # 037A\t037D\tGreek # [4]
3198 # Convert them to like
3207 # For binary properties, the final non-comment column is absent, and
3208 # assumed to be 'Y'.
3210 foreach my $range (split "\n", $swash->{'LIST'}) {
3211 $range =~ s/ \s* (?: \# .* )? $ //xg; # rmv trailing space, comments
3213 # Find the beginning and end of the range on the line
3214 my ($hex_begin, $hex_end, $map) = split "\t", $range;
3215 my $begin = hex $hex_begin;
3216 my $end = (defined $hex_end && $hex_end ne "")
3220 # Each time through the loop (after the first):
3221 # $invlist[-2] contains the beginning of the previous range processed
3222 # $invlist[-1] contains the end+1 of the previous range processed
3223 # $invmap[-2] contains the value of the previous range processed
3224 # $invmap[-1] contains the default value for missing ranges ($missing)
3226 # Thus, things are set up for the typical case of a new non-adjacent
3227 # range of non-missings to be added. But, if the new range is
3228 # adjacent, it needs to replace the [-1] element; and if the new
3229 # range is a multiple value of the previous one, it needs to be added
3230 # to the [-2] map element.
3232 # The first time through, everything will be empty. If the property
3233 # doesn't have a range that begins at 0, add one that maps to $missing
3237 push @invmap, $missing;
3240 elsif (@invlist > 1 && $invlist[-2] == $begin) {
3242 # Here we handle the case where the input has multiple entries for
3243 # each code point. mktables should have made sure that each such
3244 # range contains only one code point. At this point, $invlist[-1]
3245 # is the $missing that was added at the end of the last loop
3246 # iteration, and [-2] is the last real input code point, and that
3247 # code point is the same as the one we are adding now, making the
3248 # new one a multiple entry. Add it to the existing entry, either
3249 # by pushing it to the existing list of multiple entries, or
3250 # converting the single current entry into a list with both on it.
3251 # This is all we need do for this iteration.
3253 if ($end != $begin) {
3254 croak __PACKAGE__, ":prop_invmap: Multiple maps per code point in '$prop' require single-element ranges: begin=$begin, end=$end, map=$map";
3256 if (! ref $invmap[-2]) {
3257 $invmap[-2] = [ $invmap[-2], $map ];
3260 push @{$invmap[-2]}, $map;
3265 elsif ($invlist[-1] == $begin) {
3267 # If the input isn't in the most compact form, so that there are
3268 # two adjacent ranges that map to the same thing, they should be
3269 # combined (EXCEPT where the arrays require adjustments, in which
3270 # case everything is already set up correctly). This happens in
3271 # our constructed dt mapping, as Element [-2] is the map for the
3272 # latest range so far processed. Just set the beginning point of
3273 # the map to $missing (in invlist[-1]) to 1 beyond where this
3274 # range ends. For example, in
3277 # we have set it up so that it looks like
3281 # We now see that it should be
3284 if (! $requires_adjustment && @invlist > 1 && ( (defined $map)
3285 ? $invmap[-2] eq $map
3286 : $invmap[-2] eq 'Y'))
3288 $invlist[-1] = $end + 1;
3292 # Here, the range started in the previous iteration that maps to
3293 # $missing starts at the same code point as this range. That
3294 # means there is no gap to fill that that range was intended for,
3295 # so we just pop it off the parallel arrays.
3300 # Add the range beginning, and the range's map.
3301 push @invlist, $begin;
3302 if ($returned_prop eq 'ToDm') {
3304 # The decomposition maps are either a line like <hangul syllable>
3305 # which are to be taken as is; or a sequence of code points in hex
3306 # and separated by blanks. Convert them to decimal, and if there
3307 # is more than one, use an anonymous array as the map.
3308 if ($map =~ /^ < /x) {
3312 my @map = split " ", $map;
3314 push @invmap, $map[0];
3317 push @invmap, \@map;
3323 # Otherwise, convert hex formatted list entries to decimal; add a
3324 # 'Y' map for the missing value in binary properties, or
3325 # otherwise, use the input map unchanged.
3326 $map = ($format eq 'x')
3334 # We just started a range. It ends with $end. The gap between it and
3335 # the next element in the list must be filled with a range that maps
3336 # to the default value. If there is no gap, the next iteration will
3337 # pop this, unless there is no next iteration, and we have filled all
3338 # of the Unicode code space, so check for that and skip.
3339 if ($end < $MAX_UNICODE_CODEPOINT) {
3340 push @invlist, $end + 1;
3341 push @invmap, $missing;
3345 # If the property is empty, make all code points use the value for missing
3349 push @invmap, $missing;
3352 # And add in standard element that all non-Unicode code points map to:
3354 push @invlist, $MAX_UNICODE_CODEPOINT + 1;
3355 push @invmap, $missing;
3357 # The second component of the map are those values that require
3358 # non-standard specification, stored in SPECIALS. These override any
3359 # duplicate code points in LIST. If we are using a proxy, we may have
3360 # already set $overrides based on the proxy.
3361 $overrides = $swash->{'SPECIALS'} unless defined $overrides;
3364 # A negative $overrides implies that the SPECIALS should be ignored,
3365 # and a simple 'a' list is the value.
3366 if ($overrides < 0) {
3371 # Currently, all overrides are for properties that normally map to
3372 # single code points, but now some will map to lists of code
3373 # points (but there is an exception case handled below).
3376 # Look through the overrides.
3377 foreach my $cp_maybe_utf8 (keys %$overrides) {
3381 # If the overrides came from SPECIALS, the code point keys are
3383 if ($overrides == $swash->{'SPECIALS'}) {
3384 $cp = unpack("C0U", $cp_maybe_utf8);
3385 @map = unpack "U0U*", $swash->{'SPECIALS'}{$cp_maybe_utf8};
3387 # The empty string will show up unpacked as an empty
3389 $format = 'ale' if @map == 0;
3393 # But if we generated the overrides, we didn't bother to
3394 # pack them, and we, so far, do this only for properties
3395 # that are 'a' ones.
3396 $cp = $cp_maybe_utf8;
3397 @map = hex $overrides->{$cp};
3401 # Find the range that the override applies to.
3402 my $i = _search_invlist(\@invlist, $cp);
3403 if ($cp < $invlist[$i] || $cp >= $invlist[$i + 1]) {
3404 croak __PACKAGE__, "::prop_invmap: wrong_range, cp=$cp; i=$i, current=$invlist[$i]; next=$invlist[$i + 1]"
3407 # And what that range currently maps to
3408 my $cur_map = $invmap[$i];
3410 # If there is a gap between the next range and the code point
3411 # we are overriding, we have to add elements to both arrays to
3412 # fill that gap, using the map that applies to it, which is
3413 # $cur_map, since it is part of the current range.
3414 if ($invlist[$i + 1] > $cp + 1) {
3416 #say "Before splice:";
3417 #say 'i-2=[', $i-2, ']', sprintf("%04X maps to %s", $invlist[$i-2], $invmap[$i-2]) if $i >= 2;
3418 #say 'i-1=[', $i-1, ']', sprintf("%04X maps to %s", $invlist[$i-1], $invmap[$i-1]) if $i >= 1;
3419 #say 'i =[', $i, ']', sprintf("%04X maps to %s", $invlist[$i], $invmap[$i]);
3420 #say 'i+1=[', $i+1, ']', sprintf("%04X maps to %s", $invlist[$i+1], $invmap[$i+1]) if $i < @invlist + 1;
3421 #say 'i+2=[', $i+2, ']', sprintf("%04X maps to %s", $invlist[$i+2], $invmap[$i+2]) if $i < @invlist + 2;
3423 splice @invlist, $i + 1, 0, $cp + 1;
3424 splice @invmap, $i + 1, 0, $cur_map;
3426 #say "After splice:";
3427 #say 'i-2=[', $i-2, ']', sprintf("%04X maps to %s", $invlist[$i-2], $invmap[$i-2]) if $i >= 2;
3428 #say 'i-1=[', $i-1, ']', sprintf("%04X maps to %s", $invlist[$i-1], $invmap[$i-1]) if $i >= 1;
3429 #say 'i =[', $i, ']', sprintf("%04X maps to %s", $invlist[$i], $invmap[$i]);
3430 #say 'i+1=[', $i+1, ']', sprintf("%04X maps to %s", $invlist[$i+1], $invmap[$i+1]) if $i < @invlist + 1;
3431 #say 'i+2=[', $i+2, ']', sprintf("%04X maps to %s", $invlist[$i+2], $invmap[$i+2]) if $i < @invlist + 2;
3434 # If the remaining portion of the range is multiple code
3435 # points (ending with the one we are replacing, guaranteed by
3436 # the earlier splice). We must split it into two
3437 if ($invlist[$i] < $cp) {
3438 $i++; # Compensate for the new element
3441 #say "Before splice:";
3442 #say 'i-2=[', $i-2, ']', sprintf("%04X maps to %s", $invlist[$i-2], $invmap[$i-2]) if $i >= 2;
3443 #say 'i-1=[', $i-1, ']', sprintf("%04X maps to %s", $invlist[$i-1], $invmap[$i-1]) if $i >= 1;
3444 #say 'i =[', $i, ']', sprintf("%04X maps to %s", $invlist[$i], $invmap[$i]);
3445 #say 'i+1=[', $i+1, ']', sprintf("%04X maps to %s", $invlist[$i+1], $invmap[$i+1]) if $i < @invlist + 1;
3446 #say 'i+2=[', $i+2, ']', sprintf("%04X maps to %s", $invlist[$i+2], $invmap[$i+2]) if $i < @invlist + 2;
3448 splice @invlist, $i, 0, $cp;
3449 splice @invmap, $i, 0, 'dummy';
3451 #say "After splice:";
3452 #say 'i-2=[', $i-2, ']', sprintf("%04X maps to %s", $invlist[$i-2], $invmap[$i-2]) if $i >= 2;
3453 #say 'i-1=[', $i-1, ']', sprintf("%04X maps to %s", $invlist[$i-1], $invmap[$i-1]) if $i >= 1;
3454 #say 'i =[', $i, ']', sprintf("%04X maps to %s", $invlist[$i], $invmap[$i]);
3455 #say 'i+1=[', $i+1, ']', sprintf("%04X maps to %s", $invlist[$i+1], $invmap[$i+1]) if $i < @invlist + 1;
3456 #say 'i+2=[', $i+2, ']', sprintf("%04X maps to %s", $invlist[$i+2], $invmap[$i+2]) if $i < @invlist + 2;
3459 # Here, the range we are overriding contains a single code
3460 # point. The result could be the empty string, a single
3461 # value, or a list. If the last case, we use an anonymous
3463 $invmap[$i] = (scalar @map == 0)
3471 elsif ($format eq 'x') {
3473 # All hex-valued properties are really to code points, and have been
3474 # converted to decimal.
3477 elsif ($returned_prop eq 'ToDm') {
3480 elsif ($format eq 'sw') { # blank-separated elements to form a list.
3481 map { $_ = [ split " ", $_ ] if $_ =~ / / } @invmap;
3484 elsif ($returned_prop eq 'ToNameAlias') {
3486 # This property currently doesn't have any lists, but theoretically
3490 elsif ($returned_prop eq 'ToPerlDecimalDigit') {
3493 elsif ($returned_prop eq 'ToNv') {
3495 # The one property that has this format is stored as a delta, so needs
3496 # to indicate that need to add code point to it.
3499 elsif ($format ne 'n' && $format ne 'a') {
3501 # All others are simple scalars
3504 if ($has_multiples && $format !~ /l/) {
3505 croak __PACKAGE__, "::prop_invmap: Wrong format '$format' for prop_invmap('$prop'); should indicate has lists";
3508 return (\@invlist, \@invmap, $format, $missing);
3511 =head2 Unicode::UCD::UnicodeVersion
3513 This returns the version of the Unicode Character Database, in other words, the
3514 version of the Unicode standard the database implements. The version is a
3515 string of numbers delimited by dots (C<'.'>).
3521 sub UnicodeVersion {
3522 unless (defined $UNICODEVERSION) {
3523 openunicode(\$VERSIONFH, "version");
3525 chomp($UNICODEVERSION = <$VERSIONFH>);
3527 croak __PACKAGE__, "::VERSION: strange version '$UNICODEVERSION'"
3528 unless $UNICODEVERSION =~ /^\d+(?:\.\d+)+$/;
3530 $v_unicode_version = pack "C*", split /\./, $UNICODEVERSION;
3531 return $UNICODEVERSION;
3534 =head2 B<Blocks versus Scripts>
3536 The difference between a block and a script is that scripts are closer
3537 to the linguistic notion of a set of code points required to present
3538 languages, while block is more of an artifact of the Unicode code point
3539 numbering and separation into blocks of (mostly) 256 code points.
3541 For example the Latin B<script> is spread over several B<blocks>, such
3542 as C<Basic Latin>, C<Latin 1 Supplement>, C<Latin Extended-A>, and
3543 C<Latin Extended-B>. On the other hand, the Latin script does not
3544 contain all the characters of the C<Basic Latin> block (also known as
3545 ASCII): it includes only the letters, and not, for example, the digits
3548 For blocks see L<http://www.unicode.org/Public/UNIDATA/Blocks.txt>
3550 For scripts see UTR #24: L<http://www.unicode.org/unicode/reports/tr24/>
3552 =head2 B<Matching Scripts and Blocks>
3554 Scripts are matched with the regular-expression construct
3555 C<\p{...}> (e.g. C<\p{Tibetan}> matches characters of the Tibetan script),
3556 while C<\p{Blk=...}> is used for blocks (e.g. C<\p{Blk=Tibetan}> matches
3557 any of the 256 code points in the Tibetan block).
3559 =head2 Old-style versus new-style block names
3561 Unicode publishes the names of blocks in two different styles, though the two
3562 are equivalent under Unicode's loose matching rules.
3564 The original style uses blanks and hyphens in the block names (except for
3565 C<No_Block>), like so:
3567 Miscellaneous Mathematical Symbols-B
3569 The newer style replaces these with underscores, like this:
3571 Miscellaneous_Mathematical_Symbols_B
3573 This newer style is consistent with the values of other Unicode properties.
3574 To preserve backward compatibility, all the functions in Unicode::UCD that
3575 return block names (except one) return the old-style ones. That one function,
3576 L</prop_value_aliases()> can be used to convert from old-style to new-style:
3578 my $new_style = prop_values_aliases("block", $old_style);
3580 Perl also has single-form extensions that refer to blocks, C<In_Cyrillic>,
3581 meaning C<Block=Cyrillic>. These have always been written in the new style.
3583 To convert from new-style to old-style, follow this recipe:
3585 $old_style = charblock((prop_invlist("block=$new_style"))[0]);
3587 (which finds the range of code points in the block using C<prop_invlist>,
3588 gets the lower end of the range (0th element) and then looks up the old name
3589 for its block using C<charblock>).
3591 Note that starting in Unicode 6.1, many of the block names have shorter
3592 synonyms. These are always given in the new style.
3596 Does not yet support EBCDIC platforms.
3600 Jarkko Hietaniemi. Now maintained by perl5 porters.