Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

 "Ignoring the bad markup isn't a complete solution. Janitors still are likely to be asked to fix it."

I wasn't offering it as a complete solution. I don't feel there is a complete solution and, as I've said, don't believe it would be worth the work for essentially a handful of weekly problematic posts. As for Janitors, that's part of their purpose:

From What do Janitors do?:

What about crappily formatted postings?

...On the one hand, it could be left to the author to fix, and a /msg to the author is therefore the best course of action.

On the other hand, a janitor may feel that cleaning up a poorly formatted node, as a service to those who have to read such a node, and as a way of illustrating how nodes ought to be formatted, is reasonable.

And if the node's author is Anonymous Monk, it can't be fixed by the author, so if it's going to be fixed at all, it's got to be done by janitors. ...

 "As to posting plain text, I've never encountered difficulty including some... as in the case of the first (untagged) para in this node, nor in the case of a single sentence of narrative reply. (alternating paras with and without tags maintains readable rendering)"

What I posted was all plain text and got the following under the Title form field:

Use: <p> text here (a paragraph) </p> and: <code> code here </code> to format your post; it's "PerlMonks-approved HTML":

That was trying to post from my phone in all plain text. What you posted above is readable so I don't see a problem. Unless it brakes the page, I don't think we want to start parsing for totally valid html. That's not even a goal covered in the Janitor's doc and, as it suggests there, a private /msg to the OP can help remedy the situation. If it is a recurring problem from a specific poster suggest they change their setting to show markup errors. This is functionality which already exists but doesn't block a post from being submitted.

"...the adversities born of well-placed thoughts should be considered mercies rather than misfortunes." Don Quixote

In reply to Re^7: RFC - shortform posting guidance for newcomers by luis.roca
in thread RFC - shortform posting guidance for newcomers by ww

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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:
    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
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others lurking in the Monastery: (9)
    As of 2021-01-15 20:58 GMT
    Find Nodes?
      Voting Booth?