Front page | perl.perl5.porters |
Postings from November 2014
> commit 8c6180a91de91a1194f427fc639694f43a903a78 > Author: Karl Williamson <khw@cpan.org> > Date: Wed Nov 12 10:32:47 2014 -0700 > > Reinstate "Raise warnings for poorly supported locales" > > This reverts commit 1244bd171b8d1fd4b6179e537f7b95c38bd8f099, > thus reinstating commit 3d3a881c1b0eb9c855d257a2eea1f72666e30fbc. > > M locale.c > M pod/perldelta.pod > M pod/perldiag.pod > M pod/perllocale.pod As a result of this commit there are now dozens of new warnings in the test suite on both OS X and VMS. Haven't tried elsewhere yet. Here's a snippet from OS X: $ ./perl -I../lib re/charset.t Locale 'ja_JP.eucJP' may not work well. Some characters in it are not recognized by Perl. Locale 'ja_JP.SJIS' may not work well. Some characters in it are not recognized by Perl. Locale 'ko_KR.CP949' may not work well. Some characters in it are not recognized by Perl. Locale 'ko_KR.eucKR' may not work well. Some characters in it are not recognized by Perl. .... On VMS, tests emitting these warnings now fail with "unexpected output at test 0". The tests affected are t/run/locale.t, t/re/charset.t, t/re/fold_grind.t, and t/uni/fold.t. As far as I can tell, these are all tests where the locale system is queried to get a complete list of locales that are then iterated over. So what's the plan? Do these tests all need to be modified to suppress these warnings? Or capture and present them in a TAP-friendly comment format?