adobe pdf library c#: How to save fillable pdf form in reader application SDK utility azure wpf winforms visual studio PDFTron_PDFA_Manager_User

3.3 Basic Usage

This section covers the basic usage of PDF/A Manager, explaining all the available options and

illustrating examples.

3.3.1 How to save converted PDF/A files in a given folder?

By default, PDF/A Manager stores converted files in the current working folder. To specify another

output location, use the ‘-o’ (or --output) parameter. For example:

pdfa –o "c:\My Output" --convert 1.pdf 2.pdf 3.pdf

Note: If the specified path does not exist, PDF/A Manager will attempt to create the necessary

folders.

3.3.2 How can I control the output name for converted PDF/A files?

By default, PDF/A Manager will create a single output PDF/A document based on every input PDF

file. The output filename is constructed by appending a suffix to the name of the input PDF file. For

example, ‘my.pdf’ will be saved as ‘my_pdfa.pdf’. It is possible to change the suffix using --suffix

option. For example:

pdfa -o OUT --convert --suffix "converted" "c:\mypdfdir"

3.3.3 How do I run PDF/A Manager in validation mode?

To run PDF/A Manager in validation mode simply omit ‘-c’ or ‘--convert’ from the command line. For

example,

pdfa --noxml my.pdf

3.3.4 How do I convert/validate a password protected PDF?

PDF/A Manager will, without user intervention, decrypt and convert documents secured with a

master/owner password. If the document is secured using a user (or ‘file open’) password, PDF/A

Manager will prompt you to enter the password.

For unattended conversion, the password can also be specified directly on the command-line using

the ‘-p’ (or --password) option. For example:

pdfa -p secret -c secured.pdf

The above command line will convert PDF to PDF/A and will use the provided password (‘secret’) to

open the secured document (i.e. ‘secured.pdf’).

Note: PDF/A Manager supports all standard security options available in PDF, including 40 and 128

bit RC4 encryption, Crypt filters, and 128 AES (Advanced Encryption Standard) encryption.

How to save fillable pdf form in reader - extract form data from PDF in C#.net, ASP.NET, MVC, Ajax, WPF

Help to Read and Extract Field Data from PDF with a Convenient C# Solution

pdf data extraction; extract pdf form data to xml

How to save fillable pdf form in reader - VB.NET PDF Form Data Read library: extract form data from PDF in vb.net, ASP.NET, MVC, Ajax, WPF

Convenient VB.NET Solution to Read and Extract Field Data from PDF

how to save a filled out pdf form in reader; pdf form field recognition

3.3.5 How do I process PDF files in a batch?

PDF/A Manager supports batch conversion and validation of many PDF files in a single pass. To

convert all PDF files in a given folder(s) you can use the following syntax:

pdfa myfolder1 myfolder2 ...

The ‘--subfolders’ option can be used to recursively process all subfolders. For example, the following

line will convert all documents in ‘myfolder1’ and ‘myfolder2’ as well as all subfolders:

pdfa --subfolders myfolder1 myfolder2

By default, PDF/A Manager will convert all files with the extension ‘.pdf’. To select different files

based on the extension use the ‘--extension’ parameter. For example, to convert all PDF documents

with a custom extension ‘.blob’, you could use the following line:

pdfa --extension .blob --subfolders myfolder1

Wildcard characters can also be used to process multiple input files.

For example, if a directory contains the following PDF documents:

C:\test1 >dir

Directory of C:\test1

01/04/2009 03:35 PM <DIR> .

01/04/2009 03:35 PM <DIR> ..

05/21/2009 02:27 PM A1.pdf

05/03/2009 09:38 AM A2.pdf

05/20/2009 08:46 AM B1.pdf

05/15/2009 12:50 PM B2.pdf

To process all PDF documents in this folder, you could specify:

