Lines Matching refs:pair

284 are relatively rare.  An example of this is the "FEN" tag pair; it may have a
285 long tag value, but this particular tag pair is only used to represent a game
326 pair of quote characters (ASCII decimal value 34, hexadecimal value 0x22).  An
330 two adjacent backslashes.  Strings are commonly used as tag pair values (see
380 A PGN game is composed of two sections.  The first is the tag pair section and
381 the second is the movetext section.  The tag pair section provides information
389 8.1: Tag pair section
391 The tag pair section is composed of a series of zero or more tag pairs.
393 A tag pair is composed of four consecutive tokens: a left bracket token, a
397 The same tag name should not appear more than once in a tag pair section.
405 any adjacent pair of tokens in a tag pair.
416 have a tag pair spanning more than a single line.  Export format requires each
417 tag pair to appear left justified on a line by itself; a single empty line
418 follows the last tag pair.
426 The tag pair format is designed for expansion; initially only strings are
427 allowed as tag pair values.  Tag value formats associated with the STR (Seven
432 structure of a tag pair remains the same: left bracket, tag name, tag value,
469 pairs to conclude the tag pair section.  This helps simple scanning programs to
470 quickly determine the end of the tag pair section and the beginning of the
643 symbol tokens on the same line in the movetext.  As with the tag pair section,
729 are needed for use in some tag pair and annotation constructs.
888 movetext of a game must match the value of the game's Result tag pair.  (While
986 vary by locale.  This tag pair is associated with the use of the EPD opcode
993 vary by locale.  This tag pair is associated with the use of the EPD opcode
1000 will vary by locale.  This tag pair is associated with the use of the EPD
1017 This tag pair is associated with the use of the EPD opcode "eco" described in a
1024 Chess_ database.  This tag pair is associated with the use of the EPD opcode
1040 corresponding to the location given in the Site tag pair.
1122 position is given in the "FEN" tag pair.  This tag must appear for a game
1124 tag pair must also appear.
1131 document.  If a SetUp tag appears with a tag value of "1", the FEN tag pair is
1393 or incomplete Date tag pair data are to be avoided.  Any question mark
2452 The usage is similar to that of the "ECO" tag pair of the PGN standard.
2509 The usage is similar to that of the "NIC" tag pair of the PGN standard.
2667 <tag-section> ::= <tag-pair> <tag-section>
2670 <tag-pair> ::= [ <tag-name> <tag-value> ]
2803 The general marker pair (0x05/0x06) is used to help represent game data that
2825 20.4.2: Marker 0x02: tag pair
2827 Marker 0x02 is used to indicate a single tag pair.  There are two items that
2828 follow marker 0x02 to form the "tag pair" record; in order these are:
2830 1) string-1 (tag pair name)
2832 2) string-1 (tag pair value)
2858 permitted to appear within a general game begin/end record pair.  The general
2888 the recursive annotation is completely described between the bracket pair.  The
2899 pair.  The rav-begin/data/rav-end structures can be nested.