Hi Shree,
   Unfortunately, I'm building with an old version of Visual Studio VC++, 
version 2005 to be precise, I had to do a bit of "ugly hacking" to get it 
to work.  Definitely "quick and dirty", I would imagine with a newer 
compiler like Visual Studio 2013, it would not be necessary, and I'll try 
that later, but there were just two small problems to "fix" which didn't 
take long, and then everything worked fine even with an old compiler like 
that!

-Mark--

On Saturday, July 11, 2015 at 12:14:55 AM UTC-5, Mark Seidner wrote:
>
> Hi everyone,
>    I downloaded the latest 3.04 code from git and did a build on Windows, 
> when I tested on some english files with OEM_TESSERACT_CUBE_COMBINED, there 
> was no difference in accuracy between Tesseract 3.03 and Tesseract 3.04.  I 
> haven't tried OEM_TESSERACT_ONLY yet, to see if there's any difference 
> here, still I was surprised that accuracy was the same for both releases.  
> Also why all the hate for OEM_TESSERACT_CUBE_COMBINED?  This combination is 
> incredibly accurate for camera images.
>
> Anyone care to comment on why accuracy hasn't improved since the last 
> release?
>

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tesseract-ocr.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/42624344-5ac1-4a7d-8e4c-cd59b1e0a392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to