121–130 of 141 posts
I wonder how deep this project is in violation of the GPLv3. For starter it's based on gnu ocrad [1] but fails to state a license and to publish any source code. [1]: https://www.gnu.org/software/ocrad/
Earlier quoted context omitted.
It was suggested to me by a friend that to get good OCR results, run it through the scanner/OCR twice, then diff the results. Usually one or the other will get it right, and if you run the two results through a difference editor like 'meld', it's quick to fix.
That may work for some cases, and especially with horrible OCR engines and low quality scanners, but frankly when I did my research into this, the results varied extremely little from run to run, and you could usually easily identify specific artefacts in the source that tripped the engine up (rather than problems with the quality of the scan). E.g. letters that were damaged, or had run together, creases in the paper…
Extension is awesome and while the code is messy, it has enough little jokes to keep you amused. For those looking to access the backend OCR service, it seems to be down right now, but will hopefully come back up soon. Here were the API references I could find for the remote OCR: - GET " rel="nofollow">https://sky-lighter.appspot.com/api/read/ - GET " rel="nofollow">https://sky-lighter.appspot.com/api/lookup?url= - P…
Yeah, I made the mistake of setting the App Engine budget to $1.00. Turns out that's probably not enough for a sustained run as HN's #2. Yeah, the code is super messy, but I'd prefer if you didn't play around too much with the remote OCR service, specifically, the translation parts because Google Translate is pretty expensive per-use.
Every time I click "Allow" on "Access data on all sites" for an extension I creep closer to my security hole paranoia threshold. If it was all in JS, who cares? But this sends ajax to remote servers of course. Am I alone?
That is the wording that Google Chrome chose for "allow this extension to access the DOM on any page". It sounds bad but these are the permissions an extension needs to be able to access images and text on any page.
Here is the picture: http://thesuperslice.com/wp-content/uploads/2012/04/downtown...
And the text outcome - found it most interesting what symbols it thought it recognized:
lam
on-0'0
s.
Ic 0on
§-i-
I-*-
-unm
-$3.»;
o
G %T1
00-O
. o C-‘7' H ' .-.”-." «'~3;
.35
$16 O-O
‘D Q-=¢1
‘-M
km“
‘MIMI
DOW:
TLDR
D001”
'."'IIu
ff"
)0‘
\\
,¢-.5 ,:~L.
r/J
However, it seems to confuse letter O and number 0. Since serial numbers are not English words, I'm not sure how you would solve this unless you had a lookup for commonly used web fonts.
Anyway, good luck!
I posted a review on my blog here: http://www.sinosplice.com/life/archives/2014/04/24/can-proje...
OP, I'd be happy to work with you on improving the recognition of Chinese text. Just get in touch with me through my blog (linked to above).
