After all no-one likes to be ignored or even down-voted because of bad formatting. After a while, if nothing happens (probably because the poor monk is busy reading all the messages s/he received!) then you can send the node to the list.

While in principle I agree, people get voted down because they are expected to be at least a little clueful before posting. This means reading the site FAQ, and actually doing a minute bit of reading, before posting.

There are things that could facilitate this. I've been a proponent of being forced to read a page before the first time a monk posts. Even a random 3 question questionaire that must be answered. Something to be try and be sure as possible that they've read the FAQ, and understand the implications of using HTML in posts.

One thing that would help a little is having the code tags prestuffed into the code box on the code page. Or perhaps prestuffing the text boxes with a little bit of help text, i.e. "Have you read the FAQ? Do you know what you're doing? Can you justify this posts existence?"

Of course, the other major issue is that even if they do suddenly realize they're a complete screw-up and want to fix it, if it's a root node, they're hosed.

--Chris

e-mail jcwren

In reply to (jcwren) Re: Messaging authors of baddly formated posts by jcwren
in thread Messaging authors of baddly formated posts by mirod

Title:
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, details, 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, summary, 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.