David Abrahams wrote:
> 1. Escaping the colon in the field list doesn't work; it's treated as
> the end of the field.
> :Case Study\: Event Handling: This chapter will be dropped.
From the markup spec
A field name is made up of one or more letters,
numbers, whitespace, and punctuation, except colons (":").
That ought to be fixed to allow escaped colons. Will add it to the
> 2. I can't use the "breaking non-space" to force space into the start
> or end of literal text:
> ``\ foo \ ``
> ^^ ^^
Again, from the markup spec
No markup interpretation (including backslash-escape
interpretation) is done within inline literals.
> Maybe these behaviors "shouldn't" be surprising, but, well, they
#1 perhaps, but #2 is definitely a feature! :-)
David Goodger <http://python.net/~goodger>