Switch from tesseract to google text-recognition#1926
Draft
Switch from tesseract to google text-recognition#1926
Conversation
ArthurKun21
force-pushed
the
ml-text-recognition
branch
from
1b63ff6 to
382b04f
Compare
Collaborator
|
need to push this or update tesseract in a while https://github.com/Fate-Grand-Automata/FGA/actions/runs/14648963323/job/41109958586 https://jitpack.io/com/github/adaptech-cz/Tesseract4Android/4.7.0/build.log |
Collaborator
Author
|
The APK didn't get any smaller so I didn't continue with this approach. |
Collaborator
Author
|
Tested Google ML text recognition again. It doesn't work with the current code for numbers like x6 where it returns an empty string instead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.