On 2010-10-16, Vinay Sajip wrote:
> On Oct 16, 2:25 pm, Roberto Alsina <rals...@netmanagers.com.ar> wrote:
>> Why not just use a topic directive with the literalinclude inside it?
> Does it give as much flexibility?
Is it a case so often used by the majority of Sphinx users that it
merits special handling?
> How would captions after the content be handled?
Using a rubric instead?
The "rubric" directive inserts a "rubric" element into the document
tree. A rubric is like an informal heading that doesn't correspond to
the document's structure.
The following option is recognized:
class : text
Set a "classes" attribute value on the rubric element. See the
class directive below.
Example:
.. rubric:: My precaption
:class: precaption
.. literalinclude:: examples/example.txt
.. rubric:: My postcaption
:class: postcaption
> I may of course want to use topics elsewhere and not want to change
> the CSS for the .topic selector. Using the topic directive appears to
> add this class to the topic div.
But with a child selector, you could also create a rule for just
these headings...
--
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to sphinx-...@googlegroups.com.
To unsubscribe from this group, send email to
sphinx-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en.
