https://bugs.kde.org/show_bug.cgi?id=318798
--- Comment #28 from Chris George <technat...@gmail.com> --- This is my understanding of the problem. I could, and most likely am, wrong. In external application, create annotation. Annotation is created and assigned an Object Identifier. The file is saved. At a later date the PDF file is accessed using a script or the same application that searches for the Object Identifier and pulls its content into a file or opens the pdf at the page of the annotation. The logical method would be to pass the Object Identifier via command line. The proper method, according to the PDF 1.7 spec, page 63, is to assign unique Object Identification numbers to all indirect objects and then to increment content while maintaining the original Object Identifier. The examples are in Appendix G, pg. 1075. Pretty much all viewers that allow annotations use a short-cut, and increment the Object Identifier with each write as annotations change or other segments are added to the file. So for example, I could open a pdf in Adobe Acrobat Viewer, make an annotation, take note of the Object Identifier and then save the file. I could then open the file in any other viewer, change the annotation by adding or removing content and then save the file. This would break the Object Identifier by changing it, making any attempt to go to it in the future using the original Object Identifier futile. If the Object Identifier were to remain constant, then pulling it up at a future date with a different application or script would be possible. As it stands, it isn't. Chris On Mon, Feb 9, 2015 at 11:07 AM, Albert Astals Cid <aa...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=318798 > > --- Comment #27 from Albert Astals Cid <aa...@kde.org> --- > It would be awesome, yeah, just that noone has told me how a user is > supposed > to tell okular which annotation should be focused. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel