reknih

6 ms·

1.
by reknih 11mo ago
Front Door is down for us (as Azure‘s Twitter account confirms)
2.
by reknih 1y ago
We're pretty close, actually. The PRs for accessible PDFs [^1] and their associated documentation [^2] are landing next week. [^1]: https://github.com/typst/typst/pull/6619 [^2]: https://githu
3.
by reknih 2y ago
For the upcoming release, we decided to prioritize print layout and the shortcomings we have there. The release after (think late fall) will focus on HTML and accessible output. The plan is to create a turn-key solution for technical writin
4.
by reknih 3y ago
I put the buttons on the bottom so the user would not be overwhelmed by options at the start. Interesting to hear you'd prefer them on top of the table! Suggesting similar characters would definitely a nice feature, I'll add it fo
5.
Show HN: An interactive ASCII table with smart search and filtering(typst.app)
2 points by reknih 3y ago|3 comments
6.
The simplest package manager (for Typst)(typst.app)
5 points by reknih 3y ago|0 comments
7.
Typst, a new markup-based typesetting system, is now open source(github.com)
520 points by reknih 3y ago|146 comments
8.
by reknih 4y ago
No worries!
9.
by reknih 4y ago
Author here: this is the fault of Adobe Acrobat unfortunately. I converted the thesis to PDF/A using that software and redacted my student registration number. Acrobat apparently did not like my file, therefore it converted many pages
10.
Writing an Incremental Typesetting Engine(laurmaedje.github.io)
3 points by reknih 4y ago|0 comments
11.
by reknih 4y ago
You've got mail!
12.
by reknih 4y ago
Yes, there will be a template producing equivalently looking (and more accessible) PDFs for Physical Review and the likes.
13.
by reknih 4y ago
Yeah, that might be a problem that must be gradually solved through partnerships, outreach, and an eventual community. We already talked to a publishing industry rep about this. In the meantime, many conferences just want camera-ready PDFs
14.
by reknih 4y ago
We are targeting PDF and raster graphic output at the moment. Typst is designed to allow HTML export and we do have our eyes on it. At the moment, however, we want to focus on getting PDF export right, including options for standards like P
15.
by reknih 4y ago
The editor is a web app! Because we build Typst in Rust, we are able to deliver it as WebAssembly and embed it into the web site.
16.
by reknih 4y ago
Hey, I'm working on Typst. We try to open source Typst's libraries as soon as they are ready. The same goes for the Typst compiler: it will be open source when we go into beta. We do not want to lock anybody into our service, so y
17.
by reknih 4y ago
This is not really a meaningful comparison: You have your TeX compiler (pdfTeX, XeTeX, LuaTeX, and the older e-TeX) that takes a document in some format and produces a PDF or DVI. In my tests (that did not include e-TeX) pdfTeX tends to be
18.
by reknih 4y ago
Very valid concern. We aim for an open core model so you can always take your projects and compile them locally
19.
by reknih 4y ago
I figure I should also mention that my LaTeX alternative is called Typst. We do not have much public detail yet but there is a landing page [1] to sign up for more info and beta access as soon as it becomes available. [1]: https:/&#x2
20.
by reknih 4y ago
IMO draft seems like a crutch: Because TeX has to reprocess the whole document and the sty-files of each imported package every time, you do not have a huge budget for your document content. Instead, you are given the option to sacrifice im
21.
by reknih 4y ago
In use cases like the Markdown to PDF pipeline described in the article, sure! Documents there are also simple enough so that compile times aren't too much of a problem. However, many of the documents we like to set in TeX are more com
22.
by reknih 4y ago
The LaTeX criticisms of the article really resonated with me. Long compile times and a narrow "happy path" are the things where I feel LaTeX makes me less productive. This is a pity because, otherwise, it is a great tool with its