#178 Unnecessary disambiguation in SCID.eco

[Jeff M Lowery]

The SCID.eco contains some moves that are unnecessarily disambiguated. This causes problems with some parsers, forcing the use of less-strict checking. Here are the problem variations:

Error: error parsing 1.e4 d6 2.d4 Nf6 3.Nbd2
Error: error parsing 1.e4 d6 2.d4 Nf6 3.Nbd2 g6
Error: error parsing 1.e4 d6 2.d4 Nf6 3.Nbd2 g6 4.c3 Bg7
Error: error parsing 1.e4 e6 2.d4 d5 3.Nd2 c5 4.exd5 exd5 5.Ngf3 Nf6 6.Bb5+ Bd7 7.Bxd7+ Nbd7 8.O-O Be7 9.dxc5
Error: error parsing 1.e4 e6 2.d4 d5 3.Nd2 c5 4.exd5 exd5 5.Ngf3 Nf6 6.Bb5+ Bd7 7.Bxd7+ Nbd7 8.O-O Be7 9.dxc5 Nxc5 10.Nb3
Error: error parsing 1.e4 e5 2.Bc4 Nf6 3.d4 exd4 4.Nf3 Nxe4 5.Qxd4 Nf6 6.Bg5 Be7 7.Nc3 c6 8.O-O-O d5 9.Rhe1 Be6 10.Bd3 Nbd7 11.Qh4 Nc5 12. Nd4 Ng8
Error: error parsing 1.d4 d5 2.c4 e6 3.Nf3 Nbd7

[Jeff M Lowery]

With sloppy flag set (using chess.js npm library), I am still getting an error:

problem parsing moves: C24, "Bishop's Opening: Urusov Gambit, Forintos/Haag Variation", 1.e4 e5 2.Bc4 Nf6 3.d4 exd4 4.Nf3 Nxe4 5.Qxd4 Nf6 6.Bg5 Be7 7.Nc3 c6 8.O-O-O d5 9.Rhe1 Be6 10.Bd3 Nbd7 11.Qh4 Nc5 12. Nd4 Ng8

This is due to an extraneous space in the last move after the move number.

[Jeff M Lowery]

In the PGN I've seen, there's a space after the period in the move number. Also, captures are always denoted with an 'x', for instance:

"1.e4 e6 2.d4 d5 3.Nd2 c5 4.exd5 exd5 5.Ngf3 Nf6 6.Bb5+ Bd7 7.Bxd7+ **Nbd7** 8.O-O Be7 9.dxc5 Nxc5 10.Nb3"

Should be:
"1. e4 e6 2. d4 d5 3. Nd2 c5 4. exd5 exd5 5. Ngf3 Nf6 6. Bb5+ Bd7 7. Bxd7+ **Nbxd7** 8. O-O Be7 9. dxc5 Nxc5 10. Nb3"