Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on Sun, Jan 29, 2012 09:07 AM UTC:
To put this into context:
	This page was posted in 2005, when no-one was coming forward with the Templar-Hospitaller pairing. All I knew was that Timothy Newton had given Outback Chess the piece Kangaroo=Knight+Elephant and I wanted to match it with Knight+Dabbaba. Kangaroo seemed to follow the pattern of Gnu, Gazelle, and Bison but unlike Elephant, Camel, Zebra Dabbaba is not a beast itself so I did not see the need to use a beast name. What I did want was to pick a name equally easy to extrapolate. By the time I posted the two pages I had found the old Doughnut reference but no-one was presenting me with any evidence of other names for either piece. What criticisms were made at the time of posting I addressed - by adding more weight to the older Doughnut usage and switching from 'co-inventors' to 'inventor unspecified'.  I also named Camel+Dabbaba Casbah and Camel+Elephant Caribou but did not consider them ready for ther own pages.
	Mention on the site of Templar as a name for this piece, and Hospitaller for the Outback Chess Kangaroo, has been made only since my editorship lapsed, so any further changes that I made to the pages would have to be submitted to, and posted by, a current editor. Since the introduction of post-your-own (PYO) my personal experience has been that editors are inactive in posting corrected submissions of pre-PYO pages. If I thought that it would do any good I would add in the problematist usages with an emphasis that that is what they are and submit it, but my own priorities are updates that I have already submitted for my own pre-PYO variants in light of changes to piece names. Until these are addressed I am reluctant to inundate the editors with more updates.

Edit Form

Comment on the page Carpenter

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.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

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.