Author: Steven Edwards
Date: 06:45:11 04/08/05
Go up one level in this thread
On April 07, 2005 at 17:19:25, Andreas Guettinger wrote: >On April 07, 2005 at 16:59:33, Robert Hyatt wrote: >>On April 07, 2005 at 13:40:23, Steven Edwards wrote: >>>On April 07, 2005 at 11:34:49, Marc Lacrosse wrote: >>>>- other engines (Yace, Pharaon, ...) seem to accept the "relaxed" syntax >>>So does Symbolic's toolkit PGN reader. (Many other typical deviations are also >>>processed correctly.) But this also slows down the reader, and that's not a >>>good idea if you're frequently importing large amounts of PGN data. Crafty's >>>PGN reader is quite fast, certainly faster than Symbolic's, in part because it >>>doesn't try too many attempts at correction. Would you really want to slow it >>>down? >>Crafty already handles some non-PGN compliant things. for example zero-zero for >>castling rather than oh-oh. or 1.e4 rather than 1. e4 (missing space). A small note of caution: treating zero-zero as kingside castling will cause a problem in the admittedly rare case of a game that ended in a double forfeit. That's because PGN uses zero-zero as the game termitation indicator in that case. >>You would think that software vendors could get this right, but then ChessBase >>has modified the PGN standard anyway with their new annotation tags and crap, so >>they will probably never plan on being 100% compatible with others... I really have to put in some time on updating the PGN spec to include (optional) angle bracket forms in the movetext. These forms are quite simple; each is just a single EPD operation enclosed in angle brackets. For example, to indicate the seconds used for a move: 35. Nb5 <acs 34> Qxb5 <acs 6> An entire PV could be included: 18. Kg2 <pv Qg4+ Bg3 Qxg3#> The idea is that the code used for EPD processing can be recycled along with its documentation.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.