ENH: Fix quoting for compatibility with LaTeX

Replace the literal double-quote character in LaTeX.

It is for the rare cases where you actually want the ASCII " glyph, not typographic quotes.
chktex warns when " character is used without explicit request for the
type of quotes needed.

Author: hjmjohnson

SoftwareGuide/Latex/00-Preamble-Common.tex

@@ -13,6 +13,9 @@
 %\usepackage{siunitx}
 \usepackage[papersize={7.5in,9.25in},margin=1in]{geometry}
 \usepackage[utf8]{inputenc}
+\usepackage{csquotes}
+
+\newcommand{\shelldblquotes}[1]{\textquotedbl{}#1\textquotedbl{}}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %

SoftwareGuide/Latex/Appendices/CodingStyleGuide.tex

@@ -1420,7 +1420,7 @@ \section{Namespaces}%
 
 When declaring or defining members of the \code{itk::} namespace, for example,
 the \code{itk::} namespace prefix should not be added. That is, code within
-\code{namespace itk \{ \ldots \}}" should not use \code{itk::}.
+\code{namespace itk \{ \ldots \}} should not use \code{itk::}.
 
 The \code{::} global namespace should be used when referring to a global
 function, e.g.
@@ -3898,7 +3898,7 @@ \subsection{Regressions in Tests}%
 
 When the magnitude of the error needs to be reported, as in the above examples,
 the error message should be split into different lines, all starting with the
-error output redirection \code{std::cerr << "";}. Care must be taken to
+error output redirection \code{std::cerr << \shelldblquotes{};}. Care must be taken to
 appropriately add white space for a correct formatting of the message.
 
 

SoftwareGuide/Latex/DesignAndFunctionality/DeformableRegistration4OnBrain.tex

@@ -42,7 +42,7 @@
 \end{table}
 
 Here $\|G\|$ is the norm of the gradient at the current estimate of the
-minimum, $x$. ``Function Value" is the current value of the function, f(x).
+minimum, $x$. \enquote{Function Value} is the current value of the function, f(x).
 
 The resulting deformation field that maps the moving to the fixed image is
 shown in~\ref{fig:DeformationFieldOutput}. A difference image of two slices

SoftwareGuide/Latex/DesignAndFunctionality/Registration.tex

@@ -83,7 +83,7 @@ \section{Registration Framework}
 framework. First, we begin with some simple registration examples.
 
 
-\section{"Hello World" Registration}%
+\section{\shelldblquotes{Hello World} Registration}%
 \label{sec:IntroductionImageRegistration}
 \input{ImageRegistration1.tex}
 
@@ -618,7 +618,7 @@ \subsection{General heuristics for parameter fine-tunning}
 of the bins. Then use a plotting program such as gnuplot,
 or Matlab, or even Excel and look at the distribution.
 The number of samples to take must be enough
-for producing the same "appearance" of the joint histogram.
+for producing the same \enquote{appearance} of the joint histogram.
 As an arbitrary rule of thumb you may want to start using
 a high number of samples (80\% - 100\%). And do not
 change it until you have mastered the other parameters
@@ -651,7 +651,7 @@ \subsection{General heuristics for parameter fine-tunning}
 1.0   /  (  10.0 * pixelspacing[1]  *  imagesize[1]  )
 
 This is telling the optimizer that you consider that rotating
-the image by 57 degrees is as "significant" as translating
+the image by 57 degrees is as \enquote{significant} as translating
 the image by half its physical extent.
 
 Note that esoteric value has included the arbitrary number

SoftwareGuide/Latex/DevelopmentGuidelines/CreateAModule.tex

@@ -1033,8 +1033,8 @@ \subsubsection{C++ Runtime Tracing}%
 are generated. Python wrapping must also be enabled.
 This is accomplished by setting the CMake variables
 
-\code{CMAKE\_BUILD\_TYPE:STRING="RelWithDebInfo"} and \code{ITK\_WRAP\_PYTHON:BOOL="On"}.
-Note that the "RelWithDebInfo" build type is strongly encouraged over a "Debug"
+\code{CMAKE\_BUILD\_TYPE:STRING=\shelldblquotes{RelWithDebInfo}} and \code{ITK\_WRAP\_PYTHON:BOOL=\shelldblquotes{ON}}.
+Note that the \shelldblquotes{RelWithDebInfo} build type is strongly encouraged over a \shelldblquotes{Debug}
 build as the former will build against a standard Python distribution.
 See Section~\ref{sec:UsingCMakeForConfiguringAndBuildingITK} for a detailed
 explanation of how to build ITK locally with CMake.
@@ -1062,13 +1062,13 @@ \subsubsection{C++ Runtime Tracing}%
 \begin{itemize}
 
 \item On a Windows operating system, Microsoft Visual Studio 2019 or a similar platform
-can be used for attaching to a running process for debugging. Select "Attach To Process"
-from the Debug menu, choose "Native" code, and then search for the process PID. If
+can be used for attaching to a running process for debugging. Select \enquote{Attach To Process}
+from the Debug menu, choose \enquote{Native} code, and then search for the process PID. If
 debug symbols were generated correctly then ITK modules will appear under the list of
 loaded modules.
 
 In Visual Studio, debugging can be enabled right from the start if the Python script
-is loaded into Visual Studio as part of a "Python Project".
+is loaded into Visual Studio as part of a \enquote{Python Project}.
 Mixed mode debugging needs to be enabled, as per Visual Studio
 documentation\footnote{
 \url{https://docs.microsoft.com/en-us/visualstudio/python/debugging-mixed-mode-c-cpp-python-in-visual-studio}}.
@@ -1139,10 +1139,10 @@ \subsubsection{C++ Runtime Tracing}%
 \begin{itemize}
 
 \item The Python process must be authorized for debugging. MacOS relies on the
-process of "hardened" runtimes to mitigate security concerns, which reduces
+process of \enquote{hardened} runtimes to mitigate security concerns, which reduces
 the ability of debuggers such as \code{lldb} and other processes to attach
 to and intercept the functions of other programs. Python distributions
-are intentionally "hardened" in this way, but additional settings can be
+are intentionally \enquote{hardened} in this way, but additional settings can be
 enabled to allow just-in-time debugging.
 
 \item It may be necessary to enter developer mode to allow Python debugging.