What pain point are you perceiving?.
I'm reviewing Marked documentation, attempting to create a custom setup where, it transforms new lines starting with 'notice: ' into a specifically formatted DIV. By my understanding I need to first add a custom named tokenizer and then a renderer based on it? Or am I going about this the wrong way?

Describe the solution you'd like
I'd like to ea

Take this input.db file:

<chapter xml:id="_responsibility">
<simpara>See regular link: <xref linkend="SEC-Definitions"/>.</simpara>
<simpara>See link with endterm: <xref linkend="SEC-Definitions" endterm="link"/>.</simpara>
</chapter>
<chapter xml:id="SEC-Definitions">
<title>Definitions</title>
<simpara>Some definitions.</simpara>
</chapter>

Convert it to output.docx:

Feature request

An option to put the sidebar on the right instead of the left

I'd like there to be an option to have code blocks be line wrapped. Maybe a check box for it in Rendering -> "Syntax highlighted code block" next to "Show line numbers" etc.?

If I try hard enough I can dig through the css files in Contents/Resources/Prism/themes and change "white-space: pre;" to "white-space: pre-wrap;", but doing so breaks the code signature of the app. And that's not a very n

Clearly describe the bug

currentcolor (all lowercase) should be acceptable casing. CSS Color Module Level 4 defines it like that. Info from above link:

Multi-word keywords in CSS usually separate their component words with hyphens. currentcolor doesn’t, because it was originally introduced in SVG as a special attribute value spel