Lines Matching refs:EE

60 in Pod source, as opposed to "EE<lt>32>", which is a formatting
503 I<before> EE<lt>...> codes are resolved.
505 =item C<EE<lt>escapeE<gt>> -- a character escape
723 EE<lt>zslig>!") to STDERR (whether through printing to STDERR, or
742 In paragraphs where formatting codes (like EE<lt>...>, BE<lt>...>)
804 an approximate line number ("Nested EE<lt>>'s in Paragraph #52, near
806 number ("Nested EE<lt>>'s in Paragraph #52 of Thing/Foo.pm!").  Where
808 accompanied by an excerpt from the paragraph ("Nested EE<lt>>'s in
853 number in EE<lt>n> codes, or by an equivalent mnemonic, as in
854 EE<lt>eacute> which is exactly equivalent to EE<lt>233>.  The numbers
857 When referring to characters by using a EE<lt>n> numeric code, numbers
860 formatters must render faithfully.  Characters whose EE<lt>E<gt> numbers
863 nor as EE<lt>number> codes), except for the literal byte-sequences for
879 Besides the well-known "EE<lt>lt>" and "EE<lt>gt>" codes for
880 less-than and greater-than, Pod parsers must understand "EE<lt>sol>"
881 for "/" (solidus, slash), and "EE<lt>verbar>" for "|" (vertical bar,
882 pipe).  Pod parsers should also understand "EE<lt>lchevron>" and
883 "EE<lt>rchevron>" as legacy codes for characters 171 and 187, i.e.,
887 are now preferably expressed with the HTML/XHTML codes "EE<lt>laquo>"
888 and "EE<lt>raquo>".)
892 Pod parsers should understand all "EE<lt>html>" codes as defined
896 when faced with some unknown "EE<lt>I<identifier>>" code,
901 "EE<lt>I<identifier>>" codes by firing an event especially
903 document tree.  Such "EE<lt>I<identifier>>" may have special meaning
909 Pod parsers must also support the XHTML codes "EE<lt>quot>" for
910 character 34 (doublequote, "), "EE<lt>amp>" for character 38
911 (ampersand, &), and "EE<lt>apos>" for character 39 (apostrophe, ').
915 Note that in all cases of "EE<lt>whateverE<gt>", I<whatever> (whether
918 C<m/\A\w+\z/>.  So S<"EE<lt> 0 1 2 3 E<gt>"> is invalid, because
925 treat S<"EE<lt> 0 1 2 3 E<gt>"> or "EE<lt>e-acute>" as I<syntactically>
928 (but theoretically valid) htmlname, as in "EE<lt>qacute>"
934 Note that EE<lt>number> I<must not> be interpreted as simply
944 a EE<lt>...> sequence) is to be conveyed as "e\\*'".
1000 unknown EE<lt>thing> sequence that the parser couldn't resolve to
1002 with diacritics (like "EE<lt>eacute>"/"EE<lt>233>") to the corresponding
1006 (as from EE<lt>233> to "e"), Pod formatters may use the
1024 EE<lt>...> may freely appear in any formatting code (other than
1025 in another EE<lt>...> or in an ZE<lt>>).  That is, "XE<lt>The
1026 EE<lt>euro>1,000,000 Solution>" is valid, as is "LE<lt>The
1027 EE<lt>euro>1,000,000 Solution|Million::Euros>".
1036 NBSP character (whether as a literal, or as a "EE<lt>160>" or
1037 "EE<lt>nbsp>" code); and Pod can contain "SE<lt>foo
1081 i.e. C<EE<lt>173E<gt>> = C<EE<lt>0xADE<gt>> =
1082 C<EE<lt>shyE<gt>>).  This character expresses an optional hyphenation
1099 (and if it doesn't hyphenate it, then the C<EE<lt>shyE<gt>> doesn't
1102 so only at the points where there is a C<EE<lt>shyE<gt>> code.
1190 "|", "/", etc, and before EE<lt>...> codes are expanded.
1325 for formatting or for EE<lt>...> escapes, as in:
1330 C<EE<lt>...E<gt>> and C<ZE<lt>E<gt>> codes may occur.  That is,
1641 expand the "EE<lt>/em>" (in the first paragraph) as a formatting
1642 code, just like "EE<lt>lt>" or "EE<lt>eacute>".  But since this