diff options
| author | allen <allen@57bc7290-fb3d-4efd-a9b1-28e84cce6043> | 2001-09-18 13:37:02 +0000 |
|---|---|---|
| committer | allen <allen@57bc7290-fb3d-4efd-a9b1-28e84cce6043> | 2001-09-18 13:37:02 +0000 |
| commit | d7003aadbb261388d6e238fca9fcd163ebd00fb5 (patch) | |
| tree | 9e9e6c1bd8c86385d9319dd7828b1d6d4665b1e5 | |
| parent | cb7f0833edbe1f37e2006b773ddd32f693ec97e9 (diff) | |
Maybe this changes fixes some strange latex2html formatting
git-svn-id: http://svn.cactuscode.org/arrangements/CactusElliptic/EllBase/trunk@60 57bc7290-fb3d-4efd-a9b1-28e84cce6043
| -rw-r--r-- | doc/documentation.tex | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/documentation.tex b/doc/documentation.tex index 6a16d45..e36383a 100644 --- a/doc/documentation.tex +++ b/doc/documentation.tex @@ -89,7 +89,7 @@ will hide all of that. Another advantage is that your code will compile and run, even though certain solvers are not compiled in. In these case, you will have to do some return value checking to offer alternatives. -\subsection{\tt Ell\_LinFlat} +\subsection{{\tt Ell\_LinFlat}} To call this interface from {\bf Fortran}: \begin{verbatim} call Ell_LinFlatSolver(ierr, cctkGH, phi_gfi, M_gfi, N_gfi, @@ -160,7 +160,7 @@ c could be coded here \end{verbatim} -\subsection{\tt Ell\_LinMetric} +\subsection{{\tt Ell\_LinMetric}} To call this interface from {\bf Fortran}: \begin{verbatim} call Ell_LinMetricSolver(ierr, cctkGH, Metric_gfi, @@ -203,7 +203,7 @@ check the documentation of the elliptic solvers or check for registration infomation outputted by a cactus at runtime. \end{itemize} -\subsection{\tt Ell\_LinConfMetric} +\subsection{{\tt Ell\_LinConfMetric}} To call this interface from {\bf Fortran}: \begin{verbatim} call Ell_LinMetricSolver(ierr, cctkGH, MetricPsi_gfi, |