Second-level nested component pairs are not parsed (ignored in output)

[chrfrantz]

The following statement contains second-order nested component pairs (see I[Rtype=choice](download) { ... }), which does not parse correctly (i.e., is suppressed in parser output).

Cac{If you A([User]) A,p(with administrator access) I[Rtype=choice](click[s]) Bdir(Additional Action) Bdir,p(in the Action Panel)} you can
A([User]) can D[Stringency=2]([may]) {I[Rtype=information](delete) the Bdir,p(selected) Bdir(edits) [OR]
I[Rtype=choice](download) {Bdir1,p(selected) Bdir1(records) [OR] Bdir2,p1(all) Bdir2(records) Bdir2,p2(that were returned by the search (i.e., are shown in the resulting table))} [OR]
I[Rtype=information](print) the Bdir(page) Cex(using one of the appropriate buttons)}

This bug should be fixed. A temporary workaround is to manually spell out all component pairs (i.e., replicate the I[Rtype=choice](download) for each individual second-order nested object (e.g., selected records; all records ...); see statement below) :

Cac{If you A([User]) A,p(with administrator access) I[Rtype=choice](click[s]) Bdir(Additional Action) Bdir,p(in the Action Panel)} you can
A([User]) can D[Stringency=2]([may]) {I[Rtype=information](delete) the Bdir,p(selected) Bdir(edits) [OR]
I[Rtype=choice](download) Bdir1,p(selected) Bdir1(records) [OR] I[Rtype=choice](download) Bdir2,p1(all) Bdir2(records) Bdir2,p2(that were returned by the search (i.e., are shown in the resulting table)) [OR]
I[Rtype=information](print) the Bdir(page) Cex(using one of the appropriate buttons)}

Bug reported by U. Brady