Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
Bob Greenwade wrote on Sun, Sep 3, 2023 12:07 AM UTC:

WHen you edit your page, you have a toggle box with "Source" for every section. If you play with it for the sections where the ID is not, then nothing occur to the section where the ID is. Well, this is my own experience.

Otherwise, to prevent accident, I make a copy of the ID code in a txt file in order to use it back if necessary in case of corruption.

The next time I go to edit one of these (which I may soon do with Dealer's Chess), I'll look for that again. I tried to find tha sort of thing once before, to no avail.

But that copy of the ID code is similar to what I already do: copy and paste into an open WordPerfect document, then cut-and-paste back. It's also a tad easier to edit the ID that way (not much, but still easier).

Besides, switching to WYSIWYG for fixing simple typo's seems unnecessary. These can be fixed just as easily in the HTML source.

That's how I was able to fix the other typos and stuff. The "Shiek" typo I caught after my previous edit, and decided to wait until fixing the Satrap/Ayatollah thing, since that was a little more involved; opening the file to fix one typo didn't seem worth the trouble when I knew I'd be going in soon anyway for something bigger. That's not even considering Jean-Louis's very fine notes.

Plus, with my vision, finding some of those typos are a pain in HTML mode.


Edit Form

Comment on the page Desert Dust

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
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.