Différences

Ci-dessous, les différences entre deux révisions de la page.

--- pdftk_usage_et_exemple [2025/01/29 12:03] – [shuffle [<page ranges>]] frater
+++ pdftk_usage_et_exemple [2025/06/30 13:51] (Version actuelle) – [[drop_xfa]] frater
@@ Ligne 52: / Ligne 52: @@
 ==== SYNOPSIS ====
-<code>
+<cli bash>
-pdftk <input PDF files | - | PROMPT>
+frater@supremae:$ pdftk <input PDF files | - | PROMPT>
             [ input_pw <input PDF owner passwords | PROMPT> ]
             [ <operation> <operation arguments> ]
@@ Ligne 66: / Ligne 66: @@
             [ replacement_font <font name> ]
             [ verbose ] [ dont_ask | do_ask ]
-</code>
+</cli>
 <operation> may be empty, or:
@@ Ligne 221: / Ligne 221: @@
 For example, if you want pages named page_01.pdf, page_02.pdf, etc., pass output page_%02d.pdf to pdftk. If the pattern is omitted, then a default pattern g_%04d.pdf is appended and produces pages named pg_0001.pdf, pg_0002.pdf, etc.
 Encryption can be applied to the output by appending output options such as owner_pw, e.g.:
+<cli bash>
+frater@supremae:$ pdftk in.pdf burst owner_pw foopass
+</cli>
+=== rotate [<page ranges>] ===
+Takes a single input PDF and rotates just the specified pages. All other pages remain unchanged.  The page order remains unchanged.
+Specify the pages to rotate using the same notation as you would with cat, except you omit the pages that you aren't rotating:
 <code>
-pdftk in.pdf burst owner_pw foopass
+[<begin page number>[-<end page number>[<qualifier>]]][<page rotation>]
 </code>
-=== rotate [<page ranges>] ===
-                 Takes a single input PDF and rotates just the specified
-                 pages.  All other pages remain unchanged.  The page order
-                 remains unchanged.  Specify the pages to rotate using the
-                 same notation as you would with cat, except you omit the
-                 pages that you aren't rotating:
-                 [<begin page number>[-<end page number>[<qualifier>]]][<page
+The qualifier can be even or odd, and the page rotation can be //north//, //south//, //east//, //west//, //left//, //right//, or //down//.
-                 rotation>]
-                 The qualifier can be even or odd, and the page rotation can
+Each option sets the page rotation as follows (in degrees):
-                 be north, south, east, west, left, right, or down.
-                 Each option sets the page rotation as follows (in degrees):
+  * north: 0,
-                 north: 0, east: 90, south: 180, west: 270, left: -90, right:
+  * east: 90,
-                 +90, down: +180. left, right, and down make relative adjust-
+  * south: 180,
-                 ments to a page's rotation.
+  * west: 270,
+  * left: -90,
+  * right: +90,
+  * down: +180.
-                 The given order of the pages doesn't change the page order in
+//left//, //right//, and //down// make relative adjustments to a page's rotation.
-                 the output.
+The given order of the pages doesn't change the page order in the output.
 === generate_fdf ===
-                 Reads a single input PDF file and generates an FDF file suit-
-                 able for fill_form out of it to the given output filename or
+Reads a single input PDF file and generates an FDF file suitable for fill_form out of it to the given output filename or (if no output is given) to stdout.  Does not create a new PDF.
-                 (if no output is given) to stdout.  Does not create a new
-                 PDF.
 === fill_form <FDF data filename | XFDF data filename | - | PROMPT> ===
-                 Fills the single input PDF's form fields with the data from
-                 an FDF file, XFDF file or stdin. Enter the data filename
+Fills the single input PDF's form fields with the data from an FDF file, XFDF file or stdin. Enter the data filename after fill_form, or use - to pass the data via stdin, like so:
-                 after fill_form, or use - to pass the data via stdin, like
-                 so:
-                 pdftk form.pdf fill_form data.fdf output form.filled.pdf
+<cli>
+frater@host:~$ pdftk form.pdf fill_form data.fdf output form.filled.pdf
+</cli>
-                 If the input FDF file includes Rich Text formatted data in
-                 addition to plain text, then the Rich Text data is packed
-                 into the form fields as well as the plain text.  Pdftk also
-                 sets a flag that cues Reader/Acrobat to generate new field
-                 appearances based on the Rich Text data.  So when the user
-                 opens the PDF, the viewer will create the Rich Text appear-
-                 ance on the spot.  If the user's PDF viewer does not support
-                 Rich Text, then the user will see the plain text data
-                 instead.  If you flatten this form before Acrobat has a
-                 chance to create (and save) new field appearances, then the
-                 plain text field data is what you'll see.
-                 Also see the flatten, need_appearances, and replacement_font
+If the input FDF file includes Rich Text formatted data in addition to plain text, then the Rich Text data is packed into the form fields as well as the plain text.
-                 options.
+Pdftk also sets a flag that cues Reader/Acrobat to generate new field appearances based on the Rich Text data.
+So when the user opens the PDF, the viewer will create the Rich Text appearance on the spot.
+If the user's PDF viewer does not support Rich Text, then the user will see the plain text data instead.
+If you flatten this form before Acrobat has a chance to create (and save) new field appearances, then the plain text field data is what you'll see.
+Also see the flatten, need_appearances, and replacement_font options.
 === background <background PDF filename | - | PROMPT> ===
