You currently support creating and loading annotations embedded within a PDF FIle. However, we are storing annotations separately from our PDF files and “side-loading” them when needed. The question is, does the PDFTron API support parsing from these raw bytes. I have included some sample data below to illustrate the data we are working with.
Recently we made changes to FDFDoc.SaveAsXFDF() method so that the string parameter it takes can be either the filepath or the XML string buffer that contains the XFDF itself. Similarly there is a method to load from a file or a string (if the string is not a path). This will be included as part of the next official release (the unoffical build already include new methods).
/**
Convert FDF file to and from XFDF file
@param filepath - string containing either the XFDF file name or the xml buffer containing the XFDF
@return A new TRN_FDFDoc.
*/
static FDFDoc CreateFromXFDF( const UString& filepath );
/**
Export FDF file as an XFDF file
@param filepath - the filepath of the exported XFDF file
*/
void SaveAsXFDF( const UString& filepath );
/**
Export FDF file as a XFDF string
@return A UString containing the XFDF representation of the FDF file
*/
UString SaveAsXFDF();
With a PDF document already loaded and displayed in PDFTron, we would like to be able to dynamically add annotations created sometime after document load.
In our case, the annotation is persisted to a server as a string of text conforming to the PDF spec, so our hope is that we can leverage existing PDFTron file parsing code even though the PDF will already be fully loaded. The sequence would be:
We load a PDF file in the usual way
Sometime later we receive a message containing an annotation as a text string conforming to the PDF spec
We call some PDFTron API with the annotation represented as a text buffer
The annotation appears overlaid on the file loaded in step 1
From your response, I’m assuming that an XFDF acts as a kind of container for form elements, such as annotations, and that in my step #3 above, we would call your new API method: CreateFromXFDF() passing in the text buffer. Is this correct? If so, I see that it returns an FDFDoc. Is there some additional step to associate this FDFDoc with the originally loaded PDF?
On Thursday, April 11, 2013 5:55:37 PM UTC-7, Support wrote:
Q:
You currently support creating and loading annotations embedded within a PDF FIle. However, we are storing annotations separately from our PDF files and “side-loading” them when needed. The question is, does the PDFTron API support parsing from these raw bytes. I have included some sample data below to illustrate the data we are working with.
Recently we made changes to FDFDoc.SaveAsXFDF() method so that the string parameter it takes can be either the filepath or the XML string buffer that contains the XFDF itself. Similarly there is a method to load from a file or a string (if the string is not a path). This will be included as part of the next official release (the unoffical build already include new methods).
/**
Convert FDF file to and from XFDF file
@param filepath - string containing either the XFDF file name or the xml buffer containing the XFDF
@return A new TRN_FDFDoc.
*/
static FDFDoc CreateFromXFDF( const UString& filepath );
/**
Export FDF file as an XFDF file
@param filepath - the filepath of the exported XFDF file
*/
void SaveAsXFDF( const UString& filepath );
/**
Export FDF file as a XFDF string
@return A UString containing the XFDF representation of the FDF file
*/
UString SaveAsXFDF();