Typst 0.13 is out now(typst.app) |
Typst 0.13 is out now(typst.app) |
Typst is such a great software. With it's modern programming language like syntax I learned it much faster than Latex. It's compile duration is also much better in my experience. I am honestly more productive using Typst it this point. Though I am not a power user. I only used it for slides and notation heavy articles.
- We split the "paper" into multiple Typst files. While this organized our content nice, the VSC extension didn't recognize the bibliography imported in another file and displayed errors. Nothing major but certainly annoying.
- It couldn't deal well with SVGs and diagrams in general, so we resorted to just export graphics and include them as images.
6/10 would use again and I'm excited for the new release.
FYI the workaround to solve this is to go to the "root" file and run the "pin current file as main" or something like that of your Typst LSP. Unfortunately this needs to be done every time you reopen your project.
Typst is one of my favourite open source projects right now, mostly due to how useful it is even for non-technical users. I have converted most of my friends and their friends in my university to switch from latex / markdown / word to typst, mostly due to its ease of use, how nice does (even the default) output looks like and how powerful it is.
I am very happy that typst is still being developed and I am really surprised how many new features they add (for my use-cases it is pretty much done product:)).
I can see that being useful for lots of people, but, as a migration path (as I understood your parent https://news.ycombinator.com/item?id=43106837 to suggest), I don't think it would work. I've worked with TeX for almost 30 years and used vim for about 20 years, and suspect that "supports … some basic TeX" is likely to have the same effect for me as something that emulates vim does on a master-level vimmer—falling into the uncanny valley that's somehow worse than a totally different thing.
Honestly a better first step would be getting inserting another pdf plot to work, but seems hard https://github.com/typst/typst/issues/145
Typst looks like it might be the solution to this problem.
I'm quite happy about the workflow.
Plus now I have a template that I'll apply to the second book.
I love it.
The biggest downside is that now I dread switching to overleaf after typst!
To me it’s sorta like CSS where the availability of templates is more important than the core language (at least for people lacking design abilities).
https://github.com/messense/typst-py
I've experimented with 'transpiling' to RST with Pandoc for purposes of digital documentation - but it's not quite there. Would love to see a flavour of Typst that could be viable for digital documentation with a decent live preview experience in VSCode.
I know this isn't the purpose of Typst, but one can hope. Would also welcome advice on this subject of decent authorship digital documentation - some of these frameworks are quite frankly massive, unweildy and painful to deal with.
I'm seeing this delay lots of features in rust projects.
For example helix the text editor hasn't gotten file watching (for the purposes of updating after external edits) for years now because of apparent problems with the file watching library in rust.
Yes I (semi) wasted some time to setup a repository including CI: https://thesis.huijzer.xyz/. Link to source code and pdf are on that site. I hope it can satisfy your curiosity :p
I know of a few Rust crates that offer something like this - Minijinja, off the top of my head.
[1]: https://doc.rust-lang.org/nomicon/ffi.html#calling-rust-code...
If I weren't on mobile I'd link you to the line in the source code. Just search the repo for Knuth-Plass.
Mind you, I loved programming in Typst, and I wrote some plugins before it got its package manager, but I ended up moving back to LaTeX for this difference in quality of the final output. I should do some in depth testing at some point, because I am looking to switch back.