Additional command line options – Response files

Quick processing

-q --quick 

Processing is stopped after the first detection of an error in the corrected PDF (only applied if no report is generated).

Define the overwrite mode

--overwrite 

New files override existing files with the same name (applies to report files and to created PDF files).

Create output files only for successful conversion

--onlypdfa 

Create an output file only if the file could be converted to PDF/A.

Set the result path

  • Note: If neither an output path nor an output folder is defined, any result will be created next to the input file (default: input file name with suffix _PDFA or _NOPDFA, will be indexed if necessary).
  • Note: The use of --outputfile together with --outputfolder is not sup-­ported within one CLI call.

Path to output file

-o --outputfile=<path> 

Defines the absolute path of the destination file. The parent folder must exist.

  • Note: Consult section "Results"to see if a new file was created.

Parameters

path

absolute path to output file

Path to output folder

-f --outputfolder=<path> 

Defines an absolute path to a folder where the files resulting of an execu-­tion are stored.

Parameters

path

absolute path to output folder Out-­put file

Use an additional profile

--profile 

Run additional checks and fixups by defining a full path to a kfp or kfpx file (exported from pdfToolbox  /  pdfaPilot Desktop or Preflight in Adobe Acrobat). The input file is converted if no warnings or errors occur.

Using response files

To keep the command line call structured and straightforward, pdfaPilot CLI supports the usage of response files. These offer the possibility to define each command line switch line by line and also add some comments.

Example

Response file analyze.rsp:

################### # PDF/A analysis # --analyze # ################### # EOF 

Command line call:

pdfaPilot @analyze.rsp <PDF file> 

0 Comments

Send Your Comment

E-Mail me when someone replies to this comment