Re: [computer-go] Need for more robust SGF Readers

[Marco Scheurer <marco@xxxxxxxx>]

> Could you all please test this file with your parsers and tell my what 
> I did
> wrong (if any), and try to get your parsers not to choke on it? It 
> would be
> nice if they all would support the official SGF standard..
Indeed...

The file seems to begin with 3 illegal bytes, which does not look good 
for a text file.

Then:

Line:2 Col:3 - Error 23: property <AP> expects compose type value 
(value deleted): [ZenHacker Go Software Suite v. 0.0.0.3]

is not exactly showing respect for the standard, and we haven't reached 
RT yet.

Then:

Line:7 Col:1 - Warning 40: property <CH> isn't defined in FF[4] 
(parsing done anyway)

Why CH since CA seems to do the same thing and is defined in your file?

> I might be wrong and produced some crappy SGF, but perhaps not, as 
> Peter's
> latest work works fine, and it would be too much of a coincidence..
FYI, SGFC is the reference implementation for the SGF FF[4] standard. 
It can be found at http://www.red-bean.com/sgf/sgfc/index.html . If 
your file does not pass the SGFC test it can be considered crappy SGF.

Goban for Mac OS X uses sgfc to fix, as much as possible, illegal files 
which otherwise break its built-in parser. It is hard to tell if your 
file is opened correctly without a "clean" version of the same file 
without RT stuff to compare it to. However, I suspect that

sgfc -u RTFtest2.sgf

removes much more than what you would expect from your file, it results 
in just 5 moves and one comment.

marco

Marco Scheurer
Sen:te, Lausanne, Switzerland   http://www.sente.ch

_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/