tesseract-ocr VS typst

We are going to be using an OCR (Optical Character Recognition) engine called Tesseract for the image-to-text recognition part. It is free software, released under the Apache License. Install the engine for your desired OS from their official website. I'm using Windows for this. Add the installation path to your environment variables.

You will also need to install the Tesseract OCR engine, which can be downloaded and installed from the following link: https://github.com/tesseract-ocr/tesseract

PyTesseract Module [ Github ] EasyOCR Module [ Github ] PaddlePaddle OCR [ Github ]

It uses teseract for the OCR https://github.com/tesseract-ocr/tesseract

Last update was pretty recent, and the git mentions tesseract 5 as a dep. so it's likely moved on a bit from when you last tried it:

https://github.com/tesseract-ocr/tesseract/releases

I suppose it depends on your use-case. For personal tasks like this it should be more than sufficient, and won't need user details/cc or whatever to use it.

Tesseract is an open-source OCR engine developed by Google. It is highly accurate and supports multiple languages. This library will do all the heavy lifting for us. We'll use it in this tutorial to quickly read the text in some images.

> Does android even have native OCR?

Tesseract? https://github.com/tesseract-ocr/tesseract

Install Google Tesseract OCR (additional info how to install the engine on Linux, Mac OSX and Windows). You must be able to invoke the tesseract command as tesseract. If this isn’t the case, for example because tesseract isn’t in your PATH, you will have to change the “tesseract_cmd” variable pytesseract.pytesseract.tesseract_cmd. Under Debian/Ubuntu you can use the package tesseract-ocr. For Mac OS users. please install homebrew package tesseract.

OCR detection will be done with Tesseract.

I’ve used Tesseract for this. It seems to work well with tabular data. https://github.com/tesseract-ocr/tesseract

https://github.com/typst/typst looks promising, both the language and the tooling. I wonder where it will find its place in a world that is dominated by either Word or LaTex.

I hope in a couple of years we start seeing posts like these with Typst instead of LaTeX. It seems like setting this up would be a bit easier since Typst is much more concise than LaTeX.

[0] https://github.com/typst/typst

For writing math notes (especially in vim), I switch to using Typst (https://typst.app).

Here's a few points:

- The syntax is a lot lighter and easier to type fast. I was up and running in half hour after starting to use it. Once in a while I can look up some symbol name in the docs but that's about it.

- Empty document is a valid document. No preambles, no includes etc, it's all optional and the defaults are sensible. Just start typing.

- It's incremental. Live preview from neovim is in the browser and it's lightning fast, pretty much immediate. No pdf sync pain. No build files, makefiles and all that. Just start typing.

While it's not going to beat latex in terms of serious academic use, for personal use and notes it's close to perfect.

(And of course it's written in Rust...)

Except the main theme, which was HTML export? https://github.com/typst/typst/issues/721

Though it's in the roadmap!

I don't use LaTeX for anything these days but Typst popped up recently and seems like a decent alternative: https://github.com/typst/typst

I am surprised that no one mentions the typst. It is super smooth with typst-preview.

I suggest you ask in the discord channel: https://discord.gg/2uDybryKPe. Or open an issue or question on GitHub: https://github.com/typst/typst