(jeffa) Re: Suggest adding code tags if perlish text found in post.

We have been using this disclaimer (located just below the preview/submit buttons) for some time now:

Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible editor intervention).

So there, they have been reminded. Of course, it is up to them to know the reminder is there, and that they should not only read it, but abide by it.

Also, it is this 'editor intervention' that does what your code does. Sure it's not code, but it is robust and also handles title changes, formatting, and typos. Thanks for the code, but i am quite content being a janitor by putting the code away for awhile and picking up my manual mop. Sometimes you just can't escape data entry. :/

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on (jeffa) Re: Suggest adding code tags if perlish text found in post.

Replies are listed 'Best First'.
Re: (jeffa) Re: Suggest adding code tags if perlish text found in post. by EvdB (Deacon) on Jun 12, 2003 at 11:35 UTC
And the janitors do a superb job - no complaints there. The disclaimer is at the bottom and after a few posts most people will have found it and read it. Maybe the above 'feature' should only apply to the first 5 posts or so. I worry about you janitors, I lose sleep, I fear that RSI will creep up on you. Surely if it saves you a few edits a day? --`tidiness is the memory loss of environmental mnemonics`	[reply] [d/l]
(jeffa) 3Re: Suggest adding code tags if perlish text found in post. by jeffa (Bishop) on Jun 12, 2003 at 11:58 UTC
As for saving a few edits ... well, there are two kinds of posts that need to be editted. Easy ones and nightmare ones. Simply slapping code tags around a post is a piece of cake, but those nightmare edits require a whole lot more. Many times i will copy the original post to a gvim window so i can apply many search-n-replace edits to it. You might be surprised at the number of newbie posts that use a plethora of `<br>` tags. I think most of these have been composed in some sort of WYSIWYG editor, because entities such as < and > will be escaped. But right now, the biggest chore i have undertaken as an editor has been title changes. Sure it's easy to change one title, but you have to propagate that down and change every title. I have been meaning to write a tool to handle this, but i fear the testing part. ;) If you really want to help us editors out ... join us! That way you can see what it is all about and write some tools after a couple of days of editting. Even though i hate data entry chores, i haven't had the need to write code instead hit me, it's really not a big deal. :) jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply] [d/l]
Re: (jeffa) Re: Suggest adding code tags if perlish text found in post. by hossman (Prior) on Jun 13, 2003 at 01:02 UTC
That disclaimer only appears below the form for posting new nodes, not wen posting comments. That disclaimer does not appear on the "Preview" page itself ... just the " If something looked unlike you expected it to you might need to check out Writeup Formatting Tips" disclaimer. Personally, I think having the full version of the disclaimer show up on the "Reply" page, and on the "Preview" age (for both top level nodes, and replies) would reduce a lot of this confusion.	[reply]