7. Just another silly TeX-inspired idea... \<, \> and \& for HTML metachars. Then we can allow the rest (and therefore arbitrary markup) to go through unmunged. Does this collide with any expected normal usage?
1. I just typed the following sentences, and realized why they were wrong:
I don't know. I think it makes more sense to require whitespace on either end of *this* or /this/.
Trying to DWIM with punctuiation is just way too hairy. But this presents another problem:
char *c; /* this points not to the original string, but to the *buffer*! */
Now how the hell do you parse that? :-) admittedly, code should probably be in whatever we're calling a verbatim envinronment, but... it's just an example, I'm sure there are other possibilites for unbalanced or ambiguous asterisks. It's the same as slashes, really: note that "/this/." as used above is also a perfectly valid *nix path.
4. We could steal from POD:
I don't think this is very intuitive if you don't write POD, though. But it is nicely logical.
Another thing to steal could be C<...> markup... we'd probably want different letters, however. U<eru> for eru
, perhaps? I would appreciate a quick shortcut for CITE and CODE, at least. V<...> for short verbatim spans? The POD idoiom for verbatim blocks is just to start a paragraph with a space (spaces at the start of subsequent lines are optional), but... i think that could be improved. [[ ... ]] outside the whole paragraph? I don't know.