Link to all the other languages.

[bacula/docs] / docs / developers / generaldevel.tex

diff --git a/docs/developers/generaldevel.tex b/docs/developers/generaldevel.tex
index 9773ee7fe87ac93abe910eae4f667bcbd6a88aa3..6beb52d9e63f0c225fbef8299b966cf9d0834541 100644 (file)
--- a/docs/developers/generaldevel.tex
+++ b/docs/developers/generaldevel.tex
@@ -311,6 +311,7 @@ Getting code implemented in Bacula works roughly as follows:
    direction).  When ever possible, we would like to avoid this, and 
    ensure a continuation of the code and a sharing of the development,
    debugging, documentation, and maintenance responsibilities.
+\end{itemize}
 
 
 \subsection*{SVN Usage}
@@ -669,7 +670,7 @@ long as you are careful only to change files that you want changed,
 you have little to worry about.
 
 \subsection*{Subversion Resources}
-\link{Subversion (svn) Resources}
+\index{Subversion (svn) Resources}
 \addcontentsline{toc}{subsection}{Subversion Resources}
 
 \begin{verbatim}
@@ -707,7 +708,7 @@ Subversion Book
 \elink{http://svnbook.red-bean.com}{http://svnbook.red-bean.com}
 
 Subversion Clients
-\elink{http://subversion.tigris.org/project_packages.html}{http://subversion.tigris.org/project_packages.html}
+\elink{http://subversion.tigris.org/project\_packages.html}{http://subversion.tigris.org/project\_packages.html}
 
  (For Windows users the TortoiseSVN package is awesome)
 
@@ -999,11 +1000,11 @@ so be conservative in your use of C++ features.
    correct types whenever possible.
 
 \item Using undefined storage specifications such as (short, int, long,
-   long long, size_t ...).  The problem with all these is that the number of bytes
+   long long, size\_t ...).  The problem with all these is that the number of bytes
    they allocate depends on the compiler and the system.  Instead use
-   Bacula's types (int8_t, uint8_t, int32_t, uint32_t, int64_t, and 
-   uint64_t).  This guarantees that the variables are given exactly the
-   size you want. Please try at all possible to avoid using size_t ssize_t
+   Bacula's types (int8\_t, uint8\_t, int32\_t, uint32\_t, int64\_t, and 
+   uint64\_t).  This guarantees that the variables are given exactly the
+   size you want. Please try at all possible to avoid using size\_t ssize\_t
    and the such. They are very system dependent.  However, some system
    routines may need them, so their use is often unavoidable.
 
@@ -1011,7 +1012,7 @@ so be conservative in your use of C++ features.
    to release it. 
 
 \item Heap allocation (malloc) unless needed -- it is expensive. Use
-      POOL_MEM instead.
+      POOL\_MEM instead.
 
 \item Templates -- they can create portability problems. 
 
@@ -1033,7 +1034,7 @@ so be conservative in your use of C++ features.
 
 \item A single point of exit from all subroutines. A goto is 
      perfectly OK to use to get out early, but only to a label
-     named bail_out, and possibly an ok_out.  See current code
+     named bail\_out, and possibly an ok\_out.  See current code
      examples.
 
 \item Malloc and free within a single subroutine.