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. Dn(a 25.05.2010 06:44, Ray Smith wrote / napísal(a): > 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. > > On Fri, May 21, 2010 at 5:17 AM, Jimmy O'Regan <[email protected]> wrote: > > >> On 14 May 2010, at 14:20, MARTIN Pierre <[email protected]> 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. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "tesseract-ocr" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<tesseract-ocr%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/tesseract-ocr?hl=en. >> >> >> >
smime.p7s
Description: S/MIME Cryptographic Signature
