![]() |
#16 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,653
Karma: 730583
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
Quote:
With regard to the OCR, it's not the most polished feature. An ereader is not a very powerful device, so we only feed the OCR engine very tiny parts of the page. It can be nice for the occasional use, but if you know in advance it might be better to do the OCR on your PC first. It'll do it a heck of a lot faster. A lack of spaces in Greek certainly sounds odd. We'll have to check what's up with that. Not detecting spaces properly can sometimes happen in the Latin alphabet with italics, so I didn't think much of it. |
|
![]() |
![]() |
![]() |
#17 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 171
Karma: 1686
Join Date: Jul 2020
Location: Greece
Device: Pocketbook Touch Lux 5
|
I finally upload the screenshots I mentioned.
I still can't understand why there are only two options for the text language? What should be the second option instead of "Chinese"? Each user has to make the change manually in the defaults.lua? You're right, Frenzie, about ocr in ereaders and I understand this weakness. I just mean to use this feature for occasional use. Also it's very useful just to highlight an unrecognized text. Last edited by ichnilatis; 12-31-2020 at 08:25 AM. Reason: completion |
![]() |
![]() |
![]() |
#18 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,653
Karma: 730583
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
As I said, it's a lack of polish for that particular feature. There isn't really a reason other than that the person who implemented it isn't an active contributor anymore.
|
![]() |
![]() |
![]() |
#19 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 171
Karma: 1686
Join Date: Jul 2020
Location: Greece
Device: Pocketbook Touch Lux 5
|
|
![]() |
![]() |
![]() |
#20 | |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 171
Karma: 1686
Join Date: Jul 2020
Location: Greece
Device: Pocketbook Touch Lux 5
|
Quote:
I created the persistent.defaults.lua file by copying only the ocr lines from defaults.lua. However, when I updated KOReader, these settings did not apply as defaults.lua was replaced. How can I maintain persistent.defaults.lua settings after each update? Do I have to copy-paste these lines into default.lua every time I update KOReader? |
|
![]() |
![]() |
![]() |
#21 | |
cosiñeiro
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,316
Karma: 2200073
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Quote:
The file should be named "defaults.persistent.lua", not "persistent.defaults.lua". If you're using windows as your OS do the following: 1. with Windows explorer copy "defaults.lua" and paste it as "defaults.persistent.lua" 2. open the new file with Notepad++ 3. Remove all the lines you won't plan to override (most of them I guess) 4. Edit the rest of lines to match your preferences That's it. Changes is defaults.persistent.lua should persist, as the name implies ![]() If for some reasons you won't see your changes in the program that means you made a typo. The program will prevent you to load "broken code" and will fallback to default. Here is an example of a typo: Code:
SOME_STRING = "Unfinished string SOME_OTHER_STRING = "OK string" Last edited by pazos; 01-25-2021 at 07:48 AM. |
|
![]() |
![]() |
![]() |
#22 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 171
Karma: 1686
Join Date: Jul 2020
Location: Greece
Device: Pocketbook Touch Lux 5
|
Thank you a lot! I will check it in the next update.
At least, it's not too much to copy-paste it after every update... |
![]() |
![]() |
![]() |
#23 |
Just trying to survive
![]() ![]() ![]() Posts: 66
Karma: 210
Join Date: Mar 2009
Device: Nexus 7 2013, Galaxy Note 10.1 2014
|
I have now problems with ocr. What can I do?
|
![]() |
![]() |
![]() |
#24 |
Zealot
![]() ![]() ![]() ![]() Posts: 129
Karma: 338
Join Date: Nov 2004
Device: Ebookwise 1150, Jetbook Lite, Slick Er-701
|
I've had my share of OCR troubles too, especially when dealing with documents for work. It can be really frustrating when the technology doesn't seem to catch up with the languages or details we need it to recognize. What really turned things around for me was finding a solution that could handle a wide range of languages and document types accurately. That's where Identity Verification services, like those offered by ID Analyzer, come into play. Their advanced OCR technology is designed to accurately extract data from a variety of documents, even those that are out of focus or have low resolution. This capability is especially useful in a professional setting where accurate data capture and multilingual support are critical. Their system has proven to be reliable for me, offering peace of mind that the information is being processed correctly.
Last edited by Highroller; 03-15-2024 at 07:02 AM. |
![]() |
![]() |
![]() |
Tags |
ocr |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
OCR problem in a PDF flie | mzel | KOReader | 16 | 04-21-2020 01:09 PM |
pages in OCR | cloclo36 | Assistance | 0 | 06-03-2019 12:19 PM |
How to convert an OCR file to a Non-OCR one | res9282 | 1 | 08-05-2011 05:58 AM | |
Do I have to OCR? | Ceryta | Workshop | 7 | 05-07-2011 11:03 AM |
OCR to use | pepak | Workshop | 17 | 05-26-2008 05:30 PM |