ChessX

I know all that. Believe it or not, I actually did read the PGN standard
:-)

But at least Scid does not seem to care. I suspect Chessbase etc. does not
either.

If you think that we should not support nonstandard PGN like this, that's
ok with me. On the other hand, it may be easier to support it, if other
databases do so. If only to avoid future identical and annoying bug reports
:-)

As for the site I mentioned, the admin there is known to be most rejective
to suggestions on the whole anyway, so informing him about this would for
sure be a waste of my time.

I fixed it in CVS for now.

Although, you can inform the abovementioned site that, accoring to PGN
standard:

SAN kingside castling is indicated by the sequence "O-O"; queenside
castling is indicated by the sequence "O-O-O". Note that the upper case
letter "O" is used, not the digit zero. The use of a zero character is not
only incompatible with traditional text practices, but it can also confuse
parsing algorithms which also have to understand about move numbers and
game termination markers. Also note that the use of the letter "O" is
consistent with the practice of having all chess move symbols start with a
letter; also, it follows the convention that all non-pwn move symbols start
with an upper case letter.

This pgn is supported in Scid at least, and it is generated by the very
official site www.eskak.dk (so it is not "my" pgn).

This is due to bug in your PGNs. Castling in PGN should be represented by
O-O (letter 'O'), not 0-0 (zeros).
Do you think such buggy PGNs should be supported?