Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.1

Bug #10912 gxh8Q recognized as invalid
Submitted: 2007-05-03 02:16 UTC
From: stbrie Assigned: cellog
Status: Closed Package: Games_Chess (version 1.0.0)
PHP Version: Irrelevant OS: windows
Roadmaps: (Not assigned)    
Subscription  


 [2007-05-03 02:16 UTC] stbrie (Jack Nerad)
Description: ------------ the promotion move: gxh8Q where a pawn takes a piece on the back rank and is promoted to queen is recognized as invalid. Test script: --------------- $standard->moveSAN('gxh8Q'); Expected result: ---------------- I would expect the software to accept the move and recognize it as valid SAN, which I believe it is. Actual result: -------------- Error message: not valid algebraic move

Comments

 [2007-05-04 03:53 UTC] cellog (Greg Beaver)
it should be gxh8=Q If you can find the SAN source that defines gxh8Q as valid SAN, I'll fix it. None of my searching found this example, but I may not have been comprehensive enough. Until then, I'm marking this as bogus
 [2007-05-04 21:32 UTC] stbrie (Jack Nerad)
How about the FIDE laws of chess explanation of Algebraic notation? Search the page http://www.fide.com/official/handbook.asp?level=ee102 using your browser for 'E12', which will bring you to the pertinent section. FIDE does not use the =Q or ={Piece} to describe promotion. Rather, it omits the = reserving it for a draw symbol (exclusively?). Wikipedia mentions that using = is an alternative to the omission of same. http://en.wikipedia.org/wiki/Algebraic_chess_notation#Pawn_promotion You can leave it 'bogus' if you want. I've already got a workaround in my stuff, but I thought I'd report it anyhow.
 [2007-05-04 23:25 UTC] cellog (Greg Beaver)
no, that's good enough for me - I also coincidentally noticed an "h8Q" in Chessbase today, so I am opening this up.
 [2007-06-17 05:46 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.