Comments/Ratings for a Single Item
HTML takes more time to create .. Besides, I think the ASCII looks pretty. PS : at least I AM posting diagrams ..
|
|||||||||||||||
|
The following one is based on what physical equipment might be used. It has the advantage of being still shorter, but has the problem that such very familiar images strongly suggest FIDE moves!
Thanks for the rating and the diagrams, Charles Gilman. However, I really hope you two stop discussing how I should post my diagrams and discuss the content of the page. Thank you.
R |
|
A |
|
Q |
|
B |
|
N |
| |||||
|
p |
|
p |
|
p |
|
p |
|
p | |||||
p |
|
p |
|
p |
|
p |
|
p |
| |||||
|
N |
|
B |
|
K |
|
C |
|
R |
Chancellor : moves like rook or knight.
Archbishop : moves like bishop or knight.
Mats, you're completely missing the point here. I, the writer of this page, find using another program to create something i can easily and efficiently create in my browser to be an unnecessary burden. (I usually use Microsoft Word as my HTML editor, but I never liked the results.) ASCII diagrams take less time to download, and they're pretty and very obvious. If you don't like it, you don't have to read it. It's that simple. Browser settings are irrelevant. Because the pages are designed in such a way so that they always show text in the Courier font unless the poster checked any of the HTML boxes under the text box. So, the ASCII diagrams shouldn't be a problem. Please, STOP this discussion, because it is pointless and leads to nowhere (since I am not changing the page.) Thank you.
Now, you could've easily said that from the beginning instead of this whole argument. I tested the page in Firefox and IE, and it worked in both. So. naturally, I didn't see what the problem was. You can see the diagrams in Charles Gilman's comment. The Rooks stand for Double-Dabbabahs, Bishops for Lions, Knights for Alibabas, Queen for FAD. Editing the article to be HTML is too troublesome. I have, however, added a FFEN code using the original letters of the pieces. Thank you.
Good. Any game with royal pieces can be played like this: two normal boards of original game and duble set of pieces, expect thaet number of royal pieces is same as in original game, and royal pieces of diffirent players starts on diffirent boards. Variant: three boards, third is without royal pieces at all, but all pieces, captured on this board, costs some points, and if player captured enough pieces here, he/she can win even if his/her royal piece is checkmated (or captured, depending on game's rules). Way to indroduce lion-like piece on games with two boards is simple: piece, wich can't capture on it's board, but can capture pieces on other board by moving to square, wich correspond to square of captured piece.
As an example of how Markdown can be used to touch up pages originally done in plain text, I have revised this page in Markdown. The text was already doing bulleted lists in the same way as Markdown does, and I just left that alone. I initially marked off the diagrams as preformatted text, and then I replaced one with a diagram from the diagram designer. It was helpful that the author already included the FEN code, though I had to fix it up a bit, because he used different letters for the same pieces. I'll touch it up more later. For now, what I've done is a trial run for using Markdown to fix up plain text pages without manually adding in HTML code.
14 comments displayed
Permalink to the exact comments currently displayed.