Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: gocr - GNU Optical Character Recognition program https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216534 ------- Additional Comments From pertusus@xxxxxxx 2006-11-23 05:51 EST ------- Looking at tkispell on the web it doesn't seems to be maintained, and it is not obvious where upstream is. Looking at the gocr.tcl code, it looks like spellchecking involves putting a file named out01.txt in the current directory which is not cleaned up, and is the same file the output text is saved to in the default case... My opinion would be to disable this functionality. I did it simply by commenting out pack .abar.spell -side left I spotted another issue, the config file is found and written in the current directory, and not in $HOME! This is bad... Maybe we shouldn't ship gocr.tcl? It hasn't really be changed in 4 years. Testing a bit gtk-ocr, I found at least 2 bugs (a crash, and also at another point the files appeared but I couldn't convert them). It is saner with regard with the handling of config file, however the converted file is saved in a file with same name than input file with .txt appended without any possibility to override this, nor any explanation of where the converted file is saved to... The default image viewer here is display from ImageMagick. Looking at the cvs, it seems that it hasn't been changed in 6 years. My personal opinion is that those 2 frontends are too buggy and unmaintained to be shipped. Now regarding the segfault, I think it is problematic since it seems to me that support for widely used image formats (png, eps, jpeg) should be working in a shipped package. For devel it is not problematic, but for FC-6 and below I think this should be a must. Not supporting compressed images is not an issue in my opinion. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review