Live data from Hacker News

Gribouille 0.3.0: A Grammar of Graphics for Typst

mickael.canouil.fr

21–30 of 101 posts

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#22
post #12

Earlier quoted context omitted.

For Latex I agree thats definitely. Markdown I am unsure as Markdown is not meant for creating documents but to just have a little Richt Text Markup in READMEs and other Text files. Typst needs a compile step and altough that one is fast as hell it is still different from Markdown that renders directly from the file without an intermediary.

Right; but markdown has expanded beyond that niche. Lots of projects use markdown for other stuff - like mdbook, or for blogs. I think markdown is a great format for readme files. But for real documentation, the added features of typst are fantastic. Like, being able to write scripts, have figures and custom styling, populate data from JSON files, plugins, typography, numbered sections, footnotes and all sorts of oth…

Ordinary markdowns have had /everything/ you mention for close to 20 years, except typesetting. Academic papers and books, novels, thousands of ebooks, have been written in single file markdowns for 15 years.

Writing directly in typst is good for small things with intense typesetting like ... wedding invitations, advertisements. But it doesn't scale to serious composition by actual writers.

Writing is not typesetting.

All the forms need for the composition of all civilized text were present in word perfect 5.1, which unlike Word, Latex and Typst, permitted no typsetting during the process of writing. They were all recovered in the writers' markdowns nearly two decades ago.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#23

Earlier quoted context omitted.

For Latex I agree thats definitely. Markdown I am unsure as Markdown is not meant for creating documents but to just have a little Richt Text Markup in READMEs and other Text files. Typst needs a compile step and altough that one is fast as hell it is still different from Markdown that renders directly from the file without an intermediary.

The problem with markdown is that it's not extensible and that there is no spec. Essentially all READMEs would be better off using typst, they would make for better READMEs.

There have been theoretically precise published specs for serious markdowns for 15 years. The commonmark convention is a common specification for many including e.g the familiar simple github variant, which emphatically does have a completely perfect specification.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#24
post #7

Typst is the most important open source project of the last 5 years. I predict a future where markdown and latex are largely replaced by typst. And I couldn't be more excited. It is such a stepup from markdown and latex. Try it today if you are intrigued.

I'm not sure either matter to be honest. It's cool sure, powerful also... but when anybody has access to both vector-based editor and raster-based editor ... but also tools that incorporate them, e.g. rich text editors ... but also entire toolchain going from compilers to libraries all the way to Web based notebook with their editors and running environment that can then output printable artifacts, I don't think ther…

I cannot tell the future of typst and gribouille, but for:

> I'm fine with just text, then just readible equations below it, then an OK looking graph. I don't actually care if any of those are pixel perfect. I don't get it.

what you describe is fine for a readme or a blog post, but for books, scientific articles, or any long format, having a good layout and typography will totally impact the end result

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#25

This is awesome, is there a way to render the graphics/chart in svg so that we can implement something like hover & popup (with data information)?

Typst supports SVG output natively.

From past experience (may be different now): Typst supports SVGs that are actually vanilla SVGs. The SVG standard lets you embed a HTML page and CSS as a , which only renders properly in a browser or something that bundles one (surprise!). This is not the fault of Typst and I think Typst is correct not to go down that route.

Just a heads up if you wonder why draw.io (diagrams.net) SVGs display as black boxes.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#26
post #12

Earlier quoted context omitted.

Right; but markdown has expanded beyond that niche. Lots of projects use markdown for other stuff - like mdbook, or for blogs. I think markdown is a great format for readme files. But for real documentation, the added features of typst are fantastic. Like, being able to write scripts, have figures and custom styling, populate data from JSON files, plugins, typography, numbered sections, footnotes and all sorts of oth…

Ordinary markdowns have had /everything/ you mention for close to 20 years, except typesetting. Academic papers and books, novels, thousands of ebooks, have been written in single file markdowns for 15 years. Writing directly in typst is good for small things with intense typesetting like ... wedding invitations, advertisements. But it doesn't scale to serious composition by actual writers. Writing is not typesetting…

So LaTeX also doesn't scale to serious composition by actual writers?

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#27
post #12

Earlier quoted context omitted.

For Latex I agree thats definitely. Markdown I am unsure as Markdown is not meant for creating documents but to just have a little Richt Text Markup in READMEs and other Text files. Typst needs a compile step and altough that one is fast as hell it is still different from Markdown that renders directly from the file without an intermediary.

Right; but markdown has expanded beyond that niche. Lots of projects use markdown for other stuff - like mdbook, or for blogs. I think markdown is a great format for readme files. But for real documentation, the added features of typst are fantastic. Like, being able to write scripts, have figures and custom styling, populate data from JSON files, plugins, typography, numbered sections, footnotes and all sorts of oth…

What's the state for generating websites from Typst?

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#28

Typst is the most important open source project of the last 5 years. I predict a future where markdown and latex are largely replaced by typst. And I couldn't be more excited. It is such a stepup from markdown and latex. Try it today if you are intrigued.

Markdown and Typst serve different markets - I don't need page layouts and font choices in a pull request, for example. Typst is however a good Markdown++ in that once a collection of markdown files grows to book size, it's easy enough to port.

Typst challenging TeX would be my dream too - there's a lot of math you can port just be leaving off the backslashes. Mind you the kids these days know TeX primarily as "that language in overleaf".

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#29
post #8

Earlier quoted context omitted.

The problem with markdown is that it's not extensible and that there is no spec. Essentially all READMEs would be better off using typst, they would make for better READMEs.

I do not think that is the problem with markdown lol. There are lots of problems with markdown, especially vanilla or the more limited versions of it - but really its super power is that it is readable with a regular text editor (or `cat`) and can be rendered without a compilation step. Markdown is not competing with latex or typst, it is competing with (and has won against) .txt files

Actually basic typst is as readable as markdown, e.g. this is the example from the webapp:

  = The Typst Playground

  Welcome to the Typst Playground! This is a sandbox where you can experiment with Typst. You can type anywhere in the editor panel on the left. The preview panel to the right will update live.
  
  = Basics 
  
  Typst is a _markup_ language. You use it to express not just the content, but also the structure and formatting of your document. For example, surrounding a word with underscores _emphasizes_ it with italics and starting a line with an equals sign creates a section heading.
  
  Typst has lightweight syntax like this for the most common formatting needs. Among other things, you can use it to:
  
  - *Strongly emphasize* some text
  - Refer to @basics
  - Typeset math: $a, b in { 1/2, sqrt(4 a b) }$
  
  That's just the surface though! Typst has powerful systems for scripting, styling, introspection, and more. In the realm of a Typst document, there is nothing you can't automate.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#30
post #7

Typst is the most important open source project of the last 5 years. I predict a future where markdown and latex are largely replaced by typst. And I couldn't be more excited. It is such a stepup from markdown and latex. Try it today if you are intrigued.

I'm not sure either matter to be honest. It's cool sure, powerful also... but when anybody has access to both vector-based editor and raster-based editor ... but also tools that incorporate them, e.g. rich text editors ... but also entire toolchain going from compilers to libraries all the way to Web based notebook with their editors and running environment that can then output printable artifacts, I don't think ther…

If you've ever debugged TeX package conflicts because someone wants "that layout, except with those headers and this font", yes the whole stack needs replacing with something that does not hold all its state in global variables and has a sensible scripting language (LuaTeX never really took off).
Post reply on HN