21 Feb 2011 18:28:37 UTC
- Distribution: Pod-Advent
- Module version: 0.24
- Source (raw)
- Browse (raw)
- How to Contribute
- Issues (0)
- Testers (306 / 410 / 1)
- KwaliteeBus factor: 0
- 93.92% Coverage
- License: perl_5
- Perl: v5.6.1
- Activity24 month
- Download (22.95KB)
- MetaCPAN Explorer
- Subscribe to distribution
- This version
- Latest version
- GETTING STARTED
- SUPPORTED POD
- INTERNAL METHODS
- SEE ALSO
- COPYRIGHT & LICENSE
Pod::Advent - POD Formatter for The Perl Advent Calendar
Most likely, the included pod2advent script is all you will need:
pod2advent entry.pod > entry.html
Where the .pod is written using the tags described below. There is also a quick start at http://search.cpan.org/dist/Pod-Advent/ex/getting_started.html.
Using this module directly:
use Pod::Advent; my $pod = shift @ARGV or die "need pod filename"; my $advent = Pod::Advent->new; $advent->parse_file( \*STDIN );
=for advent_year 2009 =for advent_day 32 =for advent_title This is a sample =for advent_author Your Name Here Today's module M<My::Example> is featured on the A<http://example.com|Example Place> web site and is I<very> B<special>. =sourcedcode example.pl
Getting Started: See ex/getting_started.pod and ex/getting_started.html in the distribution for an initial template.
This module provides a POD formatter that is designed to facilitate the create of submissions for The Perl Advent Calendar (http://perladvent.pm.org) by providing authors with simple markup that will be automatically transformed to full-fill the specific formatting guidelines. This makes it easier for authors to provide calendar-ready submissions, and for the editors to save lots of time in editting submissions.
For example, 'file-, module and program names should be wrapped in <tt>,' and 'the code sample should be appended to the document from the results of a perltidy -nnn -html'. Both of these can be trivially accomplished:
This entry is for M<Foo::Bar> and the F<script.pl> program. =sourcedcode mod0.pl
The meta-data of title, date (year & day), and author is now easy to specify as well, and is used to automatically generate the full HTML header (including style) that the calendar entries require before being posted.
See ex/sample.pod and ex/sample.html in the distribution for a fuller example.
General note: HTML code in the pod source will be left alone, so it's effectively passed through. For example, these two lines are identical:
This being POD, the former should be used. Where the html is useful is more for things w/o POD equivalents, like HTML encoding and writing
—, etc or using <BR>'s, <HR>'s, etc, or including images, comments, etc. Be aware that you may need to use the
Z<>pod code to prevent some cases of html use from being interpreted as POD.
This is because POD doesn't support the case of L<http://example.com|Example>, so we introduce this A<> code for that exact purpose -- to generate <a href="URL">TEXT</a> hyperlinks.
A<http://perladvent.pm.org|The Perl Advent Calendar> A<http://perladvent.pm.org>
This is intended for module names. The first instance, it will <tt> it and hyperlink it to a http://search.cpan.org/perldoc? url. All following instances will just <tt> it. Being just for module searches, any other searches can simply use the A<> code instead.
M<Pod::Simple> M<Pod::Simple|PS> A<http://search.cpan.org/search?query=Pod::Simple::Subclassing|Pod::Simple::Subclassing> A<http://search.cpan.org/search?dist=TimeDate|TimeDate>
Insert a superscript footnote reference. See "Footnotes".
Link to a Past Advent Calendar entry. Syntax is <YYYY-D>. YYYY-12-D may also be used, as can <YYYY-D|label> (or both).
Disables spellchecking for the contents, which can be a single word or a phrase (including other pod formatting).
Include the contents of a file formatted with Perl::Tidy (including line numbers).
The line numbers are anchored, so you can refer to them with links:
Specify the title of the submission.
=for advent_title Your Entry Title
Specify the author of the submission.
=for advent_author Your Name Here
Specify the year of the submission (defaults to current year).
=for advent_year 2009
Specify the day of the submission (if currently known).
=for advent_day 99
Display a code snippet (sends it through Perl::Tidy).
=begin code my $foo = Bar->new(); $foo->do_it; =end code
Same as code, but with line numbers.
=begin codeNNN my $foo = Bar->new(); $foo->do_it; =end codeNNN
Display a snippet (e.g. data, output, etc) as <PRE>-formatted text (does not use Perl::Tidy).
=begin pre x,y,z 1,2,3 2,4,9 3,8,27 =end pre
encode_entitiesparameter is specified, then the text will be processed by HTML::Entities
::encode_entities(). This is especially handy/necessary if your text contains <'s or >'s.
Processes POD and wraps it in a <BLOCKQUOTE> section.
=begin quote "Ho-Ho-Ho!" -- S.C. =end quote
Currently behaves exactly the same as quote.
=begin eds The editors requested this directive. -- the management =end eds
Define a footnote's content. See "Footnotes".
A footnote consists of a pair of elements -- one is the "N<>" code and one is the "footnote" target. They are each pass a common identifier for the footnote. This way the author doesn't have to keep track of the numbering.
In this entry we talk about XYZ.N<foo> ... =begin footnote foo The interesting thing about this is B<bar>. =end footnote
Note that the identifier is used for an anchor name (
#footnote_foo), so it must be
The reference will appear as a superscript number. The first instance of "N<>" will be
1, the next
2, and so on.
Normal behavior. Uses <tt>
Uses <tt>. Sends text through Perl::Tidy.
Normal behavior: uses <I>
Normal behavior: uses <B>
Expected behavior (N=1..4): uses <headN>
Constructor. See Pod::Simple.
Overloaded from Pod::Simple -- if input is a filename, will add a link to it at the bottom of the generated HTML.
Also, if input is a filename, it will chdir to the filename's directory before parsing the file. Thus any files referenced (e.g. in a "sourcedcode" tag) are expected to be relative to the .pod file itself.
Accessor/mutator for the stylesheet to use. Defaults to ../style.css
Returns a boolean of whether or not spellchecking will be done (depends on presence of Text::Aspell).
Returns the number of (possible) spelling errors found while parsing.
Returns an array of the (possible) spelling errors found while parsing.
Appends text to the output buffer.
Appends a newline onto the output buffer.
Overload of method to process start of an element.
Overload of method to process end of an element.
Overload of method to process handling of text.
Resets all of the internal (package) variables.
Splits a chunk of text into words and runs it through Text::Aspell.
David Westbrook (CPAN: davidrw),
<dwestbrook at gmail.com>
Please report any bugs or feature requests to
bug-pod-advent at rt.cpan.org, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Pod-Advent. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
You can find documentation for this module with the perldoc command.
You can also look for information at:
RT: CPAN's request tracker
AnnoCPAN: Annotated CPAN documentation
http://perladvent.pm.org - The Perl Advent Calendar
http://perladvent.pm.org/2007/17 - The 2007-12-17 submission that discussed this application of Pod::Simple
Pod::Simple - The base class for Pod::Advent
Pod::Simple::Subclassing - Discusses the techniques that Pod::Advent is based on
perlpod - POD documentation
Perl::Tidy - used for formatting code
Text::Aspell - used for spellchecking
The maintainers of The Perl Advent Calendar at http://perladvent.pm.org.
The 2007 editors, Bill Ricker & Jerrad Pierce, for reviewing and providing feedback on this concept.
Copyright 2007-2011 David Westbrook, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.