In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/88d9f320ca53d033aadb3c8de37636a402a5ae5d?hp=c58bf3ba21f311e34c38379fadc8097eb7bf6600>
- Log ----------------------------------------------------------------- commit 88d9f320ca53d033aadb3c8de37636a402a5ae5d Author: Karl Williamson <[email protected]> Date: Sun Mar 15 22:25:12 2015 -0600 perlunicode: Nit, for EBCDIC M pod/perlunicode.pod commit bd940430ebc41b7b346cc761cc46be9674f34111 Author: Karl Williamson <[email protected]> Date: Sun Mar 15 21:49:55 2015 -0600 perlpodspec: Generalize for EBCDIC M pod/perlpodspec.pod ----------------------------------------------------------------------- Summary of changes: pod/perlpodspec.pod | 24 +++++++++++++----------- pod/perlunicode.pod | 2 +- 2 files changed, 14 insertions(+), 12 deletions(-) diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod index 251a55c..c3d172f 100644 --- a/pod/perlpodspec.pod +++ b/pod/perlpodspec.pod @@ -842,17 +842,19 @@ Pod::Parser, comes with modern versions of Perl. Characters in Pod documents may be conveyed either as literals, or by number in EE<lt>n> codes, or by an equivalent mnemonic, as in -EE<lt>eacute> which is exactly equivalent to EE<lt>233>. - -Characters in the range 32-126 refer to those well known US-ASCII -characters (also defined there by Unicode, with the same meaning), -which all Pod formatters must render faithfully. Characters -in the ranges 0-31 and 127-159 should not be used (neither as -literals, nor as EE<lt>number> codes), except for the -literal byte-sequences for newline (13, 13 10, or 10), and tab (9). - -Characters in the range 160-255 refer to Latin-1 characters (also -defined there by Unicode, with the same meaning). Characters above +EE<lt>eacute> which is exactly equivalent to EE<lt>233>. The numbers +are the Latin1/Unicode values, even on EBCDIC platforms. + +When referring to characters by using a EE<lt>n> numeric code, numbers +in the range 32-126 refer to those well known US-ASCII characters (also +defined there by Unicode, with the same meaning), which all Pod +formatters must render faithfully. Numbers in the ranges 0-31 and +127-159 should not be used (neither as literals, nor as EE<lt>number> +codes), except for the literal byte-sequences for newline (13, 13 10, or +10), and tab (9). + +Numbers in the range 160-255 refer to Latin-1 characters (also +defined there by Unicode, with the same meaning). Numbers above 255 should be understood to refer to Unicode characters. =item * diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index e1e4cdb..869d9a5 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -1710,7 +1710,7 @@ a valid UTF-8 character. C<UTF8SKIP(buf)> will return the number of bytes in the UTF-8 encoded character in the buffer. C<UNISKIP(chr)> will return the number of bytes -required to UTF-8-encode the Unicode character code point. C<UTF8SKIP()> +required to UTF-8-encode the code point. C<UTF8SKIP()> is useful for example for iterating over the characters of a UTF-8 encoded buffer; C<UNISKIP()> is useful, for example, in computing the size required for a UTF-8 encoded buffer. -- Perl5 Master Repository
