#66 Allegedly Ambiguous Moves giving Checkmate

[ScreenName]

I'm attaching a .pgn file with two games that ScidvsPC could not import properly. In each case, the final move administered checkmate. ScidvsPC generated an error message for each game ("Error reading move" and specifying the offending move without the '#' that indicates checkmate).

I suspect that ScidvsPC correctly recognized that, in each of these games, each of two pieces could reach the destination square; so, perhaps, ScidvsPC sees an ambiguity. But if only one of the two possible moves administers checkmate, the game score is not actually ambiguous.

Please consider updating ScidvsPC to use the information conveyed by the '#' to disambiguate.

Thanks,
Joseph Polanik

[Steven]

Hmmm... That is interesting report, cheers.

But it may be asking too much. At no other point in the software is a trailing nag used to define a move. And the PGN parser is one h-ll of a piece of code.

I just tried out chessx. It doesn't complain... but it actually selects the wrong queen move 37. Kg4 h5+ 38. Rxh5 Q1f4+ 0-1
Perhaps you could test some other chess software and relate how it goes? But i'm kindof doubtful this will be changed.

EDIT xboard, and fulvio's Scid also fail to load the games' last moves.