TalkChess.com

Also adjust the engine names. For example: "Shredder 10.0 64-bit" and "Shredder 10.0 x64" are considered by elostat to be 2 completely different engines. On a side note, let me mention that as a user of both CCRL and CEGT, I have noticed that the 2 services often use different names for the same eng...

Can you precise what's going wrong ? It is the elo values with the asterisk "*" that cannot be exported to a pgn file. These elo values seem to be built-in. I took a pgn file, removed its elo values, converted to scid format, and found that some of the games had elo values with asterisks. Then when...

Thanks Pascal.

Would it be possible to extend the ELO insertion process so that after an ELO insertion, an ELO tag is produced in pgn output? Right now the inserted ELO value stays internal to SCID, and disappears when the games in the database are output as a pgn file.

I made an option available that will make Scid more compliant to standards. I prefer to keep the old way around in case of any bad side effect. But I have a question : 1. e4 is the PGN standard, but after a variation, with black to move, what should be displayed : 2... e5 or 2. ... e5 ? 2. ... e5 T...

There is a new release available for the "40H" collection of PGN utility tools. A new tool, "gameNum" has been added. It puts a game number comment before each game in a pgn file. Sample: {Game 501} For a brief description of all 20 programs, here is a short "overview" file: overview.txt To download...

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...