You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tesseract performs extremely poorly when text is at an angle. For example, below is a scan with ~5 degrees of rotation. The first image shows the text Tesseract recognized without applying preprocessing while the second image shows what Tesseract recognized after rotating.
The maintainers of the main Tesseract repo frequently suggest adding image preprocessing steps (including auto-rotation) to workflows to address this, however this option is not ideal for web users. Given we already include the Leptonica image processing library, we should be able to expose a rotation option without much effort. Auto-rotation would be ideal, but is likely significantly more difficult to implement.
Possibly related to #588, which requests high-level functions that expose processed (binarized) images.
The text was updated successfully, but these errors were encountered:
This feature has been added in the development branch for version 4 and will be included in that release. That branch is functional at present if you would like to try it out, and is described in more detail in #662. An example has also been included to demonstrate usage.
Tesseract performs extremely poorly when text is at an angle. For example, below is a scan with ~5 degrees of rotation. The first image shows the text Tesseract recognized without applying preprocessing while the second image shows what Tesseract recognized after rotating.
The maintainers of the main Tesseract repo frequently suggest adding image preprocessing steps (including auto-rotation) to workflows to address this, however this option is not ideal for web users. Given we already include the Leptonica image processing library, we should be able to expose a rotation option without much effort. Auto-rotation would be ideal, but is likely significantly more difficult to implement.
Possibly related to #588, which requests high-level functions that expose processed (binarized) images.
The text was updated successfully, but these errors were encountered: