Lines Matching refs:formatting

60 in Pod source, as opposed to "EE<lt>32>", which is a formatting
65 directly formatting it). A B<Pod formatter> (or B<Pod translator>)
132 I<Some> command paragraphs allow formatting codes in their content
139 would to an ordinary paragraph (i.e., formatting codes like
212 is a heading. That text may contain formatting codes. Examples:
380 stipulate, for each additional command, whether formatting
391 formatting codes were referred to as "interior sequences", and
395 There are two syntaxes for formatting codes:
401 A formatting code starts with a capital letter (just US-ASCII [A-Z])
413 A formatting code starts with a capital letter (just US-ASCII [A-Z])
418 formatting code. Examples:
428 do not signify whitespace, are merely part of the formatting codes
442 of nested formatting codes, meaning that the following four example lines are
456 (potentially nested!) formatting codes. Implementors should
487 =item C<ZE<lt>E<gt>> -- a null (zero-effect) formatting code
512 This formatting code is syntactically simple, but semantically
530 If a Pod processor sees any formatting code other than the ones
534 applications to add to the above list of known formatting codes;
540 formatting codes.
552 instead of as equivalent to a "C" formatting code containing
553 only "$foo-", and then a "bar>" outside the "C" formatting code. This
562 that paragraph, the Pod parser must close that formatting code,
581 elements, whereas all Pod formatting codes are like inline-level
714 file, the formatting options in effect, version of Perl used, etc.
742 In paragraphs where formatting codes (like EE<lt>...>, BE<lt>...>)
762 in CE<lt>...> formatting codes, and never I<ever> to text in verbatim
778 formatting systems is seen as eligible for being broken across lines
1024 EE<lt>...> may freely appear in any formatting code (other than
1134 code is the most complex of the Pod formatting codes. The points below
1152 link text. Note that link text may contain formatting.)
1324 In a C<LE<lt>text|...E<gt>> code, text may contain formatting codes
1325 for formatting or for EE<lt>...> escapes, as in:
1333 Note, however, that formatting codes and ZE<lt>>'s can occur in any
1342 Note that Pod authors may use formatting codes inside the "text"
1351 that case, formatters will have to just ignore that formatting.
1549 is semantically ambiguous, in a way that makes formatting decisions
1603 situation, this is preferable to providing formatting cues that may
1641 expand the "EE<lt>/em>" (in the first paragraph) as a formatting
1652 containing formatting codes in ordinary paragraphs). The fact that