Replies: 3 comments
-
|
The issue is with the section above the move order. The parser expects the moves to follow after the last tag. In your file you have an embedded command instead. Remove the whole section starting with {[%evp as that isn't recognised by the parser (see the "Non-Standard PGNs" section under Known Limitations). According to this %evp is a chessbase tag. I took your pgn and removed the line and it now opens in the tool. Notice that the moves follow after the last tag (GameID in this example): |
Beta Was this translation helpful? Give feedback.
-
|
thank you! it is strange because the same line was not causing an error from the original pgn not splitted. |
Beta Was this translation helpful? Give feedback.
-
|
Hi arnaule, Even the original PGN in this issue now opens without issue in the new version. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The main lines of my PGN is working with your software - it is perfect!
Trying to work the other lines i used pgn-extract as stated in your documentation, adding a -w1000 as i was having the 75 error.
It generated a file with about 60 games.
Now i am getting : SyntaxError: Expected "*","0-1","1-0","1/2"..... or whitespaces but end of input found.
For example the first game of the file generate the syntax error :
[Event "?"]
[Site "?"]
[Date "2022.11.23"]
[Round "?"]
[White "?"]
[Black "?"]
[Result "*"]
[ECO "D31"]
[Annotator "?"]
[EventDate "2022.??.??"]
[PlyCount "36"]
[GameId "2076602978287251"]
{ [%evp 0,36,34,25,27,4,-11,-3,12,2,12,9,33,25,27,32,61,16,16,16,16,18,17,20,38,33,46,44,33,28,43,29,40,18,28,25,25,22,27] }
Would you know what triggers the syntax error ?
Beta Was this translation helpful? Give feedback.
All reactions