Lines Matching full:parsers

41 Pod parsers should understand it to mean any of CR (ASCII 13), LF
52 (I<Note:> Many older Pod parsers did not accept a line consisting of
173 parsers need to be able to call an event for it, or store it in some
219 supported on all Pod parsers. L<Pod::Simple> 3.41 was released on October
221 L<Pod::Simple>-based Pod parsers.
392 this term may still be found in the documentation for Pod parsers,
558 Compliant parsers must not treat "->" as special.
604 Pod parsers must recognize I<all> of the three well-known newline
609 Pod parsers should accept input lines that are of any length.
615 big-endian or little-endian) or UTF-8, Pod parsers should do the
722 Pod parsers I<may> emit warnings or error messages ("Unknown E code
734 In cases of exceptionally aberrant documents, Pod parsers may abort the
749 the paragraph).  Pod parsers should compact literal whitespace in each
757 Pod parsers should not, by default, try to coerce apostrophe (') and
788 Pod parsers should, by default, expand tabs in verbatim paragraphs as
790 processor.  Parsers may also allow an option for overriding this.
794 Pod parsers should, by default, remove newlines from the end of
803 Pod parsers, when reporting errors, should make some effort to report
814 Pod parsers, when processing a series of verbatim paragraphs one
825 processor.  Parsers may also allow an option for overriding this.
828 parsers, it is straightforward for parsers that return parse trees.
837 Pod parsers must treat a line with only spaces and/or tabs on it as a
838 "blank line" such as separates paragraphs.  (Some older parsers
880 less-than and greater-than, Pod parsers must understand "EE<lt>sol>"
882 pipe).  Pod parsers should also understand "EE<lt>lchevron>" and
892 Pod parsers should understand all "EE<lt>html>" codes as defined
894 C<www.W3.org>.  Pod parsers must understand at least the entities
895 that define characters in the range 160-255 (Latin-1).  Pod parsers,
899 E, less-than, I<identifier>, greater-than.  Or Pod parsers may offer the
909 Pod parsers must also support the XHTML codes "EE<lt>quot>" for
929 [sic].  However, Pod parsers are not required to make this
1040 parsers should consider supporting the optional parsing of "SE<lt>foo
1142 In parsing an LE<lt>...> code, Pod parsers must distinguish at least
1176 Pod parsers may also note additional attributes including:
1376 formerly optional).  Pod parsers should tolerate the C<LE<lt>"section"E<gt>>
1628 meaning as one, and Pod parsers may parse it as one.)
1820 Pod parsers, when processing a series of data paragraphs one