Fair point, I'm usually better at not jumping to conclusions on bug reports.
There's not a lot of info from the compiler or the command line, I was only able to discern what was going wrong with gdb. I'll try to include all relevant info. Wil On Feb 9, 1:39 pm, "Jimmy O'Regan" <[email protected]> wrote: > On 9 February 2012 11:39, Wil Hadden <[email protected]> wrote: > > > OK, I'll not create an issue for this for now, but the reason I > > brought it up was that I have saw isspace fail last night with text > > that was out of bounds ( the char value was -128 ). > > > When I changed the isspace to iswspace the problem was resolved. I'm > > no expert at this and I am likely to be fixing this incorrectly, but > > isspace was crashing out which meant I was unable to do any training. > > In that case, you have found an issue, just not the issue you thought. > Read this:http://catb.org/esr/faqs/smart-questions.html#symptoms > > > I can supply you with the tiff / box file if you want. > > The compiler output would be more useful, but you can also include > that in the issue if you think it's relevant. > > -- > <Sefam> Are any of the mentors around? > <jimregan> yes, they're the ones trolling you -- 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
