Replied in thread
Ah, good to know. I should be more cognizant of #CommonMark
Recent searches
Search options
#commonmark
0 posts0 participants0 posts today
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.
commonmark.orgCommonMark
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.
Continued thread
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.
Continued thread
#LiaScript möchte mit seinem zentralen Interpreter offenbar weg von #LMS wie #Moodle und sieht sich selbst als "Open-courSe" -System, das per iframe oder SCORM eingebunden werden kann.
Die #Markdown - Quelldateien liegen dabei bei Github, Dropbox oder Nextcloud.
Ein Moodle-LiaScript-Plugin dagegen gibt es nicht. Schade.
Dann bleibt also noch der handgemachte Weg über Javascript:
- #CryptPad Presentation / Slides lassen sich themen, und dies basiert auf #CodeMirror, was noch nach Arbeit aussieht. https://codemirror.net/5/mode/markdown/index.html
- #CommonMark ist standardisiertes Markdown, und mit #ShowDown immerhin einbettbar. http://demo.showdownjs.com/
codemirror.netCodeMirror: Markdown mode
If you're thinking of using any other form of #markup than #Commonmark then please don't.
https://commonmark.org/
commonmark.orgCommonMark
Continued thread
Thanks to everyone who recommended #CommonMark - it's really cool!
If you're able to help me with this small config issue, I'd be eternally grateful.
GitHubFootnotes with only one newline? · thephpleague commonmark · Discussion #1046I've got lots of Markdown like this: Isn't this interesting[^int] to the reader? [^int]: It was not! The sample footnote code at https://commonmark.thephpleague.com/2.5/extensions/footnotes/ doesn'...
Continued thread
#Pandoc normally doesn't produce that syntax when writing Markdown, so here's a #LuaFilter for that:
CodeBlock = function (cb)
local lang = cb.classes:remove(1)
if lang then
local mdcode = pandoc.write(pandoc.Pandoc{cb}, 'markdown')
return pandoc.RawBlock(
'markdown',
mdcode:gsub('^```+', '%1 ' .. lang)
)
end
end
#Markdown syntax tip for code block attributes, yielding the best rendering results with both pandoc and on platforms such as #GitLab #GitHub, #Codeberg, etc:
``` lua {#my-id .another-class}
io.stdout:write('hi!')
```
The curly-braces syntax for attributes is ignored when read as #CommonMark, the Markdown variant used by most platforms. The above ensures that syntax highlighting still works with CommonMark, and that the other attributes get respected when converting with #pandoc.
Support for #CommonMark alert-boxes was added in pandoc 3.1.10.
> [!INFO]
> This is an informational message.
Note, however, that writer (i.e., rendering) support for this is limited, and that the `alert` extension works with CommonMark, but not with pandoc-flavored Markdown.
The syntax has been made popular by GitHub: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts
GitHub DocsBasic writing and formatting syntax - GitHub DocsCreate sophisticated formatting for your prose and code on GitHub with simple syntax.
I'm still not out of the rabbit hole of searching for an #OpenSource #PersonalKnowledgeManagement software. 
I'm gonna give a second try to @zettlr tomorrow! Their docs are *surprisingly* user-friendly and they claim to stick to the pure #CommonMark where probable. It's all the while being nice to researchers with citing, inline usage of #TeXLaTeX, #MermaidJS, and pop-over #footnotes. Provision of the simple #PDF export and #Pandoc customization are welcome, too!
But, to be fair, I may be overexaggerating how good #Zettlr is because of my recent disgust with #VendorLocking. In fact, almost anything that closely follows the common spec and is #FreeSoftware might suffice already. Having something as advanced and closer to the roots is certainly refreshing!
Replied in thread
@nixCraft Saying "GTFO" to pretty much every note-taking application that keeps adding its own stuff that's hard to overwrite, navigate and, worst of all, not compliant with #CommonMark, making viewing experience increasingly awful in programs from KWrite down to vim.
Sometimes, I have to wonder if an app like Logseq wants to justify its own 16th derivative standard for #Markdown, while keeping you locked-in to ecosystem of its maintainer. Sure, the intentions were bright, but after many years of no progress and no transparency you'd probably feel a bit uncomfortable with this grey box.
Bummer. @github doesn't support rendering markdown "definition lists", because they use cmark-gfm, which is a fork of cmark, which implements Common Mark, which still hasn't added support for markdown definition lists to their specification.
https://talk.commonmark.org/t/description-list/289
#github #cmark #commonmark #markdown
CommonMark Discussion · Description ListNot commonly found in most implementations afaik, though I quite like the semantics and it provides an opportunity for yet-another list format… Any imps that do use <dd>, <dl> etc? Or any particular reason they’ve been avoided?
Replied in thread
@edwiebe @EpiphanicSynchronicity @obsidianmd
FYI #Djot is 90% like #Markdown but as much complete as the alternatives and it is by the author of #Pandoc and #Commonmark spec:
djot.netdjot
Replied in thread
@theory @Perl Yes. I didn’t dig into the other PRs; I just thought to point out that #CPAN already has a solution for outside dependencies in the Alien namespace and went looking there.
Unfortunately it seem the #Perl #CommonMark maintainer resisted four years ago and let the PR languish. The repo itself has also not seen any commits since then either.
So good luck to all concerned. Maybe reach out directly per #PAUSE: https://pause.perl.org/pause/query?ACTION=pause_04about#takeover
pause.perl.orgPAUSE: The CPAN back stage entrance
Replied in thread
@theory @Perl This sounds like an XY problem. Why not just depend on Alien::cmark? https://metacpan.org/pod/Alien::cmark
metacpan.orgAlien::cmark - Alien wrapper for cmark - metacpan.orgAlien wrapper for cmark
Continued thread
Playground: https://djot.net/playground/
Summary of #Djot, an improved alternative to #Markdown and #Commonmark.
#Markdown / #CommonMark feature—unprefixed lines become part of the previous bullet list item or block quote:
* List item
Unindented line
<ul>
<li>List item
Unindented line</li>
</ul>
> Quoted line
Unprefixed line
<blockquote>
<p>Quoted line
Unprefixed line</p>
</blockquote>
Try it out online: https://spec.commonmark.org/dingus/
Do you use this feature?
spec.commonmark.orgcommonmark.js demo
Q1: Which one do you regularly use, why?
Q2: Which one was easier to learn for you?
Q3: What are you using it for? (Blogging, eBook, research papers, others)
#Pandoc 3 introduced #Markdown support for #wikilinks:
[[pandoc|https://github.com]]
There is no consensus across tools whether the link title should come before or after the pipe character, so pandoc supports both. Choose by enabling either of the new extensions
+wikilinks_title_after_pipe
or
+wikilinks_title_before_pipe
Works with #CommonMark, too: for GitHub wiki input, use gfm+wikilinks_title_after_pipe