newbie question - Compiling Teseract / Language Support

[lcg]

I have noticed that when you download Tesseract 2.04 the 'tessdata'
directory contains the language files but with 0 bytes.
Do you need to replace these files with the language files (ex
tesseract-2.00.eng.tar.gz) before you compile Tesseract or not?

I am compiling on a Mac for an iPhone App. I was able to complete the
compile using the file with 0-bytes but when I replace them I get the
following error: specifed architecture type (arm) for file (lnsout/
libtesseract_full.a.arm) does not match it's cputype (16777223) and
cpusubtype (3) (should be cputype (12) and cpusubtype (0))

[Ray Smith]

That's a strange sounding error, but the way it works is:
Download and unpack the source and any tessdata files for the languages you want.
Configre, make, and make install.
Since I don't know how to have optional files for make install, make fills in the blanks with empty files for languages that you don't have, so you have to unpack the language files first, or you get into trouble overwriting the empty files.

If anyone knows how to allow optional files for make install with auto tools, then that would make it easier...

Ray.

--

You received this message because you are subscribed to the Google Groups "tesseract-ocr" group.
To post to this group, send email to tesser...@googlegroups.com.
To unsubscribe from this group, send email to tesseract-oc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=.

[Eugene Reimer]

Wouldn't the simplest solution be for the "install" to not install any
language-files. Then the install-instructions would say to install the
language-files one wants AFTER installing tesseract; the only other
change would be the location one is instructed to copy them to.

That would also solve the problem of losing ones language-files whenever
upgrading.

[lcg]

Thanks Ray and Eugene for your answers.
In fact I almost managed to cross-compile Tesseract for the iPhone on
Snow Leopard. The ARM part is OK but the i386 was a nightmare as the
Simulator only works with i386 and as default Snow Leopard uses
x86_64.

Having said that, do I need to first import the language and compile
or does it make no difference? I am really new with Tesseract and not
yet sure if the language files are needed when I compile of if I will
only need them when I run the App

Thanks - Laurent

On Dec 2, 5:45 am, Ray Smith <theraysm...@gmail.com> wrote:
> That's a strange sounding error, but the way it works is:
> Download and unpack the source and any tessdata files for the languages you
> want.
> Configre, make, and make install.
> Since I don't know how to have optional files for make install, make fills
> in the blanks with empty files for languages that you don't have, so you
> have to unpack the language files first, or you get into trouble overwriting
> the empty files.
>
> If anyone knows how to allow optional files for make install with auto
> tools, then that would make it easier...
>
> Ray.
>

> On Nov 22, 2009 8:06 PM, "lcg" <laurentgarnie...@yahoo.com> wrote:
>
> I have noticed that when you download Tesseract 2.04 the 'tessdata'
> directory contains the language files but with 0 bytes.
> Do you need to replace these files with the language files (ex
> tesseract-2.00.eng.tar.gz) before you compile Tesseract or not?
>
> I am compiling on a Mac for an iPhone App. I was able to complete the
> compile using the file with 0-bytes but when I replace them I get the
> following error: specifed architecture type (arm) for file (lnsout/
> libtesseract_full.a.arm) does not match it's cputype (16777223) and
> cpusubtype (3) (should be cputype (12) and cpusubtype (0))
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "tesseract-ocr" group.
> To post to this group, send email to tesser...@googlegroups.com.
> To unsubscribe from this group, send email to

> tesseract-oc...@googlegroups.com<tesseract-ocr%2Bunsubscribe@goog legroups.com>
> .