-                 Applies a PDF watermark to the background of a single input
-                 PDF.  Pass the background PDF's filename after background
-                 like so:
-                 pdftk in.pdf background back.pdf output out.pdf
+Applies a PDF watermark to the background of a single input PDF.
+Pass the background PDF's filename after background like so:
-                 Pdftk uses only the first page from the background PDF and
+<cli bash>
-                 applies it to every page of the input PDF.  This page is
+frater@supremae:$ pdftk in.pdf background back.pdf output out.pdf
-                 scaled and rotated as needed to fit the input page.  You can
+</cli>
-                 use - to pass a background PDF into pdftk via stdin.
-                 If the input PDF does not have a transparent background (such
+Pdftk uses only the first page from the background PDF and applies it to every page of the input PDF.
-                 as a PDF created from page scans) then the resulting back-
+This page is scaled and rotated as needed to fit the input page.  You can use - to pass a background PDF into pdftk via stdin.
-                 ground won't be visible - use the stamp operation instead.
+If the input PDF does not have a transparent background (such as a PDF created from page scans) then the resulting background won't be visible - use the stamp operation instead.
 === multibackground <background PDF filename | - | PROMPT> ===
-                 Same as the background operation, but applies each page of
-                 the background PDF to the corresponding page of the input
+Same as the background operation, but applies each page of the background PDF to the corresponding page of the input PDF.
-                 PDF.  If the input PDF has more pages than the stamp PDF,
+If the input PDF has more pages than the stamp PDF, then the final stamp page is repeated across these remaining pages in the input PDF.
-                 then the final stamp page is repeated across these remaining
-                 pages in the input PDF.
 === stamp <stamp PDF filename | - | PROMPT> ===
-                 This behaves just like the background operation except it
-                 overlays the stamp PDF page on top of the input PDF docu-
-                 ment's pages.  This works best if the stamp PDF page has a
-                 transparent background.
+This behaves just like the background operation except it overlays the stamp PDF page on top of the input PDF document's pages.
+This works best if the stamp PDF page has a transparent background.
 === multistamp <stamp PDF filename | - | PROMPT> ===
-                 Same as the stamp operation, but applies each page of the
-                 background PDF to the corresponding page of the input PDF.
+Same as the stamp operation, but applies each page of the background PDF to the corresponding page of the input PDF.
-                 If the input PDF has more pages than the stamp PDF, then the
+If the input PDF has more pages than the stamp PDF, then the final stamp page is repeated across these remaining pages in the input PDF.
-                 final stamp page is repeated across these remaining pages in
-                 the input PDF.
 === dump_data ===