c:\>pdfa --noxml c:/test1/*.pdf

To process all PDF documents staring with ‘A’, you could specify:

pdfa --noxml c:/test1/A*.pdf

Or to process all PDF documents ending with ‘1’, you could specify:

pdfa --noxml c:/test1/*1.pdf

You can use either of the two standard wildcards — the question mark (?) and the asterisk (*) — to

specify filename and path arguments on the command line.

The wildcards are expanded in the same manner as operating system commands. (Please refer to

your operating system user's guide if you are unfamiliar with wildcards). Enclosing an argument in

double quotation marks (" ") suppresses the wildcard expansion. Within quoted arguments, you can

represent quotation marks literally by preceding the double-quotation-mark character with a

backslash (\). If no matches are found for the wildcard argument, the argument is passed literally.

C# Create PDF from OpenOffice to convert odt, odp files to PDF in

An advanced .NET control to change ODT, ODS, ODP forms to fillable PDF formats in Visual C# .NET. Description: Convert to PDF/TIFF and save it on the disk.

extracting data from pdf forms to excel; extract data out of pdf file

C# Create PDF Library SDK to convert PDF from other file formats

file. Create and save editable PDF with a blank page, bookmarks, links, signatures, etc. Create fillable PDF document with fields.

how to fill out a pdf form with reader; how to fill pdf form in reader

3.3.6 Does PDF/A Manager have any dependencies on third party components/software?

PDF/A Manager is a completely stand alone application and does not include any dependencies on

third-party components or software.

3.3.7 How do I web-optimize PDF/A files for fast web or network access?

PDF/A Manager can linearize output PDF documents for fast web or network access. This can

greatly improve document loading time if you plan to share documents on the web or local network.

To linearize (i.e web-optimize) all output documents add -l or --linearize option in the command-line.

3.3.8 What is the difference between PDF/A-1b and PDF/A-1a?

PDF/A-1b is a subset of PDF/A-1a specification. As a result every PDF/A-1a file is also a valid

PDF/A-1b document. The main difference is that PDF/A-1a additionally requires that PDF specifies

logical structure as well as Unicode mapping for all text in the document.

The primary purpose of logical structure is to offer accessibility features for visually impaired people

(similar to ‘Alt’ tags in HTML).

Compared to PDF/A-1b there is no well defined process to validate or convert PDF/A-1a (besides a

handful of simple checks). Because the semantic information may be missing from input document

and because there is no universally agreed way to reconstruct or to represent this information the

usefulness of PDF/A-1a is open to debate.

By default PDF/A Manager will preserve tags, logical structure, and color information in input PDF

files.

3.3.9 Can I integrate PDF/A Manager with my client/server application?

PDF/A Manager can be easily integrated into third-party client and server-based applications.

Besides command-line utility PDF/A Manager is part of PDFNet SDK and can be accessed from any

programming language (including C#, VB.Net, C/C++, Java, VB6, Perl, Python, Ruby, Delphi, etc).

3.3.10 I didn’t find the answer to my question in the user manual. Are there any other helpful

resources?

You may want to search the PDF/A Manager Knowledge Base forum (which can be accessed via

PDFTron’s website at: www.pdftron.com

) or to simply forward your question to PDFTron’s technical

support team via support@pdftron.com

VB.NET Create PDF Library SDK to convert PDF from other file

Create and save editable PDF with a blank page, bookmarks, links, signatures, etc. Create fillable PDF document with fields in Visual Basic .NET application.

extracting data from pdf forms; pdf data extraction to excel

C# Create PDF from PowerPoint Library to convert pptx, ppt to PDF

Convert multiple pages PowerPoint to fillable and editable PDF documents. Description: Convert to PDF/TIFF and save it on the disk. Parameters:

how to save a pdf form in reader; how to extract data from pdf to excel

3.4 Exit Codes

To provide additional feedback, PDF/A Manager returns exit codes after completing processing. The

exit codes can be used to provide user feedback for logging, etc. This is particularly important for

applications running in an unattended environment.

The following table lists possible exit codes and their description:

Exit Code

Description

All files converted successfully.

Document is secured. Need a valid password to

open the document.

Error opening the input file(s).

An unknown exception encountered.

All codes other then ‘0’ indicate that there was an error during the conversion process.

The following illustrates a sample Windows batch script that processes exit codes:

@echo off rem convert all PDF files in ‘data’ folder

pdfa ./data

if errorlevel 1 goto passwd

if errorlevel 2 goto inputerr

if errorlevel 3 goto othererror

if errorlevel 0 goto exit

:passwd

echo Document is protected. Need a valid password to open the document.

goto exit

:inputerr

echo No input files specified.

goto exit

:othererror

echo An error encountered during processing.

goto exit

:exit

C# Create PDF from Excel Library to convert xlsx, xls to PDF in C#

Create fillable and editable PDF documents from Excel in both .NET WinForms and ASP.NET. Description: Convert to PDF/TIFF and save it on the disk.

html form output to pdf; saving pdf forms in acrobat reader

C# Create PDF from Word Library to convert docx, doc to PDF in C#.

Convert multiple pages Word to fillable and editable PDF documents in both .NET WinForms and ASP.NET. Description: Convert to PDF/TIFF and save it on the

extract data from pdf forms; exporting pdf data to excel

4. PDF/A Manager Reporting

This section covers PDF/A Manager report formats and all the possible error conversion and

validation options.

4.1 PDF/A Manager XML Report Format

By default PDF/A Manager stores details of validation and conversion processing in an XML file. The

report is saved as ‘report.xml’ in the output directory. Similarly, the style sheet for the report is saved

as ‘report.xsl’ in the output directory. Double clicking on ‘report.xml’ will launch a web browser display

HTML report as shown in the following figure:

Figure 4.1

Typical PDF/A Manager

Report

C# PDF Text Box Edit Library: add, delete, update PDF text box in

Able to create a fillable and editable text box Annot_9.pdf"; // open a PDF file PDFDocument the page PDFAnnotHandler.AddAnnotation(page, annot); // save to a

pdf form save in reader; pdf data extraction open source

The report includes the following information:

The date and time when the report was generated

A listing of files that fail validation prior to conversion. The information in this table includes

the input PDF filename, error code, error message, and a list of relevant PDF object

numbers.

A listing of files that pass validation and for which no conversion is necessary.

A listing of files that fail validation after to conversion. Usually this list includes files that can’t

be fully converted to PDF/A without significant information loss.

A final list of files that pass validation after conversion.

The general structure of XML report is as follows:

<?xml version="1.0" encoding="utf-8"?>

<?xml-stylesheet type="text/xsl" href="report.xsl"?>

<Error Code="e_PDFA232" Message="Not a valid ICC color profile"

Refs="3"/>

</Fail>

</Validation>

<Error Code="e_PDFA185" Message="'obj' not followed by EOL marker"

Refs="1, 2, 3, 4, 5, 6, 7, 8, 9, 12"/>

<Error Code="e_PDFA341" Message="The font is not embedded"

Refs="16, 17, 18"/>

<Error Code="e_PDFA353" Message="Embedded TrueType font program..."

Refs="16, 17, 18"/>

<Error Code="e_PDFA723" Message="The XMP Metadata stream is not

valid" Refs="39"/>

<Error Code="e_PDFA2331" Message="Device-specific color space used,

but no GTS_PDFA1 OutputIntent" Refs="1, 4, 14"/>

</Fail>

</Validation>

</PDFAManagerReport>

To disable report generation, simply include ‘--noxml’ in the command-line string. Disabling XML

report generation will direct processing results to the console window.

c:\PDFA\ >pdfa --noxml -c -o OUT my.pdf

Processing...

VLD-[FAIL]: my.pdf

- e_PDFA185: 'obj' not followed by EOL marker

Obj Refs:1, 2, 3, 4, 5, 6, 7, 8, 9, 12

- e_PDFA341: The font is not embedded

Obj Refs:16, 17, 18

- e_PDFA723: The XMP Metadata stream is not valid

Obj Refs:39

- e_PDFA2331: Device-specific color space used, but no GTS_PDFA1 Output Intent

Obj Refs:1, 4, 14

CNV-[PASS]: my_pdfa.pdf

4.2 PDF/A Manager Validation and Conversion Error Codes

PDF/A Manager analyzes the content of existing PDF files and performs a sequence of modifications

in order to produce a PDF/A compliant document. Features that are not suitable for long-term

archiving (such as encryption, obsolete compression schemes, missing fonts, or device-dependent

color) are replaced with their PDF/A compliant equivalents.

4.2.1 PDF/A Level B Validation Errors

The following table is a non-exhaustive list of checks and conversions performed by PDF/A Manager

for Level B Validation:

Error Code

Description

e_PDFA0_1_1

Corrupt document

e_PDFA0_1_2

Corrupt content stream.

e_PDFA0_1_3

Using JPEG2000 compression (PDF 1.4 compatibility).

e_PDFA0_1_4

Contains compressed object streams (PDF 1.4 compatibility).

e_PDFA0_1_5

Contains cross-reference streams (PDF 1.4 compatibility).

e_PDFA1_2_1

Document does not start with % character.

e_PDFA1_2_2

File header line not followed by % and 4 characters > 127.

e_PDFA1_3_1

The trailer dictionary does not contain ID.

e_PDFA1_3_2

Trailer dictionary contains Encrypt.

e_PDFA1_3_3

Data after last EOF marker.

e_ PDFA1_3_4

Linearized file: ID in 1st page and last trailer are different.

e_PDFA1_4_1

Subsection header: starting object number and range not separated by a

single space.

e_PDFA1_4_2

'xref' and cross reference subsection header not separated by a single

EOL marker.

e_PDFA1_6_1

Invalid hexadecimal strings used.

e_PDFA1_7_1

The 'stream' token is not followed by CR and LF or a single LF.

e_PDFA1_7_2

The 'endstream' token is not preceded by EOL.

e_PDFA1_7_3

The value of Length does not match the number of bytes.

e_PDFA1_7_4

A stream object dictionary contains the F, FFilter, or FDecodeParms keys.

e_PDFA1_8_1

Object number and generation number are not separated by a single

white-space.

e_PDFA1_8_2

Generation number and 'obj' are not separated by a single white-space.

e_PDFA1_8_3

Object number not preceded by EOL marker

e_PDFA1_8_4

'endobj' not preceded by EOL marker

e_PDFA1_8_5

'obj' not followed by EOL marker

e_PDFA1_8_6

'endobj' not followed by EOL marker

e_PDFA1_10_1

Using LZW compression.

e_PDFA1_11_1

A file specification dictionary contains the EF key.

e_PDFA1_11_2

Contains the EmbeddedFiles key

e_PDFA1_12_1

Array contains more than 8191 elements

e_PDFA1_12_2

Dictionary contains more than 4095 elements

e_PDFA1_12_3

Name with more than 127 bytes

e_PDFA1_12_4

Contains an integer value outside of the allowed range

e_PDFA1_12_5

Exceeds the maximum number (8,388,607) of indirect objects in a PDF

file.

e_PDFA1_12_6

The number of nested q/Q operators is greater than 28

e_PDFA1_13_1

Optional content (layers) not allowed.

e_PDFA2_2_1

DestOutputProfile-s in OutputIntents array do not match.

e_PDFA2_3_2

Not a valid ICC color profile.

e_PDFA2_3_3

The N entry does not match the number of color components in the

embedded ICC profile.

e_PDFA2_3_3_1

Device-specific color space used, but no GTS_PDFA1 OutputIntent.

e_PDFA2_3_3_2

Device-specific color space, does not match OutputIntent.

e_PDFA2_3_4_1

Device-specific color space used in an alternate color space.

e_PDFA2_4_1

Image with Alternates key.

e_PDFA2_4_2

Image with OPI key.

e_PDFA2_4_3

Image with invalid rendering intent.

e_PDFA2_4_4

Image with Interpolate key set to true

e_PDFA2_5_1

XObject with OPI key.

e_PDFA2_5_2

PostScript XObject.

e_PDFA2_6_1

Contains a reference XObject.

e_PDFA2_7_1

Contains an XObject that is not supported (e.g. PostScript XObject

e_PDFA2_8_1

Contains an invalid Transfer Curve in the extended graphics state.

e_PDFA2_9_1

Use of an invalid rendering intent

e_PDFA2_10_1

Illegal operator.

e_PDFA3_2_1

Embedded font is damaged.

e_PDFA3_3_1

Incompatible CIDSystemInfo entries

e_PDFA3_3_2

Type 2 CIDFont without CIDToGIDMap

e_PDFA3_3_3_1

CMap not embedded

e_PDFA3_3_3_2

Inconsistent WMode in embedded CMap dictionary and stream.

e_PDFA3_4_1

The font is not embedded.

e_PDFA3_5_1

Embedded composite (Type0) font program does not define all font

glyphs.

e_PDFA3_5_2

Embedded Type1 font program does not define all font glyphs.

e_PDFA3_5_3

Embedded TrueType font program does not define all font glyphs.

e_PDFA3_5_4

The font descriptor dictionary does not include a CIDSet stream for

CIDFont subset.

e_PDFA3_5_5

The font descriptor dictionary does not include a CharSet string for Type1

font subset.

e_PDFA3_6_1

Widths in embedded font are inconsistent with /Widths entry in the font

dictionary.

e_PDFA3_7_1

A non-symbolic TrueType font must use WinAnsiEncoding or

MacRomanEncoding.

e_PDFA3_7_2

A symbolic TrueType font must not specify encoding.

e_PDFA3_7_3

A symbolic TrueType font does not have exactly one entry in cmap table.

e_PDFA4_1

Transparency used (ExtGState with soft mask).

e_PDFA4_2

Transparency used (XObject with soft mask).

e_PDFA4_3

Transparency used (Form XObject with transparency group).

e_PDFA4_4

Transparency used (Blend mode is not 'Normal').

e_PDFA4_5

Transparency used ('CA' value is not 1.0).

e_PDFA4_6

Transparency used ('ca' value is not 1.0).

e_PDFA5_2_1

Unknown annotation type.

e_PDFA5_2_2

FileAttachment annotation is not permitted.

e_PDFA5_2_3

Sound annotation is not permitted.

e_PDFA5_2_4

Movie annotation is not permitted.

e_PDFA5_2_5

Redact annotation is not permitted.

e_PDFA5_2_6

3D annotation is not permitted.

e_PDFA5_2_7

Caret annotation is not permitted.

e_PDFA5_2_8

Watermark annotation is not permitted.

e_PDFA5_2_9

Polygon annotation is not permitted.

e_PDFA5_2_10

PolyLine annotation is not permitted.

e_PDFA5_2_11

Screen annotation is not permitted.

e_PDFA5_3_1

An annotation dictionary contains the CA key with a value other than 1.0.

e_PDFA5_3_2_1

An annotation dictionary is missing F key.

e_PDFA5_3_2_2

An annotation's 'Print' flag is not set

e_PDFA5_3_2_3

An annotation's 'Hidden' flag is set.

e_PDFA5_3_2_4

An annotation's 'Invisible' flag is set.

e_PDFA5_3_2_5

An annotation's 'NoView' flag is set.

e_PDFA5_3_3_1

An annotation's C entry present but no OutputIntent present

e_PDFA5_3_3_2

An annotation's C entry present but OutputIntent has non-RGB destination

profile

e_PDFA5_3_3_3

An annotation's IC entry present but no OutputIntent present

e_PDFA5_3_3_4

An annotation's IC entry present and OutputIntent has non-RGB

destination profile

e_PDFA5_3_4_1

An annotation AP dictionary has entries other than the N entry.

Documents you may be interested

adobe pdf library c# : How to save fillable pdf form in reader application SDK utility azure wpf winforms visual studio PDFTron_PDFA_Manager_User_Manual1-part1905