Red Hat Bugzilla – Bug 999912
MATE document viewer (Atril): case-sensitive search impossible, DjVu search broken
Last modified: 2014-03-30 02:09:00 EDT
Description of problem:
Any text document viewer _should_ be capable do (optional) case-sensitive search,
but it seems as Atril lacks this functionality, and searching is implemented somehow badly. Concretely:
- button/checkbox for specifying case-significant/caseless searching missing (tested on PDF and DjVu documents)
- entering text with upper-case character in "Find:" results to not finding
text in document, although this text is there! (tested with DjVu document)
Version-Release number of selected component (if applicable):
Searching function should be able do at least optional case-sensitive/nonsensitive search, eventualy more advanced search options as searching text on word boundary, searching by regexp etc.
Broken searching in DJVU documents should be corrected (e.g. djview4 DjVu viewer search docoments without problems)
You should file out a issue report at upstream.
Upstream is informed.
mate-document-viewer-1.6.2-2.fc20 has been submitted as an update for Fedora 20.
mate-document-viewer-1.6.2-2.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mate-document-viewer-1.6.2-2.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Thanks for elimination this problem. It would be good if the version for F19 was available, as I have no F20 yet. Or I can try build F19 package yourself.
Follow link in comment 4 ;)
or use updates-testing.
mate-document-viewer-1.6.2-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mate-document-viewer-1.6.2-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.