justified. Certain interior sequences are recognized both
here and in commands:
- I<text> italicize text, used for emphasis or variables
- B<text> embolden text, used for switches and programs
- S<text> text contains non-breaking spaces
- C<code> literal code
+ I<text> Italicize text, used for emphasis or variables
+ B<text> Embolden text, used for switches and programs
+ S<text> Text contains non-breaking spaces
+ C<code> Render code in a typewriter font, or give some other
+ indication that this represents program text
L<name> A link (cross reference) to name
L<name> manual page
L<name/ident> item in manual page
L<text|name/"sec">
L<text|"sec">
L<text|/"sec">
-
+
F<file> Used for filenames
X<index> An index entry
Z<> A zero-width character
E<html> Some non-numeric HTML entity, such
as E<Agrave>
+Most of the time, you will only need a single set of angle brackets to
+delimit the beginning and end of interior sequences. However, sometimes
+you will want to put a right angle bracket (or greater-than sign '>')
+inside of a sequence. This is particularly common when using a sequence
+to provide a different font-type for a snippet of code. As with all
+things in Perl, there is more than one way to do it. One way is to
+simply escape the closing bracket using an C<E> sequence:
+
+ C<$a E<lt>=E<gt> $b>
+
+This will produce: "C<$a E<lt>=E<gt> $b>"
+
+A more readable, and perhaps more "plain" way is to use an alternate set of
+delimiters that doesn't require a ">" to be escaped. As of perl5.5.660,
+doubled angle brackets ("<<" and ">>") may be used I<if and only if there
+is whitespace immediately following the opening delimiter and immediately
+preceding the closing delimiter!> For example, the following will do the
+trick:
+
+ C<< $a <=> $b >>
+
+In fact, you can use as many repeated angle-brackets as you like so
+long as you have the same number of them in the opening and closing
+delimiters, and make sure that whitespace immediately follows the last
+'<' of the opening delimiter, and immediately precedes the first '>' of
+the closing delimiter. So the following will also work:
+
+ C<<< $a <=> $b >>>
+ C<<<< $a <=> $b >>>>
+
+This is currently supported by pod2text (Pod::Text), pod2man (Pod::Man),
+and any other pod2xxx and Pod::Xxxx translator that uses Pod::Parser
+1.093 or later.
+
+
=head2 The Intent
That's it. The intent is simplicity, not power. I wanted paragraphs
LE<lt>fooE<gt> manpage>, if you want the translated document to read
sensibly.
-If you don need or want total control of the text used for a
-link in the output use the form LE<lt>show this text|fooE<gt>
-instead.
+If you need total control of the text used for a link in the output
+use the form LE<lt>show this text|fooE<gt> instead.
=item *
-The script F<pod/checkpods.PL> in the Perl source distribution
-provides skeletal checking for lines that look empty but aren't
-B<only>, but is there as a placeholder until someone writes
-Pod::Checker. The best way to check your pod is to pass it through
+The B<podchecker> command is provided to check pod syntax
+for errors and warnings. For example, it checks for completely
+blank lines in pod segments and for unknown escape sequences.
+It is still advised to pass it through
one or more translators and proofread the result, or print out the
result and proofread that. Some of the problems found may be bugs in
the translators, which you may or may not wish to work around.
=head1 SEE ALSO
-L<pod2man> and L<perlsyn/"PODs: Embedded Documentation">
+L<pod2man>, L<perlsyn/"PODs: Embedded Documentation">,
+L<podchecker>
=head1 AUTHOR
projects / p5sagit/p5-mst-13.2.git / blobdiff