[computer-go] Need for more robust SGF Readers

["Frank de Groot" <frank@xxxxxxxxxxxxx>]

Hi colleagues,

I have added a SGF property "RT" that contains compressed RTF.
All chars that need to be escaped, are escaped in this example:

www.zenhacker.com/RTFtest2.sgf

I escaped , \ ] ) ;

Unfortunately, most SGF Readers I tested choked on this (IMO 100% legal)
SGF.

The results are:

SmartGo chokes as soon as RT property encountered (no more nodes processed).

Multigo chokes as soon as RT property encountered (no more nodes processed).

MFOG chokes as soon as RT property encountered (no more nodes processed).
With "Unexpected end of file".

CGoban chokes as soon as RT property encountered (no more nodes processed).
With: "Bogus Token".

WinMGT produces bogus variations and comments filled with garbage.

gGo: "Corrupt SGF"

But.. (I already was thinking "I am producing garbage SGF!")


glGo: 100% compatible!

I only had to escape the bare minimum of characters as well.

Chapeau for Peter Strempel!

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

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

Best regards & thanks,
Frank

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