The Chess Variant Pages



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2012-05-12 UTC
At Harvard I sat in on graduate courses taught by Sheldon Glashow and did not really understand a full sentence of lectures then. Likewise to Physics, there are levels of appreciation of CVs developed or developing. Start with any CV and learn the rules, then graduate to articles about cvs. //// Gilman is cataloguing frantically to get credit for a 1000 p-ts, realizing they can be done en masse. Why M&Bxxs are a difficult ''read'' compared to the German and French glossaries Knappen has linked can be explained. Gilman through M&Bxxs is naming and listing specific p-ts numbering over 2000 without overmuch explanation.  One is left to figure out the piece-type definition from the suffixes and constructed name.  It's do-able but not very easily for the average reader, so you just take them one at a time as needed.  I search a M&Bxx just to find a sentence on a Hopper or what a Point as a Pawn means, as two small examples. The 21 M&Bxxs are a Reference like a Dictionary.  You don't read all the 'H' words to get clear on 'Heredity', just the one word or one or two piece-types.
Frankly Gilman's transitions from 2-d to 3-d and back, from Scout to Dueller, on and on and on, are confusing at best, unnecessary to read more than paragraph or sentence needed to answer an argument.  However, digging into any section or topic more than that, it is found to have incredible accuracy and consistency. Far more so than Betza's little effort of the past, http://www.chessvariants.org/index/displaycomment.php?commentid=614. Betza's work distracts differently by his constant sarcasm and dispersed diluted substance. In comprehensiveness, M&Bxxs including glossary and indexes, are unlikely to be surpassed any decade soon before year 2060.  Take it or leave it. Or be shamed it was done under your watch without recognition.

Edit Form

Comment on the page Suffix Index to Man and Beast

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.