One final email on the subject. I¹m not sure if it might be easier to import each sgf file and then export it right back out as a Plain Text file. The plain text file is human readable and as long as the analysis and rollout data is in the exported text file that you need that might be the easiest option without understanding the mechanics of the C code or the SGF file format.
This is assuming ³Plain Text² export gives you all the information you need. On 04/06/09 11:06 PM, "Dan O'Farrell" <[email protected]> wrote: > Hi, > > I'm hoping someone can help me. > > I'm designing a database to hold the content of an analysed sgf file for > querying & reporting purposes. > > The problem I have is trying to understand the actual values held in an > analysed sgf file i.e. what the various values mean. > > I've read up on the FF4 file format and understand the structure. > > I can deduce what some of the actual values are but with others I'm left > guessing. > > I'm not a C/C++ programmer so deciphering the source code would be a > nightmare. > > My question is this...is there an internal document to the gnubg developers > which specifies what the various values in a sgf file are and what they > mean?. > If there is, would it be possible for me to have a copy of the document (or > documents)? > > > Any help would be much appreciated. > > > Regards, > > Dan > > > _______________________________________________ > Bug-gnubg mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-gnubg
_______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
