https://bugs.kde.org/show_bug.cgi?id=318798
--- Comment #32 from Chris George <technat...@gmail.com> --- Using poppler, examine the file and read a "copy" as text into a database. Make the annotations. Then again using poppler, read the annotated file. Diff to find the Object ID, make note in the database. Manipulate the crap out of the file. Add annotations, delete annotations, edit annotations. As long as the annotation still exists with its unique identifier, I can pull the content out of the pdf via a python script and supply okular with a command line argument to open the file at the correct location. It would be simpler if the pdf reader supplied the Object Identifier as part of what is visible about the annotation. Chris On Tue, Feb 10, 2015 at 12:44 PM, Albert Astals Cid <aa...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=318798 > > --- Comment #31 from Albert Astals Cid <aa...@kde.org> --- > Veeeeeeery long text, you're still not telling me how you as a user are > going > to tell in the command line which annotation you want to open, are you > going to > tell me "182 2" so i open generation 2 of object 182? How are you even > going to > know the anotation you want it's object 182? > > -- > 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