define _HPUX_SOURCE under HP-UX, otherwise many things are not defined in standard...

[wxWidgets.git] / docs / latex / wx / tdb.tex

diff --git a/docs/latex/wx/tdb.tex b/docs/latex/wx/tdb.tex
index bc458335d4842953b4f199e355c85c2aa45829de..71a470d202c3793f526839cf81f0b1adfaae969c 100644 (file)
--- a/docs/latex/wx/tdb.tex
+++ b/docs/latex/wx/tdb.tex
@@ -835,9 +835,9 @@ they also needed to take in to account different database manufacturers and
 different ODBC driver manufacturers. Because of all the possible combinations 
 of OS/database/drivers, it is impossible to say that these classes will work 
 perfectly with datasource ABC, ODBC driver XYZ, on platform LMN. You may run 
-in to some incompatibilities or unsupported features when moving your 
+into some incompatibilities or unsupported features when moving your 
 application from one environment to another. But that is what makes 
-cross-platform programming fun. It is also pinpoints one of the great 
+cross-platform programming fun. It also pinpoints one of the great 
 things about open source software. It can evolve!
 
 The most common difference between different database/ODBC driver 
@@ -920,8 +920,8 @@ and OS on which the program will be compiled/run is Unicode capable.
 
 The one major difference in writing code that can be compiled in either 
 unicode or non-unicode builds that is specific to the wxODBC classes is to 
-use the SQL_C_WXCHAR datatype for string columns rather than SQL_C_CHAR or 
-SQL_C_WCHAR.
+use the SQL\_C\_WXCHAR datatype for string columns rather than SQL\_C\_CHAR or 
+SQL\_C\_WCHAR.
 
 \subsection{wxODBC - Sample Code}\label{wxodbcsamplecode1}