From: Eric macshogi com> Date: 30 jan 2007 Subject: PSN description Hello, I remember a mail in the list talking about the PSN limitation=20=20 regardings variations, comments and so on. I have met those=20=20 limitations as well, and I have chosen to extend the PSN format to be=20= =20 able to store all I needed in a game score. Those extensions are already available in the shogi gmes collection,=20=20 in my page. For variations, I use parenthesis ( and ). Each time you want to open=20= =20 a variation, you add a ( in your gamescore. You close it with a ).=20=20 There is no limitation on the depth of variations, so no limitations=20=20 on the use of ( and ). As soon as each open parenthesis is closed. By=20= =20 construction, the depth is limited to 16 in MacShogi, but even if=20=20 this is enough in the majority of cases, this limitation should be=20=20 removed. For comments, I have chosen to use brackets, so that everything which=20= =20 is between { and } should be regarded as a comment. If you want to=20=20 explain a sequence of moves with comments, such as in the well known=20=20 Reijer's This week in Shujan Shogi, then it is better to open a=20=20 variation and to limit the comment part to the text itself. So that=20=20 you will be able to see the board automatically even in the orginal=20=20 comment. A comment can be added for any move or before the first move=20= =20 as well (just after the games description). For pratical use, I have preferred to encode all comments in the UTF8=20= =20 encoding. It is very convenient for all Japanese names but I=20=20 understand that it is not always easy to handle in all operating=20=20 systems. I have added other improvements concerning the moves notation. They=20=20 are : - allowing shorcut for capture : "Px1d xL" instead of "Px1d Lx1d" - allowing short notation in case of multiple pieces controlling the=20=20 same square : "G45b" instead of "G4a5b" or "Sc4d" instead of "S3c4d" The idea is to use a minimum of digits or letters for each move. In a=20= =20 single game, this is not important, but for the complete games=20=20 collection, those bytes are rapidly converted in kilobytes. Another idea was to implement easily the complete kifu notation=20=20 later : in the kifu notation, you need to handle the "right",=20=20 "straigth", "left" description often, which are not in the PSN=20=20 description at all. I have added another point : I specify the time used in minute for a=20=20 move in brackets without space or comment : {3} for 3 minutes for=20=20 example. I wanted a simple way to store them. This is the only case=20=20 where two "comments" can be added for a move. Usually, when two=20=20 comments are found for a move, they are automatically concatened and=20=20 output as one comment only. Here are my two cents for the PSN format. Best shogi wishes, =C9ric ---------------- Study Shogi and read shogi reportages at http://eric.macshogi.com/ The first Mac OS X Shogi Database Program at http://www.macshogi.com/ --^---------------------------------------------------------------- This email was sent to: = shogi-l shogi net EASY UNSUBSCRIBE click here: http://topica.com/u/?a2i6Ys.= aBVYf3.= c2hvZ2kt Or send an email to: shogi-unsubscribe topica com For Topica's complete suite of email marketing solutions visit: http://www.topica.com/?p=3DTEXFOOTER --^----------------------------------------------------------------