-                 Reads a single input PDF file and reports its metadata, book-
-                 marks (a/k/a outlines), page metrics (media, rotation and
+Reads a single input PDF file and reports its metadata, bookmarks (a/k/a outlines), page metrics (media, rotation and labels), data embedded by STAMPtk (see STAMPtk's embed option) and other data to the given output filename or (if no output is given) to stdout.  Non-ASCII characters are encoded as XML numerical entities.  Does not create a new PDF.
-                 labels), data embedded by STAMPtk (see STAMPtk's embed
-                 option) and other data to the given output filename or (if no
-                 output is given) to stdout.  Non-ASCII characters are encoded
-                 as XML numerical entities.  Does not create a new PDF.
 === dump_data_utf8 ===
-                 Same as dump_data except that the output is encoded as UTF-8.
+Same as dump_data except that the output is encoded as UTF-8.
 === dump_data_fields ===
-                 Reads a single input PDF file and reports form field statis-
-                 tics to the given output filename or (if no output is given)
+Reads a single input PDF file and reports form field statistics to the given output filename or (if no output is given) to stdout. Non-ASCII characters are encoded as XML numerical entities. Does not create a new PDF.
-                 to stdout. Non-ASCII characters are encoded as XML numerical
-                 entities. Does not create a new PDF.
 === dump_data_fields_utf8 ===
-                 Same as dump_data_fields except that the output is encoded as
-                 UTF-8.
+Same as dump_data_fields except that the output is encoded as UTF-8.
 === dump_data_annots ===
-                 This operation currently reports only link annotations.
-                 Reads a single input PDF file and reports annotation informa-
+This operation currently reports only link annotations. Reads a single input PDF file and reports annotation information to the given output filename or (if no output is given) to stdout. Non-ASCII characters are encoded as XML numerical entities. Does not create a new PDF.
-                 tion to the given output filename or (if no output is given)
-                 to stdout. Non-ASCII characters are encoded as XML numerical
-                 entities. Does not create a new PDF.
 === update_info <info data filename | - | PROMPT> ===
-                 Changes the bookmarks, page labels, page sizes, page rota-
-                 tions, and metadata in a single PDF's Info dictionary to
-                 match the input data file. The input data file uses the same
-                 syntax as the output from dump_data. Non-ASCII characters
-                 should be encoded as XML numerical entities.
-                 This operation does not change the metadata stored in the
+Changes the bookmarks, page labels, page sizes, page rotations, and metadata in a single PDF's Info dictionary to match the input data file. The input data file uses the same syntax as the output from dump_data. Non-ASCII characters should be encoded as XML numerical entities.
-                 PDF's XMP stream, if it has one. (For this reason you should
-                 include a ModDate entry in your updated info with a current
-                 date/timestamp, format: D:YYYYMMDDHHmmSS, e.g. D:201307241346
-                 - omitted data after YYYY revert to default values.)
-                 For example:
+This operation does not change the metadata stored in the PDF's XMP stream, if it has one. (For this reason you should include a ModDate entry in your updated info with a current date/timestamp, format: D:YYYYMMDDHHmmSS, e.g. D:201307241346- omitted data after YYYY revert to default values.)
-                 pdftk in.pdf update_info in.info output out.pdf
+For example:
+<cli bash>
+frater@supremae:$ pdftk in.pdf update_info in.info output out.pdf
+</cli>
 === update_info_utf8 <info data filename | - | PROMPT> ===
-                 Same as update_info except that the input is encoded as
-                 UTF-8.
+Same as update_info except that the input is encoded as UTF-8.
 === attach_files <attachment filenames | PROMPT> [to_page <page number | PROMPT> | relation <relationship>] ===
-                 Packs arbitrary files into a PDF using PDF's file attachment
-                 features. More than one attachment may be listed after
-                 attach_files. Attachments are added at the document level
-                 unless the optional to_page option is given, in which case
-                 the files are attached to the given page number (the first
-                 page is 1, the final page is end). Attachments at the docu-
-                 ment level may be tagged with a relationship among Source,
-                 Data, Alternative, Supplement, and Unspecified (default).
-                 For example:
+Packs arbitrary files into a PDF using PDF's file attachment features. More than one attachment may be listed after attach_files. Attachments are added at the document level unless the optional to_page option is given, in which case the files are attached to the given page number (the first page is 1, the final page is end). Attachments at the document level may be tagged with a relationship among Source, Data, Alternative, Supplement, and Unspecified (default).
-                 pdftk in.pdf attach_files table1.html table2.html to_page 6
+For example:
-                 output out.pdf
-                 pdftk in.pdf attach_files in.tex relation Source output
+<cli bash>
-                 out.pdf
+frater@supremae:$ pdftk in.pdf attach_files table1.html table2.html to_page 6 output out.pdf
+</cli>
+<cli bash>
+frater@supremae:$ pdftk in.pdf attach_files in.tex relation Source output out.pdf
+</cli>
 === unpack_files ===
-                 Copies all of the attachments from the input PDF into the
+Copies all of the attachments from the input PDF into the current folder or to an output directory given after output.
-                 current folder or to an output directory given after output.
-                 For example:
-                 pdftk report.pdf unpack_files output ~/atts/
+For example:
-                 or, interactively:
+<cli bash>
+frater@supremae:$ pdftk report.pdf unpack_files output ~/atts/
+</cli>
-                 pdftk report.pdf unpack_files output PROMPT
+or, interactively:
+<cli bash>
+frater@supremae:$ pdftk report.pdf unpack_files output PROMPT
+</cli>
 === [output <output filename | - | PROMPT>] ===
