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

Enter Your Reply

The Comment You're Replying To
Ben Reiniger wrote on Wed, May 12, 2021 03:12 AM UTC in reply to H. G. Muller from Tue May 11 05:02 PM:

@H.G., The change was to conform better to FFEN notation; together with that change occuring back in 2018, I think fixing the handful of pages in the comment I linked to last time is the better solution.

Here's the comments recording the change in behavior:
https://www.chessvariants.com/index/listcomments.php?itemid=DiagramDesigner&order=DESC&first=36719&last=36723


On this page, I copied out Pieces section to Notepad++, and used this regex:

find: (drawdiagram.php\?code[^&{"]*)\.
repl: $1$2$3{.}

This finds periods after drawdiagram.php?code and any number of characters that are not among &, {, ". The exclusions prevent searching beyond the ffen code from the drawdiagram script. The match always gets the furthest ., and so we replace from the rightmost side; repeating this (and the excluded {) eventually replaces everything we want.

This means I have to mash "replace all" until all the replacements are done, but that's fine.

There's a bigger issue with generated images, like the ZEBU (.ZRH) and BISON (.JZ). When copying from the webUI editor, the surrounding squiggly brackets got url-encoded, so that they were missed by the regex, and the leading . got caught and changed. I manually fixed these two.

I'll ponder ways to improve this process, but thought I'd describe it here so that (1) I'll remember, and (2) anybody (handier with regex?) can provide feedback.

Finally, the diagram containing the forward-only versions had suffered a newline in its url, which together with some added indentation for some reason, interpreted the additional whitespaces as requesting stones added to the board. I fixed that as well.


And on a possibly totally unrelated note: some of the math expressions are weird, seemingly including extraneous characters just before every exponent character?


Edit Form

Comment on the page Man and Beast 03: From Ungulates Outward

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.