PR for issue 257: Tesseract1.doOCR method doesn't take into account the stride of the image

[kpentaris]

#257

[nguyenq]

Normally, bytes per line = bytes per pixel * image width, as mentioned in:

https://stackoverflow.com/questions/51590161/bytes-per-pixel-bytes-per-line-how-to-use-function-nativesetimagebytes-in-tes
https://stackoverflow.com/questions/9513227/what-is-meant-by-bytesperline-in-qimage

Can you cite some references that support your formula? And please attach an image file that would fail in the current implementation.

Thanks.

[kpentaris]

Here is an SO question that explains this (also has a link to MSDN docs): https://stackoverflow.com/questions/29912303/stride-and-padding-of-an-image

[nguyenq]

Can you attach a sample image that would cause the problem with the current version? It would help in testing pre- and post-fix.