Closed mrbastian closed 1 year ago
After upgrading to 5.3, we encountered this issue in leptonica 1.83.0, which is fixed in patch 1.83.1
I'll add it to my todo list for coming week, also have to fix some other bugs in some other projects.
I just published a new package with the latest tesseract and leptonica versions
After upgrading to 5.3, we encountered this issue in leptonica 1.83.0, which is fixed in patch 1.83.1