Fixed '_' chars that were not quoted with a '\'

Fixed layout problems for functions that had overloaded \func{} defs for the function.  Problem was that there needs to be a blank line between them, or they all get concatenated
Changed a bunch of "char*" to "char *", as the (just slightly) larger number of occurances use "char *" rather than "char*" throughout the .tex files


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@13574 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/latex/wx/function.tex

@@ -2954,8 +2954,9 @@ wxWindows errors. See also \helpref{wxError}{wxerror}.
 
 \membersection{::wxLogError}\label{wxlogerror}
 
+\func{void}{wxLogError}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
+
 \func{void}{wxLogError}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogError}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
 
 The functions to use for error messages, i.e. the messages that must be shown
 to the user. The default processing is to pop up a message box to inform the
@@ -2963,8 +2964,9 @@ user about it.
 
 \membersection{::wxLogFatalError}\label{wxlogfatalerror}
 
+\func{void}{wxLogFatalError}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
+
 \func{void}{wxLogFatalError}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogFatalError}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
 
 Like \helpref{wxLogError}{wxlogerror}, but also
 terminates the program with the exit code 3. Using {\it abort()} standard
@@ -2972,16 +2974,18 @@ function also terminates the program with this exit code.
 
 \membersection{::wxLogWarning}\label{wxlogwarning}
 
+\func{void}{wxLogWarning}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
+
 \func{void}{wxLogWarning}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogWarning}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
 
 For warnings - they are also normally shown to the user, but don't interrupt
 the program work.
 
 \membersection{::wxLogMessage}\label{wxlogmessage}
 
+\func{void}{wxLogMessage}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
+
 \func{void}{wxLogMessage}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogMessage}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
 
 For all normal, informational messages. They also appear in a message box by
 default (but it can be changed). Notice that the standard behaviour is to not
@@ -2992,7 +2996,8 @@ meaningless.
 \membersection{::wxLogVerbose}\label{wxlogverbose}
 
 \func{void}{wxLogVerbose}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogVerbose}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
+
+\func{void}{wxLogVerbose}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 For verbose output. Normally, it is suppressed, but
 might be activated if the user wishes to know more details about the program
@@ -3000,11 +3005,13 @@ progress (another, but possibly confusing name for the same function is {\bf wxL
 
 \membersection{::wxLogStatus}\label{wxlogstatus}
 
+\func{void}{wxLogStatus}{\param{wxFrame *}{frame}, \param{const char *}{formatString}, \param{va\_list }{argPtr}}
+
 \func{void}{wxLogStatus}{\param{wxFrame *}{frame}, \param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogStatus}{\param{wxFrame *}{frame}, \param{const char*}{ formatString}, \param{va_list}{argPtr}}
+
+\func{void}{wxLogStatus}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 \func{void}{wxLogStatus}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogStatus}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
 
 Messages logged by these functions will appear in the statusbar of the {\it
 frame} or of the top level application window by default (i.e. when using
@@ -3015,7 +3022,8 @@ If the target frame doesn't have a statusbar, the message will be lost.
 \membersection{::wxLogSysError}\label{wxlogsyserror}
 
 \func{void}{wxLogSysError}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogSysError}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
+
+\func{void}{wxLogSysError}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 Mostly used by wxWindows itself, but might be handy for logging errors after
 system call (API function) failure. It logs the specified message text as well
@@ -3031,7 +3039,8 @@ of this function takes the error code explicitly as the first argument.
 \membersection{::wxLogDebug}\label{wxlogdebug}
 
 \func{void}{wxLogDebug}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogDebug}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
+
+\func{void}{wxLogDebug}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 The right functions for debug output. They only do something in debug
 mode (when the preprocessor symbol \_\_WXDEBUG\_\_ is defined) and expand to
@@ -3040,13 +3049,15 @@ nothing in release mode (otherwise).
 \membersection{::wxLogTrace}\label{wxlogtrace}
 
 \func{void}{wxLogTrace}{\param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogTrace}{\param{const char*}{ formatString}, \param{va_list}{argPtr}}
+\func{void}{wxLogTrace}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 \func{void}{wxLogTrace}{\param{const char *}{mask}, \param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogTrace}{\param{const char *}{mask}, \param{const char *}{formatString}, \param{va_list}{argPtr}}
+
+\func{void}{wxLogTrace}{\param{const char *}{mask}, \param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 \func{void}{wxLogTrace}{\param{wxTraceMask}{ mask}, \param{const char *}{formatString}, \param{...}{}}
-\func{void}{wxLogTrace}{\param{wxTraceMask}{ mask}, \param{const char *}{formatString}, \param{va_list}{argPtr}}
+
+\func{void}{wxLogTrace}{\param{wxTraceMask}{ mask}, \param{const char *}{formatString}, \param{va\_list }{argPtr}}
 
 As {\bf wxLogDebug}, trace functions only do something in debug build and
 expand to nothing in the release one. The reason for making