Mistaking 0 for O

[treehs]

The input file

The result

Its able to recognize the two 0’s in the middle however the last 0 is seen as an O.
Another similar example:

This happens on both engine 1 and 2
Are there any fixes to this?

[admin]

O vs 0 is always tricky for OCR processing

In this case I got it working by enlarging the image by 200%:

Result:

[treehs]

Sorry to ask but, what do you mean by enlarge? Zoom or upscale or some other thing?