diff --git a/Document-Processing/PDF/PDF-Library/NET/Working-with-Annotations.md b/Document-Processing/PDF/PDF-Library/NET/Working-with-Annotations.md index 8805c4bea..5d6933f83 100644 --- a/Document-Processing/PDF/PDF-Library/NET/Working-with-Annotations.md +++ b/Document-Processing/PDF/PDF-Library/NET/Working-with-Annotations.md @@ -5833,7 +5833,7 @@ freeText.SetAppearance(true); -## Missing annotation after importing the data into the PDF document +### Missing annotation after importing the data into the PDF document @@ -5936,3 +5936,30 @@ lDoc.Close(True)
Issue
+### Why are annotation comments and review history not properly linked to their parent annotations when loading a PDF document? + + + + + + + + + + + + + + +
Exception + When loading certain PDF documents, annotation comments and review history may not be correctly linked to their parent annotations. As a result, the annotation hierarchy (such as sticky notes with replies) can appear flat or fragmented, making it difficult to track comments and review history. +
Reason + Linking between annotations relies on specific relationships defined in the PDF's annotation dictionary. If comments (such as pop-up notes or replies) are not properly referenced or classified in the dictionary, the PDF parser may fail to associate them with their parent annotations. This is especially important for popup annotations (used for sticky notes and comments), as proper classification ensures they are managed correctly during parsing and rendering. +
Solution + To ensure annotation comments and review history are properly linked:
+ 1. Verify that popup annotations and review comments in the PDF are correctly classified and referenced in the annotation dictionary.
+ 2. Use PDF tools or libraries that adhere to the PDF specification for managing annotation parent-child relationships.
+ 3. When generating or editing PDFs, ensure that comments and replies are created as child annotations linked to their parent through the appropriate dictionary structure (for example, by setting the /Parent entry in the annotation dictionary).
+
+ Following these steps will ensure that annotation histories are accurately loaded, rendered, and navigable, providing a clear and traceable experience for reviewers and readers. +
\ No newline at end of file