#commonmark — Public Fediverse posts

#Markdown has horrible edge cases and despite the valiant effort of #CommonMark, the dialects seem to diverge and multiply over time. I consider switching my personal stuff to #djot where possible: https://djot.net/

Ideas:
- Stop working on #smu https://github.com/karlb/smu and maintain either https://github.com/karlb/cdjot or https://github.com/karlb/minipandoc instead
- Use https://github.com/karlb/gemtext.lua to generate #gemtext (for #geminiprotocol instead of the unmaintained https://github.com/karlb/md2gemini

Thoughts?

#Markdown has horrible edge cases and despite the valiant effort of #CommonMark, the dialects seem to diverge and multiply over time. I consider switching my personal stuff to #djot where possible: https://djot.net/

Ideas:
- Stop working on #smu https://github.com/karlb/smu and maintain either https://github.com/karlb/cdjot or https://github.com/karlb/minipandoc instead
- Use https://github.com/karlb/gemtext.lua to generate #gemtext (for #geminiprotocol instead of the unmaintained https://github.com/karlb/md2gemini

Thoughts?

#Markdown has horrible edge cases and despite the valiant effort of #CommonMark, the dialects seem to diverge and multiply over time. I consider switching my personal stuff to #djot where possible: https://djot.net/

Ideas:
- Stop working on #smu https://github.com/karlb/smu and maintain either https://github.com/karlb/cdjot or https://github.com/karlb/minipandoc instead
- Use https://github.com/karlb/gemtext.lua to generate #gemtext (for #geminiprotocol instead of the unmaintained https://github.com/karlb/md2gemini

Thoughts?

🥳 New Kitten¹ release!

Implemented workaround:

There is a bug in the CommonMark spec that results in preformatted code with empty lines nested in an HTML node not rendering correctly.²

In Kitten, this previously threw an error (see #294³ and also #318⁴).

Kitten now works around the issue in its own parser.

Full change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md

Enjoy!

:kitten:💕

¹ https://kitten.small-web.org
² https://github.com/commonmark/commonmark-spec/issues/807
³ https://codeberg.org/kitten/app/issues/294
⁴ https://codeberg.org/kitten/app/issues/318

#Kitten #KittenRelease #SmallWeb #SmallTech #CommonMark #spec #bug #workaround #Markdown #web #dev #NodeJS

🥳 New Kitten¹ release!

Implemented workaround:

There is a bug in the CommonMark spec that results in preformatted code with empty lines nested in an HTML node not rendering correctly.²

In Kitten, this previously threw an error (see #294³ and also #318⁴).

Kitten now works around the issue in its own parser.

Full change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md

Enjoy!

:kitten:💕

¹ https://kitten.small-web.org
² https://github.com/commonmark/commonmark-spec/issues/807
³ https://codeberg.org/kitten/app/issues/294
⁴ https://codeberg.org/kitten/app/issues/318

#Kitten #KittenRelease #SmallWeb #SmallTech #CommonMark #spec #bug #workaround #Markdown #web #dev #NodeJS

🥳 New Kitten¹ release!

Implemented workaround:

There is a bug in the CommonMark spec that results in preformatted code with empty lines nested in an HTML node not rendering correctly.²

In Kitten, this previously threw an error (see #294³ and also #318⁴).

Kitten now works around the issue in its own parser.

Full change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md

Enjoy!

:kitten:💕

¹ https://kitten.small-web.org
² https://github.com/commonmark/commonmark-spec/issues/807
³ https://codeberg.org/kitten/app/issues/294
⁴ https://codeberg.org/kitten/app/issues/318

#Kitten #KittenRelease #SmallWeb #SmallTech #CommonMark #spec #bug #workaround #Markdown #web #dev #NodeJS

🥳 New Kitten¹ release!

Implemented workaround:

There is a bug in the CommonMark spec that results in preformatted code with empty lines nested in an HTML node not rendering correctly.²

In Kitten, this previously threw an error (see #294³ and also #318⁴).

Kitten now works around the issue in its own parser.

Full change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md

Enjoy!

:kitten:💕

¹ https://kitten.small-web.org
² https://github.com/commonmark/commonmark-spec/issues/807
³ https://codeberg.org/kitten/app/issues/294
⁴ https://codeberg.org/kitten/app/issues/318

#Kitten #KittenRelease #SmallWeb #SmallTech #CommonMark #spec #bug #workaround #Markdown #web #dev #NodeJS

🥳 New Kitten¹ release!

Implemented workaround:

There is a bug in the CommonMark spec that results in preformatted code with empty lines nested in an HTML node not rendering correctly.²

In Kitten, this previously threw an error (see #294³ and also #318⁴).

Kitten now works around the issue in its own parser.

Full change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md

Enjoy!

:kitten:💕

¹ https://kitten.small-web.org
² https://github.com/commonmark/commonmark-spec/issues/807
³ https://codeberg.org/kitten/app/issues/294
⁴ https://codeberg.org/kitten/app/issues/318

#Kitten #KittenRelease #SmallWeb #SmallTech #CommonMark #spec #bug #workaround #Markdown #web #dev #NodeJS

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

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.

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.

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.

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.

#PIM #publicvoit

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.

#PIM #publicvoit

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.

#PIM #publicvoit

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.

#PIM #publicvoit

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.

#PIM #publicvoit

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

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

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

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

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

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

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

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

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

#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
==================

#Heading #Markdown

#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
==================

#Heading #Markdown

#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
==================

#Heading #Markdown

#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
==================

#Heading #Markdown

#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
==================

#Heading #Markdown

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).

#pandoc #Markdown #Japanese #Korean #Chinese

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).

#pandoc #Markdown #Japanese #Korean #Chinese

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).

#pandoc #Markdown #Japanese #Korean #Chinese

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).

#pandoc #Markdown #Japanese #Korean #Chinese

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).

#pandoc #Markdown #Japanese #Korean #Chinese

#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

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 #commonMark #parsing #bug

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! :)

#100DaysToOffload #20

#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

https://codeberg.org/splitcells-net/net.splitcells.network/src/commit/6e1a2cc357a2da9fb20b0c15337fdd8d2213e56c/projects/net.splitcells.website.server/src/main/java/net/splitcells/website/server/notify/NotificationQueueParser.java

#Java #CommonMark #OpenSource

@dmoonfire @sotolf

Ah, good to know. I should be more cognizant of #CommonMark

Questo sito contiene un utile guida con esercizi interattivi per imparare il #Markdown:

https://commonmark.org/

Rettifico come da commenti: in realtà è il sito ufficiale del #CommonMark, una sua possibile standardizzazione. Infatti ne esistono molte varianti.

#CodiceSegreto #Informatica #Tecnologia