> hi,
> $ tesseract 205c.tif 205c --psm 6 -c 
> tessedit_char_whitelist=ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789=+&
> as per my knowledge tessedit_char_whitelist works with tesseract 3 not 
> with tesseract 4. 
>
> - show quoted text -
>
>> - show quoted text -
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "tesseract-ocr" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tesseract-ocr/a552cd6a-2c06-4d79-80ec-a973aaecf2fa%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tesseract-ocr/a552cd6a-2c06-4d79-80ec-a973aaecf2fa%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> Thanks & regards,
> Ashwini 
>

That was true with 4.0.0, but not with 4.1.0 -- the version that I am 
using: https://github.com/tesseract-ocr/tesseract/releases

4.1.0 Release 
> <https://github.com/tesseract-ocr/tesseract/releases/tag/4.1.0> 
>
> [image: @zdenop] <https://github.com/zdenop> zdenop 
> <https://github.com/zdenop> released this on Jul 7 ยท 601 commits 
> <https://github.com/tesseract-ocr/tesseract/compare/4.1.0...master> to 
> master since this release 
>
>    - Added new renders Alto, LSTMBox, WordStrBox.
>    - Added character boxes in hOCR output.
>    - Added python training scripts (experimental) as alternative shell 
>    scripts.
>    - Better support AVX / AVX2 / SSE.
>    - Disable OpenMP support by default (see e.g. #1171 
>    <https://github.com/tesseract-ocr/tesseract/issues/1171>, #1081 
>    <https://github.com/tesseract-ocr/tesseract/issues/1081>).
>    - Fix for bounding box problem.
>    - *Implemented support for whitelist/blacklist in LSTM engine.*
>    - Improved cmake configuration.
>    - Code modernization and improvements.
>    - A lot of bug fixes...
>
> Furthermore, if I run that command by itself without the space variable, 
then it whitelists the characters just fine--just as I said in the post.

But even if the whitelist weren't working, it would still be a bug because 
it says in the release notes that whitelist is working.

Should I submit this bug report? Does anyone else think this deserves a bug 
report?

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/063b89a0-489f-4282-a693-f3369aee8b92%40googlegroups.com.

Reply via email to