In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/1a3afb4f8c551b292b5b34f7244ed71f9ac01cfd?hp=e2bb786192adfa315ea974b5f630d7040aa6f6ac>
- Log ----------------------------------------------------------------- commit 1a3afb4f8c551b292b5b34f7244ed71f9ac01cfd Author: Karl Williamson <[email protected]> Date: Fri Feb 27 11:57:03 2015 -0700 Revert "perlpod and spec: s/Latin-1/CP-1252/" This reverts commit e2bb786192adfa315ea974b5f630d7040aa6f6ac. These doc changes apply to Pod::Simple version 3.30, which, alas, was created too late to be included in Perl v5.22, so this change to the docs in blead is premature. I plan to apply the patch in 5.23. ----------------------------------------------------------------------- Summary of changes: pod/perlpod.pod | 6 +++--- pod/perlpodspec.pod | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/pod/perlpod.pod b/pod/perlpod.pod index d675de7..12b156b 100644 --- a/pod/perlpod.pod +++ b/pod/perlpod.pod @@ -286,7 +286,7 @@ 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 CP-1252 versus +module. Some pod formatters may try to guess between a Latin-1 versus UTF-8 encoding, but they may guess wrong. It's best to be explicit if you use anything besides strict ASCII. Examples: @@ -496,7 +496,7 @@ e with an acute (/-shaped) accent. C<EE<lt>numberE<gt>> -The ASCII/CP-1252/Unicode character with that number. A +The ASCII/Latin-1/Unicode character with that number. A leading "0x" means that I<number> is hex, as in C<EE<lt>0x201EE<gt>>. A leading "0" means that I<number> is octal, as in C<EE<lt>075E<gt>>. Otherwise I<number> is interpreted as being @@ -505,7 +505,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 CP-1252 characters, like +to use compromised renderings of Latin-1 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 a2a4f8f..f2af63e 100644 --- a/pod/perlpodspec.pod +++ b/pod/perlpodspec.pod @@ -607,7 +607,7 @@ 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 CP-1252. +valid as a UTF-8 sequence, or otherwise as Latin-1. Future versions of this specification may specify how Pod can accept other encodings. Presumably treatment of other @@ -641,7 +641,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 CP-1252. (A better check is to pass a copy of the sequence to +in Latin-1. (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