-              The output PDF filename may not be set to the name of an input
-              filename. Use - to output to stdout.  When using the dump_data
+The output PDF filename may not be set to the name of an input filename. Use - to output to stdout.
-              operation, use output to set the name of the output data file.
+When using the dump_data operation, use output to set the name of the output data file. When using the unpack_files operation, use output to set the name of an output directory.  When using the burst operation, you can use output to control the resulting PDF page filenames (described above).
-              When using the unpack_files operation, use output to set the
-              name of an output directory.  When using the burst operation,
-              you can use output to control the resulting PDF page filenames
-              (described above).
 === [encrypt_40bit | encrypt_128bit | encrypt_aes128] ===
-              If an output PDF user or owner password is given, the output PDF
-              encryption algorithm defaults to AES-128. The weaker RC4 40-bit
+If an output PDF user or owner password is given, the output PDF encryption algorithm defaults to AES-128. The weaker RC4 40-bit and RC4 128-bit algorithms can be chosen by specifying encrypt_40bit or encrypt_128bit (discouraged).
-              and RC4 128-bit algorithms can be chosen by specifying
-              encrypt_40bit or encrypt_128bit (discouraged).
 === [allow <permissions>] ===
-              Permissions are applied to the output PDF only if an encryption
-              strength is specified or an owner or user password is given.  If
-              permissions are not specified, they default to 'none,' which
-              means all of the following features are disabled.
-              The permissions section may include one or more of the following
+Permissions are applied to the output PDF only if an encryption strength is specified or an owner or user password is given.
-              features:
+If permissions are not specified, they default to 'none,' which means all of the following features are disabled.
-              Printing
+The permissions section may include one or more of the following features:
-                     Top Quality Printing
+{{tablelayout?rowsHeaderSource=Auto}}
+^ Printing           | Top Quality Printing                                                    |
-              DegradedPrinting
+^ DegradedPrinting   | Lower Quality Printing                                                  |
-                     Lower Quality Printing
+^ ModifyContents     | Also allows Assembly                                                    |
+^ Assembly           |                                                                         |
-              ModifyContents
+^ CopyContents       | Also allows ScreenReaders                                               |
-                     Also allows Assembly
+^ ScreenReaders      |                                                                         |
+^ ModifyAnnotations  | Also allows FillIn                                                      |
-              Assembly
+^ FillIn             |                                                                         |
+^ AllFeatures        | Allows the user to perform all of the above, and top quality printing.  |
-              CopyContents
-                     Also allows ScreenReaders
-              ScreenReaders
-              ModifyAnnotations
-                     Also allows FillIn
-              FillIn
-              AllFeatures
-                     Allows the user to perform all of the above, and top
-                     quality printing.
 === [owner_pw <owner password | PROMPT>] ===
 === [user_pw <user password | PROMPT>] ===
-              If an encryption strength is given but no passwords are sup-
-              plied, then the owner and user passwords remain empty, which
+If an encryption strength is given but no passwords are supplied, then the owner and user passwords remain empty, which means that the resulting PDF may be opened and its security parameters altered by anybody.
-              means that the resulting PDF may be opened and its security
-              parameters altered by anybody.
 === [compress | uncompress] ===
-              These are only useful when you want to edit PDF code in a text
-              editor like vim or emacs.  Remove PDF page stream compression by
+These are only useful when you want to edit PDF code in a text editor like vim or emacs.
-              applying the uncompress filter. Use the compress filter to
+Remove PDF page stream compression by applying the uncompress filter. Use the compress filter to restore compression.
-              restore compression.
 === [flatten] ===
-              Use this option to merge an input PDF's interactive form fields
-              (and their data) with the PDF's pages. Only one input PDF may be
+Use this option to merge an input PDF's interactive form fields (and their data) with the PDF's pages. Only one input PDF may be given. Sometimes used with the fill_form operation.
-              given. Sometimes used with the fill_form operation.
 === [need_appearances] ===
-              Sets a flag that cues Reader/Acrobat to generate new field
-              appearances based on the form field values.  Use this when fill-
+Sets a flag that cues Reader/Acrobat to generate new field appearances based on the form field values.  Use this when filling a form with non-ASCII text to ensure the best presentation in Adobe Reader or Acrobat.  It won't work when combined with the flatten option.
-              ing a form with non-ASCII text to ensure the best presentation
-              in Adobe Reader or Acrobat.  It won't work when combined with
-              the flatten option.
 === [replacement_font <font name>] ===
-              Use the specified font to display text in form fields. This
-              option is useful when filling a form with non-ASCII text that is
+Use the specified font to display text in form fields. This option is useful when filling a form with non-ASCII text that is not supported by the fonts included in the input PDF. font name may be either the file name or the family name of a font, but using a file name is more reliable. Currently only TrueType fonts with Unicode text are supported.
-              not supported by the fonts included in the input PDF. font name
-              may be either the file name or the family name of a font, but
-              using a file name is more reliable. Currently only TrueType
-              fonts with Unicode text are supported.
 === [keep_first_id | keep_final_id] ===
