[DOCUMENTATION] English:

- manual fixes (<code>true</code> ==> <constant>TRUE</constant>)

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@15742 44c647ce-9c0f-0410-b52a-842ac1e357ba

documentation/manual/en/module_specs/Zend_Cache-Frontends.xml

@@ -76,7 +76,7 @@
                           <row>
                               <entry><code>write_control</code></entry>
                               <entry><code>boolean</code></entry>
-                              <entry><code>true</code></entry>
+                              <entry><constant>TRUE</constant></entry>
                               <entry>
                                 Enable / disable write control (the cache is read
                                 just after writing to detect corrupt entries), enabling write_control
@@ -299,7 +299,7 @@ echo 'This is never cached ('.time().').';
                           <row>
                               <entry><code>cache_by_default</code></entry>
                               <entry><code>boolean</code></entry>
-                              <entry><code>true</code></entry>
+                              <entry><constant>TRUE</constant></entry>
                               <entry>
                                   if true, function calls will be cached by default
                               </entry>
@@ -387,7 +387,7 @@ $cache->call('veryExpensiveFunc', $params);
                          <row>
                               <entry><code>cache_by_default</code></entry>
                               <entry><code>boolean</code></entry>
-                              <entry><code>true</code></entry>
+                              <entry><constant>TRUE</constant></entry>
                               <entry>
                                   if true, calls will be cached by default
                               </entry>

documentation/manual/en/module_specs/Zend_Config-TheoryOfOperation.xml

@@ -73,7 +73,7 @@
         <note>
             <para>
                 The <classname>Zend_Config</classname> object that is performing the merge must have been constructed
-                to allow modifications, by passing <code>true</code> as the second parameter of the constructor.
+                to allow modifications, by passing <constant>TRUE</constant> as the second parameter of the constructor.
                 The <code>setReadOnly()</code> method can then be used to prevent any further modifications
                 after the merge is complete.
             </para>

documentation/manual/en/module_specs/Zend_Config_Ini.xml

@@ -17,7 +17,7 @@
             <ulink url="http://php.net/parse_ini_file"><code>parse_ini_file()</code></ulink>
             PHP function. Please review this documentation to be aware of its specific behaviors,
             which propagate to <classname>Zend_Config_Ini</classname>, such as how the special values of
-            <code>true</code>, <constant>FALSE</constant>, <code>yes</code>, <code>no</code>,
+            <constant>TRUE</constant>, <constant>FALSE</constant>, <code>yes</code>, <code>no</code>,
             and <code>null</code> are handled.
         </para>
     </note>

documentation/manual/en/module_specs/Zend_Console_Getopt-Fetching.xml

