some HTML links \urlref'ied

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

diff --git a/docs/latex/wx/body.tex b/docs/latex/wx/body.tex
index b4a7c6fe2cdcb92a2ed354cd82a1698fbea9fab2..c43630c00fe2906b8478bfcc7f05657123f8a82f 100644 (file)
--- a/docs/latex/wx/body.tex
+++ b/docs/latex/wx/body.tex
@@ -190,12 +190,9 @@ Metrowerks CodeWarrior.
 
 \section{Availability and location of wxWindows}
 
-wxWindows is available by anonymous FTP and World Wide Web:
-
-\begin{verbatim}
-  ftp://www.remstar.com/pub/wxwin
-  http://www.wxwindows.org
-\end{verbatim}
+wxWindows is available by anonymous FTP and World Wide Web
+from \urlref{ftp://www.remstar.com/pub/wxwin}{ftp://www.remstar.com/pub/wxwin} 
+and/or \urlref{http://www.wxwindows.org}{http://www.wxwindows.org}
 
 You can also buy a CD-ROM using the form on the Web site, or by contacting:
 
@@ -727,8 +724,8 @@ See the \helpref{debugging overview}{debuggingoverview} for further information.
 
 \subsection{Check Windows debug messages}
 
-Under Windows, it's worth running your program with DbgView (available from
-{\tt http://www.sysinternals.com} running or
+Under Windows, it's worth running your program with 
+\urlref{DbgView}{http://www.sysinternals.com} running or
 some other program that shows Windows-generated debug messages. It's
 possible it'll show invalid handles being used. You may have fun seeing
 what commercial programs cause these normally hidden errors! Microsoft

diff --git a/docs/latex/wx/tlog.tex b/docs/latex/wx/tlog.tex
index 76ad6ce6266e8b721a6f2fbab024a429df4d2048..4109e8c4907cfabeb21fa577f468d9ae7e8c5297 100644 (file)
--- a/docs/latex/wx/tlog.tex
+++ b/docs/latex/wx/tlog.tex
@@ -45,8 +45,8 @@ first argument.
 does anything at all in the debug mode (when the preprocessor symbol
 \_\_WXDEBUG\_\_ is defined) and expands to nothing in release mode (otherwise).
 {\bf Tip:} under Windows, you must either run the program under debugger or
-use a 3rd party program such as DbgView (from 
-{\tt http://www.sysinternals.com}) to actually see the debug output.
+use a 3rd party program such as \urlref{DbgView}{http://www.sysinternals.com} 
+to actually see the debug output.
 \item{\bf wxLogTrace} as {\bf wxLogDebug} only does something in debug
 build. The reason for making it a separate function from it is that usually
 there are a lot of trace messages, so it might make sense to separate them