diff options
| author | Ricardo SIGNES <rjbs@cpan.org> | 2009-05-24 10:11:26 +0200 |
|---|---|---|
| committer | Steffen Mueller <smueller@cpan.org> | 2009-05-24 10:11:26 +0200 |
| commit | 6fbdb1ccd21ee1b840432cead5fae6bef06cf2c8 (patch) | |
| tree | 5ba8065e7534083d38b2a351c9e2e6ab209b181c /pod | |
| parent | e69c155ade49d196491f1d9c96c161b71bb34010 (diff) | |
| download | perl-6fbdb1ccd21ee1b840432cead5fae6bef06cf2c8.tar.gz | |
perlpodspec corrections
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/.perlpodspec.pod.swp | bin | 0 -> 86016 bytes | |||
| -rw-r--r-- | pod/perlpodspec.pod | 8 |
2 files changed, 4 insertions, 4 deletions
diff --git a/pod/.perlpodspec.pod.swp b/pod/.perlpodspec.pod.swp Binary files differnew file mode 100644 index 0000000000..9ab858a9a5 --- /dev/null +++ b/pod/.perlpodspec.pod.swp diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod index 1edd1ba7ad..8973a7080c 100644 --- a/pod/perlpodspec.pod +++ b/pod/perlpodspec.pod @@ -189,7 +189,7 @@ is a verbatim paragraph, because its first line starts with a literal whitespace character (and there's no "=begin"..."=end" region around). The "=begin I<identifier>" ... "=end I<identifier>" commands stop -paragraphs that they surround from being parsed as data or verbatim +paragraphs that they surround from being parsed as ordinary or verbatim paragraphs, if I<identifier> doesn't begin with a colon. This is discussed in detail in the section L</About Data Paragraphs and "=beginE<sol>=end" Regions>. @@ -337,7 +337,7 @@ paragraph. This command, which should occur early in the document (at least before any non-US-ASCII data!), declares that this document is encoded in the encoding I<encodingname>, which must be -an encoding name that L<Encoding> recognizes. (Encoding's list +an encoding name that L<Encode> recognizes. (Encode's list of supported encodings, in L<Encode::Supported>, is useful here.) If the Pod parser cannot decode the declared encoding, it should emit a warning and may abort parsing the document @@ -346,8 +346,8 @@ altogether. A document having more than one "=encoding" line should be considered an error. Pod processors may silently tolerate this if the not-first "=encoding" lines are just duplicates of the -first one (e.g., if there's a "=use utf8" line, and later on -another "=use utf8" line). But Pod processors should complain if +first one (e.g., if there's a "=encoding utf8" line, and later on +another "=encoding utf8" line). But Pod processors should complain if there are contradictory "=encoding" lines in the same document (e.g., if there is a "=encoding utf8" early in the document and "=encoding big5" later). Pod processors that recognize BOMs |