Hello Pierre and people, I've been following this thread from its beginning. I think that your idea worth very much and is very valuable in this situation.
How can a serious project depend on ONLY ONE guy (that Ray) who is missing ? …and he doesn’t answer emails for MONTHS, is unreachable and leaved the project LOCKED as rthomas said ? If this project should rely on only one person, he doesn’t seem to be in conditions to do that. What should be the reason to continue waiting for him ? The description of the situation even reminds me to the “Jacob” character, in Lost TV series. The fork seems to be a nice idea, perhaps a new wiki with tutorials and better documentation would be also very helpful for increasing the activity of contributors. I don’t know OCRopus but here: http://googlesystem.blogspot.com/2007/04/open-source-ocr-software-sponsored-by.htmlthey tell that it’s partly based on Tesseract…I’m curious about how the Tesseract modifications are being managed. Anyone knows something about that ? Perhaps if some of you are used to write to OCRopus list it would be a good idea to ask there about what’s the reason of the lack of support here. I mostly agree with you Pierre about what you said about relying on extern libraries, but I think that there is an exception to be made, the boost libraries, don’t you agree? I encourage those who had been following this thread silently as me to share their opinion. Cheers, Andres 2010/4/8 MARTIN Pierre <[email protected]> > > Ocropus is much better candidate for contributing, and it even uses > > distributed version control (Mercurial). > Agreed. > > > The unfortunate downside is > > that at least awareness of Ubuntu and Python are required. But on the > > other hand Ubuntu+Python is much more fun to learn than the mathematics > > and algorithms (in C++) behind OCR. > i have both, well, Python a while ago but that's obviously only a syntax > problem. i'm very used to high level OOP languages (ObjC mostly) and Python > is not that far from it. Unfortunatelly, this project really doesn't suits > my target. i'm requiring opensource (Or at least easily portable by myself > on each major release, which is really not the case right now), and most of > all closed sources when required by a commercial license. > > Also, i notive that OCROpus is getting into the same (And i think wrong) > direction than Tesseract is about to take: relying on various totally > un-related libraries. An OCR library should be only relying on the input > format (Which at best would be raw picture LSB / MSB 1bpp data), not a > leptonica-ish wrapper. > > i'm actually reading Tesseract source code, and i have quite a lot of > enlightenements doing this, so i think i'll be writing an eMail to Ray very > soon. > > Anyone interested with joining my action, and edventually helping me > writing it (As you may have noticed, my english became poor over time :D). > > Thanks anyway for your advices which i honnestly find really valuable, > everyone. > Pierre. > > -- > 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. > > -- 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]. For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en.
