https://sourceforge.net/p/docutils/support-requests/6/2023-04-18T20:43:25.037000ZRecent changes to 6: What is the proper way to register transform settings?2023-04-18T20:43:25.037000Z2023-04-18T20:43:25.037000ZGünter Mildehttps://sourceforge.net/u/milde/https://sourceforge.net56f92ff76b8312283bdfce350f685525b8c1bf29

<div class="markdown_content"><p>The "clean" way would be a custom parser component.<br/> Sub-classing <code>docutils.parsers.rst.Parser</code> is easy, <br/> specifying the custom parser to the generic <code>docutils</code> CLI is easy, too,<br/> the tricky part may be to convince Sphinx, Pelican, Nikola, etc. to use it.</p></div>

2021-08-23T21:27:31.621000Z2021-08-23T21:27:31.621000ZClément Pit-Claudelhttps://sourceforge.net/u/createsoftware/https://sourceforge.net1e399da3fcab27d55a1e571e1d4d1f65dd599022

<div class="markdown_content"><p>I have a Python package that defines custom Docutils directives and roles. It does not need a custom reader, writer, or parser: it just uses <code>directives.register_directive</code> or <code>roles.register_canonical_role</code>. Then, it runs transforms registered using <code>nodes.pending</code> nodes.</p> <p>These transforms take settings. What is the proper way to register them? One issue I'm running into is that although custom components can declare a <code>settings_spec</code>, transforms cannot.</p> <p>When I'm calling docutils myself, it's easy to use the <code>settings_spec</code> provided by <code>docutils.core.publish_*</code>.</p> <p>But when I'm calling docutils through Sphinx, Pelican, Nikola, etc, I don't have control on that parameter. So, what is the recommended way to tell Docutils about these additional settings? Should I override the <code>settings_spec</code> of the default <code>OptionsParser</code>?</p></div>