Open GoogleCodeExporter opened 9 years ago
when ocr something in Japanese or Chinese ,the result characters are always
irrecognizable (Garbled as the attached image), how to make it correct?
Original comment by aven...@gmail.com
on 12 Apr 2011 at 8:37
Attachments:
@aven...:
The application demos only for English!
I have modified "tessedit.cpp" file for configuration tessdata folder!
You can find it at
http://tesseractdotnet.googlecode.com/svn/trunk/dotnetwrapper/TesseractEngineWra
pper/
Original comment by congnguy...@gmail.com
on 13 Apr 2011 at 4:21
Hi congnguy...
thanks for you reply . actually I modified the ocr setting ( i.e. lang) in the source code according to the image content before run it .
"The application demos only for English!" do you mean that this wrapper is just
for english ? if so ,is it possible to make it compatible to other languages?
please give me some instructions .
thanks again!
Original comment by aven...@gmail.com
on 13 Apr 2011 at 1:00
No, wrapper supports any language, but demo is only for English!
Default, tesseract engine always load tessdata from default path enviroment!
You can download tessedit.cpp, and configure according project settings to
build with preprosessor BUILDASDLL!
Original comment by congnguy...@gmail.com
on 13 Apr 2011 at 3:53
OCR cannot do with Viet language, can you explain to me?
Original comment by phamphih...@gmail.com
on 17 Apr 2011 at 10:14
Attachments:
And it also cannot do with image rotated?
Original comment by phamphih...@gmail.com
on 17 Apr 2011 at 10:20
Attachments:
Sorry for long time no updating project!
I don't have time to work on project now!
So I have released the version included the work space I have worked on!
Hope that it will resolve existed issues!
Cong.
Original comment by congnguy...@gmail.com
on 16 May 2011 at 3:27
Hi comg.
Great job! I'm always keep my eyes on this project.
the only problem making me feeling bad is that I still cannot get the correct
result when ocr something like Japanese or Chinese . With your help ,these
characters can be extracted correctly ,but the result is also irrecognizable.
I checked and modified anything you mentioned , but it didnot work . I donnot
know where the problem is . -_-
Original comment by aven...@gmail.com
on 16 May 2011 at 5:02
[deleted comment]
Hello please guide how to overcome this error.
Original comment by muhammad...@gmail.com
on 11 Feb 2014 at 4:46
Attachments:
Original issue reported on code.google.com by
aven...@gmail.com
on 12 Apr 2011 at 8:24Attachments: