pdftotext only called if present in system, minor edit

David and Raul had both reported that because 'pdftotext' wasn't available
on their system, the project failed (even though the PDF was built!). So
with this commit, we first check if the system has 'pdftotext' and call it
only if its is available.

Some minor edits were made, building upon Boud's previous commit.

1 files changed, 2 insertions, 2 deletions

diff --git a/paper.tex b/paper.tex
index 56e4246..f9f09f8 100644
--- a/paper.tex
+++ b/paper.tex
@@ -431,7 +431,7 @@ We have seen that providing a complete \emph{and} customizable template with a c
 
 Secondly, to satisfy the completeness criteria, all the necessary software of the project must be built on various POSIX-compatible systems (we actively test Maneage on several different GNU/Linux distributions and on macOS).
 This requires maintenance by our core team and consumes time and energy.
-However, the PM and analysis share the same job manager.
+However, the PM and analysis share the same job manager (Make), design principles and conventions.
 Our experience so far has shown that users' experience in the analysis empowers some of them to add or fix their required software on their own systems.
 Later, they share them as commits on the core branch, thus propagating it to all derived projects.
 This has already occurred multiple times.
@@ -447,7 +447,7 @@ However, the proof of concept already shows many advantages in adopting the crit
 For example, publication of projects with these criteria on a wide scale will allow automatic workflow generation, optimized for desired characteristics of the results (for example, via machine learning).
 Because of the completeness criteria, algorithms and data selection can be similarly optimized.
 Furthermore, through elements like the macros, natural language processing can also be included, automatically analyzing the connection between an analysis with the resulting narrative \emph{and} the history of that analysis/narrative.
-Parsers can be written over projects for meta-research and data provenance studies, for example, to generate ``research objects''.
+Parsers can be written over projects for meta-research and provenance studies, for example, to generate ``research objects''.
 As another example, when a bug is found in one software package, all affected projects can be found and the scale of the effect can be measured.
 Combined with SoftwareHeritage, precise high-level science parts of Maneage projects can be accurately cited (e.g., failed/abandoned tests at any historical point).
 Many components of ``machine-actionable'' data management plans can be automatically filled out by Maneage, which is useful for project PIs and grant funders.