I think I've more or less decided that I want a #reStructuredText to SXML parser in R6RS #Scheme.
I'm going to try to spend 30 minutes a day working on one, and see how I get on.
rST has been a text-based markup of choice for many years (alongside org-mode), and I was always disappointed by the ascendancy of the inferior #Markdown. It deserves an independent reimplementation.
I finally got around to rebuilding my website using #Python #Django and #reStructuredText . It is now allows me to easily write about projects and write blog posts.
One of my biggest and most useful (to me) hobby projects is my language learning tool #xiaolongdictionary . The last couple of days I have written about the tool and its features extensively [1].
I think I will still improve the writing and extend it in the future.
[1]: https://web.xiaolong-hosting.com/projects/project/xiaolong-dictionary
#Papirus 's icon for #ReText is annoying me right now. I'll just do something about that.
By the way, is there an accepted logo for #reStructuredText anywhere, other than the LaTeX-like wordmark on Wikipedia?
I just published a Sphinx extension to add colspan and rowspan to .rst tables: https://pypi.org/project/rst-table-span/
@bithive @timpritlove Me too, because it has a specification from the beginning and not a post specification effort as common mark.
However, Markdown is easy to learn and suits use cases that are enough for many users.
#Markdown Is a Disaster: Why and What to Do Instead
https://karl-voit.at/2025/08/17/Markdown-disaster/
Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.
#publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin
Peter Brett
Zelphir Kaltstahl
AndrewC
ragectl
Rasmus "raek" [rɛːkʰ] SA5RJS
No Time To Play
Nico
GripNews
Daniel Bohrer
Karl Voit 