-              When combining pages from multiple PDFs, use one of these
-              options to copy the document ID from either the first or final
+When combining pages from multiple PDFs, use one of these options to copy the document ID from either the first or final input document into the new output PDF. Otherwise pdftk creates a new document ID for the output PDF. When no operation is given, pdftk always uses the ID from the (single) input PDF.
-              input document into the new output PDF. Otherwise pdftk creates
-              a new document ID for the output PDF. When no operation is
-              given, pdftk always uses the ID from the (single) input PDF.
 === [drop_xfa] ===
-              If your input PDF is a form created using Acrobat 7 or Adobe
-              Designer, then it probably has XFA data.  Filling such a form
-              using pdftk yields a PDF with data that fails to display in
-              Acrobat 7 (and 6?).  The workaround solution is to remove the
-              form's XFA data, either before you fill the form using pdftk or
-              at the time you fill the form. Using this option causes pdftk to
-              omit the XFA data from the output PDF form.
-              This option is only useful when running pdftk on a single input
+If your input PDF is a form created using Acrobat 7 or Adobe Designer, then it probably has XFA data.
-              PDF.  When assembling a PDF from multiple inputs using pdftk,
+Filling such a form using pdftk yields a PDF with data that fails to display in Acrobat 7 (and 6?).
-              any XFA data in the input is automatically omitted.
+The workaround solution is to remove the form's XFA data, either before you fill the form using pdftk or at the time you fill the form. Using this option causes pdftk to omit the XFA data from the output PDF form.
+This option is only useful when running pdftk on a single input PDF.
+When assembling a PDF from multiple inputs using pdftk, any XFA data in the input is automatically omitted.
 === [drop_xmp] ===
-              Many PDFs store document metadata using both an Info dictionary
-              (old school) and an XMP stream (new school).  Pdftk's
-              update_info operation can update the Info dictionary, but not
-              the XMP stream.  The proper remedy for this is to include a
-              ModDate entry in your updated info with a current date/time-
-              stamp. The date/timestamp format is: D:YYYYMMDDHHmmSS, e.g.
-              D:201307241346 - omitted data after YYYY revert to default val-
-              ues. This newer ModDate should cue PDF viewers that the Info
-              metadata is more current than the XMP data.
-              Alternatively, you might prefer to remove the XMP stream from
+Many PDFs store document metadata using both an Info dictionary (old school) and an XMP stream (new school).
-              the PDF altogether - that's what this option does.  Note that
+Pdftk's update_info operation can update the Info dictionary, but not the XMP stream.
-              objects inside the PDF might have their own, separate XMP meta-
+The proper remedy for this is to include a ModDate entry in your updated info with a current date/timestamp.
-              data streams, and that drop_xmp does not remove those.  It only
+The date/timestamp format is: D:YYYYMMDDHHmmSS, e.g. D:201307241346 - omitted data after YYYY revert to default values. This newer ModDate should cue PDF viewers that the Info metadata is more current than the XMP data.
-              removes the PDF's document-level XMP stream.
+Alternatively, you might prefer to remove the XMP stream from the PDF altogether - that's what this option does.
+Note that objects inside the PDF might have their own, separate XMP metadata streams, and that drop_xmp does not remove those.  It only removes the PDF's document-level XMP stream.
 === [verbose] ===
-              By default, pdftk runs quietly. Append verbose to the end and it
-              will speak up.
+By default, pdftk runs quietly. Append verbose to the end and it will speak up.
 === [dont_ask | do_ask] ===
-              Depending on the compile-time settings (see ASK_ABOUT_WARNINGS),
-              pdftk might prompt you for further input when it encounters a
-              problem, such as a bad password. Override this default behavior
-              by adding dont_ask (so pdftk won't ask you what to do) or do_ask
-              (so pdftk will ask you what to do).
-              When running in dont_ask mode, pdftk will over-write files with
+Depending on the compile-time settings (see ASK_ABOUT_WARNINGS), pdftk might prompt you for further input when it encounters a problem, such as a bad password. Override this default behavior by adding dont_ask (so pdftk won't ask you what to do) or do_ask (so pdftk will ask you what to do).
-              its output without notice.
+When running in dont_ask mode, pdftk will over-write files with its output without notice.
 ==== EXAMPLES ====

Nox-Rhea WiKi

Outils pour utilisateurs

Outils du site

Différences

Outils de la page