Summary: | Six Suggestions For Okular | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | lybkexskmguugovejv |
Component: | New backend wishes | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED MOVED | ||
Severity: | normal | CC: | oliver.sander |
Priority: | NOR | ||
Version: | 24.08.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
lybkexskmguugovejv
2024-11-11 02:16:08 UTC
Please file individual issues for each of your suggestions. Please check beforehand whether other people have filed the same issue, to avoid duplicates. This is not to say that your suggestions are bad, but combining several issues in one bugtracker thread makes it very difficult to keep track of what has been done and what not. 7. Saving a large epub requires it to reload, to avoid this I simply don't save often, which causes me to lose data in highlights, or lose 30 seconds waiting for the process to finish. Also, it took time for me to elaborate these seven points. To disqualify it simply as this, wasted my free time trying to improve this software as much as those working on the code as well do for free. It's a truly unfair label to status as resolved so the maintainers never be able to see PRACTICAL IMPROVEMENTS suggestions that has been for years. There's not a more disrespectful way to imply a request website signup was this useless thanks to a bureaucratic template. It's posted. I tried helping. If it doesn't please someone reading like this you can bury again. Please read my message again. Setting the status to RESOLVED MOVED does not mean that we don't care. It is simply that we cannot work with bugtracker entries that combine several unrelated issues. Therefore I was asking you to open separate entries for each of your suggestions. |