I still haven’t given up on the apostrophe stuff, and I though it might be better to make this specific problem a separate topic.
(Note that this no longer has anything to do with curly quotes. From here on we will assume that all quotes are in fact straight, no matter how they look.)
I’ve added a rule that makes ASK WHAT’S WORTH SEEING kind of work:
A first after reading a command rule (this is the really standardize apostrophes rule): if the player's command includes "what's": replace the matched text with "what is";
We could ask what is worth seeing in the New Church.
>ask what’s worth seeing
“So tell me, what should I be looking for in the New Church?” we ask.
“Other than God?” he asks dryly.
Hm — the volunteers aren’t very well trained, are they? I was expecting something about the points of architectural interest.
*** Run-time problem P39: Attempt to say a snippet value which is currently invalid: words 5 to 4.
The run-time problem clearly has something to do with changing the number of words in the input (the single word WHAT’S is changed to the two word WHAT IS.) But it also has something to do with ASK: the problem won’t happen if you type WHAT’S WORTH SEEING without the ASK.
I really don’t know where the game is trying to actually print the player input, which I assume is what “Attempt to say a snippet value” means. I suspect it may have something to do with the Smarter Parser extension, which stores the input as “the reborn command”, and does string operations on it.
Also, the Subcommands extension does things with snippets which I don’t quite understand.
EDIT: If I include the word THE anywhere in the input, the run-time problem won’t happen. Perhaps this has something to do with it triggering the cut the the rule.