[@Clare]
>”Then what? If it can solve issues, why are you care about what engine it use? Ridiculous.”
If John S already has a different front-end to tesseract, then another one would not produce better results. People generally do not want to have multiple front-ends to the same tool. Therefore, it is a fair question.
From the list of front-ends of tesseract listed on Github, this program is not listed as a front-end to tesseract. Regardless, it still could be, just not in the list on Github. So, again, a fair question.
Also, if John S has an alternative OCR tool that is known to outperform tesseract, then again, knowing if this tool is a front-end to tesseract would be helpful.
For any one of these points, you can substitute any other OCR engine in the place of “tesseract,” and it would still be a fair question.
Myself, I’m like John S. I always want to know what OCR engine is being used, so I am glad John S. asked. Hopefully, someone else might know the answer and not consider the question ridiculous.