TalkChess.com

Thanks Pascal.

Any chance you will fix the bug with pgn output that does NOT leave a white space after the period following a move number? In other words, Scid outputs "5.Nf3" instead of "5. Nf3".

open a dos command window and type

copy con empty.ctg

then hit <enter>
then press <control> and hit <Z>

and you have it.

A much more common "faulty" PGN interpretation is the lack of a white space between the dot after move number and the corresponding white move : "1.Nc3" (should be "1. Nc3"). Another common "fault" is incorrect writing of promotion moves. Some major GUI's do not produce strictly correct PGN. This i...

<snipped> Some gui(s) used by both CCRL and CEGT produces pgns that violate an important pgn principle. [/code] I do not understand what is the importance of the principle that you give. I see no big problem if irrelevant information is posted. If the reason is size of the pgn then I think that it ...

Some gui(s) used by both CCRL and CEGT produces pgns that violate an important pgn principle. This gui assumes there is ALWAYS ambiguity when 2 of the same pieces can move to the same square. However, if one of these pieces cannot legally move to the square, then the gui does not notice that there i...

Just a quick question... I understand long games like 40/40 are good for books, but is this not a bit of overkill for determining engine strength? I see that an engines performance at 40/4 will correlate at roughly .98 with how it will play at 40/40. Might it not be more efficient to scratch 40/40 ...