Replace TRUE/FALSE with boolean values true/false - part 4r14.1.x

Manually cherry-picked from commit 4d495175

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 20 insertions, 20 deletions

diff --git a/doc/html/ntqftp.html b/doc/html/ntqftp.html
index f65d6ee28..5ffa51638 100644
--- a/doc/html/ntqftp.html
+++ b/doc/html/ntqftp.html
@@ -164,14 +164,14 @@ FTP server, you would write this:
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">HostLookup</a> )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">Connecting</a> )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">Connected</a> )
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 1, FALSE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 1, false )
 
     <a href="ntqnetworkprotocol.html#start">start</a>( 2 )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">LoggedIn</a> )
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 2, FALSE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 2, false )
 
     <a href="ntqnetworkprotocol.html#start">start</a>( 3 )
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 3, FALSE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 3, false )
 
     <a href="ntqnetworkprotocol.html#start">start</a>( 4 )
     <a href="#dataTransferProgress">dataTransferProgress</a>( 0, 3798 )
@@ -179,14 +179,14 @@ FTP server, you would write this:
     <a href="#readyRead">readyRead</a>()
     <a href="#dataTransferProgress">dataTransferProgress</a>( 3798, 3798 )
     <a href="#readyRead">readyRead</a>()
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 4, FALSE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 4, false )
 
     <a href="ntqnetworkprotocol.html#start">start</a>( 5 )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">Closing</a> )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">Unconnected</a> )
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 5, FALSE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 5, false )
 
-    <a href="#done">done</a>( FALSE )
+    <a href="#done">done</a>( false )
     </pre>
  
 <p> The <a href="#dataTransferProgress">dataTransferProgress</a>() signal in the above example is useful
@@ -203,12 +203,12 @@ like this:
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">HostLookup</a> )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">Connecting</a> )
     <a href="#stateChanged">stateChanged</a>( <a href="#State-enum">Connected</a> )
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 1, FALSE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 1, false )
 
     <a href="ntqnetworkprotocol.html#start">start</a>( 2 )
-    <a href="ntqnetworkprotocol.html#finished">finished</a>( 2, TRUE )
+    <a href="ntqnetworkprotocol.html#finished">finished</a>( 2, true )
 
-    <a href="#done">done</a>( TRUE )
+    <a href="#done">done</a>( true )
     </pre>
  
 <p> You can then get details about the error with the <a href="#error">error</a>() and
@@ -297,11 +297,11 @@ Aborts the current command and deletes all scheduled commands.
 <a href="#commandFinished">commandFinished</a>() signal has not been emitted), this function
 sends an <tt>ABORT</tt> command to the server. When the server replies
 that the command is aborted, the commandFinished() signal with the
-<tt>error</tt> argument set to <tt>TRUE</tt> is emitted for the command. Due
+<tt>error</tt> argument set to <tt>true</tt> is emitted for the command. Due
 to timing issues, it is possible that the command had already
 finished before the abort request reached the server, in which
 case, the commandFinished() signal is emitted with the <tt>error</tt>
-argument set to <tt>FALSE</tt>.
+argument set to <tt>false</tt>.
 <p> For all other commands that are affected by the <a href="#abort">abort</a>(), no
 signals are emitted.
 <p> If you don't start further FTP commands directly after the
@@ -310,7 +310,7 @@ signal is emitted.
 <p> <b>Warning:</b> Some FTP servers, for example the BSD FTP daemon (version
 0.3), wrongly return a positive reply even when an abort has
 occurred. For these servers the commandFinished() signal has its
-error flag set to <tt>FALSE</tt>, even though the command did not
+error flag set to <tt>false</tt>, even though the command did not
 complete successfully.
 <p> <p>See also <a href="#clearPendingCommands">clearPendingCommands</a>().
 
@@ -360,8 +360,8 @@ emitted.
 </h3>
 
 <p> This signal is emitted when processing the command identified by
-<em>id</em> has finished. <em>error</em> is TRUE if an error occurred during
-the processing; otherwise <em>error</em> is FALSE.
+<em>id</em> has finished. <em>error</em> is true if an error occurred during
+the processing; otherwise <em>error</em> is false.
 <p> <p>See also <a href="#commandStarted">commandStarted</a>(), <a href="#done">done</a>(), <a href="#error">error</a>(), and <a href="#errorString">errorString</a>().
 
 <p>Example: <a href="ftpclient-example.html#x747">network/ftpclient/ftpmainwindow.ui.h</a>.
@@ -432,8 +432,8 @@ bytes, since for large files these values might need to be
 
 <p> This signal is emitted when the last pending command has finished;
 (it is emitted after the last command's <a href="#commandFinished">commandFinished</a>() signal).
-<em>error</em> is TRUE if an error occurred during the processing;
-otherwise <em>error</em> is FALSE.
+<em>error</em> is true if an error occurred during the processing;
+otherwise <em>error</em> is false.
 <p> <p>See also <a href="#commandFinished">commandFinished</a>(), <a href="#error">error</a>(), and <a href="#errorString">errorString</a>().
 
 <p>Example: <a href="ftpclient-example.html#x753">network/ftpclient/ftpmainwindow.ui.h</a>.
@@ -441,7 +441,7 @@ otherwise <em>error</em> is FALSE.
 </h3>
 Returns the last error that occurred. This is useful to find out
 what when wrong when receiving a <a href="#commandFinished">commandFinished</a>() or a <a href="#done">done</a>()
-signal with the <tt>error</tt> argument set to <tt>TRUE</tt>.
+signal with the <tt>error</tt> argument set to <tt>true</tt>.
 <p> If you start a new command, the error status is reset to <a href="#Error-enum">NoError</a>.
 
 <h3 class=fn><a href="ntqstring.html">TQString</a> <a name="errorString"></a>TQFtp::errorString () const
@@ -449,7 +449,7 @@ signal with the <tt>error</tt> argument set to <tt>TRUE</tt>.
 Returns a human-readable description of the last error that
 occurred. This is useful for presenting a error message to the
 user when receiving a <a href="#commandFinished">commandFinished</a>() or a <a href="#done">done</a>() signal with
-the <tt>error</tt> argument set to <tt>TRUE</tt>.
+the <tt>error</tt> argument set to <tt>true</tt>.
 <p> The error string is often (but not always) the reply from the
 server, so it is not always possible to translate the string. If
 the message comes from TQt, the string has already passed through
@@ -488,8 +488,8 @@ emitted.
 <p>Example: <a href="ftpclient-example.html#x755">network/ftpclient/ftpmainwindow.ui.h</a>.
 <h3 class=fn>bool <a name="hasPendingCommands"></a>TQFtp::hasPendingCommands () const
 </h3>
-Returns TRUE if there are any commands scheduled that have not yet
-been executed; otherwise returns FALSE.
+Returns true if there are any commands scheduled that have not yet
+been executed; otherwise returns false.
 <p> The command that is being executed is <em>not</em> considered as a
 scheduled command.
 <p> <p>See also <a href="#clearPendingCommands">clearPendingCommands</a>(), <a href="#currentId">currentId</a>(), and <a href="#currentCommand">currentCommand</a>().