> Excellent, Chris, stated in a good way that notes the key points in
> order. The number one point about press IS the endpress command. It
> even is worth noting that it IS one word, endpress, not 'end press'
> as you do, as point number two. Very cool nuanced training document,
> all GMs should use this, I think.
Thank you. While I *think* that nJudge 1.7.6 will parse "end press" as
"endpress", the most active nJudge (USOS) was running 1.5.0 last I
checked so I think it's still im****tant to use it as one word.
Interestingly enough, I have more trouble with trailing spaces than
interjected spaces. Because of the encoding scheme favored by Microsoft
products, a trailing space can cause "endpress" to be rendered by the
judge as "endpress=20". The result is often something like this:
endpress=20
signoff=20
------=_Part_109324_8027342.1174309132351
Content-Type: text/html; charset=Base64
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<html>signon Egamename mypassword
Right now, USAL is the only nJudge I'm aware of that has filtering in
place to prevent that. Alan has generously offered to share the
scripts, but they're written in Procmail so they are not trivial to add
to the judge distribution - and those who have already climbed a
rather steep learning curve to install and to run the judge software
are not necessarily prepared to learn yet another obscure application.
I also left off my post here a a paragraph that I know needs to be
rewritten... The one where I threaten to boot a (novice) player if he
is late for spring '01 and hasn't sent any press yet.
Chris
|
