Balearica
Balearica
There are currently many issues related to how Tesseract.js handles errors within workers. For example, the issues below are all either directly about promises never resolving, or are more difficult...
At present, our automated tests all specify local paths (e.g. corePath, langPath, etc.). This creates a blindspot for problems relating to how the default values for these arguments are set...
Tests will randomly fail. This seems to happen for the (newly added) Node 16 and Node 18 versions. The most common error is below. ``` Uncaught Error: expected '84,101,115,115,101,114,97,99,116,46,106,115,10' to...
At present the automated tests recognize a set of images and compare the result *exactly* to an expected result. This is not robust, as any update to the OCR engine...
### Expected Behavior: The API function `PrintVariables` prints current parameters to a file, and `ReadConfigFile` reads parameters from a file. Intuitively, `ReadConfigFile` should be able to read the files that...
This would be one way of fixing #876, and should probably happen eventually regardless.
# Summary ## Major New Features 1. **Significantly** smaller file sizes 1. 54% smaller file sizes for English, 73% smaller for Chinese (see #806 for details) 2. This results in...
When workers are created one at a time for a scheduler, Chrome downloads the code and lang data once for the first worker, and then uses the cached version for...
Since Version 4, Tesseract.js has allowed for setting parameters for a single recognition job (see #665). However, it does not look like the types were ever updated--the following code results...