RestructuredText: warning and note directives are not properly rendered

[berndschatz]

text of warning / note directives should be rendered in a box or/and in another color.

Currently it looks like this:

note

This is a note

but it should look somehow like here -->

see also -->
https://sublime-and-sphinx-guide.readthedocs.io/en/latest/notes_warnings.html

IMHO this would be a big improvement for the readability of technical documentation with less effort for you for the implementation.

[ichordev]

Notes used to render with a little blue "info" icon, and warnings with a little yellow "warning" icon... but not anymore.

[flying-sheep]

Maybe this broke it? https://github.blog/changelog/2023-12-14-new-markdown-extension-alerts-provide-distinctive-styling-for-significant-content/

[berndschatz]

Maybe this broke it? https://github.blog/changelog/2023-12-14-new-markdown-extension-alerts-provide-distinctive-styling-for-significant-content/

This is markdown (that is designed for small blog entries),
we use/need RestructuredText (that is designed for technical documentation).

[flying-sheep]

Hold your horses, I’m with you haha. In this community discussion, they describe that they broke the rendering for the old markdown way of doing admonitions.

What I’m implying (but could have been clear about) is that maybe they still make rST render to whatever intermediate representation the old Markdown syntax rendered to and that way broke it?

Or maybe they never supported it, I don’t remember. Since they do support admonition rendering in Markdown, they should make rST and Asciidoc admonitions render the same way.

[berndschatz]

Don't know what they do, the docutils works fine, so i assume they have some own stuff: post/pre-processor
before / after using the docutils !?
Or do they implement a complete own ResT parser !?

PS: Regarding automated testing, there are probably still a few areas for improvement for ResT (and markdown):

[github-actions]

Stale issue message

[flying-sheep]

Not-a-stale-issue response

@humans please pin and make the bot go away thanks

[ErraticMaker]

Just for reference #68 was closed several years ago, because at the time it couldn't be implemented. I'm hoping that things have changed enough since then that'll be possible to provide the same experience to ReST than it is available with GFM.

[github-actions]

Stale issue message

[flying-sheep]

Still not stale. Please please add a label that shuts up the bot!

[flying-sheep]

@jmeridth could you please take a look here? Either #68 needs to be reopened or this needs to be triaged and labelled correctly.

The closing reason for #68 is no longer valid

[jmeridth]

@jmeridth could you please take a look here? Either #68 needs to be reopened or this needs to be triaged and labelled correctly.

The closing reason for #68 is no longer valid

@flying-sheep Taking a look. I've also added the keep label to avoid being flagged by the stale bot. Thanks for the bump.