No dashes in strategy move names. See Fig. 21 in the paper on GTE

[stengel]

"Solved" by using commas instead of dashes. Should be a choosable parameter, blank no good
as used as separator in strategic form. Also omitted "," if moves are single letters have been implemented - although sometimes commas still appear with single letters. Not clear why.

Generated strategy names in the extensive form are too long
with the intermediate dashes. Even worse, these dashes become
long dashes in conversion from XFIG to PDF.
Solution: no dashes, just juxtaposition for single-letter
move names. At some further point, we can extend this as
follows: If a move has 2 or more letters, insert a comma
before and after, and change at the end all double commas
into single blanks and remove leading and trailing commas.
(The "comma" character should be a parameter that can later
maybe configured; use a single routine for that, which is
easy to write - the same for blanks instead of commas can
also be used to pre-process input strings that may have
multiple blanks in them.)