Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Pod-Simple CPAN distribution.

Report information
The Basics
Id: 59555
Status: rejected
Priority: 0/
Queue: Pod-Simple

People
Owner: Nobody in particular
Requestors: david [...] kineticode.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



CC: pod-people [...] perl.org
Subject: `=item 1. Text` Doesn't Produce Ordered List Item
Date: Mon, 19 Jul 2010 21:55:33 -0700
To: bug-pod-simple [...] rt.cpan.org
From: David E. Wheeler <david [...] kineticode.com>
This Pod: =over =item 1 Item 1 =item 2 Item 2 =back Yields this output from Pod::Simple: % perldoc -MPod::Simple::XHTML list.pod <html> <head> <title></title> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> </head> <body> <h1 id="Title">Title</h1> <dl> <dt>1 Item 1</dt> <dd> </dd> <dt>2 Item 2</dt> <dd> </dd> </dl> </body> </html> A definition list isn't what I would expect. If I use an asterisk instead of numbers (e.g., `=item * some text`), I'd get an unordered list. So why shouldn't `=item 1 some text` give me an ordered list? FWIW, pod2html does. So should `item 1 some text` be an ordered list item, as suggested output by pod2html, or a definition list as currently implemented by Pod::Simple? I think the former. Thoughts? Thanks, David
I'd expect an unordered list; the current output is also invalid HTML5. It gets more complex however, when you consider cases such as this: =over =item 1 Item 1 =item 2 Item 2 =item 3 Item 3 Some text for Item 3 =item 4 Item 4 =back -- Cheers, ZZ [ https://metacpan.org/author/ZOFFIX ]
Subject: Re: [rt.cpan.org #59555] `=item 1. Text` Doesn't Produce Ordered List Item
Date: Mon, 9 Mar 2015 17:13:06 -0700
To: bug-Pod-Simple [...] rt.cpan.org
From: "David E. Wheeler" <david [...] kineticode.com>
perlpodspec says: Show quoted text
> * An "=over" ... "=back" region containing only > "m/\A=item\s+\d+\.?\s*\z/" paragraphs, each one (or each group of > them) followed by some number of ordinary/verbatim paragraphs, > other nested "=over" ... "=back" regions, "=for..." paragraphs, > and/or "=begin"..."=end" codes. Note that the numbers must start > at 1 in each section, and must proceed in order and without > skipping numbers.
Ordered list `=item`s cannot have anything other than digits optionally followed by a period. As for unordered lists match `m/\A=item\s+\d+\.?\s*\z/`, so it wouldn’t be that, either. The current output is correct. Best, David