I just learned that #commonmark treats a tab indentation as 4 spaces worth. Which leads to very weird results when spaced and tabs are combined, e.g. to align with long enumeration markers (numbers above 10 or 100 even) or blockquote markers.
Oh my.
I just learned that #commonmark treats a tab indentation as 4 spaces worth. Which leads to very weird results when spaced and tabs are combined, e.g. to align with long enumeration markers (numbers above 10 or 100 even) or blockquote markers.
Oh my.
What in the world authors of the #CommonMark specification thought when they established https://spec.commonmark.org/0.31.2/#example-540 ; really? How much is this example supported by the current implementations?
RE: https://graz.social/@publicvoit/115875810144458821
I really do like how #SilverBullet is explaining the consequences of using their version of #Markdown on https://silverbullet.md/Markdown (#CommonMark).
With statements like that, people learn about the consequences of using that tool.
They can either accept this or think about the negative effects before investing too much energy and data.
I really urge any (#MD-)tool to include such a warning statement on their project page. It's for the benefit of your users.
One of the reasons why I most probably would recommend switching to SilverBullet if you - for some reason - can't use #orgmode with #Emacs which is IMO the optimum tool for many set of requirements: https://karl-voit.at/2021/01/18/tool-choices/
I'll migrate my wife's #PKM from #logseq (recent changes are a no-go to me) to SilverBullet or preferably Emacs. My upcoming #GLT26 Org-mode workshop (no recording) will tell her.
Why #Markdown's emphasis syntax (**) fails outside of Western languages: A deep dive into #CommonMark's “delimiter run” flaws and their impact on #CJK users.
A must-read for anyone interested in #internationalization and the future of Markdown:
https://hackers.pub/@yurume/019b912a-cc3b-7e45-9227-d08f0d1eafe8
One Open-source Project Daily
Markdown parser, done right. 100% CommonMark support, extensions, syntax plugins & high speed
https://github.com/markdown-it/markdown-it
#1ospd #opensource #commonmark #javascript #markdown
ok, backport of #flexmark ext-typographic to #commonmark #java is a bust. the parser is just too different. different approach needed. post-processor... or pre-processor? shocked to discover btw, apparently no-one ever ported #smartypants to java? what, did they think it was beneath them?
i should have known this would happen. Day two of working with #commonmark-#java and I'm already writing an extension.
i *need* smart quotes & typography. only existing extension for it i found is in #Flexmark... which seems sadly to have fallen moribund, but it's also depending on features of its forked parser than the OG commonmark-java doesn't have. because you need contextual awareness. Seeing what I can do with SourceSpans but it might need to be a PostProcessor instead.
#MarkDown too
#CommonMark and its variants, like #gfm, allow to span setext-style header across multiple lines:
Line one
and two
--------
Note that this allows to insert line breaks in headings
The Hobbit\
or\
There and Back Again
==================
Why do I like #OrgMode as a markup language....
Compare the output of:
```
pandoc --list-extensions=X
```
for #CommonMark #Markdown, and OrgMode...
Markdown dialects have yet to truly converge on a nice set of features....
OrgMode has...
The trouble I have faced tonight: You can have alerts in CommonMark but not Markdown, and you can have citations in Markdown but not CommonMark. This /is/ a limitation of #Pandoc but the point remains...
In OrgMode, I can have many features from many a Markdown dialect. Sadly, #Hakyll doesn't support metadata extraction from OrgMode markup yet... There is a trick though! That is for later...
Line breaks within a paragraph are treated as spaces in Markdown. However, this gives bad results in East Asian languages, where spaces between words are unusual. Use
pandoc -f markdown+east_asian_line_breaks
to ensure that line breaks between East Asian wide characters get ignored.
The extension also works with #CommonMark (commonmark), GitHub Flavored Markdown (gfm), and pandoc's CommonMark extension (commonmark_x).
Just discovered the interactive #Markdown tutorial from #Commonmark: https://commonmark.org/help/ What a great resource!
(Discovered it through #Jupyter, where they have embedded this into the help menu.)
Just ran into a basic flaw in the commonmark spec/parser.
https://github.com/commonmark/commonmark-spec/issues/807
Going to try and work around it in Kitten as I’m using Markdown-it, which implements the commonmark spec, and exhibits the same behaviour.
(This is going to delay the next release as I’m considering it a blocker.)
#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
New #blog post: Why I Love Markdown
https://rldane.space/why-i-love-markdown.html
1131 words
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @twizzay @orbitalmartian @adamsdesk @krafter @roguefoam @solusspider @clayton @giantspacesquid
(I will happily add/remove you from the chorus upon request! :)
#rlDaneWriting #Technology #Markdown #CommonMark #Wiki #WikkaWiki #MediaWiki #TiddlyWiki #ADHD #Humor #ADHDHumor #HumoUr
Package Manager for Markdown
I'm working on a project that is intended to encourage folk to make markdown text files which can be bundled together in different bundles of text files using a package manager.
Question for coders; Which package manager would you suggest I use?
Main criterias (in order) are:
1. Easy for someone with basic command line skills to edit the file and update version numbers and add additional packages.
2. All being equal, more commonly and easy to setup is preferred.
#Markdown #CommonMark #PackageManager #Programming #Dev
#NPM #RubyGems #Cargo #PickingAMastodonInstance
#Ruby #Python #Rust #Javascript #NodeJs #Lisp #CommonGuide
Parsing the start and end of projects for the notification queue
Ah, good to know. I should be more cognizant of #CommonMark
Questo sito contiene un utile guida con esercizi interattivi per imparare il #Markdown:
Rettifico come da commenti: in realtà è il sito ufficiale del #CommonMark, una sua possibile standardizzazione. Infatti ne esistono molte varianti.
Getting close to being happy with how I organise the content for a module I have been entrusted with.
It is a #Git organised set of notes for a #flippedClassroom module.
All notes are written in #CommonMark (#OrgMode if it was just me ;-))
#Pandoc is at the heart of preparing the written notes.
+ Custom templates help satisfy local branding requirements
+ Pandoc features enable #moodle compatible HTML to be generated with #MathJax maths and embedded resources. (Moodle is just a carrier!)
+ Use #CSL to generate references
#Make enables targets to generate ALL THE TARGETS, ensuring correct pandoc options are used:
+ Standalone HTML for local use, with #SimpleCSS for styling
+ HTML optimised for Moodle;
+ LaTeX;
+ PDF (via LaTeX)
+ DOCX
Slides and assessment specs are still LaTeX.
Ja, das gefällt mir schon besser.
#CommonMark / #ShowDown ist schlank, lässt sich gut in #Moodle verwenden und produziert einen style-baren HTML-Code.
Was müsste man tun, damit das die hakelige Markdown-Implementierung offiziell ersetzen kann? Immerhin funktioniert ShowDown auch serverseitig. 🤔
Was mir jetzt noch fehlt, ist ein "Präsentationsmodus" für das Textfeld. ...
Vorerst wird das wohl nichts mehr, aber LisScript und Cryptpad können es ja immerhin auch, also sollte da doch irgendow ein Weg sein.