Lines Matching refs:command

58 2.3 If new command structures are to be introduced they should be specified in
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
90 An embedded  command may occur at any position in a standard PGN comment, ie
94 [%clk 1:05:23]  is the embedded command string.
97 The command string is structured as follows.
100 A command name consisting of one or more alphanumeric characters.
109 The characters [% are redefined to indicate the start of a command sequence when
124 describe a generalised command syntax, not to impose a particular set of
128 example above is the proposed command name for recording move times. See section
131 In general software encountering an embedded command it does not understand
143 A command is followed by a single space and then either by a single operand or
154 [%command 1:45:12,Nf6,"very interesting, but wrong"]
156 This command has four operands, a time value, a san move value and a double
164 they terminate both the last operand and the command.
173 [%command "very tense start to the
176 This command has four operands, the first is a double quote delimitted string,
180 The command is terminated by a single ] character.
189 We propose the following commands for time handling  The first is  the command
197 format h:mm:ss (except for the mct command which requires hh:mm:ss)
202 4.2 The clk command.
208 software producing pgn from games played on DGT boards include this command
211 The clk command is intended for the *automatic* recording of time values by
216 4.3 Elapsed Game Time : the egt command
224 4.4 Elapsed Move Time : the emt command
231 4.5 Mechanical Clock Time : the mct command
264 currently displayed clock time of the running clock. As for the clk command this
320 8.4. PGN generated directly from DGT boards will have a clk command like the one
324 additional text comments and commands (cf the %emt command after whites third