@HG: I'm embarrassed to answer you. I see Betza's notation as a convenient and intuitive way of describing the moves of a chess piece. I believe XBetza's notation has another goal, that of being able to be understood by an AI for the cases not covered by the basic notation. In that respect, what you have done works. I can't say which form is the best because I am very soon lost in the deciphering (even with strong effort, I'm lost in the explanations).
I would have said that a Ship should be something like F&$vR, I use other characters as examples, but they could be anything, & meaning "then" and $ meaning "away from the starting square in both x and y". A Gryphon would be F&$R, a Snake vW&$B, an Osprey D&$B. That would permit to differentiate a N&$B (Unicornio from Grant Acedrex) from a N&$R (used in some large CVs).
But this is just a "user's" point of view, ignorant of the constraint of programming and consistency with the rest of the XBetza language.
@HG: I'm embarrassed to answer you. I see Betza's notation as a convenient and intuitive way of describing the moves of a chess piece. I believe XBetza's notation has another goal, that of being able to be understood by an AI for the cases not covered by the basic notation. In that respect, what you have done works. I can't say which form is the best because I am very soon lost in the deciphering (even with strong effort, I'm lost in the explanations).
I would have said that a Ship should be something like F&$vR, I use other characters as examples, but they could be anything, & meaning "then" and $ meaning "away from the starting square in both x and y". A Gryphon would be F&$R, a Snake vW&$B, an Osprey D&$B. That would permit to differentiate a N&$B (Unicornio from Grant Acedrex) from a N&$R (used in some large CVs).
But this is just a "user's" point of view, ignorant of the constraint of programming and consistency with the rest of the XBetza language.