Re: Forking tesseract.

[Devin Kennedy]

On Thu, May 13, 2010 at 6:13 AM, James Le Cuirot
<ch...@aura-online.co.uk> wrote:
> I have created new autotools files so that Tesseract can be built as
> shared libraries (using libtool), which would allow other projects to
> link against it much more easily. Unfortunately, the Linux
> distributions (admittedly just Gentoo so far) are reluctant to use
> these changes without them being accepted upstream.

I sympathize with your position. For over a year, I have been
maintaining a local branch tracking the tesseract-ocr svn trunk with
some patches applied that do pretty much the same thing you're
describing, for some personal projects. I've also been building my
own .debs for Ubuntu for easy deployment in some projects I'm working
on.

I haven't talked to the official Debian package maintainer, Jeffrey
Ratcliffe, but I know he's applying some patches against upstream for
a couple of things, so maybe he might be amenable to including at
least some subset of your changes.

I was going to make a ticket and post my patches, but I saw your posts
to #174 and decided to watch and see if it went anywhere:

http://code.google.com/p/tesseract-ocr/issues/detail?id=174

Unfortunately, nothing seems to have come of it. It would be nice to
hear from Ray Smith, even if we can just get a WontFix ...

Best,
Devin

--
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=en.

[MARTIN Pierre]

>> I have created new autotools files so that Tesseract can be built as
>> shared libraries (using libtool), which would allow other projects to
>> link against it much more easily. Unfortunately, the Linux
>> distributions (admittedly just Gentoo so far) are reluctant to use
>> these changes without them being accepted upstream.
> I sympathize with your position. For over a year, I have been
> maintaining a local branch tracking the tesseract-ocr svn trunk with
> some patches applied that do pretty much the same thing you're
> describing, for some personal projects. I've also been building my
> own .debs for Ubuntu for easy deployment in some projects I'm working
> on.

i'm still very enthusiast with this project of forking Tesseract. But as i said before, i won't do it alone, and i had not hear about you guys. What amount of time and what skills could you be dedicating to this project?

Best regards,
Pierre.

[Jimmy O'Regan]

On 14 May 2010, at 14:20, MARTIN Pierre <hick...@gmail.com> wrote:

>>> I have created new autotools files so that Tesseract can be built as
>>> shared libraries (using libtool), which would allow other projects
>>> to
>>> link against it much more easily. Unfortunately, the Linux
>>> distributions (admittedly just Gentoo so far) are reluctant to use
>>> these changes without them being accepted upstream.
>> I sympathize with your position. For over a year, I have been
>> maintaining a local branch tracking the tesseract-ocr svn trunk with
>> some patches applied that do pretty much the same thing you're
>> describing, for some personal projects. I've also been building my
>> own .debs for Ubuntu for easy deployment in some projects I'm working
>> on.
> i'm still very enthusiast with this project of forking Tesseract.
> But as i said before, i won't do it alone, and i had not hear about
> you guys. What amount of time and what skills could you be
> dedicating to this project?

FWIW, there has been some recent activity in SVN, and several issues
that had patches attached have been committed. If you haven't already
submitted an issue+patch, perhaps now is the time to do so.

[Ray Smith]

I would be very happy for someone to take over maintenance of the autotools part of tesseract. Even better if a team of you can do it... I don't get much time to deal with that, and it doesn't get much priority, since we have our own build system, and windows has to have its own. With someone looking after the build side, I am hopeful that, after 3.00 becomes a tarball, I can keep the svn trunk fully up-to-date with the source code and then maybe you guys can decide when it is a good time to make a new tarball release.

I made a big hole in the issues list last week, and will attempt to work through the rest this week, as there are useful patches in there that should be applied, and useful bug reports for bugs that can be fixed. WIth the issues list down to a more manageable size, it should be easier to keep up with it. There is too much for me to manage on my own though, and it is overwhelming to see that just about every wiki page has as many comments attached as there are open issues

I saved a lot of time by putting a filter on the forum, but that meant I didn't look at it either, which is not satisfactory. I created the tesseract-dev forum for developers specifically, but it didn't take off. It would help to have a division between the more mundane parts of the forum and the other items that require my specific attention.

So please, anyone who wants to help out maintain this site, rather than fork it, let me know, and I will add you to the list of developers. We are still actively developing the code at Google, and I want to be able to get the code out where people can use it.

Ray.

[Jimmy O'Regan]

On 25 May 2010 05:44, Ray Smith <thera...@gmail.com> wrote:
> I would be very happy for someone to take over maintenance of the autotools
> part of tesseract. Even better if a team of you can do it... I don't get
> much time to deal with that, and it doesn't get much priority, since we have
> our own build system, and windows has to have its own. With someone looking
> after the build side, I am hopeful that, after 3.00 becomes a tarball, I can
> keep the svn trunk fully up-to-date with the source code and then maybe you
> guys can decide when it is a good time to make a new tarball release.
>

I'll take you up on that; I want shared libraries :)

Maybe one month from now would be a good time to set for a release; it
gives enough time to have organised testing.

> I made a big hole in the issues list last week, and will attempt to work
> through the rest this week, as there are useful patches in there that should
> be applied, and useful bug reports for bugs that can be fixed. WIth the
> issues list down to a more manageable size, it should be easier to keep up
> with it. There is too much for me to manage on my own though, and it is
> overwhelming to see that just about every wiki page has as many comments
> attached as there are open issues
>
> I saved a lot of time by putting a filter on the forum, but that meant I
> didn't look at it either, which is not satisfactory. I created the
> tesseract-dev forum for developers specifically, but it didn't take off. It
> would help to have a division between the more mundane parts of the forum
> and the other items that require my specific attention.
>

I think all of the relevant threads have an issue filed, so you're not
missing much.

It might be a good time to revive the tesseract-dev list; the interest
clearly exists.

> So please, anyone who wants to help out maintain this site, rather than fork
> it, let me know, and I will add you to the list of developers. We are still
> actively developing the code at Google, and I want to be able to get the
> code out where people can use it.
>

--
<Leftmost> jimregan, that's because deep inside you, you are evil.
<Leftmost> Also not-so-deep inside you.

[Ray Smith]

OK, you have the job. I tidied up the tesseract-dev group too.
Ray.

[Zdenko Podobný]

Hello,

do you intend to release also tiff/box files for (new) languages (in )

Can you provide some short example for punc-dawg and number-dawg file?

BR,

Zd.

tesseract-oc...@googlegroups.com<tesseract-ocr%2Bunsu...@googlegroups.com>

[Elmer Fittery]

Sorry but no.

[zdenko podobny]

No what?

BTW: this question was intended to Ray Smith/google or provider of data in svn. Do you speak on their behalf?

Zd.

To unsubscribe from this group, send email to tesseract-oc...@googlegroups.com.