Indeed, this is a problem. The code used for automation recognizes the white and black pieces through GAME-code operators isupper and islower, which only detect the cases where all characters in the piece names are letters of the specified case. AFAIK there are no similar GAME-code commands that ignore non-alphabetic characters, or just look at the first alphabetic character of the string they act on. So piece sets with non-alphabetic names (or mixed case) are basically incompatible with GAME code.
It is a weak spot of GAME Courier anyway that the names of the image files have to 'leak' into the code; this whole concept of piece sets is an annoying limitation. It would be much better if the mapping internal name -> image URL could be arbitrarily specified on a piece-by-piece basis during creation of a piece set, rather than forcing the user to choose between a limited number of sets, none of which satisfying the needs. If the existence of some standard sets would be desirable for simple applications (e.g. 'modest variants'), they can always be provided as standard 'piece-include files', which pre-define the mappings.
Indeed, this is a problem. The code used for automation recognizes the white and black pieces through GAME-code operators isupper and islower, which only detect the cases where all characters in the piece names are letters of the specified case. AFAIK there are no similar GAME-code commands that ignore non-alphabetic characters, or just look at the first alphabetic character of the string they act on. So piece sets with non-alphabetic names (or mixed case) are basically incompatible with GAME code.
It is a weak spot of GAME Courier anyway that the names of the image files have to 'leak' into the code; this whole concept of piece sets is an annoying limitation. It would be much better if the mapping internal name -> image URL could be arbitrarily specified on a piece-by-piece basis during creation of a piece set, rather than forcing the user to choose between a limited number of sets, none of which satisfying the needs. If the existence of some standard sets would be desirable for simple applications (e.g. 'modest variants'), they can always be provided as standard 'piece-include files', which pre-define the mappings.