Wondering if this issue was fixed in Tesseract 3.05.02. Any ideas?
On Friday, August 10, 2018 at 7:51:59 AM UTC-4, Mehul Bhardwaj wrote:
>
> Hi,
>
> I went through this discussion thread and updated to Tesseract 3.05.02.
> Previously I was working with version 3.05. I was getting the same error
Hi,
I went through this discussion thread and updated to Tesseract 3.05.02.
Previously I was working with version 3.05. I was getting the same error of
"FAILURE: Couldn't find a matching blob" for about 15% of my training
characters.
But even after updating, I am still getting the exact same
Thank you for your help with these issues. The 3.05 branch now has all the
issues fixed that I found.
On Tuesday, June 5, 2018 at 8:59:08 AM UTC-6, zdenop wrote:
>
> Yes, it is ok, but you do not have to create separate issue for PR (PR is
> a issue too)
>
> Zdenko
>
>
> ut 5. 6. 2018 o 16:52
Yes, it is ok, but you do not have to create separate issue for PR (PR is a
issue too)
Zdenko
ut 5. 6. 2018 o 16:52 Paul Kitchen
napísal(a):
> ZDenko,
>
> I'm new to this so hopefully I did everything correctly. Here is the issue
> I created:
>
>
ZDenko,
I'm new to this so hopefully I did everything correctly. Here is the issue
I created:
https://github.com/tesseract-ocr/tesseract/issues/1636
And here is the pull request:
https://github.com/tesseract-ocr/tesseract/pull/1637
On Tuesday, June 5, 2018 at 7:23:41 AM UTC-6, zdenop wrote:
You need to fork official repository and then you have all permission you
need. When you make your changes you can send pull request to official
repository with your changes.
Zdenko
ut 5. 6. 2018 o 15:06 Paul Kitchen
napísal(a):
> ZDenko,
>
> Unfortunately I don't seem to have write
ZDenko,
Unfortunately I don't seem to have write permissions on the tesseract repo
so I am unable to create a branch off of master to make the changes. Who do
I need to lobby to get write permission?
On Tuesday, June 5, 2018 at 3:00:23 AM UTC-6, zdenop wrote:
>
> Please make PR for master
Please make PR for master (4.0) branch and I will cherry-pick for 3.05...
Zdenko
ut 5. 6. 2018 o 4:38 Paul Kitchen
napísal(a):
> ZDenko,
>
> I checked out the latest tesseract code and updated to branch 3.05. I see
> that the int64_t area bug is already fixed (thanks!). I also see that the
>
Here is a sample of the problem it causes. I run the following to train the
attached image and box file:
tesseract gdt.symbols.exp0.tif gdt.symbols.exp0 box.train
And here is the output:
Tesseract Open Source OCR Engine v3.05.00dev with Leptonica
Page 1
Bad box coordinates in boxfile string!
Stefan,
Paul suggest to modified also LoadDataFromFile (ccutil/genericvector.h).
That modification is not needed?
Zdenko
po 4. 6. 2018 o 17:32 'Stefan Weil' via tesseract-ocr <
tesseract-ocr@googlegroups.com> napísal(a):
> As far as I see 4.0.0 is good. I have sent a pull request which
As far as I see 4.0.0 is good. I have sent a pull request which backports
the fix from 4.0.0 (a simplified variant of Paul's fix) to 3.05.
Stefan
--
You received this message because you are subscribed to the Google Groups
"tesseract-ocr" group.
To unsubscribe from this group and stop
Paul,
at the moment focus is on 4.0 release. But I understand that some user
still need/prefer to use 3.05.
Can you create some test/demonstration case for you last bugfix? Is it not
fixed in 4.00...
Zdenko
ne 3. 6. 2018 o 4:03 Paul Kitchen
napísal(a):
> Zdenko,
>
> Thanks for making that
Zdenko,
Thanks for making that fix. I am currently running tesseract from source on
my computer. I've already made the fix on my source. However, if the fix
were in an official release, then I could go back to using the officially
released product.
I did find one other bug that I fixed
Please check if this is ok now. If yes, I am willing to make 3.05.02
release ;-)
Zdenko
so 2. 6. 2018 o 10:16 Zdenko Podobny napísal(a):
> done in
> https://github.com/tesseract-ocr/tesseract/commit/bc5dfc4b953babcc865f68a55c3bf415f4280b1a
> Zdenko
>
>
> št 31. 5. 2018 o 22:39 shree
done in
https://github.com/tesseract-ocr/tesseract/commit/bc5dfc4b953babcc865f68a55c3bf415f4280b1a
Zdenko
št 31. 5. 2018 o 22:39 shree napísal(a):
> This has been an issue for long. Thanks for finding the problem.
>
> Please submit a PR on github.
>
> On Friday, June 1, 2018 at 1:55:25 AM
15 matches
Mail list logo
