Originally posted by Meadows
Consider the Nimzo-Indian line:
1. d4 Nf6 2. c4 e6 3. Nc3 Bb4 4. e3 c5 5. Nge2
My question is about the 5th move's notation. Without thinking, I would notate this as Nge2, computer's do it automatically (although that could be a programming thing; an engine I made once would do the same) and the only book I have to hand at this moment (Starting Out: T ...[text shortened]... is position, however, it's quite clear that only one knight can move to e2. Can anyone help?
Why would an ambiguity be avoided? I would like it to go to the other direction: More unambiguity, more unneccessary information (to a point).
In the example a Ne2 would be preferred, according to the thread initiator. But even this notation give unambiguity, right? Why not the minimalistic N2 or Ne? Since there is only one knight that can go to the second row, then Ne would be sufficient?
Nad what about when there is only one piece that can go to only one square? Why have anything at all? Or just a hyphen (-) to indicte that no notation is neccesary?
I use long notation when making notes in games. Weather unambiguity or not. Why? Because when you write a mistake, then clues in the notation gives information of what it should be.
If I write (by mistake) Qg6 when it should be Bg6, and both pieces actually can go there, then something will be wrong. But if i wrote Bg2-g6 instead of Bf7-g6 then I can easily deduce that I meant the queen, not the bishop. I can easily repair the mistake if I have more information than I need.
I go a step further: When I take a piece, I also write which piece I take: Like Qg2xBg7. This make's it possible to go through the game in backward direction, if I need. I can track the game from the last position to the first, if I want. From a diagram, I can easily see what move, even if a piece is taken, that led to the current position.
I always write e.p. for en passant, ++ for double check, and if a check is a discovered one with what piece the king is checked (but I don't have any symbol for that one).
I call this extended notation for 'The Fabian Notation'. The disadvantage is that you cannot store these extra things in a computerized database, and FIDE tells us that only the short algebraic notation is allowed in tournament game protocolls.
I find the Fabian Notation very easy to read games from the protocoll. The short algebraic notation makes is much harder to follow the game.