You can use our python bindings for both[3,4], although they might be slightly outdated:
[1] https://code.google.com/p/tesseract-ocr/
[2] http://libccv.org/doc/doc-swt/
Does it still work with an up-to-date ccv?
Although SWIG might work better now.
On one hand, they really try to push everybody to upgrade to their newest and shiniest, by making a lot of stuff (like this) only available on Windows 8+.
On the other hand, they don't even bother to put in a box with "What operating systems will this work on", so you don't have to do trial/error, research WinRT, and then be disappointed when you realize this will apparently never work on Windows 7. And maybe only in Metro apps? What is Windows Runtime and am I just supposed to know this?
I really enjoy coding C# and working in .NET. Microsoft has some really great stable techs which work well for years and years - but increasingly if you want anything new and shiny from them, you have to run the newest OS. Which if you work with anything related to enterprise, good luck only targetting Windows 8.
And honestly, despite working almost exclusively with MS tech, I just don't really trust any platform from them that doesn't have significant traction and track record as they all too often just give up and try something new - and sometimes without real replacements available.
Minimum supported client Windows 8.1 [Windows Store apps only]
Minimum supported server Windows Server 2012 R2 [Windows Store apps only]
Minimum supported phone Windows Phone 8
[2] http://msdn.microsoft.com/en-us/library/windows/apps/xaml/wi...
If you subscribe to MSDN like any Windows developer, this has been explained multiple times in the last two years.
Just for the clueless ones.
Windows Runtime is an evolution of COM, based on the ideas that were on the genesis of .NET. Namely Ext-VOS.
http://blogs.msdn.com/b/dsyme/archive/2012/07/05/more-c-net-...
So a native version of .NET, so to speak. And unless Windows 9 changes it, the future of Windows APIs.
The .NET runtime starting with Windows 8 acquired additional capabilities:
- Ahead of time compilation to native code for Windows Phone apps, with the MDIL binary format
- Consumption and creation of Windows Runtime components
> but increasingly if you want anything new and shiny from them, you have to run the newest OS.
No different from other commercial vendors.
nb: haven't actually tested past installation at this stage.
edit: nope :(
packages\Microsoft.Windows.Ocr.1.0.0\lib\win81
Why would I think they might be .NET libraries if they have 'x86' and 'x64' labels? Because C++/CLI has to be compiled to separate dlls, I believe.
When calling native code outside the CLR the runtime needs to know which type of marshaling code to generate.
It also plays a role when using unsafe code blocks in .NET.
Tessarect can be used everywhere, and is used dominantly on open platforms. This is a offering from Microsoft to be used on their platform only.
They may both be good, but they have widely different platform targets.
so far, this microsoft OCR is just bunch of words without any prove that it actually works, what so ever. show me some pictures or videos of results.
But from my experience, what adds to the slowness is pre-processing the image to make it suitable for OCR, especially tesseract. I still haven't found the magic combination of filters because every image is different, especially if your source them from users camera phones.
http://msdn.microsoft.com/en-us/library/windows/apps/xaml/wi...
I found a few libraries, but they only worked with relatively perfect scans (my goal is to be able to just use a phone). When I get home definitely going to give this a go.
I freely admit that I do not speak Korean, but if one compares "Chinese Simplified" characters (listed as "Very good") with those in the Korean alphabet, I am surprised those two entries aren't transposed.
Is there something that makes recognizing Korean harder than Chinese Simplified, or was that just a product management decision?
Now I would be more interested in an image correction library
".... Blurry images Handwritten or cursive text Artistic font styles Small text size (less than 15 pixels for Western languages, or less than 20 pixels for East Asian languages) Complex backgrounds Shadows or glare over text Perspective distortion Oversized or dropped capital letters at the beginnings of words Subscript, superscript, or strikethrough text"