It looks like unicharset_extractor.cpp is the only place that
std::filesystem::path is used and that was introduced relatively recently:
https://github.com/tesseract-ocr/tesseract/commit/8a26329623a017277364bc5670266c7e964c8a07?diff=split&w=1
so it probably wouldn't be hard to restore compatibilit
std::filesystem::path[1] is part of the C++17 standard and Tesseract
requires this standard for a long time (4-5 years)[2]. So you suggest
reverting this decision?
[1] https://en.cppreference.com/w/cpp/filesystem/path
[2]
https://github.com/search?q=repo%3Atesseract-ocr%2Ftesseract+C%2B%2B17&type
When I do
```js
tesseract
.recognize(`C:\\Users\\osain\\OneDrive\\Desktop\\1992 Spring\\
Document_20240109_0014.jpg`, {
lang: "eng",
oem: 1,
psm: 0,
})
.then((text) => {
console.log(text )
}) ```
I was expecting to get some orientation info on the image, l
No Print
console.log("Result:", text);
Here not covert file exp .txt
ในวันที่ พ. 10 ม.ค. 2024 เวลา 23:44 Zdenko Podobny
เขียนว่า:
> Tesseract is not trained for handwritten text.
>
> Zdenko
>
>
> st 10. 1. 2024 o 7:02 Sandeep Shakya
> napísal(a):
>
>> import tesseract from "node-tesseract-
Unfortunately you don't.
Instead of showing irrelevant information, make sure tesseract (outside of
wrapper) is providing expected results.
You are claiming "I keep getting an error that I have to set the
TESSDATA_PREFIX" but your only relevant screenshot (you made it hardly
readable) shows that
5 matches
Mail list logo
