31–40 of 48 posts
Earlier quoted context omitted.
Is it still possible to generate pixel correct hOCR when using SWT? Also, what is the main advantage of SWT - improving speed or accuracy?
I'm not sure about speed, but for accuracy, it's great. We've had terrible results with tesseract when giving it text that wasn't properly cropped with SWT.
is this better than the terrassect OCR?
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.
We had great results using tesseract-ocr[1] with SWT (state of the art text detection algorithm, via libccv[2]) on Linux. 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/ [3] https://github.com/veezio/pytesseract [4] https://github.com/veezio/pyccv
Does it still work with an up-to-date ccv?
We had great results using tesseract-ocr[1] with SWT (state of the art text detection algorithm, via libccv[2]) on Linux. 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/ [3] https://github.com/veezio/pytesseract [4] https://github.com/veezio/pyccv
Be aware that SWT is patented [1] if you want to use it commercially. [1] http://www.google.com/patents/US20090285482
is this better than the terrassect OCR?
I think that's a sort of apples and pears type of comparison. 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.
is this better than the terrassect OCR?
I think that's a sort of apples and pears type of comparison. 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.
We had great results using tesseract-ocr[1] with SWT (state of the art text detection algorithm, via libccv[2]) on Linux. 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/ [3] https://github.com/veezio/pytesseract [4] https://github.com/veezio/pyccv
Be aware that SWT is patented [1] if you want to use it commercially. [1] http://www.google.com/patents/US20090285482
Earlier quoted context omitted.
Ah, don't know how I missed that. Thanks. Crazy that it's limited to 8.1, and not even working on 8.0. I really wonder if there is a valid technical reason, or they just use it to push upgrades.
It's crazy that it's Windows Store only. On my only Windows machine the Windows Store won't even open because I have UAC disabled.
Earlier quoted context omitted.
This is really one of my big frustrations with Microsoft. 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…
> What is Windows Runtime and am I just supposed to know this? 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.…
Now it has just been 5 years since Windows 7 and apparently it's already completely outdated. It's only 2 years since Windows 8.0, and it's already out!
If this is the way Microsoft is going, then it's a huge change for anybody dealing with enterprise. I used to be able to develop on the same system using the same techs as my customers - now I may sit on Windows 8.1, but I can't use any new shiny features as my customers are still on Windows 7. Many of them just upgraded.
Sure, this may be the way others are doing it. It may be the new normal. But I still think Microsoft is shooting themselves in the foot big time regarding anything related to businesses.
In this case I'm actively researching an OCR solution. Tesseract is annoying compared to a nicely integrated .NET solution. But I'm not able to choose the solution from Microsoft. It will be at least 5 years until our customers have upgraded again, and by then - well, we're probably not going to switch OCR tech.
Instead we will be relying on third parties, open source projects - things that are not tied as much to Microsoft or the .NET ecosystem. I didn't mind being tightly tied to MS tech, I often preferred it as it was easier and worked great - but in this case I don't even have a choice. Basically I just wish Microsoft would stay Microsoft instead of trying to be Apple.
-- And regarding following MSDN. I develop WPF/C#, and I don't follow anything at all. I don't care about hype or news. I care about solid techs that are mature and sticking around for a long time. Most of the stuff being announced will significantly change or be cancelled anyway. When a product has stuck around for 3 versions and is having a pretty good following, then I might be interested. If my customers are actually able to run it of course.
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.