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

[Will Jordan]

------- 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         




------- Additional Comments From will.jordan gmail com  2008-07-13 13:16 -------
I'm wondering if there has been any activity on solving this bug in the past few months, or are things at a standstill regarding the annotations feature? As a PhD student this bug is the most anticipated feature in all of KDE4 for me, and has been ever since I heard the first early reports on Okular's development.

Two main suggestions have been provided so far:
1. Recent LibPoppler patches allow saving back to PDF files. Okular would have to update its framework to allow saving to files in general, and saving annotations to PDF files in particular.
2. Bundle the annotations XML with the document into a new bundle format (.okular), which would work with any document type but would be a solution specific to Okular and other programs that add specific compatibility for this format.

I have a couple more suggestions:
3. Rather than save the annotations XML into an internal directory, attempt to save it in the same directory as the opened document matching the filename (ex. for document.pdf create a file document.pdf.okular in the same directory). This will make the annotation file more accessible to the end user and would simply solve many of the usability issues with the current system.
4. Okular needs to add the ability to extract annotations that are 'baked-in' to the PDF file into its own XML format, so that the user isn't left with the situation where half of his annotations are in one place/format and half are somewhere else for the same document.
5. If no other work is being done on an annotations solution, I would love to see Jonathan's packages added into the main distribution. Even if it is an incomplete, hackish, temporary PDF-only solution, it is MUCH better than not having anything until a fully robust, document-universal solution is finally ready many more months/years down the line.