Version: (using Devel) provide "system check" (auto?) Since it looks now okular is rather loosely dependant of the external tools it would be good to provide system check (similar to Kile or Krusader). I am not only sure if this should be automatic, or on demand. This way user will be not surprises she/he cannot read format XYZ.
> Since it looks now okular is rather loosely dependant of the external tools Can you explain this nonsense? Or better, instead of explaining _your_ solution, please tell the _problem_.
We don't depend on any external tool, we depend on external libraries, but that is not something the user can fix on runtime, has to be fixed by the distribution/user on compile time. What could be a interesting idea is a list of installed plugins and the mimetype each plugin supports. So at least he can know what he can read. The problem is helping him what to do if he can't read format XYZ. Not sure if that adds great value
It is possible to install okular without unrar for example. So user can run okular without knowing (because okular does not do any checks) that reading cbr format is not possible. User will know it only when she/he actually try to open it. However, when user install okular she/he can be online, but when reading this or that format, she/he can be off-line and it could be to late to install anything. So it would be useful to have summary what is missing to have full capabilities of okular -- just an information, like in krusader or kile. Albert -- it helps kile and krusader a lot, because user can know in advance what to install to have all features enabled. So why it won't help okular user? Hiding such info is not helping for sure (or testing one by one after install -- can I read chm, can I read pdf, can I read djview...)
> It is possible to install okular without unrar for example. True, but distros should take care to show/provide hints about optional dependecies of application to the user. And if you install from sources, you know what you are doing. The comparison with Kile is quite unfair, as Kile relies quite a lot on other applications/components, and without those can be also unuseful at all (while Okular without unrar cannot just read cbr files, while it still can read cbz, for example). Oh, and a side note: can you please *stop* repating the bug subject as the first line in the comment? Thanks.
I am not comparing, I am saying it is useful. Also I posted a report against distro, because you are right it is job of the distro too. Side note: I was explicitly asked to ADD those subjects, and I can tell it is quite useful (not for me) despite it requires more effort on my side. So sorry, I will keep doing it because from time to time somebody changes summary to such degree it is impossible to tell what was the original. I can't tell in advance if the summary will be changed or not. So I think it is best solution found so far.
(Reply to the side note: right to the "people" area, just above the comment area, there is a "View Bug Activity" link. If - among the other info - the subject is changed, the change is visible there, so it *is* possible to know how things changed in a bug report.)
(Side note: many thanks! It works, so less work for me ;-) ).