Right - some POD formatters use heuristics like /^\d+/ on what follows =item to detect whether this is a numbered list. In the specific case of HTML output, you have 2 choices: 1. always use the full text behind =item and generate a definition list (<dl>,<dt>,<dd>), except with "=item *" which should result in a <ul> 2. or check for "^=item\s+(\d+)\.?$", verify that $1 equals 1,2,3... in sequence, and if so, generate a <ol>. If not, fall back to <dl>. Note that <li> allows a value=... attribute, which is however deprecated. See http://www.w3.org/TR/html4/struct/lists.html#edef-OL
To keep things simple, my personal vote goes to 1. HTH, Marek -----Ursprüngliche Nachricht----- Von: Karl Williamson [mailto:pub...@khwilliamson.com] Gesendet: Sonntag, 26. Juni 2011 05:53 An: pod-people@perl.org Betreff: Z<> in =item In perldiag.pod, there is a line like this =item Z<>500 Server error All the other items form a definition list. My guess is that this is to make sure that the 500 isn't mistaken for a numbered =item in the list. However, with html, anyway, I don't see any difference in the output with and without the Z<>, and podchecker ignores the Z<> and says that the list has mismatched item types. Can someone explain?
