Re: How 'bout a <pre> (and other stuff) warning?

I completely agree, except you are preaching to the choir. The preview already includes the text:

If something looked unlike you expected it to you might need to check out Writeup Formatting Tips

and:

Are you posting in the right place? Check out Where should I post X? to know for sure.

Posts may use any of the Perl Monks Approved HTML tags: a, 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.

Snippets of code or other preformatted text should be wrapped in <code> tags, not <pre> tags. In fact, <pre> tags should almost never be used.

Outside of code tags, you may need to use entities for some characters: "&" is "&", "<" is "<", ">" is ">", "[" is "[", "]" is "]"

See Writeup Formatting Tips and other pages linked from there for more info.

which seems to be completely ignored by many who post, especially those who are fairly new to PerlMonks. Why should some additional text make any difference?

DWIM is Perl's answer to Gödel

Comment on Re: How 'bout a <pre> (and other stuff) warning?

Replies are listed 'Best First'.

Re^2: How 'bout a <pre> (and other stuff) warning?
by grep (Monsignor) on Oct 19, 2006 at 22:23 UTC

bold red

something like:
Did you really mean to use <pre> tags?
Please use a descriptive title (avoid 1 word titles or module names as the entire title)

grep

One dead unjugged rabbit fish later

[reply]
[d/l]

Re^3: How 'bout a <pre> (and other stuff) warning?

by TGI (Parson) on Oct 22, 2006 at 03:07 UTC

Ooh, how about blinking text? ;)

Seriously, the bold red works best when used sparingly. For example the words "bold red" in your post stand out and grab my attention, but the sentences you wrote just sort of disappear on my screen.

How about something like:

Warning:

Your node may have some problems -

Please limit the use of <pre> tags. When possible, use <code> tags instead.
Please use a descriptive title (avoid 1 word titles or module names as the entire title)

TGI says moo

[reply]
[d/l]
[select]

Re^4: How 'bout a <pre> (and other stuff) warning?

by grep (Monsignor) on Oct 22, 2006 at 04:05 UTC

but

OMG PLEASE PLEASE CAN WE USE THE <MARQUEE> TAG!!!!!!!! :^>~

grep

One dead unjugged rabbit fish later

[reply]

Re^2: How 'bout a <pre> (and other stuff) warning?
by blazar (Canon) on Oct 20, 2006 at 08:53 UTC

I completely agree, except you are preaching to the choir. The preview already includes the text:
[snip]

That's what I meant with "which is not really an excuse for not reading that they're discouraged anyway" in my reply to this comment of yours.

OTOH with "visually distinctive" I meant something that should really catch the eye, e.g. like someone else said, bold red, at least in default themes - if someone changes that, he will be on his own. But then again chances are he/she will already know what he/she is doing. And of course all this wouldn't be in substitution of the current warnings and reminders, but in complement to them: of course one may not want to see such visually "invasive" warnings under normal circumstances.

[reply]
[d/l]