In perl.git, the branch blead has been updated <https://perl5.git.perl.org/perl.git/commitdiff/008723685161a22b8f080bf12eeccada6d55c162?hp=48988e37c210b95dc6f228038eb4e6e04e60ea20>
- Log ----------------------------------------------------------------- commit 008723685161a22b8f080bf12eeccada6d55c162 Author: Tony Cook <[email protected]> Date: Thu Jun 27 11:48:25 2019 +1000 (perl #134187) how do we know it's a Turkic locale Not by name. ----------------------------------------------------------------------- Summary of changes: pod/perllocale.pod | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/pod/perllocale.pod b/pod/perllocale.pod index 15498d9d5e..905be3c195 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -42,9 +42,13 @@ C<ge>. Starting in v5.26, Perl can handle these reasonably as well, depending on the platform's implementation. However, for earlier releases or for better control, use L<Unicode::Collate>. There are actually two slightly different types of UTF-8 locales: one for Turkic -languages and one for everything else. Starting in Perl v5.30, Perl -seamlessly handles both types; previously only the non-Turkic one was -supported. +languages and one for everything else. + +Starting in Perl v5.30, Perl detects Turkic locales by their +behaviour, and seamlessly handles both types; previously only the +non-Turkic one was supported. The name of the locale is ignored, if +your system has a C<tr_TR.UTF-8> locale and it doesn't behave like a +Turkic locale, perl will treat it like a non-Turkic locale. Perl continues to support the old non UTF-8 locales as well. There are currently no UTF-8 locales for EBCDIC platforms. -- Perl5 Master Repository
