DOC: Fix PDF file properties in Book 2

[albert-github]

Fix the PDF file properties: set the SupressPDFMark variable to true in the eps files.

The properties of the eps figures generated by gnuplot at the time the PDF is generated were ovewriting the LaTeX hyperref settings of the book, effectively modifying the title, author, subject, and keywords of the PDF file.

Relevant thread:
https://groups.google.com/g/comp.graphics.apps.gnuplot/c/WTjwj-lbC90

[jhlegarreta]

Why do these changes need 2 commits, both having the very same subject, one modifying the changes of the former?

Also, in the absence of a more elaborated commit message body, I do not see how these changes address the PDF file properties of the book. The PDF properties of a multi-page document are unique, and (I'd dare to say) defined at a single place.

[albert-github]

@jhlegarreta
The first commit unfortunately had an error (the / was missing).

For a more elaborate explanation see the comments with the issue #78 and for the result see the GHA artifacts at https://github.com/InsightSoftwareConsortium/ITKSoftwareGuide/actions/runs/14056672763

[jhlegarreta]

@jhlegarreta
The first commit unfortunately had an error (the / was missing).

Squash commits, please.

For a more elaborate explanation see the comments with the issue #78 and for the result see the GHA artifacts at https://github.com/InsightSoftwareConsortium/ITKSoftwareGuide/actions/runs/14056672763

Please, provide a self-contained explanation in the commit message body.

[albert-github]

I don't know how to squash or to amend the commit message.
@dzenanz can you have a look at it?

[dzenanz]

I squashed both PRs.

[jhlegarreta]

Provided an appropriate commit message body. Removed the commented lines: the commit message body says it all.

[jhlegarreta]

I don't know how to squash or to amend the commit message.

Assuming you are at the appropriate branch, that no other commits have been added to it in the meantime and there is 2 commits that you want to squash:

$ git rebase -i HEAD~2

Something like this will then appear in your editor:

pick hash1 Commit1_message_subject
pick hash2 Commit2_message_subject

Change to

pick hash1 Commit1_message_subject
s hash2 Commit2_message_subject

Your configured editor will show something like:

# This is a combination of 2 commits.
# This is the 1st commit message:

(...)

# This is the commit message #2:

(...)

Edit the message (merge, reword, etc.), save, exit, and you are done.

If you have not committed yet, simply amend your previous commit:

$ git commit --amend --no-edit

If you need to edit the commit message, drop the ---no-edit part.