RHEL 7.6.0 PC (i440FX + PIIX, 1996)
%
355ſ c %
404 Not Found
Not Found
The requested URL was not found on this server.
Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.
0 'lah 8]1h
d
_ ub
&=LV[( ? '# !!!!!!! INTERNAL PERL USE ONLY !!!!!!!
# This helper module is for internal use by core Perl only. This module is
# subject to change or removal at any time without notice. Don't use it
# directly. Use the public module instead.
package _charnames;
use strict;
use warnings;
use File::Spec;
our $VERSION = '1.31';
use unicore::Name; # mktables-generated algorithmically-defined names
use bytes (); # for $bytes::hint_bits
use re "/aa"; # Everything in here should be ASCII
$Carp::Internal{ (__PACKAGE__) } = 1;
# Translate between Unicode character names and their code points. This is a
# submodule of package , used to allow \N{...} to be autoloaded,
# but it was decided not to autoload the various functions in charnames; the
# splitting allows this behavior.
#
# The official names with their code points are stored in a table in
# lib/unicore/Name.pl which is read in as a large string (almost 3/4 Mb in
# Unicode 6.0). Each code point/name combination is separated by a \n in the
# string. (Some of the CJK and the Hangul syllable names are determined
# instead algorithmically via subroutines stored instead in
# lib/unicore/Name.pm). Because of the large size of this table, it isn't
# converted into hashes for faster lookup.
#
# But, user defined aliases are stored in their own hashes, as are Perl
# extensions to the official names. These are checked first before looking at
# the official table.
#
# Basically, the table is grepped for the input code point (viacode()) or
# name (the other functions), and the corresponding value on the same line is
# returned. The grepping is done by turning the input into a regular
# expression. Thus, the same table does double duty, used by both name and
# code point lookup. (If we were to have hashes, we would need two, one for
# each lookup direction.)
#
# For loose name matching, the logical thing would be to have a table
# with all the ignorable characters squeezed out, and then grep it with the
# similiarly-squeezed input name. (And this is in fact how the lookups are
# done with the small Perl extension hashes.) But since we need to be able to
# go from code point to official name, the original table would still need to
# exist. Due to the large size of the table, it was decided to not read
# another very large string into memory for a second table. Instead, the
# regular expression of the input name is modified to have optional spaces and
# dashes between characters. For example, in strict matching, the regular
# expression would be:
# qr/\tDIGIT ONE$/m
# Under loose matching, the blank would be squeezed out, and the re would be:
# qr/\tD[- ]?I[- ]?G[- ]?I[- ]?T[- ]?O[- ]?N[- ]?E$/m
# which matches a blank or dash between any characters in the official table.
#
# This is also how script lookup is done. Basically the re looks like
# qr/ (?:LATIN|GREEK|CYRILLIC) (?:SMALL )?LETTER $name/
# where $name is the loose or strict regex for the remainder of the name.
# The hashes are stored as utf8 strings. This makes it easier to deal with
# sequences. I (khw) also tried making Name.pl utf8, but it slowed things
# down by a factor of 7. I then tried making Name.pl store the ut8
# equivalents but not calling them utf8. That led to similar speed as leaving
# it alone, but since that is harder for a human to parse, I left it as-is.
my %system_aliases = (
'SINGLE-SHIFT 2' => pack("U", 0x8E),
'SINGLE-SHIFT 3' => pack("U", 0x8F),
'PRIVATE USE 1' => pack("U", 0x91),
'PRIVATE USE 2'