TheJoeFin
Version 2.7.1 Not Correctly Capturing Column of Numbers
Not impressed with the latest version. The previous version worked much better for me. One example is my attempts to capture a column of numbers. Any single-digit number is ignored and not captured. Only two digits and above are captured.
Hello @GaryGraham54 sorry to hear you are not getting reliable results. Please provide a screenshot of something similar to what you are trying to OCR so I can reproduce the issue on my device, and work on making an improvement.
Thank you for your response. Below is a screenshot of the data I am trying to capture. [image: image.png]
However, every attempt I make with various different Text Grab settings always results in the single-digit numbers being ignored and only two-digit and higher numbers being captured. 73 15 10 16 54 10 30 157 25 14 11 11 17 16 10
Thanks again for your assistance.
Gary Graham
Email: @.***
CONFIDENTIAL COMMUNICATION: This email message and any attachment may contain privileged and confidential information intended only for the use of the individual or entity to which the email is addressed. If the reader of this message is not the intended recipient or the employee or agent responsible to deliver it to the intended recipient, that person is hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify us as soon as possible by telephone (collect calls will be accepted). Thank you for your cooperation and assistance.
On Wed, Oct 5, 2022 at 3:35 PM Joseph Finney @.***> wrote:
Hello @GaryGraham54 https://github.com/GaryGraham54 sorry to hear you are not getting reliable results. Please provide a screenshot of something similar to what you are trying to OCR so I can reproduce the issue on my device, and work on making an improvement.
— Reply to this email directly, view it on GitHub https://github.com/TheJoeFin/Text-Grab/issues/194#issuecomment-1268872780, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYS6FQUUURDMZSTXJUWNXNTWBXJ73ANCNFSM6AAAAAAQ5VRMEQ . You are receiving this because you were mentioned.Message ID: @.***>
@GaryGraham54 the image did not come through to GitHub, feel free to email [email protected] to connect directly on this issue.
Need to test this with Tesseract and see if this is a general OCR issue or specifically related to the Windows OCR API
@GaryGraham54 I tested this scenario with Tesseract and did not get good results. I am thinking OCR is not well suited for this scenario. I am not sure what else I can do with Text Grab to fix this issue so I will be marking it as Won't Fix and closing the issue. If something comes up later which changes the issue can be reopened.
Thank you, I appreciate your efforts. What puzzles me is that it worked flawlessly prior to that recent update. Thanks again, Gary
On Wed, Nov 2, 2022 at 9:40 PM Joseph Finney @.***> wrote:
@GaryGraham54 https://github.com/GaryGraham54 I tested this scenario with Tesseract and did not get good results. I am thinking OCR is not well suited for this scenario. I am not sure what else I can do with Text Grab to fix this issue so I will be marking it as Won't Fix and closing the issue. If something comes up later which changes the issue can be reopened.
— Reply to this email directly, view it on GitHub https://github.com/TheJoeFin/Text-Grab/issues/194#issuecomment-1301552762, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYS6FQUA7R4JVU6UVZG33LDWGMJY7ANCNFSM6AAAAAAQ5VRMEQ . You are receiving this because you were mentioned.Message ID: @.***>
@GaryGraham54 the previous versions of Text Grab are still available in the GitHub releases section. Can you please retest and find which version works for you? Then I can look through the differences and hopefully find a fix. Also details about your system would be helpful such as Windows version, display scaling, and resolution.