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)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
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 janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
