It breaks the whole idea of Markdown - to be as natural as possible.
This is like markdown with CSS Slap in , such a disgrace.
It is not simple and as ugly as CSS.
Quarkdown – Markdown with Superpowers
121–130 of 151 posts
Re: Quarkdown – Markdown with Superpowers
#122Cool. The biggest question for me is:
Why not LaTex or org-modes?
Tex is the superior typesetting, and since the advent of LLMs getting things done in Tex became a breeze.
Org-mode is the superior universal markup for, well everything, only downside is the default editor.
Re: Quarkdown – Markdown with Superpowers
#123For my app, I chose a slightly different approach, focusing on readability and easy handling of large Mermaid diagrams. For example, I recently added a full-screen mode with map-like navigation: https://mdview.io/s/97af684b
Re: Quarkdown – Markdown with Superpowers
#124Earlier quoted context omitted.
I'm sorry, what exactly is the issue with typst?
They made a new format with basically no accessibility. We finally got latex usable by blind people with acceptable html output, I’m not moving to something worse.
In what ways is HTML produced by transpiling LaTeX more accessible that HTML produced by Typst?
Re: Quarkdown – Markdown with Superpowers
#125If it were simple and easy to remember complex plaintext syntax, we'd all be using LaTeX to do things. Unfortuantely, thats not true. Personally, I even switch away from rst to md. Took me a while to realize, but md is easier to remember / less magic.
Re: Quarkdown – Markdown with Superpowers
#126Earlier quoted context omitted.
Would you consider "fixing" the bold syntax on v3? I have always believed that instead of **bold** and *italic*, it should be *bold* and _italic_. That extra asterisk is a poor design decision in markdown. It really makes it inconvenient to edit Markdown on a phone or tablet.
It always bugs me that _underscore_ is the syntax for italics rather than underline. I’m sure back in the old days of READMEs, long before markdown was a thing, the conventions were this: /italics/ _underline_ *bold*
Since this seems to boil down to personal choice, has anyone considered a customisable alternative? Like a frontmatter that declares which character is bold, which is italic. You could easily convert between them according to local preference, much like tabs/spaces.
Re: Quarkdown – Markdown with Superpowers
#127Earlier quoted context omitted.
It always bugs me that _underscore_ is the syntax for italics rather than underline. I’m sure back in the old days of READMEs, long before markdown was a thing, the conventions were this: /italics/ _underline_ *bold*
My /usr/bin/ folder wants to know which bit gets italicised :)
Same as in my_snake_case_name :)
Re: Quarkdown – Markdown with Superpowers
#128Earlier quoted context omitted.
It always bugs me that _underscore_ is the syntax for italics rather than underline. I’m sure back in the old days of READMEs, long before markdown was a thing, the conventions were this: /italics/ _underline_ *bold*
My /usr/bin/ folder wants to know which bit gets italicised :)
I know this is a throwaway joke, but I was interested anyway...
According to my own local Markdown formatters, the answer would be both "usr" and "bin", with the surrounding slashes removed, but the internal slash remaining. In other words:
usr/bin
(but underlined instead of italic!)
Of course, this problem is nothing new since a filename might easily be named `_my_file_`.
Re: Quarkdown – Markdown with Superpowers
#129Earlier quoted context omitted.
To me, one of the big features of markdown is it's half WYSIWYG. By that I mean, the basics reuse the way we faked formatting to do real formatting. The input is (usually) perfectly readable on its own. Even if you don't know (or remember) how to author a markdown file, you can probably still read it just fine. The tables still look like tables. The paragraphs are just paragraphs. I do still have to look up how to do…
That’s exactly why I built Quarkdown. Flat learning curve for basic formatting, powerful customizations for the rest. Spot on!
I think that's an interesting idea, but you hit the landing page and there's loads of syntax thrown in your face and you're like, man, I need to learn a lot.
But I think this kind of brings up another problem, which is that you can choose not to use stuff if you're writing, but if you're reading other people's docs or editing them, then you need to know all the syntax they use. Most OSS projects with markdown docs today, anyone can open an MR to improve them.
Re: Quarkdown – Markdown with Superpowers
#130Earlier quoted context omitted.
They made a new format with basically no accessibility. We finally got latex usable by blind people with acceptable html output, I’m not moving to something worse.
In what ways is HTML produced by transpiling LaTeX more accessible that HTML produced by Typst?
The HTML generated by LaTeX is currently very good (you can read basically every paper on arXiV in HTML). The html generated by Typst just.. doesn't really work currently. I checked a few weeks ago, tables didn't output sensibly. Looking at the docs their plan doesn't seem to be to aim for total coverage in general.