Re: Nested, titled sections
Jeffrey C. Jacobs <[email protected]>
| Newsgroups | gmane.text.docutils.user |
|---|---|
| Message-ID | <[email protected]> |
David Goodger <goodger <at> python.org> writes:
> > What's the right way to specify a limited-scope subsection?
>
> Use "topic" or "sidebar" directives. Probably topic:
> http://docutils.sourceforge.net/docs/ref/rst/directives.html#topic
Thank you David. I looked over the documentation for topic and sidebar
and I think maybe this way of specifying isn't ideal as these would be
normal text elements in the flow. It goes back to the formal definition
of how one writes a screenplay using RST.
Right now I'm using Field Lists but that won't allow embedded
admonitions so I'm looking for a better way.
Currently::
:Character:
`(action)`:parenthetical:
Dialog
Proposal with topics::
.. topic:: Character
.. admonition:: parenthetical
(action)
Dialog
Proposal with Definition Lists::
Character
.. admonition:: parenthetical
(action)
Dialog
I'm not sure if I'm able to embed adminitions in a topic or a definition
list but as suggested in the developers list an admonition is a better
document type than a role since parenthetical is typically on a line by
itself.
I do worry though about how wordy the admonitions are relative to how
concise the current specification is, but I think processing of the
generated doctree would be incorrect. So thanks again for your help but
if you have more suggestions on how to resolve this issue I'd greatly
appreciate it.
Jeffrey.
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF