In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/8f226aeeda55a51eee04feb4b605d30997d9b592?hp=a2917a7e6fef2fa2027199f241df86589c5a75f6>
- Log ----------------------------------------------------------------- commit 8f226aeeda55a51eee04feb4b605d30997d9b592 Author: David E. Wheeler <[email protected]> Date: Thu Feb 26 22:35:52 2015 -0500 Reinstate reverted "perlpod and spec: s/Latin-1/CP-1252/" This reverts 1a3afb4f8c551b292b5b34f7244ed71f9ac01cfd which reverted e2bb786192adfa315ea974b5f630d7040aa6f6ac, thus reinstating the latter. In thinking about this and discussing it with rjbs, I (khw) realized that this pod text really should go in to v5.22. I made minor clarifications and fixed the author name of the original commit. M pod/perlpod.pod M pod/perlpodspec.pod commit 9d1ee7270f0fadaef492639aab74023e69bd9fad Author: Karl Williamson <[email protected]> Date: Mon Mar 9 10:26:46 2015 -0600 Update David Wheeler's email address M AUTHORS M Porting/checkAUTHORS.pl commit 3ec5bdac85ca04c415755d178d35bed85bbffd49 Author: Karl Williamson <[email protected]> Date: Mon Mar 9 10:06:44 2015 -0600 AUTHORS: Add comment M AUTHORS ----------------------------------------------------------------------- Summary of changes: AUTHORS | 5 ++++- Porting/checkAUTHORS.pl | 4 +++- pod/perlpod.pod | 5 +++-- pod/perlpodspec.pod | 5 +++-- 4 files changed, 13 insertions(+), 6 deletions(-) diff --git a/AUTHORS b/AUTHORS index c1b6ae2..9326d21 100644 --- a/AUTHORS +++ b/AUTHORS @@ -11,6 +11,9 @@ # is strictly forbidden. (Passive distribution with the Perl source # code kit is, of course, allowed.) # +# This should contain the preferred addresses. Alternate addresses are in +# Porting/checkAUTHORS.pl. +# # After editing, please run: make test_porting -- A. C. Yardley <[email protected]> @@ -330,7 +333,7 @@ David Starks-Browning <[email protected]> David Steinbrunner <[email protected]> David Sundstrom <[email protected]> David M. Syzdek <[email protected]> -David Wheeler <[email protected]> +David Wheeler <[email protected]> Davin Milun <[email protected]> Dean Roehrich <[email protected]> Dee Newcum <[email protected]> diff --git a/Porting/checkAUTHORS.pl b/Porting/checkAUTHORS.pl index 8e6a726..fc76d97 100755 --- a/Porting/checkAUTHORS.pl +++ b/Porting/checkAUTHORS.pl @@ -591,7 +591,9 @@ dan\100sidhe.org sugalsd\100lbcc.cc.or.us + sugalskd\100osshe.edu daniel\100bitpusher.com daniel\100biz.bitpusher.com david.dyck\100fluke.com dcd\100tc.fluke.com -david\100kineticode.com david\100wheeler.com +david\100justatheory.com david\100wheeler.net ++ david\100kineticode.com ++ david\100wheeler.com + david\100wheeler.net dennis\100booking.com dennis\100camel.ams6.corp.booking.com + dennis.kaarsemaker\100booking.com diff --git a/pod/perlpod.pod b/pod/perlpod.pod index 12b156b..41053af 100644 --- a/pod/perlpod.pod +++ b/pod/perlpod.pod @@ -286,7 +286,8 @@ users won't need this; but if your encoding isn't US-ASCII, then put a C<=encoding I<encodingname>> command very early in the document so that pod formatters will know how to decode the document. For I<encodingname>, use a name recognized by the L<Encode::Supported> -module. Some pod formatters may try to guess between a Latin-1 versus +module. Some pod formatters may try to guess between a Latin-1 or +CP-1252 versus UTF-8 encoding, but they may guess wrong. It's best to be explicit if you use anything besides strict ASCII. Examples: @@ -505,7 +506,7 @@ in decimal, as in C<EE<lt>181E<gt>>. Note that older Pod formatters might not recognize octal or hex numeric escapes, and that many formatters cannot reliably render characters above 255. (Some formatters may even have -to use compromised renderings of Latin-1 characters, like +to use compromised renderings of Latin-1/CP-1252 characters, like rendering C<EE<lt>eacuteE<gt>> as just a plain "e".) =back diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod index f2af63e..251a55c 100644 --- a/pod/perlpodspec.pod +++ b/pod/perlpodspec.pod @@ -607,7 +607,8 @@ as signaling that the file is Unicode encoded as in UTF-16 (whether big-endian or little-endian) or UTF-8, Pod parsers should do the same. Otherwise, the character encoding should be understood as being UTF-8 if the first highbit byte sequence in the file seems -valid as a UTF-8 sequence, or otherwise as Latin-1. +valid as a UTF-8 sequence, or otherwise as CP-1252 (earlier versions of +this specification used Latin-1 instead of CP-1252). Future versions of this specification may specify how Pod can accept other encodings. Presumably treatment of other @@ -641,7 +642,7 @@ I<and> whether the next byte is in the range 0x80 - 0xBF. If so, the parser may conclude that this file is in UTF-8, and all highbit sequences in the file should be assumed to be UTF-8. Otherwise the parser should treat the file as being -in Latin-1. (A better check is to pass a copy of the sequence to +in CP-1252. (A better check is to pass a copy of the sequence to L<utf8::decode()|utf8> which performs a full validity check on the sequence and returns TRUE if it is valid UTF-8, FALSE otherwise. This function is always pre-loaded, is fast because it is written in C, and -- Perl5 Master Repository
