Typically, it is the text to be displayed for the annotation or, if the annotation does not display text, an alternate description of the annotation’s contents in human-readable form.
This item will be closed as its subject is too broad. Please refer to the information below for the individual markup annotations.
As of now, the currently supported markup annotations are:
Text
Line
Highlight
Underline
Squiggly
StrikeOut
Stamp
The unsupported annotations and their respective feedback items are:
FreeText
Square
Circle
Polygon
PolyLine
Caret
Ink
FileAttachment
Sound
The common annotation properties are described in table "Entries common to all annotation dictionaries" of the Pdf specification.
Declined: Handling a partial annotation import-export could lead to exporting invalid PDF documents.
When exporting a document referencing PdfProcessing`s .NET Standard assemblies with PdfComplianceLevel set an exception is thrown.
A Link annotation must have an associated action, destination, or named destination specifying what should happen when the annotation is activated. When merging documents with invalid Link annotations, an ArgumentException is thrown with the message 'Value cannot be null. Parameter name: namedDestination'
Workaround: Remove the invalid annotations:
foreach (var annotation in document.Annotations.ToList())
{
var link = annotation as Link;
if (link != null && link.Action == null && link.Destination == null && link.NamedDestination == null)
{
(annotation.Parent as RadFixedPage).Annotations.Remove(annotation);
}
}
I have read that there limitations to PDF files being imported, however, the file being imported was generated with FixedContentEditor, so, should be able to import?
using (Stream stream = Stream){
try
{
this._document = provider.Import(stream);
_InputPath = fileName;
}
catch (Exception e)
{
Errors = "Could not open file " + fileName + ": " + e.Message;
this._document = null;
}
}
}