Lines Matching refs:a

12 PGNs combination of a formal specification for computer use with easy
14 format of choice for representing chess games. This is a major success and a
19 changes. There is also a huge body of software which implements the current
48 This rules out new syntactical elements. Steve Edwards himself proposed a format
59 such a way that they are usable for other extensions if needed.
61 The intention here is to provide a generalised syntax that will enable other
69 new command syntax into PGN comments. This is a kludge and such an obvious one
73 Apart from a general command syntax we propose several specific commands
76 We also propose the addition of a tag to the header to handle the state of the
83 Interpreting time information for a game is either difficult or impossible if
84 the time controls in force are not known. PGN has a TimeControl tag for this and
90 An embedded  command may occur at any position in a standard PGN comment, ie
102 Either a single parameter or a comma delimited list of parameter values.
109 The characters [% are redefined to indicate the start of a command sequence when
112 As all ASCII characters are legal in a comment string it is not possible to rely
124 describe a generalised command syntax, not to impose a particular set of
127 We *are* proposing a set of commands to deal with time handling. "clk" in the
143 A command is followed by a single space and then either by a single operand or
144 by a comma separated list of operands.
147 i) a set containing any ascii characters except the comma and right hand square
150 ii) a double quoted string containing a set of any ascii characters except the
156 This command has four operands, a time value, a san move value and a double
167 i) The operand list is separated using a comma rather than a space.
170 So it is possible to pass a full FEN string as an unquoted operand as in the
176 This command has four operands, the first is a double quote delimitted string,
177 the second is a FEN, the third is e4 and the fourth is d4.
180 The command is terminated by a single ] character.
196 All these commands take one and only one parameter which is a time value in the
213 mechanical clocks which show a clock time rather than the time remaining to the
220 The elapsed time that a player has used for all moves in the game up to that
228 The elapsed time that a player used for the commented move.
234 The time actualy displayed on a mechanical clock. Notice that here the time
238 The syntax described above allows us to encode a move time for a *completed
239 move*. This is all well and good but during transmission of a live game it can
244 We propose that this information should be encoded in a new header tag.
248 As only one clock is running at a time only one tag is necessary.
254 It is followed by a string constructed as follows:
259 the situation where a player forgets to switch the clocks. It also allows us to
262 The second character is a "/" seperator.
263 The rest of the string is a time in the format h:mm:ss which indicates the
272 the example below) they are mainly intended to cover the case where a game is
281 Clearly when manipulating time information about a game details of the time
301 suprised here takes a full [%emt 0:20:00] on this move} Bb4 {[%clk 1:54:25]}
316 8.3. The Clock tag, which is only relevant during live transmission of a game,
320 8.4. PGN generated directly from DGT boards will have a clk command like the one
328 may be multiple commands in a single comment.
354 Note also that there is already a [Time] tag - this denotes the time of the game