Author: Mathieu Pagé
Date: 06:43:01 06/09/04
Go up one level in this thread
><?xml version='1.0'?>
><Games>
><Game>
><Event>"ICC tourney 517 (15 1)"</Event>
><Site>"Internet Chess Club"</Site>
><Date>"2004.04.23"</Date>
><Round>"1"</Round>
><White>"PostModernist"</White>
><Black>"Trueno"</Black>
><Result>"1-0"</Result>
><ICCResult>"Black resigns"</ICCResult>
><WhiteElo>"2423"</WhiteElo>
><BlackElo>"1862"</BlackElo>
><Opening>"French: Winawer, advance variation"</Opening>
><ECO>"C16"</ECO>
><NIC>"FR.09"</NIC>
><Time>"14:04:48"</Time>
><TimeControl>"900+1"</TimeControl>
>
><Moves> 1. e4 e6 2. d4 d5 3. Nc3 Bb4 4. e5 Nc6 5. Nf3 Nge7 6. Bd3 Bxc3+
>7. bxc3 O-O 8. Bxh7+ Kxh7 9. Ng5+ Kg8 10. Qh5 Re8 11. Ba3 Nb4 12. Bxb4 c5
>13. Bxc5 Qd6 {Black resigns} 1-0 </Moves>
></Game>
></Games>
Hi,
I'm not sure if I'm not the only one thinking like this, but I really hate the
algebraique notation that pgn use. It is maybe more human-readable, but it is a
real pain to parse. I prefer long algebraique notation (1. a2a4 e7e6 ...) The
converter from pgn to xml will need some chess knowledge in order to do the
translation, but I think that it will make the parsing of the <Moves></Moves>
tag lot faster since we will not have to do move generation to translate the
move to our internal move format (Maybe not for every engines, but for most).
dont you think ?
Mathieu P.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.