Assigned
Status Update
No update yet.
Comments
va...@google.com
nr...@google.com
Hello,
Thank you for reaching out.
This issue was forwarded to our product team. Please keep in mind that this issue has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.
Kind Regards
Description
I noticed that as early as I could observe of March 7th, sometimes Google Vision API has been picking up the non-existent symbols "23" either to the left or to the right of "#" symbols. The only correlation between "#" and "23" I could think of is that the # sign is U+0023 in Unicode, but in the past when Unicode characters were returned it was never returned this way.
What you expected to happen:
I expected just the # symbol to be picked up without the "23"
Steps to reproduce:
Attached example image where this problem is encountered. I was using google-cloud-vision Python API. I could reproduce this problem on both the API version I was using (3.4.5) as well as the latest 3.7.2 version. I was doing the full_text_annotation operation.
Other information (workarounds you have tried, documentation consulted, etc):
I know that according to the release notes they announced they are switching over to a new OCR model 90 days after December 5th (