| Summary: | Save annotations internally (docdata) | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | Jonathan Schmidt-Dominé <devel> |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 1.3.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Jonathan Schmidt-Dominé
2018-07-20 00:19:55 UTC
*** This bug has been marked as a duplicate of bug 394775 *** Thanks Christoph for refering to the duplicate, I had not found it, sorry. Would you mind telling me if there is any major problem with saving annotations internally impeding other features? Or is it just a general usability decision to replace it by another behaviour? (so I would be warned if I want to maintain a fork) Thank you very much! It was a general usability decision. Saving annotations into the PDF itself was one of the most frequently requested features for Okular. We didn't want to maintain two user interfaces for the feature--one of which did what people expected and another that didn't do that and was full of bugs (for example, if you used Dolphin to change the name of a PDF with externally-saved annotations, the external annotations wouldn't be associated with the document anymore). Thank you very much, Nate! |