-
I'm not sure what you're referring to because when justification is enabled Typst uses almost the same line breaking algorithm as TeX. [1]
One problem we had was over-eager hyphenation. We've addressed that recently. [2]
[1]: https://github.com/typst/typst/blob/9b001e21121ab7b5645aa36f...
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
A number of past discussions and related things: https://hn.algolia.com/?q=typst
1 year ago, 146 comments: https://news.ycombinator.com/item?id=35250210
8 months ago, 34 comments: https://news.ycombinator.com/item?id=38354422
2 years ago, 53 comments: https://news.ycombinator.com/item?id=34423590
2 years ago 30 comments: https://news.ycombinator.com/item?id=32209794
-
FWIW there is already partial LaTeX support in Typst via the mitex package:
https://github.com/mitex-rs/mitex
-
I guess this is a competitor to services such as overleaf [1] and codimd [2]. Although this is yet another syntax, it seems to be supported by pandoc [3]. Lately, I have been using Quarto [4] more and more as I program in R, which also produces very nice outputs, especially HTML. But none of these solve the academic usage problems of (1) producing nice diffs for reviewers, and (2) can easily be shared with, and commented by, non-technical collaborators. Thus, I fear Word will be difficult to replace for many years, at least in my field, for scientific writing
[1] https://github.com/overleaf/overleaf
[2] https://github.com/hackmdio/codimd
[3] https://pandoc.org/typst-property-output.html
[4] https://quarto.org/
-
I guess this is a competitor to services such as overleaf [1] and codimd [2]. Although this is yet another syntax, it seems to be supported by pandoc [3]. Lately, I have been using Quarto [4] more and more as I program in R, which also produces very nice outputs, especially HTML. But none of these solve the academic usage problems of (1) producing nice diffs for reviewers, and (2) can easily be shared with, and commented by, non-technical collaborators. Thus, I fear Word will be difficult to replace for many years, at least in my field, for scientific writing
[1] https://github.com/overleaf/overleaf
[2] https://github.com/hackmdio/codimd
[3] https://pandoc.org/typst-property-output.html
[4] https://quarto.org/
-
A few of my Markdown documents:
* https://impacts.to/downloads/lowres/impacts.pdf
* https://whitemagicsoftware.com/softcover/technical.pdf
* https://whitemagicsoftware.com/softcover/jekyll-hyde.pdf
Respectfully, keeping presentation logic and content completely separated while having precise control over layout is possible even with Markdown, as my example documents demonstrate. ConTeXt is an exquisite typesetting system that makes keeping such separation possible.
The deeper issue relates to the software's architecture, which, IMO, systems like Typst, Obsidian, and others fail to implement broadly enough. Here's KeenWrite's architecture (the "Proposed" row):
https://gitlab.com/DaveJarvis/KeenWrite/-/raw/main/docs/imag...
Although only Markdown is currently implemented, it's possible to plug other text-based input formats to produce an XHTML document. The instructions for how to typeset XHTML documents are defined by a theme. You can think of a theme as an XML to TeX translation system. From there, going from XML to TeX is straightforward (using ConTeXt), allowing full control over the final output format.
I am the author of KeenWrite. The following tutorial shows how its themes work:
https://www.youtube.com/watch?v=3QpX70O5S30&list=PLB-WIt1cZY...
-
-
Not the OP but I use pandoc-crossref for this: https://lierdakil.github.io/pandoc-crossref/
-
Quarto appears a popular alternative, out of interest is anyone using Zettlr?
https://www.zettlr.com/
-
LaTeX's support is already problematic. Most people just don't use it in sufficient intensity to notice. We produce thousands of (mostly) hand written technical reports a year using LaTeX and there are all sorts of subtle issues cropping up. It's a distribution of many, many packages from many developers, and maintenance can be spotty and vary. Unlike some people would like to believe, stuff breaks all the time.
Check this out for example: https://github.com/tabu-issues-for-future-maintainer/tabu
This used to be the most recommended package for tables.
This bug is still not fixed after at least 9 years AFAIK: https://tex.stackexchange.com/questions/203629/longtable-and...
It affects us regularly.
I'm not even going to comment on the fact that all of the following packages provide some sort of tabular feature: array, table, tabu, tabular, tabularx, longtable, supertabular, longtabu, xltabular, lxtable, booktabs, tabularray, ctable. Good luck figuring out which one does what you need and has the least side effects with everything else.
Also, while I'm not familiar with the internals of the LaTeX project, I keep reading the same names, most of which appear to be getting closer and closer to retirement. I wonder if suitable successors will pick up the task of maintaining LaTeX in the future.
-
https://github.com/chomosuke/typst-preview.nvim
It looks similar to Gilles Castel's famous note-taking setup:
https://castel.dev/post/lecture-notes-1/
I would love to see someone combine this with Anki for quick math flashcard creation
