topic If you are using character in Product Forum https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91092#M41181 If you are using character matching the my guess would be that you are using the wrong font - some fonts are very similar where some characters match but others are subtly different. Unfortunately often the only solution to finding the right font is brute force, although usually apps tend to use common fonts like Tahoma, Arial, Segoe UI etc.Alternatively try the OCR option - you don't need a font but you have accept the fact that the OCR engine (Google Tesseract) will 'work out' the result rather than give you a 100% match like Character matching does. Tue, 17 Jan 2017 20:48:00 GMT John__Carter 2017-01-17T20:48:00Z Surface Automation Reading issue https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91090#M41179 Hi, I have some problem in reading the data from an image with surface automation. The text is: INC0018316, while the result from reading stage is IN 0018 1. Why do some of the characters can't be recognised, and how should I solve this problem? Thanks~ Tue, 17 Jan 2017 03:54:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91090#M41179 SIMENG_WANG 2017-01-17T03:54:00Z Your readings depend alot on https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91091#M41180 Your readings depend alot on how you choose to read. You can either just read the text directly automatically or do it by defining a new font in Blue Prism. With this not working for you, I would definitely advise you to define a specific font for this text and use that instead of the generic reader function. Tue, 17 Jan 2017 15:34:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91091#M41180 TimMorthorst1 2017-01-17T15:34:00Z If you are using character https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91092#M41181 If you are using character matching the my guess would be that you are using the wrong font - some fonts are very similar where some characters match but others are subtly different. Unfortunately often the only solution to finding the right font is brute force, although usually apps tend to use common fonts like Tahoma, Arial, Segoe UI etc.Alternatively try the OCR option - you don't need a font but you have accept the fact that the OCR engine (Google Tesseract) will 'work out' the result rather than give you a 100% match like Character matching does. Tue, 17 Jan 2017 20:48:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91092#M41181 John__Carter 2017-01-17T20:48:00Z Thank you guys! Problem https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91093#M41182 Thank you guys! Problem solved by using OCR method. Tue, 24 Jan 2017 04:14:00 GMT https://community.blueprism.com/t5/Product-Forum/Surface-Automation-Reading-issue/m-p/91093#M41182 SIMENG_WANG 2017-01-24T04:14:00Z