[Okular-devel] [Bug 151614] store annotations with documents

[Roman I Khimov]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151614         
rik osrc info changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rik osrc info



------- Additional Comments From rik osrc info  2008-08-01 18:32 -------
Several things to say.

First of all, IMHO, PDF/PS/DVI and some others are not supposed to be edited in any way (yep, I know about PDF interactive features and that's not sane, IMO). They're final, finishing formats, so to say. Changing such files is not a good idea. At least I'm not expecting _viewer_ to _change_ my files (yep, Adobe seems to be doing that and that's not a good reason to follow, IMO). 

Then, there's privacy issue. What if I want to annotate some document, but don't want to share annotations?

To summarize I expect document data to be verbatim, not changed by viewing and I don't want to mess _my_ data (annotations) with the document data.

Then, as Okular user with ability to annotate any document (not only PDF), I'd expect that it will also give ability to share this annotations for any document format.

So, IMO, separated annotations as it is now is absolutely fine and sane way of things. Of course, if anyone implements _option_ to save annotations in the PDF, I have nothing against that, but as long as it is _option_ and not default one.

We just have a problem of transmitting metadata (annotations) along with the document. I don't think .okular format is good way to handle it (yet another file format (even if it's something like tarball in reality), doh!), it's better just to have two "Export Okular metadata" (or "Export annotations") and "Import Okular metadata" buttons that will just copy xml from dark internals of ~/.kde4 to user-specified place and that's it.

BTW, saving xml in the same dir by default is not a good idea, IMO, don't litter user directories with strange files! Just give ability to export/import.

Now, one another thing to handle is document renaming, but as pointed above several times, that is easily done by hashing (MD5/SHA1, pick any, there is no need for strong cryptographic function) and checking hashes when detection by url gives nothing.

Well, that's my IMHO on this popular issue, if anyone cares.