X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlpodspec.pod;h=5e38e2c184c1c6475909a7dc28129a37b5ae96c4;hb=03f3e794d79fbb3655a305de34b922dd4020d2ec;hp=0b60dfd967c4d536ac82551b675a1baf84bed6c5;hpb=75f15e9f00f368613ca4c59248fc2f6b4315911c;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod index 0b60dfd..5e38e2c 100644 --- a/pod/perlpodspec.pod +++ b/pod/perlpodspec.pod @@ -65,7 +65,7 @@ directly formatting it). A B (or B) is a module or program that converts Pod to some other format (HTML, plaintext, TeX, PostScript, RTF). A B might be a formatter or translator, or might be a program that does something -else with the Pod (like wordcounting it, scanning for index points, +else with the Pod (like counting words, scanning for index points, etc.). Pod content is contained in B. A Pod block starts with a @@ -724,7 +724,7 @@ period-space-space or period-newline sequences). Pod parsers should not, by default, try to coerce apostrophe (') and quote (") into smart quotes (little 9's, 66's, 99's, etc), nor try to turn backtick (`) into anything else but a single backtick character -(distinct from an openquote character!), nor "--" into anything but +(distinct from an open quote character!), nor "--" into anything but two minus signs. They I do any of those things to text in CE...> formatting codes, and never I to text in verbatim paragraphs. @@ -959,7 +959,7 @@ for idiosyncratic mappings of Unicode-to-I. =item * -It is up to individual Pod formatter to display good judgment when +It is up to individual Pod formatter to display good judgement when confronted with an unrenderable character (which is distinct from an unknown EEthing> sequence that the parser couldn't resolve to anything, renderable or not). It is good practice to map Latin letters @@ -1130,7 +1130,7 @@ is "perlfunc". In "LE/CAVEATS>", the name is undef.) =item Fourth: The section (AKA "item" in older perlpods), or undef if none. E.g., -in L, "DESCRIPTION" is the section. (Note +in "LEGetopt::Std/DESCRIPTIONE", "DESCRIPTION" is the section. (Note that this is not the same as a manpage section like the "5" in "man 5 crontab". "Section Foo" in the Pod sense means the part of the text that's introduced by the heading or item whose text is "Foo".) @@ -1333,7 +1333,7 @@ given CfooE> code. =item * Previous versions of perlpod allowed for a CsectionE> syntax -(as in "CObject AttributesE>"), which was not easily distinguishable +(as in CObject AttributesE>), which was not easily distinguishable from CnameE> syntax. This syntax is no longer in the specification, and has been replaced by the C"section"E> syntax (where the quotes were formerly optional). Pod parsers should tolerate @@ -1541,7 +1541,7 @@ probably want to format it like so: Ut Enim -But (for the forseeable future), Pod does not provide any way for Pod +But (for the foreseeable future), Pod does not provide any way for Pod authors to distinguish which grouping is meant by the above "=item"-cluster structure. So formatters should format it like so: