Patch for 5.30 perldelta for Unicode versions

--------------F35920A5182AC2E14B641517
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


--------------F35920A5182AC2E14B641517
Content-Type: text/x-patch;
 name="0097-Fix-up-perldelta-in-regard-to-Unicode-versions.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename*0="0097-Fix-up-perldelta-in-regard-to-Unicode-versions.patch"

From 09c5ea194f4528c45f7eee1d4e872f38c359adb9 Mon Sep 17 00:00:00 2001
From: Karl Williamson <khw@cpan.org>
Date: Mon, 13 May 2019 10:11:06 -0600
Subject: [PATCH 97/97] Fix up perldelta in regard to Unicode versions

---
 pod/perldelta.pod | 37 +++++++++++--------------------------
 1 file changed, 11 insertions(+), 26 deletions(-)

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index d01f69684b..683fe2ed88 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -18,9 +18,18 @@ sv_utf8_(downgrade|decode) are no longer marked as experimental [perl #133788]
 
 =head1 Core Enhancements
 
-=head2 Unicode 11.0 is supported
+=head2 Unicode 12.1 is supported
 
-For details, see L<https://www.unicode.org/versions/Unicode11.0.0/>.
+Because of a change in Unicode release cycles, Perl jumps from Unicode
+10.0 in Perl 5.28 to Unicode 12.1 in Perl 5.30.
+
+For details on the Unicode changes, see
+L<https://www.unicode.org/versions/Unicode11.0.0/> for 11.0;
+L<https://www.unicode.org/versions/Unicode12.0.0/> for 12.0;
+and
+L<https://www.unicode.org/versions/Unicode12.1.0/> for 12.1.
+(Unicode 12.1 differs from 12.0 only in the addition of a single
+character, that for the new Japanese era name.)
 
 The Word_Break property, as in past Perl releases, remains tailored to
 behave more in line with expectations of Perl users.  This means that
@@ -31,19 +40,6 @@ as causing breaks: TAB, NO BREAK SPACE, and FIGURE SPACE (U+2007).  We
 have decided to continue to use the previous Perl tailoring with regards
 to these.
 
-As of July 2018, another aspect of Unicode 11.0 is causing problems, and
-that is the changing the Georgian script to have both lower and
-uppercase letters.  It turns out that many devices do not have fonts
-installed that can display the new uppercase letters, and people using
-Georgian are finding their text more or less illegible.  It is being
-suggested that implementations delay their adoption of this portion of
-11.0.
-
-But since the next stable release of Perl is almost a year away, this
-aspect of 11.0 is being left in, with the option to back it out if
-things haven't improved by that time, or if we get too many complaints
-about the development release being unusable for Georgian users.
-
 =head2 The upper limit C<"n"> specifiable in a regular expression
 quantifier of the form C<"{m,n}"> has been doubled to 65534
 
@@ -51,17 +47,6 @@ The meaning of an unbounded upper quantifier C<"{m,}"> remains unchanged.
 It matches 2**31 - 1 times on most platforms, and more on ones where a C
 language short variable is more than 4 bytes long.
 
-=head2 Unicode 12.0 is supported
-
-For details, see L<https://www.unicode.org/versions/Unicode12.0.0/>.
-
-Because of a change in Unicode release cycles, Perl jumps from Unicode
-10.0 in Perl 5.28 to Unicode 12.0 in Perl 5.30.
-
-=head2 Perl now supports draft Unicode 12.1
-
-Unicode 12.1 differs from 12.0 only in the addition of a single
-character, that for the new Japanese era name.
 
 =head2 Wildcards in Unicode property value specifications are now
 partially supported
-- 
2.17.1


--------------F35920A5182AC2E14B641517--
0
public
5/13/2019 4:15:20 PM
perl.perl5.porters 47705 articles. 1 followers. Follow

2 Replies
34 Views

Similar Articles

[PageSpeed] 35

*thumbs up*

On Mon, May 13, 2019 at 9:15 AM Karl Williamson <public@khwilliamson.com> wrote:
0
perl
5/13/2019 4:32:04 PM
Applied!


On 5/13/19 7:15 PM, Karl Williamson wrote:
0
xsawyerx
5/15/2019 4:30:27 AM
Reply: