Live data from Hacker News

Quarkdown: A modern Markdown-based typesetting system

github.com

251–260 of 285 posts

Re: Quarkdown: A modern Markdown-based typesetting system

#251
post #82
post #60

Earlier quoted context omitted.

Last I checked Typst can't emit HTML.

They do now, experimentally. The support is getting improved a lot currently.

I've also heard that pandoc now supports typst, and will turn typst format files into html, independent of typst's own code. Have not confirmed.

Re: Quarkdown: A modern Markdown-based typesetting system

#252
post #82

Earlier quoted context omitted.

They do now, experimentally. The support is getting improved a lot currently.

It works really well, I've written three blog posts using typst. Post: https://ezb.io/thoughts/interaction_nets/lambda_calculus/202... Typst source: https://github.com/enricozb/enricozb.github.io/blob/master/t...

That Typst source looks really clean. I may go back to look into its HTML support.

Thanks for sharing!

Re: Quarkdown: A modern Markdown-based typesetting system

#253
post #223
post #185

Since 70% of comments under each of these posts are always "why not LaTeX?!", I want to start by reaffirming: yes, I do want a modern Markdown-based typesetting system. There even is a place of several of them. It would be absolutely nice to replace LaTeX, simply because it's old trash with remarkably inconvenient syntax, so, yes, a system with full control over markup is desirable. And if it necessarily increases ve…

LaTeX is not "old trash". It's one of the best piece of software ever written. Just don't import bs in your document.

I’d argue that Typst probably beats it on all levels. Have you ever seen a LaTeX document? (The question is rhetorical, of course you have) Just because it was the best thing before doesn’t mean it still is now. I’d say the only thing it still has going for it is momentum.

Re: Quarkdown: A modern Markdown-based typesetting system

#255

My first impression was this looks nothing like Markdown. It looks cool, but hardly resembles anything I've seen in Markdown before.

I felt the same way, though once I scrolled down to the LaTeX comparison it was more obvious. The first few code examples being how you define a function don't lend themselves to showcasing how markdown-esque the actual usage is.

Re: Quarkdown: A modern Markdown-based typesetting system

#256
post #253
post #223

Earlier quoted context omitted.

LaTeX is not "old trash". It's one of the best piece of software ever written. Just don't import bs in your document.

I’d argue that Typst probably beats it on all levels. Have you ever seen a LaTeX document? (The question is rhetorical, of course you have) Just because it was the best thing before doesn’t mean it still is now. I’d say the only thing it still has going for it is momentum.

I looked at the Typst documentation and from what I could tell, it has 3 hard-coded "Modes" for 3 hard-coded kinds of syntax (normal, math, code). I couldn't find any way to add any custom syntax - is there a way to do this?

Tex/LaTeX are completely syntactically extensible. For example, a logician might want to use the software with any number of their notations, or a physicist drawing Feynmann diagrams, etc. I think at one point Lillypad used it for typesetting sheet music.

Edit: i found it! https://typst.app/docs/guides/guide-for-latex-users/#package...

Re: Quarkdown: A modern Markdown-based typesetting system

#257
I get that people don't like the braces in TeX but ... :-)

I'm only half sarcastic here, I don't like them either. I have recently been using pandoc[1] to do the things they are talking about, I had added some stuff in perl using the Template Toolkit[2] to make HTML pages. My issue is that I have very different fugue states for writing vs. coding. Switching states breaks my flow so I've been trying to make the two modes as orthogonal as possible.

I'm curious if anyone has used something like this to go straight to PNG. My use case is that I have a surplus epaper display that can display pngs it fetches from the network and I've been forwarding it my todo list. Have been doing this with a LuaTeX flow but would like something a bit more seamless.

[1] Pandoc -- https://pandoc.org/

[2] Template Toolkit -- https://template-toolkit.org/

Re: Quarkdown: A modern Markdown-based typesetting system

#258

My FOSS text editor, KeenWrite[1], takes a similar approach: Markdown -> XHTML -> TeX -> PDF. The software architecture shows how you can have processor chains: https://gitlab.com/DaveJarvis/KeenWrite/-/blob/main/docs/ima... I developed KeenWrite to help write a sci-fi novel where I can use variables for character names, places, etc. See the tutorials[2] for details. For anyone still using pandoc and shell scripts, m…

For me, the issue is not document conversion and is content de-duplication. Product A and Product B manual will share number of sections. Any spelling or grammar error must be updated in Product A and B manuals. They man share the same additions.

So far LaTex has been the only solution to allow binding shared sections into multiple document builds. These are for internal and customer facing information. Only binding duplication is in the revision overview sections pertaining to each document build.

Re: Quarkdown: A modern Markdown-based typesetting system

#259
post #82

Earlier quoted context omitted.

They do now, experimentally. The support is getting improved a lot currently.

It works really well, I've written three blog posts using typst. Post: https://ezb.io/thoughts/interaction_nets/lambda_calculus/202... Typst source: https://github.com/enricozb/enricozb.github.io/blob/master/t...

Looks like typst has a "programming language" to do diagrams inline... that's a lot of effort to learn!

Re: Quarkdown: A modern Markdown-based typesetting system

#260

Would be interesting to see a compare and contrast between this and Typst, which has gotten a lot of attention recently. Kinda surprising that it isn't mentioned in their feature comparison matrix at all.

Looking at the "mock" document (https://github.com/iamgio/quarkdown/tree/main/mock) which is supposed to be a comprehensive and detailed guide for all visual elements, I don't see ways of getting anything other than basic markdown tables. How do you get merged cells? Cell formatting? Typst has some nice ways of implementing sophisticated grids and tables.

Also how do you implement things like different page numbering for front matter content and the main content? In general, the "simplicity" of markdown seems to be taking away a lot of granular control that people use LaTeX and Typst for.

Post reply on HN