Tesseract-OCR-iOS Mac OSX support

Apr 25 '14 10:04 zeasy

I have same question ! If not, why not? I think it should because it is present in cocapods

Jul 08 '14 09:07 diimdeep

You are free to port it to mac and provide a pull request with your changes.

Oct 01 '14 06:10 ws233

is any tutorial or examples exist, how port to mac?

Dec 02 '14 13:12 3a4oT

tesseract-ocr the upstream c++ library and engine is supported on Mac and is available in macports. A discussion on why this project, an obj-c wrapper, currently doesn't work is being held on #60

Dec 02 '14 18:12 zachberger

If we add a mac support, we should change the name of the repo to something like TesseractOCR-objC. Also, it seems it will take a lot of efforts to port this to mac, but we can try this.

And if we start this, how we should do it? Use the same code, but insert a lot of define switches like #ifdef target_macos #elseif target_ios #endif or use different projects for iOS/mac?

Jan 05 '15 20:01 ws233

Yeah OSX uses AppKit and iOS uses UIKit which seem to use different things for the same name.

For example, UIImage on iOS is actually NSImage on OSX. :(

We could potentially use a #define to create platform-independent strings for some of the incompatibilities. For the image example, we could make #define TESSERACT_IMAGE which could map to NSImage for OSX and UIImage on iOS, then update all the methods to use that.

There might be more severe API incompatibilities we will uncover if we start to do the transition. I think we should wait to work on this until the 4.0.0 release is done so that we have a more stable API to work with before we start analyzing the differences in the two platforms. What do you think?