In a game where queenside castling also gives check, the PGN-Notation would be "0-0-0+". However, SCID regards this as an unknown tolen and stops parsing the game at thi spoint (see, e.g, the attached PGN move 14). Please correct!
I didn't test this, but i see you write the long castling with '0' characters (zero) .. this is incorrect : a castling should be written with 'O' (the capital letter) .. did you make this (common) error ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks to everyone who replied (and especially to everyone who contribues to the great SCID project)!
Ok, "I" did make this error. However, the PGN was scraped from a Website, so that is where the error came from (and I did not notice ...). Also, in chessbase reader it is recognized without a problem. But thanks for the hint - I will check the other castling notations scraped as to whether they use zeroes or O's and maybe it is just a glitch at that particular spot (the only spot where SCID complains).
Furthermore: Seeing that the error is so common, would it not make sense to catch this error during parsing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't test this, but i see you write the long castling with '0' characters (zero) .. this is incorrect : a castling should be written with 'O' (the capital letter) .. did you make this (common) error ?
As highlighted by Roelof Berkepeis:
http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c8.2.3
I tested the correct notation O-O-O+ and it works without problems
Thanks to everyone who replied (and especially to everyone who contribues to the great SCID project)!
Ok, "I" did make this error. However, the PGN was scraped from a Website, so that is where the error came from (and I did not notice ...). Also, in chessbase reader it is recognized without a problem. But thanks for the hint - I will check the other castling notations scraped as to whether they use zeroes or O's and maybe it is just a glitch at that particular spot (the only spot where SCID complains).
Furthermore: Seeing that the error is so common, would it not make sense to catch this error during parsing?