Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Ben Reiniger wrote on Mon, Nov 23, 2015 04:50 AM UTC:
I was hoping for a solution that would scale images enough so that lines
were not broken.  (Alignment for boards with different rank sizes is
another issue, which I had not considered yet.)  I was looking for a way
that the js output could be treated as a single object to be scaled to fit
the screen; perhaps flattening to a single image would do that in addition
to being better for other reasons.

By "transition to single images hosted on this site" do you mean on the
author's end?

For ASCII diagrams I am mostly concerned with old pages (90s ones :P) that
already use them (and whose authors might no longer be active).  I suppose
changing msdisplay to add P tags and a monospace font will make any
"non-HTML" page without an ASCII diagram better on mobile, and will make
such pages with a wide ASCII diagram bad on mobile, but just in a different
way than at present.

I had thought about introducing a more sophisticated text entry method
(e.g. CKEditor or TinyMCE), which could render "Uses HTML" obsolete (for
future pages): every page would use HTML, but the user wouldn't need to
worry about coding.  On top of that, we could be a little more careful
about what we allow our users to submit (whitelisting html elements and
customizing to allow Muller's [diagram], the ffen2diag script, etc.).  If
we think we want to and can manage to move to a third-party CMS, then I
won't keep looking into this.  (This is outside my tech comfort zone, so
it would take me a while anyway.)

Edit Form
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.