[okular] [Bug 394775] Annotations in the separated XML files

[ederag]

https://bugs.kde.org/show_bug.cgi?id=394775

--- Comment #16 from ederag <edera at gmx.fr> ---
Good news: an experimental helper script seems to workaround our use case.
(there are issues, it's not ready to share yet)
It required a two line hack (not satisfying yet) to okular,
so that the archive holds the original file, 
and the annotations in its metadata.xml.
The helper is using sha512sum, so the annotations follow file renames.

So if okular would keep the ability/option to store annotations in
metadata.xml,
together with an option to avoid https://bugs.kde.org/show_bug.cgi?id=397097,
then chances are we could all be happy.

Why think so ?
The reasons for burning things into the pdf were indeed compelling:
- confusion on renames, 
- use cases opposite to ours (https://bugs.kde.org/show_bug.cgi?id=315552)
- and security issues with forms data
(https://bugs.kde.org/show_bug.cgi?id=267350)

The latter forces to burn the form data into the pdf.
So it was decided to burn annotations into as well.

Yet there is a strong difference between forms and annotations:
one writes *into* a form ("fill a form"), while
one *adds* an annotation *onto* a document.

Please don't get me wrong, 
I'm not prying to change the default behavior at all.
Just advocating that our use case makes sense as well, 
and would be a nice option to have.

-- 
You are receiving this mail because:
You are the assignee for the bug.