From: Guenter M. <mi...@us...> - 2015-04-20 07:14:29
|
On 2015-04-19, David Goodger wrote: > On Apr 19, 2015 3:22 PM, "Guenter Milde" <mi...@us...> wrote: >> On 2015-04-14, David Goodger wrote: >> > On Tue, Apr 14, 2015 at 3:13 PM, Jeffrey C. Jacobs >> ><dar...@ti...> wrote: >> >> David Goodger <goodger <at> python.org> writes: ... >> The idea was to use a block element instead of a role. This could be a >> generic admonition, an (ab)used pre-defined admonition (note, hint, ...) > or >> a custom directive (whether the parentheses are added by the directive or >> required in the source is up to the implementation):: >> Character >> .. parenthetical:: action >> Dialog > That does work. But I'd recommend a less verbose option. >> Or you could simply put the `action` in a separate paragraph: >> Character >> `action` >> Dialog > Yes, but I believe there should not be any blank lines between sections of > dialog and parentheticals (in the output). Of course, a transform could do > that too. A custom paragraph style for "parenthetical" paragraphs should suffice. (Most printed documents use indendation instead of vertical space as paragraph separator anyway.) >> Another, [...] option would be to (ab)use the >> "classifier" of a definition list term ... ... > Unfortunately that won't work, because such parentheticals can occur in > arbitrary positions (not just at the beginning of dialog, but in the middle > or at the end), and there can be multiple instances. The pattern doesn't > match definition list classifiers at all. OK. Then it is up to role (inline element) vs. directive (block element). It should even be possible to transform all "parenthetical" role nodes to block elements (paragraphs with class value "parenthetical", say) in a transform. +1 less verbose markup (no need for blank lines) -1 the role can be used at places where no block level markup is allowed -- requires test and error mechanism that comes "for free" if you use a directive. Günter |