Oh. Well here’s my request: I would like an extension that makes a segmented substitutions for different kinds of casing. So you could write “[upper case]some stuff[end casing]” and the stuff would get printed in upper case. Or, and this is the one I really want, you could write “[capitalize]some stuff[end casing]” and the first letter of the stuff would get capitalized.
This may seem trivial, but I have just been writing something where I’d like to put a couple of lists at the beginnings of sentences and OY GEVALT. One list came from Emily Short’s Complex Listing extension and I had to write about seven different phrases to be able to tell the phrase that actually prints the text that I wanted to start with a capital letter. The other seemed like it should be a simple “[A list of things that…]”, but the list started with a number, and the “[A list of]” call doesn’t capitalize numbers.
This seems like it would either be pretty simple to do or very complex. The interaction with Complex Listing in particular seems like it might be kind of hairy; since the phrase in Complex Listing that does the work (“dump list”) directly says stuff instead of generating a text/indexed text, perhaps the only way to do this is to use Text Capture to buffer the text inside the substitution, apply the casing to that, and then spit it out? Oy gevalt, again. But without something like this Inform will be pretty intolerant of different ways of constructing sentences.
In general, I wish the list writer weren’t so inaccessible to Inform 7, though its behavior is clearly quite involved so I can see why it’s something of a black box. Also, since there isn’t a thread for Complex Listing, it would be good if it could be made to play nicely with numbers (it produces output like “You can see here a pencil, a paper, an eraser, a clipboard, a desk, a desk, a desk, and a desk”) but that would be hard to do.
EDIT: OK, so that wasn’t exactly concise.