Fixed more '_' issues

Fixed all places that \begin{verbatim} and \end{verbatim} were not on lines by themselves (which tex2rtf cannot handle).
Changed all \verb$....$ occurrances to \tt{....}


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

docs/latex/wx/calctrl.tex

@@ -85,14 +85,16 @@ Note that changing the selected date will result in either of
 The following are the possible return values for 
 \helpref{HitTest}{wxcalendarctrlhittest} method:
 
+{\small
 \begin{verbatim}
 enum wxCalendarHitTestResult
-\{
+{
     wxCAL_HITTEST_NOWHERE,      // outside of anything
     wxCAL_HITTEST_HEADER,       // on the header (weekdays)
     wxCAL_HITTEST_DAY           // on a day in the calendar
-\};
+}
 \end{verbatim}
+}
 
 \wxheading{See also}
 
@@ -296,9 +298,9 @@ Here are the possible kinds of borders which may be used to decorate a date:
 \begin{verbatim}
 enum wxCalendarDateBorder
 {
-    wxCAL\_BORDER\_NONE,          // no border (default)
-    wxCAL\_BORDER\_SQUARE,        // a rectangular border
-    wxCAL\_BORDER\_ROUND          // a round border
+    wxCAL_BORDER_NONE,          // no border (default)
+    wxCAL_BORDER_SQUARE,        // a rectangular border
+    wxCAL_BORDER_ROUND          // a round border
 }
 \end{verbatim}
 

docs/latex/wx/classes.tex

@@ -171,7 +171,7 @@
 \input mbcnvut8.tex
 \input mdi.tex
 \input memorydc.tex
-\input fs_mem.tex
+\input fs\_mem.tex
 \input strmmem.tex
 \input menu.tex
 \input menuitem.tex

docs/latex/wx/config.tex

@@ -257,7 +257,7 @@ Currently, only two types of data are supported: string and long (but it might
 change in the near future). To work with other types: for {\it int} or {\it
 bool} you can work with function taking/returning {\it long} and just use the
 casts. Better yet, just use {\it long} for all variables which you're going to
-save in the config file: chances are that \verb$sizeof(bool) == sizeof(int) == sizeof(long)$ anyhow on your system. For {\it float}, {\it double} and, in
+save in the config file: chances are that \tt{sizeof(bool) == sizeof(int) == sizeof(long)} anyhow on your system. For {\it float}, {\it double} and, in
 general, any other type you'd have to translate them to/from string
 representation and use string functions.
 
@@ -309,8 +309,8 @@ config file:
   UserData = %windir%\\data.dat
 \end{verbatim}
 
