X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlpodspec.pod;h=8973a7080cde2c6fc5e8e97390a8b45cb85cc58c;hb=5b7d14ffe3988c7f70fd9dc76be9c44168d17a62;hp=1edd1ba7ade41e16126e7170fefca5553d3ac3dd;hpb=8a3f7e956e4ecb8411420b3ffddb5c454f612bd4;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod index 1edd1ba..8973a70 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" ... "=end I" 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 doesn't begin with a colon. This is discussed in detail in the section L=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, which must be -an encoding name that L recognizes. (Encoding's list +an encoding name that L recognizes. (Encode's list of supported encodings, in L, 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