Poll
Poll Question: How should we use algebraic notation in chess variants?
bars   pie

Solution #1: one uppercase letter    
  0 (0.0%)
Solution #2: two uppercase letters    
  0 (0.0%)
Solution #3: one or two uppercase letters    
  0 (0.0%)
Solution #4: use coordinate notation instead    
  0 (0.0%)
Another solution not mentioned above    
  0 (0.0%)
No opinion or I just want to see the results    
  2 (100.0%)




Total votes: 2
« Created by: Marc Benford on: 07/28/26 at 21:49:06 »
Normal Topic How should we use algebraic notation in variants? (Read 191 times)
an ordinary chessplayer
God Member
*****
Offline


I used to be not bad.

Posts: 1832
Location: Columbus, OH (USA)
Joined: 01/02/15
Re: How should we use algebraic notation in variants?
Reply #1 - yesterday at 15:39:21
Post Tools
I vote for solution #1.

Piece names can vary by language, so even if you choose names with unambiguous first letters in some arbitrary language, there may be ambiguity in some other language. This already happens in standard chess. In English, King and Knight both start with K. Nowadays it is usual to use N for Knight, although I have seen S (from the German Springer). Thus it already happens that the piece letter doesn't have to be the first letter of the piece name.

Piece letters are also used for constructing FENs, so multi-character representations are undesirable there.

The usual way is for the parser to have an internal array of pieces, and allow the user to specify an array of letters to represent them. The same array is used for both notation and fen. See how pgn-extract and xboard/winboard do it. It works well. The piece letters shouldn't matter, as long as they make sense to the user and there is a way to notify the parser. Also, although I haven't looked at it in detail, ICC and FICS have been handling variants for a long time, might be worthwhile checking there.

One of the many things I like about Tarrasch Chess GUI is that it can act as a pgn notation translator: open a pgn with piece letters in one language, then change language, and the piece letters are updated.
  
Back to top
 
IP Logged
 
Marc Benford
Full Member
***
Offline


I Love ChessPublishing!

Posts: 147
Joined: 07/17/13
How should we use algebraic notation in variants?
07/28/26 at 21:49:06
Post Tools
How should we use algebraic notation in chess variants with very many different types of pieces?

Solution #1: Give one unique uppercase letter to each type of piece. The first problem is that many pieces start with the same letter (for example, aanca/alfil/alibaba/amazon/antelope/archbishop, camel/cannon/centaur/chancellor/crab, general/giraffe/gnu/grasshopper/gryphon), so either most pieces would have a letter that is not the first letter of their names (such as N for the knight), or we would have to invent completely new names for most pieces (we wouldn't be able to use the names that they are usually known by). The second problem is that this solution wouldn't work if there are more than 26 different types of pieces, since there are only 26 letters in the alphabet.

Solution #2: Give two uppercase letters to each type of piece. For example, QU would be the queen, RO would be the rook, BI would be the bishop. I assume that both letters would need to be uppercase, otherwise we might confuse them with the letters that represent the file (a to h), which are lowercase.

Solution #3: Give two uppercase letters to each type of piece, except for the most common types of pieces which should have only one uppercase letter. For example, Q would be the Queen, R would be the rook, B would be the bishop, AL would be the alfil, AM would be the amazon, CA would be the camel, CH would be the chancellor.

Solution #4: Don't use algebraic notation. Use coordinate notation instead. For example, instead of saying 1. Nf3, we would say 1. g1-f3.

Share your opinion.
What is the best solution?
What are the pros and cons of each solution?
Are there other solutions that I didn't consider?
  
Back to top
 
IP Logged
 
Bookmarks: del.icio.us Digg Facebook Google Google+ Linked in reddit StumbleUpon Twitter Yahoo