@@ -75,7 +75,7 @@ try {
             of an option. If the option had a parameter, this method returns
             the value of the parameter. If the option had no parameter but
             the user did specify it on the command-line, the method returns
-            <code>true</code>. Otherwise the method returns <code>null</code>.
+            <constant>TRUE</constant>. Otherwise the method returns <code>null</code>.
         </para>
         <example id="zend.console.getopt.fetching.byname.example.setoption">
             <title>Using getOption()</title>
@@ -119,7 +119,7 @@ $p_parameter = $opts->p; // null if not set
                     As a string: use the <code>toString()</code> method. The options
                     are returned as a space-separated string of "<code>flag=value</code>"
                     pairs. The value of an option that does not have a parameter
-                    is the literal string "<code>true</code>".
+                    is the literal string "<constant>TRUE</constant>".
                 </para>
             </listitem>
             <listitem>

documentation/manual/en/module_specs/Zend_Controller-ActionHelpers-ContextSwitch.xml

@@ -378,7 +378,7 @@ class FooController extends Zend_Controller_Action
                 </para>
 
                 <para>
-                    A value of <code>true</code> for the context will mark
+                    A value of <constant>TRUE</constant> for the context will mark
                     all available contexts as available for the action.
                 </para>
 

documentation/manual/en/module_specs/Zend_Controller-ActionHelpers-Json.xml

@@ -76,7 +76,7 @@ class FooController extends Zend_Controller_Action
             If you have a separate layout for JSON responses -- perhaps to wrap
             the JSON response in some sort of context -- each method in the JSON
             helper accepts a second, optional argument: a flag to enable or
-            disable layouts. Passing a boolean <code>true</code> value will keep
+            disable layouts. Passing a boolean <constant>TRUE</constant> value will keep
             layouts enabled:
         </para>
 
@@ -102,7 +102,7 @@ $this->_helper->json($data, array('keepLayouts' => true);
             <classname>Zend_Json::encode()</classname> allows the encoding of native JSON
             expressions using <code>Zend_Json_Expr</code> objects. This option
             is disabled by default. To enable this option, pass a boolean
-            <code>true</code> value to the <code>enableJsonExprFinder</code>
+            <constant>TRUE</constant> value to the <code>enableJsonExprFinder</code>
             option:
         </para>
 

documentation/manual/en/module_specs/Zend_Controller-FrontController.xml

@@ -405,7 +405,7 @@ Zend_Controller_Front::run('../application/controllers');
                 <para>
                     <code>returnResponse($flag)</code> is used to tell the front
                     controller whether to return the response
-                    (<code>true</code>) from <code>dispatch()</code>, or if the
+                    (<constant>TRUE</constant>) from <code>dispatch()</code>, or if the
                     response should be automatically emitted
                     (<constant>FALSE</constant>). By default, the response is
                     automatically emitted (by calling

documentation/manual/en/module_specs/Zend_Db_Adapter.xml

@@ -367,7 +367,7 @@ $db = Zend_Db::factory('Db2', $params);
                 <para>
                     You can specify this option by the constant
                     <classname>Zend_Db::AUTO_QUOTE_IDENTIFIERS</classname>. If the value
-                    is <code>true</code> (the default), identifiers like table
+                    is <constant>TRUE</constant> (the default), identifiers like table
                     names, column names, and even aliases are delimited in all
                     SQL syntax generated by the Adapter object. This makes it
                     simple to use identifiers that contain SQL keywords, or

documentation/manual/en/module_specs/Zend_Db_Profiler.xml

@@ -48,7 +48,7 @@ $db->getProfiler()->setEnabled(true);
         </para>
 
         <para>
-            A boolean argument sets the profiler to enabled if it is a <code>true</code> value, or disabled if
+            A boolean argument sets the profiler to enabled if it is a <constant>TRUE</constant> value, or disabled if
             <constant>FALSE</constant>. The profiler class is the adapter's default profiler class,
             <classname>Zend_Db_Profiler</classname>.
             <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Db_Table.xml

@@ -485,7 +485,7 @@ $data = array(
 
             <para>
                 In <classname>Zend_Db_Table_Abstract</classname>, if you define the protected variable
-                <varname>$_sequence</varname> to be the Boolean value <code>true</code>, then the class
+                <varname>$_sequence</varname> to be the Boolean value <constant>TRUE</constant>, then the class
                 assumes that the table has an auto-incrementing primary key.
             </para>
 
@@ -517,7 +517,7 @@ class Bugs extends Zend_Db_Table_Abstract
                 for new rows. IBM DB2 has an <code>IDENTITY</code> notation that works similarly.
                 If you use either of these notations, treat your <classname>Zend_Db_Table</classname> class as having an
                 auto-incrementing column with respect to declaring the <varname>$_sequence</varname>
-                member as <code>true</code>.
+                member as <constant>TRUE</constant>.
             </para>
 
         </sect3>
@@ -1397,7 +1397,7 @@ $bugs = new Bugs(array('metadataCache' => $cache));
             <para>
                 Since the information returned from the adapter's describeTable() method is an
                 array, ensure that the <code>automatic_serialization</code> option is set to
-                <code>true</code> for the <classname>Zend_Cache_Core</classname> frontend.
+                <constant>TRUE</constant> for the <classname>Zend_Cache_Core</classname> frontend.
             </para>
 
         </note>

documentation/manual/en/module_specs/Zend_Debug.xml

@@ -34,7 +34,7 @@ Zend_Debug::dump($var, $label=null, $echo=true);
     <para>
         The boolean <varname>$echo</varname> argument specifies whether the output
         of <classname>Zend_Debug::dump()</classname> is echoed or not.
-        If <code>true</code>, the output is echoed.
+        If <constant>TRUE</constant>, the output is echoed.
         Regardless of the value of the <varname>$echo</varname> argument, the
         return value of this method contains the output.
     </para>

documentation/manual/en/module_specs/Zend_Feed-ConsumingRss.xml

@@ -137,7 +137,7 @@ if ($item->propname()) {
 
     <para>
         If you use <code>$item->propname</code> instead, you will always get an empty object which will
-        evaluate to <code>TRUE</code>, so your check will fail.
+        evaluate to <constant>TRUE</constant>, so your check will fail.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Filter_Input.xml

@@ -273,7 +273,7 @@ $input->setData($newData);
 
             <para>
                 If all input data pass the validation rules, the
-                <code>isValid()</code> method returns <code>true</code>.
+                <code>isValid()</code> method returns <constant>TRUE</constant>.
                 If any field is invalid or any required field is missing,
                 <code>isValid()</code> returns <constant>FALSE</constant>.
             </para>
@@ -288,7 +288,7 @@ if ($input->isValid()) {
                 This method accepts an optional string argument, naming
                 an individual field. If the specified field passed validation
                 and is ready for fetching, <code>isValid('fieldName')</code>
-                returns <code>true</code>.
+                returns <constant>TRUE</constant>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -554,7 +554,7 @@ $filters = array(
                 specify a password string in two fields, and they must type the
                 same string in both fields. Suppose you implement a validator
                 class that takes an array argument, and returns
-                <code>true</code> if all the values in the array are equal to
+                <constant>TRUE</constant> if all the values in the array are equal to
                 each other.
             </para>
 
@@ -684,7 +684,7 @@ echo $input->month; // echoes 1
 
             <para>
                 If in your case an empty string should be considered valid, you
-                can set the metacommand 'allowEmpty' to <code>true</code>.
+                can set the metacommand 'allowEmpty' to <constant>TRUE</constant>.
                 Then the input data passes validation if it is present in the
                 input data, but has the value of an empty string.
             </para>
@@ -746,7 +746,7 @@ $input->setOptions($options);
 
             <para>
                 Alternatively, if the value of the 'breakChainOnFailure'
-                metacommand is <code>true</code>, the validator chain
+                metacommand is <constant>TRUE</constant>, the validator chain
                 terminates after the first validator fails. The input data is
                 not checked against subsequent validators in the chain, so it
                 might cause more violations even if you correct the one

documentation/manual/en/module_specs/Zend_Form-Elements.xml

@@ -387,7 +387,7 @@ $element->addPrefixPath('My_Validator', 'My/Validator/', 'validate');
 
         <para>
             If failing a particular validation should prevent later validators
-            from firing, pass boolean <code>true</code> as the second parameter:
+            from firing, pass boolean <constant>TRUE</constant> as the second parameter:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -653,7 +653,7 @@ $messages = $element->getMessages();
             <listitem><para>
                     <code>setRequired($flag)</code> and
                     <code>isRequired()</code> allow you to set and retrieve the
-                    status of the 'required' flag. When set to boolean <code>true</code>, this
+                    status of the 'required' flag. When set to boolean <constant>TRUE</constant>, this
                     flag requires that the element be in the data processed by
                     <classname>Zend_Form</classname>.
             </para></listitem>

documentation/manual/en/module_specs/Zend_Gdata_Gapps.xml

@@ -285,7 +285,7 @@ $user = $user->save();
                     A user can be forced to change their password at their
                     next login by setting the
                     <code>login->changePasswordAtNextLogin</code> property to
-                    <code>true</code>.
+                    <constant>TRUE</constant>.
                 </para>
 
                 <programlisting language="php"><![CDATA[
@@ -322,7 +322,7 @@ $gdata->restoreUser('foo');
                 <para>
                     Alternatively, you can set the UserEntry's
                     <code>login->suspended</code> property to
-                    <code>true</code>.
+                    <constant>TRUE</constant>.
                 </para>
 
                 <programlisting language="php"><![CDATA[
@@ -345,7 +345,7 @@ $user = $user->save();
                 <para>
                     Users can be granted the ability to administer your domain
                     by setting their <code>login->admin</code> property to
-                    <code>true</code>.
+                    <constant>TRUE</constant>.
                 </para>
 
                 <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Gdata_Gbase.xml

@@ -274,7 +274,7 @@ foreach ($feed->entries as $entry) {
             A customer/owner can access his own Customer Items feed to insert, update, or delete their items. These operations do not apply to the public snippets feed.
         </para>
         <para>
-            You can test a feed operation before it is actually executed by setting the dry-run flag (<code>$dryRun</code>) to <code>true</code>. Once you are sure that you want to submit the data, set it to <constant>FALSE</constant> to execute the operation.
+            You can test a feed operation before it is actually executed by setting the dry-run flag (<code>$dryRun</code>) to <constant>TRUE</constant>. Once you are sure that you want to submit the data, set it to <constant>FALSE</constant> to execute the operation.
         </para>
         <sect3 id="zend.gdata.gbase.crud.insert">
             <title>Insert an Item</title>

documentation/manual/en/module_specs/Zend_Ldap.xml

@@ -85,7 +85,7 @@ echo "$acctname\n";
 
             <para>
                 If <code>bind()</code> is called with a non-DN username but <code>bindRequiresDN</code> is
-                <code>true</code> and no username in DN form was supplied as an option, the bind will fail. However, if
+                <constant>TRUE</constant> and no username in DN form was supplied as an option, the bind will fail. However, if
                 a username in DN form is supplied in the options array, <classname>Zend_Ldap</classname> will first bind with
                 that username, retrieve the account DN for the username supplied to <code>bind()</code> and then re-
                 bind with that DN.
@@ -117,7 +117,7 @@ echo "$acctname\n";
 ]]></programlisting>
 
                 The <code>bind()</code> call in this example sees that the username '<code>abaker</code>' is not in DN
-                form, finds <code>bindRequiresDn</code> is <code>true</code>, uses
+                form, finds <code>bindRequiresDn</code> is <constant>TRUE</constant>, uses
                 '<code>CN=user1,DC=foo,DC=net</code>' and '<code>pass1</code>' to bind, retrieves the DN for
                 '<code>abaker</code>', unbinds and then rebinds with the newly discovered
                 '<code>CN=Alice Baker,OU=Sales,DC=foo,DC=net</code>'.
@@ -160,7 +160,7 @@ echo "$acctname\n";
                         <entry>useStartTls</entry>
                         <entry>
                             Whether or not the LDAP client should use TLS (aka SSLv2) encrypted transport. A value of
-                            <code>true</code> is strongly favored in production environments to prevent passwords from
+                            <constant>TRUE</constant> is strongly favored in production environments to prevent passwords from
                             be transmitted in clear text. The default value is <constant>FALSE</constant>, as servers
                             frequently require that a certificate be installed separately after installation.
                             The <code>useSsl</code> and <code>useStartTls</code> options are mutually exclusive.
@@ -190,7 +190,7 @@ echo "$acctname\n";
                       <row>
                         <entry>bindRequiresDn</entry>
                         <entry>
-                            If <code>true</code>, this instructs <classname>Zend_Ldap</classname> to retrieve the DN for the
+                            If <constant>TRUE</constant>, this instructs <classname>Zend_Ldap</classname> to retrieve the DN for the
                             account used to bind if the username is not already in DN form. The default value is
                             <constant>FALSE</constant>.
                         </entry>
@@ -231,7 +231,7 @@ echo "$acctname\n";
                             <ulink url="http://php.net/printf"><code>printf()</code></ulink> style expression that must
                             contain one '<code>%s</code>' to accommodate the username. The default value is
                             '<code>(&amp;(objectClass=user)(sAMAccountName=%s))</code>' unless
-                            <code>bindRequiresDn</code> is set to <code>true</code>, in which case the default is
+                            <code>bindRequiresDn</code> is set to <constant>TRUE</constant>, in which case the default is
                             '<code>(&amp;(objectClass=posixAccount)(uid=%s))</code>'. Users of custom schemas may need
                             to change this option.
                         </entry>
@@ -242,14 +242,14 @@ echo "$acctname\n";
                             Some LDAP servers can be configured to accept an empty string
                             password as an anonymous bind. This behavior is almost always
                             undesirable. For this reason, empty passwords are explicitly
-                            disallowed. Set this value to <code>true</code> to allow an
+                            disallowed. Set this value to <constant>TRUE</constant> to allow an
                             empty string password to be submitted during the bind.
                         </entry>
                       </row>
                       <row>
                         <entry>optReferrals</entry>
                         <entry>
-                            If set to <code>true</code>, this option indicates to the LDAP client that referrals should
+                            If set to <constant>TRUE</constant>, this option indicates to the LDAP client that referrals should
                             be followed. The default value is <constant>FALSE</constant>.
                         </entry>
                       </row>

documentation/manual/en/module_specs/Zend_Loader.xml

@@ -57,7 +57,7 @@ Zend_Loader::loadFile($filename, $dirs=null, $once=false);
         </para>
 
         <para>
-            The <code>$once</code> argument is a boolean. If <code>TRUE</code>,
+            The <code>$once</code> argument is a boolean. If <constant>TRUE</constant>,
             <classname>Zend_Loader::loadFile()</classname> uses the PHP function
             <ulink url="http://php.net/include"><code>include_once()</code></ulink>
             for loading the file, otherwise the PHP function
@@ -121,7 +121,7 @@ Zend_Loader::loadClass('Container_Tree',
 
         <para>
             The static method <classname>Zend_Loader::isReadable($pathname)</classname>
-            returns <code>TRUE</code> if a file at the specified pathname exists
+            returns <constant>TRUE</constant> if a file at the specified pathname exists
             and is readable, <constant>FALSE</constant> otherwise.
         </para>
 
@@ -218,7 +218,7 @@ Zend_Loader::registerAutoload('My_Loader');
         <para>
             You can remove an autoload callback. The
             <code>registerAutoload()</code> has an optional second argument,
-            which is <code>true</code> by default. If this argument is
+            which is <constant>TRUE</constant> by default. If this argument is
             <constant>FALSE</constant>, the autoload callback is unregistered from the
             SPL autoload stack.
         </para>

documentation/manual/en/module_specs/Zend_Locale-Functions.xml

@@ -1271,7 +1271,7 @@ if (Zend_Locale::isLocale($input)) {
         <para>
             Still it's sometimes usefull to prevent this automatic degrading, and this is where the second
             parameter of <code>isLocale()</code> comes in place. The <code>strict</code> parameter defaults to
-            <constant>FALSE</constant> and can be used to prevent degrading when set to <code>true</code>.
+            <constant>FALSE</constant> and can be used to prevent degrading when set to <constant>TRUE</constant>.
         </para>
 
         <example id="zend.locale.detection.example-2">

documentation/manual/en/module_specs/Zend_Measure-Edit.xml

@@ -151,7 +151,7 @@ echo $sum;
 
         <para>
             Measurements can also be compared, but without automatic unit conversion. Thus, <code>equals()</code>
-            returns <code>TRUE</code>, only if both the value and the unit of measure are identical.
+            returns <constant>TRUE</constant>, only if both the value and the unit of measure are identical.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Memory-MemoryObjects.xml

@@ -248,10 +248,10 @@ public function isLocked();
 
             <para>
                 The <code>isLocked()</code> method can be used to check if
-                object is locked. It returns <code>true</code> if the object
+                object is locked. It returns <constant>TRUE</constant> if the object
                 is locked, or <constant>FALSE</constant> if it is not locked.
-                This is always <code>true</code> for "locked" objects,
-                and may be either <code>true</code> or <constant>FALSE</constant>
+                This is always <constant>TRUE</constant> for "locked" objects,
+                and may be either <constant>TRUE</constant> or <constant>FALSE</constant>
                 for "movable" objects.
             </para>
 

documentation/manual/en/module_specs/Zend_Navigation-Pages-Common.xml

@@ -156,7 +156,7 @@
                 <row>
                     <entry><code>visible</code></entry>
                     <entry><code>bool</code></entry>
-                    <entry><code>true</code></entry>
+                    <entry><constant>TRUE</constant></entry>
                     <entry>
                         Whether page should be visible for the user, or just
                         be a part of the structure. Invisible pages are skipped

documentation/manual/en/module_specs/Zend_Navigation-Pages-MVC.xml

@@ -72,7 +72,7 @@
                 <row>
                     <entry><code>reset_params</code></entry>
                     <entry><code>bool</code></entry>
-                    <entry><code>true</code></entry>
+                    <entry><constant>TRUE</constant></entry>
                     <entry>
                         Whether user params should be reset
                         when generating href to the page.

documentation/manual/en/module_specs/Zend_ProgressBar_Adapter_JsPull.xml

@@ -11,7 +11,7 @@
         like the JSON string which is send by the jsPush adapter. The only
         difference is, that it contains an additional parameter,
         <code>finished</code>, which is either <constant>FALSE</constant> when
-        <code>update()</code> is called or <code>true</code>, when
+        <code>update()</code> is called or <constant>TRUE</constant>, when
         <code>finish()</code> is called.
     </para>
     <para>
@@ -23,7 +23,7 @@
         <listitem>
             <para>
                 <code>exitAfterSend</code>: Exits the current request after the
-                data were send to the browser. Default is <code>true</code>.
+                data were send to the browser. Default is <constant>TRUE</constant>.
             </para>
         </listitem>
     </itemizedlist>

documentation/manual/en/module_specs/Zend_Search_Lucene-Queries.xml

@@ -197,7 +197,7 @@ $hits  = $index->find($query);
             <itemizedlist>
                 <listitem>
                     <para>
-                        <code>true</code> is used to define required term.
+                        <constant>TRUE</constant> is used to define required term.
                     </para>
                 </listitem>
                 <listitem>
@@ -327,7 +327,7 @@ $hits  = $index->find($query);
             <itemizedlist>
                 <listitem>
                     <para>
-                        <code>true</code> is used to define required subquery.
+                        <constant>TRUE</constant> is used to define required subquery.
                     </para>
                 </listitem>
                 <listitem>

documentation/manual/en/module_specs/Zend_Session-AdvancedUsage.xml

@@ -76,7 +76,7 @@ php_value session.auto_start 0
                 <itemizedlist mark="opencircle">
                     <listitem>
                         <para>
-                            Unconditionally set the <code>strict</code> option to <code>true</code> using
+                            Unconditionally set the <code>strict</code> option to <constant>TRUE</constant> using
                             <classname>Zend_Session::setOptions()</classname> in your bootstrap.
                         </para>
                     </listitem>
@@ -258,7 +258,7 @@ else {
         </para>
 
         <para>
-            To enable this behavior, pass <code>true</code> to the second constructor argument when creating the last
+            To enable this behavior, pass <constant>TRUE</constant> to the second constructor argument when creating the last
             allowed instance of <classname>Zend_Session_Namespace</classname>. Any subsequent attempt to instantiate the same
             namespace would result in a thrown exception.
         </para>

documentation/manual/en/module_specs/Zend_Session-GlobalSessionManagement.xml

@@ -417,14 +417,14 @@ if (!isset($defaultNamespace->initialized)) {
             <classname>Zend_Session::destroy()</classname> destroys all of the persistent data associated with the current
             session. However, no variables in PHP are affected, so your namespaced sessions (instances of
             <classname>Zend_Session_Namespace</classname>) remain readable. To complete a "logout", set the optional parameter to
-            <code>true</code> (the default) to also delete the user agent's session id cookie. The optional
+            <constant>TRUE</constant> (the default) to also delete the user agent's session id cookie. The optional
             <code>$readonly</code> parameter removes the ability to create new <classname>Zend_Session_Namespace</classname>
             instances and for <classname>Zend_Session</classname> methods to write to the session data store.
         </para>
 
         <para>
             If you see the error message, "Cannot modify header information - headers already sent", then either avoid
-            using <code>true</code> as the value for the first argument (requesting removal of the session cookie), or
+            using <constant>TRUE</constant> as the value for the first argument (requesting removal of the session cookie), or
             see <xref linkend="zend.session.global_session_management.headers_sent" />. Thus,
             <classname>Zend_Session::destroy(true)</classname> must either be called before PHP has sent HTTP headers, or output
             buffering must be enabled. Also, the total output sent must not exceed the set buffer size, in order to

documentation/manual/en/module_specs/Zend_Soap_Server.xml

@@ -319,7 +319,7 @@ $request = $server->getLastRequest();
 
             <para>
                 <classname>Zend_Soap_Server::handle()</classname> method automatically emits generated response to the output stream.
-                It may be blocked using <code>setReturnResponse()</code> with <code>true</code> or <constant>FALSE</constant>
+                It may be blocked using <code>setReturnResponse()</code> with <constant>TRUE</constant> or <constant>FALSE</constant>
                 as a parameter<footnote>
                                 <para>
                                     Current state of the Return Response flag may be requested with

documentation/manual/en/module_specs/Zend_Validate-EmailAddress.xml

@@ -104,7 +104,7 @@ $validator = new Zend_Validate_EmailAddress(Zend_Validate_Hostname::ALLOW_DNS,
                                             true);
 ]]></programlisting>
 
-        Alternatively you can either pass <code>true</code> or <constant>FALSE</constant> to
+        Alternatively you can either pass <constant>TRUE</constant> or <constant>FALSE</constant> to
         <code>$validator->setValidateMx()</code> to enable or disable MX validation.
     </para>
 

documentation/manual/en/module_specs/Zend_Validate-Set.xml

@@ -12,7 +12,7 @@
     <sect2 id="zend.validate.set.alnum">
         <title>Alnum</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> contains only alphabetic
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> contains only alphabetic
             and digit characters. This validator includes an option to also consider white space
             characters as valid.
         </para>
@@ -30,7 +30,7 @@
     <sect2 id="zend.validate.set.alpha">
         <title>Alpha</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> contains only alphabetic
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> contains only alphabetic
             characters. This validator includes an option to also consider white space characters
             as valid.
         </para>
@@ -52,7 +52,7 @@
     <sect2 id="zend.validate.set.between">
         <title>Between</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is between the minimum and
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is between the minimum and
             maximum boundary values. The comparison is inclusive by default (<code>$value</code> may
             equal a boundary value), though this may be overridden in order to do a strict
             comparison, where <code>$value</code> must be strictly greater than the minimum and
@@ -63,7 +63,7 @@
     <sect2 id="zend.validate.set.ccnum">
         <title>Ccnum</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> follows the Luhn algorithm
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> follows the Luhn algorithm
             (mod-10 checksum) for credit card numbers.
         </para>
     </sect2>
@@ -71,7 +71,7 @@
     <sect2 id="zend.validate.set.date">
         <title>Date</title>
         <para>
-            Returns <code>true</code> if <code>$value</code> is a valid date of the format
+            Returns <constant>TRUE</constant> if <code>$value</code> is a valid date of the format
             <code>YYYY-MM-DD</code>. If the optional <code>locale</code> option is set then the date
             will be validated according to the set locale. And if the optional <code>format</code>
             option is set this format is used for the validation. for details about the optional
@@ -85,7 +85,7 @@
     <sect2 id="zend.validate.set.digits">
         <title>Digits</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> only contains digit
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> only contains digit
             characters.
         </para>
     </sect2>
@@ -95,7 +95,7 @@
     <sect2 id="zend.validate.set.float">
         <title>Float</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is a floating-point value.
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is a floating-point value.
             Since Zend Framework 1.8 this validator takes into account the actual locale from
             browser, environment or application wide set locale. You can of course use the
             get/setLocale accessors to change the used locale or give it while creating a instance
@@ -106,7 +106,7 @@
     <sect2 id="zend.validate.set.greater_than">
         <title>GreaterThan</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is greater than the minimum
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is greater than the minimum
             boundary.
         </para>
     </sect2>
@@ -114,7 +114,7 @@
     <sect2 id="zend.validate.set.hex">
         <title>Hex</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> contains only hexadecimal
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> contains only hexadecimal
             digit characters.
         </para>
     </sect2>
@@ -124,7 +124,7 @@
     <sect2 id="zend.validate.set.iban">
         <title>Iban</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> contains a valid IBAN
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> contains a valid IBAN
             (International Bank Account Number). IBAN numbers are validated against the country
             where they are used and by a checksum.
         </para>
@@ -169,8 +169,8 @@ if ($validator->isValid($iban)) {
     <sect2 id="zend.validate.set.in_array">
         <title>InArray</title>
         <para>
-            Returns <code>true</code> if and only if a "needle" <code>$value</code> is contained in
-            a "haystack" array. If the strict option is <code>true</code>, then the type of
+            Returns <constant>TRUE</constant> if and only if a "needle" <code>$value</code> is contained in
+            a "haystack" array. If the strict option is <constant>TRUE</constant>, then the type of
             <code>$value</code> is also checked.
         </para>
     </sect2>
@@ -178,7 +178,7 @@ if ($validator->isValid($iban)) {
     <sect2 id="zend.validate.set.int">
         <title>Int</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is a valid integer. Since
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is a valid integer. Since
             Zend Framework 1.8 this validator takes into account the actual locale from browser,
             environment or application wide set locale. You can of course use the get/setLocale
             accessors to change the used locale or give it while creating a instance of this
@@ -189,14 +189,14 @@ if ($validator->isValid($iban)) {
     <sect2 id="zend.validate.set.ip">
         <title>Ip</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is a valid IP address.
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is a valid IP address.
         </para>
     </sect2>
 
     <sect2 id="zend.validate.set.less_than">
         <title>LessThan</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is less than the maximum
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is less than the maximum
             boundary.
         </para>
     </sect2>
@@ -204,14 +204,14 @@ if ($validator->isValid($iban)) {
     <sect2 id="zend.validate.set.not_empty">
         <title>NotEmpty</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> is not an empty value.
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> is not an empty value.
         </para>
     </sect2>
 
     <sect2 id="zend.validate.set.regex">
         <title>Regex</title>
         <para>
-            Returns <code>true</code> if and only if <code>$value</code> matches against a regular
+            Returns <constant>TRUE</constant> if and only if <code>$value</code> matches against a regular
             expression pattern.
         </para>
     </sect2>
@@ -221,7 +221,7 @@ if ($validator->isValid($iban)) {
     <sect2 id="zend.validate.set.string_length">
         <title>StringLength</title>
         <para>
-            Returns <code>true</code> if and only if the string length of <code>$value</code> is at
+            Returns <constant>TRUE</constant> if and only if the string length of <code>$value</code> is at
             least a minimum and no greater than a maximum (when the max option is not
             <code>null</code>). The <code>setMin()</code> method throws an exception if the minimum
             length is set to a value greater than the set maximum length, and the

documentation/manual/en/module_specs/Zend_Validate-Sitemap.xml

@@ -17,7 +17,7 @@
             'hourly', 'daily', 'weekly', 'monthly', 'yearly', or 'never'.
         </para>
         <para>
-            Returns <code>true</code> if and only if the value is a string
+            Returns <constant>TRUE</constant> if and only if the value is a string
             and is equal to one of the frequencies specified above.
         </para>
     </sect3>
@@ -32,7 +32,7 @@
             about time.
         </para>
         <para>
-            Returns <code>true</code> if and only if the given value is
+            Returns <constant>TRUE</constant> if and only if the given value is
             a string and is valid according to the protocol.
         </para>
 

documentation/manual/en/module_specs/Zend_Validate-ValidatorChains.xml

@@ -40,7 +40,7 @@ if ($validatorChain->isValid($username)) {
         In some cases it makes sense to have a validator break the chain if its validation process
         fails. <classname>Zend_Validate</classname> supports such use cases with the second
         parameter to the <code>addValidator()</code> method. By setting
-        <code>$breakChainOnFailure</code> to <code>true</code>, the added validator will break the
+        <code>$breakChainOnFailure</code> to <constant>TRUE</constant>, the added validator will break the
         chain execution upon failure, which avoids running any other validations that are determined
         to be unnecessary or inappropriate for the situation. If the above example were written as
         follows, then the alphanumeric validation would not occur if the string length validation

documentation/manual/en/module_specs/Zend_Validate-WritingValidators.xml

@@ -37,7 +37,7 @@
         message variables and message templates that correspond to the types of validation failures
         that can occur. If a value fails your validation tests, then <code>isValid()</code> should
         return <constant>FALSE</constant>. If the value passes your validation tests, then
-        <code>isValid()</code> should return <code>true</code>.
+        <code>isValid()</code> should return <constant>TRUE</constant>.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Validate.xml

@@ -43,7 +43,7 @@
             <classname>Zend_Validate_Interface</classname>, which defines two methods,
             <code>isValid()</code> and <code>getMessages()</code>. The
             <code>isValid()</code> method performs validation upon the provided
-            value, returning <code>true</code> if and only if the value passes
+            value, returning <constant>TRUE</constant> if and only if the value passes
             against the validation criteria.
         </para>
 

documentation/manual/en/module_specs/Zend_View-Helpers-Json.xml

@@ -43,9 +43,9 @@ Content-Type: application/json
 
         <para>
             To keep layouts, the second parameter needs to be boolean
-            <code>true</code>. When the second parameter is an array, keeping
+            <constant>TRUE</constant>. When the second parameter is an array, keeping
             layouts can be achieved by including a <code>keepLayouts</code> key
-            with a value of a boolean <code>true</code>.
+            with a value of a boolean <constant>TRUE</constant>.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -60,7 +60,7 @@ echo $this->json($this->data, array('keepLayouts' => true));
             <classname>Zend_Json::encode</classname> allows the encoding of native JSON
             expressions using <classname>Zend_Json_Expr</classname> objects. This option
             is disabled by default. To enable this option, pass a boolean
-            <code>true</code> to the <code>enableJsonExprFinder</code> key of
+            <constant>TRUE</constant> to the <code>enableJsonExprFinder</code> key of
             the options array:
         </para>
 

documentation/manual/en/module_specs/Zend_View-Helpers-Navigation.xml

@@ -1889,7 +1889,7 @@ foreach ($this->container as $page) {
                 <para>
                     <code>{get|set}UseXmlDeclaration()</code> gets/sets a
                     flag indicating whether the XML declaration should be
-                    included when rendering. Default is <code>true</code>.
+                    included when rendering. Default is <constant>TRUE</constant>.
                 </para>
            </listitem>
            <listitem>
@@ -1897,7 +1897,7 @@ foreach ($this->container as $page) {
                     <code>{get|set}UseSitemapValidators()</code> gets/sets a
                     flag indicating whether sitemap validators should be
                     used when generating the DOM sitemap. Default is
-                    <code>true</code>.
+                    <constant>TRUE</constant>.
                 </para>
            </listitem>
            <listitem>
@@ -1905,7 +1905,7 @@ foreach ($this->container as $page) {
                     <code>{get|set}UseSchemaValidation()</code> gets/sets a
                     flag indicating whether the helper should use XML Schema
                     validation when generating the DOM sitemap. Default is
-                    <constant>FALSE</constant>. If <code>true</code>.
+                    <constant>FALSE</constant>. If <constant>TRUE</constant>.
                 </para>
            </listitem>
            <listitem>
@@ -2177,21 +2177,21 @@ echo $this->navigation()
                <para>
                    <code>{get|set}InjectContainer()</code> gets/sets a flag
                    indicating whether the container should be injected to
-                   proxied helpers. Default is <code>true</code>.
+                   proxied helpers. Default is <constant>TRUE</constant>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <code>{get|set}InjectAcl()</code> gets/sets a flag
                    indicating whether the ACL/role should be injected to
-                   proxied helpers. Default is <code>true</code>.
+                   proxied helpers. Default is <constant>TRUE</constant>.
                </para>
            </listitem>
            <listitem>
                <para>
                    <code>{get|set}InjectTranslator()</code> gets/sets a flag
                    indicating whether the translator should be injected to
-                   proxied helpers. Default is <code>true</code>.
+                   proxied helpers. Default is <constant>TRUE</constant>.
                </para>
            </listitem>
            <listitem>