Lines Matching refs:literal

58 to literal whitespace.  That is, sequences of whitespace characters
137 whitespace in the form of literal spaces and/or tabs is not
143 literal space or tab, and this paragraph must not be inside a "=begin
146 starts with a literal space or tab, but I<is> inside a
165 "I<identifier>" does I<not> begin with a literal colon (":").  In
188 is a verbatim paragraph, because its first line starts with a literal
477 on literal "|" and/or "/" (in the right order!), and so on,
604 file begins with the two literal byte values 0xFE 0xFF, this is
606 literal byte value 0xFF 0xFE, this is the BOM for little-endian
607 UTF-16.  If the file begins with the three literal byte values
712 text, like "=head1"), literal whitespace should generally be considered
713 "insignificant", in that one literal space has the same meaning as any
714 (nonzero) number of literal spaces, literal newlines, and literal tabs
716 the paragraph).  Pod parsers should compact literal whitespace in each
828 literal byte-sequences for newline (13, 13 10, or 10), and tab (9).
862 but may pass it through as a string consisting of the literal characters
1000 NBSP character (whether as a literal, or as a "EE<lt>160>" or
1391 *".)  Whether "*" is rendered as a literal asterisk, an "o", or as