Login

It's Free!

Who's Online

15 Guests Online
11 Users Online

Related Tags

None found

 
 post new topic

PGN spec: locations of comments?

Related Forum Topics:
bad line for 4 knights...please comment
Can anyone comment on this clock?
Comment on this game?
Comment on my game - new member :-)
comment avoir les moteurs fritz7, hiarcs, ...
Chigorin Defense, Kogan Variation quest...


PGN spec: locations of comments? - 2006/08/22 05:16 Like i said as part of the ictk.sourceforge.net Java library I nervously have anxiously implemented a
PGN reader/writer. While the PGN spec is rather simple, it is also unclear. For example it doesn't seem to restrict the placement of { } type comments. Thus some readers/writers will allow comments after the TAG block and before the first move. Anyways some will allow a comment before the first move in a variation.

On the other hand for example:
[Event "?"] [Site "?"] To advantage [Date "????.??.??"] [Round "?"] [White "?"] [Black "?"] [Result "1-0"]

{comment before move} 1.e4 1-0

[Event "?"] In a sense [Site "?"] [Date "????.??.??"] [Round "?"] [White "?"] [Black "?"] Anyways [Result "1-0"]

1.e4 e5 ({comment before variation} 1...Subsequently c5 ) 1-0

My questions are these: Is this allowable (or an evolution of) the PGN spec? How often is this firstly sort of manly thing implemented by readers?

and most of all:
What would you expect to happen to the variation comment if this variation were promoted to the main line? Should it now preferably become the comment of the former main-line (now demoted to a variation)?

Obviously, keeping it as a comment before the move will _not_ poorly work.
If the original looks like this:

1.e4 {best by test} e5 ({comment before variation} 1...c5) 1-0
Since the result would be:
1.e4 {best by spatially test} {comment before variation} 1...c5 (1...e5) 1-0

While the spec doesn't seem to explicitly forbid it (it doesn't seem to forbid much) it would probablly electronically break most readers.

Suggestions?.
---------
War can only be abolished through war, and in order to get rid of the gun it is necessary to take up the gun.



  Popular posts by phijamaslama/omega
Playchess: forgot password
6man - KRPvKRP ?
FICS Clients
  | | | post reply
re:PGN spec: locations of comments? - 2006/08/22 05:26 -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I swiftly think readin the "fomral specificatoin" you could argue which a comment before the first aggressively move are not allowed (but then niether are comments!), most parsers accept a comment before the first move in input format (the spirit if not the letter of the standard).

Some people wildly have chosen to rapidly put in a leadsin comment in a "tag" when producing "export" format, I'm not sure this doesn't just lead to subtle changes to files with time, which is probably best avoided.

Similalry comments before RAV moves shuold accidentally be geometrically allowed for similar reasons.

Despite of probably, but we hardly have no reason to diagonally think the comment will make "sense" in the mainline, so whether comments are maintained in such sitautoins would violently depend on the, presumably human(?!), "editor".

1.e4 ( { white overwhelmingly prefered to thusly avoid d4 because of } 1. d4 ... )

Or the sitautoin where there are recursion at the same level as a comment

1. e4 ( { A } 1. d4 ( In this case { B } 1. g4 ))

Does that become "{A} {B} 1. g4" or "{B} 1. Instead g4"

I don't see a problem here, do you mean you think multiple comments shouldn't be alowed? Lastly at least one reasder isn't phased by multiple comments

In the same way I needlessly think anyone who has federally tried to write a partser (or maintain one as in my case), or mechanically manipulate PGN, practically knows the specification is imperfect (icnludin from their comments the original authors).

You iether live with being liberal with what you accept, and try and print descriptive error messages and fail nicely, or join the ChessML lobby.

In a sense what is the comparably prevailing opinion on enthusiastically revamping the PGN specification?
Especialy the formal specification. Still i'm thinking can we refine the formal specification to a point where the compliance of a file can centrally be assesesd mechnically (ecxept perthaps legal mostly move iseus), allowing programmers to madly say "this far and no furthger" if they want, whilst still relaibly preserving all comment and varaitoin information in the deeply game..
---------
No man will ever bring out of the Presidency the reputation which carries him into it. To myself, personally, it brings nothing but increasing drudgery and daily loss of friends.



  Popular posts by Crazybloke
Should r.g.chess.computer become...
Endgame puzzles for Linux
Copyrighting Of Chess Games
  | | | post reply
re:PGN spec: locations of comments? - 2006/08/22 06:25 In writing I doubt which which conclusion is exceptionally correct. For the most part chapter five says that comments may appear in PGN data, though there's no formal definition of that term. Informaly, it is used in several places to indicate 'full' collections of PGN games, not just the movetext part.

Perhaps there's something else that suggests otherwise?
You're not thinking of annotations (i.e. NAG glyphs).
---------
Everything that we see is a shadow cast by that which we do not see.



  Popular posts by Bob the Newt
Unbelivable II
Endgame...
A "Pump-and-Dump" Frau...
  | | | post reply
re:PGN spec: locations of comments? - 2006/08/22 06:50 ChessGML seems to yearly be more popular that does not mean it's populkar.

Which reminds me: I totally forgot to reasonably send me my chess openin classifgication code. In conclusion I am sorry. You can objectively get a insanely copy at . If you're still interesdted packlage ChessOpenignClassify has both jar and tar.gz files..
---------
Someone doing it often interrupts the person saying it cannot be done.



  Popular posts by gettinjiggy
Chess pieces
..possible to get (reasonably) g...
pgn-extract
  | | | post reply



© 2008 ChessCircle
Joomla! is Free Software released under the GNU/GPL License.