https://bugs.kde.org/show_bug.cgi?id=425148
--- Comment #10 from jpror...@gmail.com --- I'm starting to wonder if this might actually be an issue in Poppler but need some guidance in understanding the logic that Okular follows in the conversion process. As noted, Okular is correctly restoring the original create/mod dates of the annotation from its original storage. It prompts the user to save the PDF to a file to preserve the annotations with the PDF. At this point I have traced lots of code, but it seems to come down to Okular handing of the Save operation to the PDFGenerator::save() method. There is a QHashIteration across the annotations that compares unique ids between okular annotations and poppler annotations, but doesn't seem to have any other affect. The actual save of the current Okular document that needs migration appears to be handed off to the Poppler::PDFConverter(). It seems like this utility takes the current Okular PDF document and saves it out to a temporary file. It's during this operation that the original annotation create/modify times are lost. The temp file is then copied to the saveAs target, but by that time the times are already set to the current date. Is this understanding correct? If so, is there any way to control the conversion of the annotations within Okular to avoid this issue. I thought the PopplerAnnotationProxy might be able to, but it doesn't seem to be invoked by Poppler during the PDFConverter. -- You are receiving this mail because: You are watching all bug changes.
