summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2015-03-19 22:16:15 -0600
committerKarl Williamson <khw@cpan.org>2015-03-19 22:53:01 -0600
commitf74610c0d32655484f95568623dd38d1c519f224 (patch)
tree1a54bad17f31964470eb8f52416ca5a5e6cefc37 /lib
parent28807e1d2b555609915f7f5b3d5e6fe1ee7e9c5d (diff)
downloadperl-f74610c0d32655484f95568623dd38d1c519f224.tar.gz
unicore/README.perl:perl with older Unicode versions
I tried to make the necessary changes for Perl v5.22 to work with old Unicode versions, but ran out of time before the code freeze, with 5.1 being the earliest version. The sticking point there is that the Capital Sharp S, U+1E9E, was defined in that release. Because of its anomalous behavior with the infamous lower case sharp s, U+00DF, there is a bunch of hard-coded references to it in the C code which need to be adjusted to handle it's absence.
Diffstat (limited to 'lib')
-rw-r--r--lib/unicore/README.perl21
1 files changed, 12 insertions, 9 deletions
diff --git a/lib/unicore/README.perl b/lib/unicore/README.perl
index 56d98fa012..ef5fec6295 100644
--- a/lib/unicore/README.perl
+++ b/lib/unicore/README.perl
@@ -1,12 +1,15 @@
-# Perl should compile and reasonably run any version of Unicode. That doesn't
-# mean that the test suite will run without showing errors. A few of the
-# very-Unicode specific test files have been modified to account for different
-# versions, but most have not. For example, some tests use characters that
-# aren't encoded in all Unicode versions; others have hard-coded the General
-# Categories that were correct at the time the test was written. Perl itself
-# will not compile under Unicode releases prior to 3.0 without a simple change to
-# Unicode::Normalize. mktables contains instructions for this, as well as other
-# hints for using older Unicode versions.
+# The goal is for perl to compile and reasonably run any version of Unicode.
+# But in v5.22, the earliest version that this works for is Unicode 5.1.
+# Working reasonably well doesn't mean that the test suite will run without
+# showing errors. You may be able to compile an earlier version, and get
+# things to sort-of work. A few of the very-Unicode specific test files have been
+# modified to account for different versions, but most have not. For example,
+# some tests use characters that aren't encoded in all Unicode versions; others
+# have hard-coded the General Categories for a code point that were correct at
+# the time the test was written. Perl itself will not compile under Unicode
+# releases prior to 3.0 without a simple change to Unicode::Normalize.
+# mktables contains instructions for this, as well as other hints for using
+# older Unicode versions.
# The *.txt files were copied from