The warning seems easy enough to implement, but I wonder how many people would actually see it--unless it was presented in an annoying fashion (which could itself be problematic).

I'm not certain it would be easy to devise a workable way to automatically add <READMORE> tags. Sure, you could do it after the first couple of paragraphs, but you might not have a set of paragraphs in a row. Also, there are stylistic differences in posting. For example, I'm pretty careful to close my <P> tags (and I notice that you appear to be pretty careful in your use as well), but not every one does this. For example, a certain monk initially posted his (assumption) nodes initially posted using a fixed type style (e.g. <PRE>, <TT>, and so on). A simple count of paragraphs would not be sufficient for his nodes.

Put another way, the easiest nodes to automatically parse for appropriate <READMORE> tags are probably not the ones that need them.

So I vote for considering the warning, but not the automatic inclusion (unless we can determine a set of simple rules that will catch most of the problems).

In the mean time, you can always /msg the CB (or a janitor) if you see a node that might benefit from a well-placed <READMORE> tag.

--f

In reply to Re: Auto-READMORE feature? by footpad
in thread Auto-READMORE feature? by ChemBoy

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.