-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My suggestion with GO is that you make whatever tools YOU use flexible enough to handle either format, either implicitly, or via some kind of configuration.
You might have a user selectable "export" format and the import format could be easily made smart enough to handle either case. - - Don Dave Dyer wrote: >> However, I am in favor of changing the SGF format to allow coordinate encoding using the "standard" coordinates system rather than the one created just for SGF; i.e., "a1" vs "aa". > > I routinely use sgf for non-go games and completely ignore the > standard set of tag names and contents. This works fine for me > because I only have to be compatibile with myself - anyone else > who wanted to read sgf-encoded trax games (for example) would > have to follow my example. > > The problem with this for Go is that all the existing tools which > are Go oriented would be unlikely to follow your lead on "improving" > the format. > > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHHPZbDsOllbwnSikRAg5ZAKC/wR305Zw/EwEjIZzdc4BfR1yPwgCfVAWB KIYnP0evrWVWfZ8S9kg9op4= =ZlwM -----END PGP SIGNATURE----- _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