-the call to \verb$config->Read("UserData")$ will return something like
-\verb$"/home/zeitlin/data"$ if you're lucky enough to run a Linux system ;-)
+the call to \tt{config->Read("UserData")} will return something like
+\tt{"/home/zeitlin/data"} if you're lucky enough to run a Linux system ;-)
 
 Although this feature is very useful, it may be annoying if you read a value
 which containts '\$' or '\%' symbols (\% is used for environment variables
@@ -593,12 +593,20 @@ if the key is not found.
 
 NB: writing
 
-{\small \begin{verbatim} conf->Read("key", 0); \end{verbatim} }
+{\small
+\begin{verbatim}
+    conf->Read("key", 0);
+\end{verbatim}
+}
 
 won't work because the call is ambiguous: compiler can not choose between two
 {\it Read} functions. Instead, write:
 
-{\small \begin{verbatim} conf->Read("key", 0l); \end{verbatim} }
+{\small
+\begin{verbatim}
+    conf->Read("key", 0l);
+\end{verbatim}
+}
 
 \constfunc{bool}{Read}{\param{const wxString\& }{ key}, \param{double*}{ d}}
 

docs/latex/wx/doctempl.tex

@@ -57,7 +57,7 @@ A pointer to the document manager for which this template was created.
 
 \member{wxString}{m\_fileFilter}
 
-The file filter (such as \verb$*.txt$) to be used in file selector dialogs.
+The file filter (such as \tt{*.txt}) to be used in file selector dialogs.
 
 \membersection{wxDocTemplate::m\_flags}
 
@@ -92,7 +92,7 @@ a wxDocManager instance, and before doing any document or view operations.
 {\it descr} is a short description of what the template is for. This string will be displayed in the
 file filter list of Windows file selectors.
 
-{\it filter} is an appropriate file filter such as \verb$*.txt$.
+{\it filter} is an appropriate file filter such as \tt{*.txt}.
 
 {\it dir} is the default directory to use for file selectors.
 

docs/latex/wx/function.tex

@@ -2482,7 +2482,7 @@ loading from resource data.
 \func{bool}{wxResourceAddIdentifier}{\param{const wxString\& }{name}, \param{int }{value}}
 
 Used for associating a name with an integer identifier (equivalent to dynamically\rtfsp
-\verb$#$defining a name to an integer). Unlikely to be used by an application except
+\tt{#}defining a name to an integer). Unlikely to be used by an application except
 perhaps for implementing resource functionality for interpreted languages.
 
 \membersection{::wxResourceClear}
@@ -2648,7 +2648,7 @@ load an entire {\tt .wxr file} into a string.
 
 \func{bool}{wxResourceRegisterBitmapData}{\param{const wxString\& }{name}, \param{char** }{xpm\_data}}
 
-Makes \verb$#$included XBM or XPM bitmap data known to the wxWindows resource system.
+Makes \tt{#}included XBM or XPM bitmap data known to the wxWindows resource system.
 This is required if other resources will use the bitmap data, since otherwise there
 is no connection between names used in resources, and the global bitmap data.
 

docs/latex/wx/htmlhlpf.tex

@@ -39,7 +39,7 @@ with some error. See also
 \wxheading{Contents file (.hhc)}
 
 Contents file has HTML syntax and it can be parsed by regular HTML parser. It contains exactly one list
-(\verb$<ul>$....\verb$</ul>$ statement):
+(\tt{<ul>}....\tt{</ul>} statement):
 
 \begin{verbatim}
 <ul>
@@ -63,7 +63,7 @@ You can modify value attributes of param tags. {\it topic name} is name of chapt
 contents, {\it filename.htm} is HTML page name (relative to .hhp file) and {\it numeric\_id} is optional 
 - it is used only when you use \helpref{wxHtmlHelpController::Display(int)}{wxhtmlhelpcontrollerdisplay}
 
-Items in the list may be nested - one \verb$<li>$ statement may contain a \verb$<ul>$ sub-statement:
+Items in the list may be nested - one \tt{<li>} statement may contain a \tt{<ul>} sub-statement:
 
 \begin{verbatim}
 <ul>

docs/latex/wx/locale.tex

@@ -6,8 +6,8 @@ generalization of the C locale concept.
 In wxWindows this class manages message catalogs which contain the translations
 of the strings used to the current language.
 
-\perlnote{In wxPerl the {\tt Wx} module exports a '_' function
-that corresponds to the '_' C++ macro.
+\perlnote{In wxPerl the {\tt Wx} module exports a '\_' function
+that corresponds to the '\_' C++ macro.
 \begin{verbatim}
   use Wx qw(_);
 

docs/latex/wx/mdi.tex

@@ -493,7 +493,7 @@ on the background.
 
 Note that it is probably impossible to have a client window that scrolls as well as painting
 a bitmap or pattern, since in {\bf OnScroll}, the scrollbar positions always return zero.
-(Solutions to: \verb$julian.smart@ukonline.co.uk$).
+(Solutions to: \tt{julian.smart@ukonline.co.uk}).
 
 \wxheading{See also}
 

docs/latex/wx/porting.tex

@@ -57,7 +57,8 @@ for some notes on using member functions for callbacks. wxWindows 2.0 will banis
 callback functions (and OnMenuCommand), and nearly all event handling will be done by functions taking a single event argument.
 So in future you will have code like:
 
-{\small\begin{verbatim}
+{\small
+\begin{verbatim}
 void MyFrame::OnOK(wxCommandEvent& event)
 {
         ...
@@ -258,7 +259,8 @@ returned in wxWindows 1.xx, your application will need to be changed. Usually yo
 simplify your application's allocation and deallocation of memory for the returned string,
 and simply assign the result to a wxString object. For example, replace this:
 
-{\small\begin{verbatim}
+{\small
+\begin{verbatim}
   char* s = wxFunctionThatReturnsString();
   s = copystring(s); // Take a copy in case it is temporary
   .... // Do something with it
@@ -268,7 +270,8 @@ and simply assign the result to a wxString object. For example, replace this:
 
 with this:
 
-{\small\begin{verbatim}
+{\small
+\begin{verbatim}
   wxString s = wxFunctionThatReturnsString();
   .... // Do something with it
 \end{verbatim}

docs/latex/wx/print.tex

@@ -830,7 +830,7 @@ checked) from within the overridden function, since it calls wxDC::StartDoc.
 
 \pythonnote{If this method is overridden in a Python class then the
 base class version can be called by using the method
-{\tt base_OnBeginDocument(startPage, endPage)}. }
+{\tt base\_OnBeginDocument(startPage, endPage)}. }
 
 \membersection{wxPrintout::OnEndDocument}\label{wxprintoutonenddocument}
 

docs/latex/wx/tdb.tex

@@ -1308,31 +1308,31 @@ for selection and the columns returned may be specified.
 
 Examples:
 
-\verb$SELECT * FROM Book$
+\tt{SELECT * FROM Book}
 
 Selects all rows and columns from table Book.
 
-\verb$SELECT Title, RetailPriceAmount FROM Book WHERE RetailPriceAmount > 20.0$
+\tt{SELECT Title, RetailPriceAmount FROM Book WHERE RetailPriceAmount > 20.0}
 
 Selects columns Title and RetailPriceAmount from table Book, returning only
 the rows that match the WHERE clause.
 
-\verb$SELECT * FROM Book WHERE CatCode = 'LL' OR CatCode = 'RR'$
+\tt{SELECT * FROM Book WHERE CatCode = 'LL' OR CatCode = 'RR'}
 
 Selects all columns from table Book, returning only
 the rows that match the WHERE clause.
 
-\verb$SELECT * FROM Book WHERE CatCode IS NULL$
+\tt{SELECT * FROM Book WHERE CatCode IS NULL}
 
 Selects all columns from table Book, returning only rows where the CatCode column
 is NULL.
 
-\verb$SELECT * FROM Book ORDER BY Title$
+\tt{SELECT * FROM Book ORDER BY Title}
 
 Selects all columns from table Book, ordering by Title, in ascending order. To specify
 descending order, add DESC after the ORDER BY Title clause.
 
-\verb$SELECT Title FROM Book WHERE RetailPriceAmount >= 20.0 AND RetailPriceAmount <= 35.0$
+\tt{SELECT Title FROM Book WHERE RetailPriceAmount >= 20.0 AND RetailPriceAmount <= 35.0}
 
 Selects records where RetailPriceAmount conforms to the WHERE expression.
 
@@ -1342,7 +1342,7 @@ Updates records in a table.
 
 Example:
 
-\verb$UPDATE Incident SET X = 123 WHERE ASSET = 'BD34'$
+\tt{UPDATE Incident SET X = 123 WHERE ASSET = 'BD34'}
 
 This example sets a field in column `X' to the number 123, for the record
 where the column ASSET has the value `BD34'.