Re: [tesseract-ocr] Re: Need help training Simplified Chinese.

2017-06-26 Thread ShreeDevi Kumar
On Tue, Jun 27, 2017 at 10:18 AM, Clement wrote: > I downloaded the alpha source code from the link below: > https://github.com/tesseract-ocr/tesseract/releases/tag/4.00.00alpha > > I installed using the following commands: > $ ./autogen.sh > $ ./configure PKG_CONFIG_PATH=/usr/local/lib/pkgconfig

[tesseract-ocr] Re: Need help training Simplified Chinese.

2017-06-26 Thread Clement
I downloaded the alpha source code from the link below: https://github.com/tesseract-ocr/tesseract/releases/tag/4.00.00alpha I installed using the following commands: $ ./autogen.sh $ ./configure PKG_CONFIG_PATH=/usr/local/lib/pkgconfig LIBLEPT_HEADERSDIR=/usr/local/include

Re: [tesseract-ocr] ./configure failling for me

2017-06-26 Thread ShreeDevi Kumar
Also see https://github.com/tesseract-ocr/tesseract/issues/919 related to building on Centos ShreeDevi भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com On Tue, Jun 27, 2017 at 8:54 AM, ShreeDevi Kumar wrote:

Re: [tesseract-ocr] ./configure failling for me

2017-06-26 Thread ShreeDevi Kumar
Have you tried: ensure that autoconf-archive is installed. Don't forget to run ./autogen.sh after the installation of autoconf-archive. as per https://github.com/tesseract-ocr/tesseract/wiki/Compiling ShreeDevi भजन - कीर्तन - आरती @

[tesseract-ocr] ./configure failling for me

2017-06-26 Thread Luke Quinn
So i am trying to get tesseract installed following this guide (the git guide failed at the same point as well) https://medium.com/@lucas63/installing-tesseract-3-04-in-ubuntu-14-04-1dae8b748a32. Now I get to the point where i run ./configure for tesseract but i get this error output

Re: [tesseract-ocr] Re: unicharset_extractor extracting zero values

2017-06-26 Thread David Barishev
I have successfully compiled from the latest branch. Thank you for all the support. On Wednesday, June 21, 2017 at 2:56:22 PM UTC+3, shree wrote: > > > > On Tuesday, June 20, 2017 at 9:09:53 PM UTC+5:30, shree wrote: >> >> I got the same error building 3.05.01 and have filed it as an issue - >>