You say this code generates "a
host of interesting errors when run through a validator"
followed by "comments based on sample output available at
Had you validated the output of the script you would have
seen that it didn't generate the sample, a much earlier
revision did. I neglected to update the sample because it
wasn't as important to me as the code. After all it was
only a sample, nothing i expected anyone to bother
validating and criticizing on PERLmonks!
Next time please run the perl code before running off to
the HTML validator.
And if you're really worried about a 5 space alignment
variation in lynx (how nit picky can you get?) try looking
at the source code to find out why it does that, and fix
your copy, if you actually use lynx and can't live with it.
I gave you the code for free, it's the least you could do.
Update: I changed this node when i
realized how ridiculous the criticism was. Apologies to
davorg for eliminating the context of his reply.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||