Created attachment 137148 [details] [review]
doc: Fix bracket escaping in Ducktype API design file

There’s no need to escape closing brackets if the paired opening bracket
is escaped (or doesn’t need escaping).

See
https://github.com/projectmallard/mallard-ducktype/issues/16#issuecomment-362590519.

Signed-off-by: Philip Withnall <withnall@endlessm.com>

Comment on attachment 137148 [details] [review]
doc: Fix bracket escaping in Ducktype API design file

Review of attachment 137148 [details] [review]:
-----------------------------------------------------------------

I'll take your word for it.

Is https://github.com/projectmallard/mallard-ducktype the current home for the parser/de facto spec?

Is Ducktype still a good format for us to be using here?

(In reply to Simon McVittie from comment #2)
> Comment on attachment 137148 [details] [review] [review]
> doc: Fix bracket escaping in Ducktype API design file
> 
> Review of attachment 137148 [details] [review] [review]:
> -----------------------------------------------------------------
> 
> I'll take your word for it.

I tested it with the latest version of Ducktype.

> Is https://github.com/projectmallard/mallard-ducktype the current home for
> the parser/de facto spec?

Yes.

> Is Ducktype still a good format for us to be using here?

I see no downsides to using it. Ducktype is about to reach version 1.0 (I was talking to Shaun at FOSDEM), so it doesn’t seem to be going away.

I'll apply this soon.

(In reply to Philip Withnall from comment #3)
> (In reply to Simon McVittie from comment #2)
> > Is https://github.com/projectmallard/mallard-ducktype the current home for
> > the parser/de facto spec?
> 
> Yes.
> 
> > Is Ducktype still a good format for us to be using here?
> 
> I see no downsides to using it. Ducktype is about to reach version 1.0 (I
> was talking to Shaun at FOSDEM), so it doesn’t seem to be going away.

OK, I've prepared Debian packaging for v0.3 + git commits.

This was fixed in 1.12.4 and 1.13.0.