On 11/18/2010 06:42 PM, Pascal Georges wrote: Hi,
> 2010/11/17<joost.t.h...@planet.nl>: >> From: Pascal Georges [mailto:pascal.georg...@free.fr] >> Sent: Wed 17-11-2010 13:06 >> Hi, >>>> 2010/11/17 Joost 't Hart<joost.t.h...@planet.nl>: >>>> Decided to remove the annotator string completely and let the engine >>>> run up to the move number specified. >>> Do you mean the "Annotator opBlunder" one ? >> Yes. >>> If so it should remain in place as it is useful for some people (like >>> me). >> Fair enough, and thanks for getting involved. >> >> But please be invited to dig a little deeper than this... >> >> Can you explain the desired behaviour? I recently fixed the operation >> that adds an annotator tag, as it used to destroy everything that was >> already in the game's extra-tags section. >> >> The code that adds the opBlunder annotator tag is activated every move, >> as soon as "book" is left. This means that a complete poem of tags >> is added, depending on how deep the opening search goes. It also means >> that since the fix the poem can actually be read :-) . >> >> Should not be, right, or should it? > I did not check CVS for some time. The desired behavior is to have a > tag that points where an opening blunder was played. I see no poetry > in Scid 4.2.2, simply opBlunder is a way to check a bunch of games but > only up to the Nth plies. > "opBlunder" is not an untranslated tag but something anybody can look > at when searching for games with a blunder in the opening. Clear. The name is just some unique name. But the poetry really should have been there, as the annotator tag was added after each move. In CVS this has been corrected. You do not recognize this in 4.2.2. because of another problem: Any new annotator addition destroyed the previous one (and all the other tags in the extra-tags section). This has also been corrected. >> Which tag is the one you're looking for? The first one, after we go out >> of book, or the final one, at the end of the opening search? > The first one is the best, but the third blunder can be also useful. OK, in CVS the first one is added. In CVS, the engine annotates always at least one move after the game went out of book, even if the annotation depth was reached in book. Is this a problem? I hope not, otherwise the machinery will need another serious fixup... >> I guess, so far you were used to seeing only the last one? >> On the other hand, only the first tag can possibly be meaningful, since >> once out of book we do not return anyway... >> >> Does opBlunder refer to some untranslated string? Or is this "the name >> of the annotator"? > Putting the opBlunder token in the Annotator filed was a choice, but > indeed meaningless (it is nothing to do with an Annotator name). So it > could go anywhere if a better place is found. I think it is a good place, the extra field that is. Maybe we can invent a specific extra tag for it, but adding it as a way of annotating (which it is), is not a bad idea at all, imho. >> What does the color in the annotator tag tell you? My impression was >> that the implementation might be wrong, in that if it is Black to go >> out of book first, "white" is added to the tag at that moment. > 7 (white) means white blundered at move 7. OK, done in CVS. >> Finally: Do you expect the opBlunder tag to replace the default engine >> annotator tag (suppose the user checks that annotation option as well), >> or do you expect them both (in a comma-separated list)? > Both, I think. Currently it is either/or. I will correct this later tonight. > Pascal > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2& L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Scid-users mailing list > Scid-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/scid-users > ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users