[MANUAL] English:

- structural fixes (no translations needed)

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

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

@@ -1,11 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.memory.memory-objects">
-
     <title>Memory Objects</title>
 
     <sect2 id="zend.memory.memory-objects.movable">
-
         <title>Movable</title>
 
         <para>
@@ -20,11 +18,9 @@ $memObject = $memoryManager->create($data);
             "Movable" means that such objects may be swapped and unloaded from
             memory and then loaded when application code accesses the object.
         </para>
-
     </sect2>
 
     <sect2 id="zend.memory.memory-objects.locked">
-
         <title>Locked</title>
 
         <para>
@@ -61,16 +57,15 @@ $memObject = $memoryManager->createLocked($data);
             guarantees virtually the same performance as working with a string
             variable. The overhead is a single dereference to get the class property.
         </para>
-
     </sect2>
 
     <sect2 id="zend.memory.memory-objects.value">
-
         <title>Memory container 'value' property</title>
 
         <para>
             Use the memory container (movable or locked) '<code>value</code>'
             property to operate with memory object data:
+
             <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->create($data);
 
@@ -87,8 +82,8 @@ $memObject->value = substr($memObject->value, $start, $length);
         </para>
 
         <para>
-            An alternative way to access memory object data is to use the
-            <link linkend="zend.memory.memory-objects.api.getRef"><methodname>getRef()</methodname></link>
+            An alternative way to access memory object data is to use the <link
+                linkend="zend.memory.memory-objects.api.getRef"><methodname>getRef()</methodname></link>
             method. This method <emphasis>must</emphasis> be used for <acronym>PHP</acronym>
             versions before 5.2. It also may have to be used in some other
             cases for performance reasons.
@@ -96,7 +91,6 @@ $memObject->value = substr($memObject->value, $start, $length);
     </sect2>
 
     <sect2 id="zend.memory.memory-objects.api">
-
         <title>Memory container interface</title>
 
         <para>
@@ -104,7 +98,6 @@ $memObject->value = substr($memObject->value, $start, $length);
         </para>
 
         <sect3 id="zend.memory.memory-objects.api.getRef">
-
             <title>getRef() method</title>
 
             <programlisting language="php"><![CDATA[
@@ -134,6 +127,7 @@ public function &getRef();
                 which is changed directly by user application.
                 So, it's a good idea to use the <methodname>getRef()</methodname> method
                 for value data processing:
+
                 <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->create($data);
 
@@ -145,19 +139,19 @@ for ($count = 0; $count < strlen($value); $count++) {
 }
 ]]></programlisting>
             </para>
-
         </sect3>
 
         <sect3 id="zend.memory.memory-objects.api.touch">
-
             <title>touch() method</title>
 
             <programlisting language="php"><![CDATA[
 public function touch();
 ]]></programlisting>
+
             <para>
                 The <methodname>touch()</methodname> method should be used in common with
                 <methodname>getRef()</methodname>. It signals that object value has been changed:
+
                 <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->create($data);
 ...
@@ -174,13 +168,10 @@ for ($count = 0; $count < strlen($value); $count++) {
 
 $memObject->touch();
 ]]></programlisting>
-
             </para>
-
         </sect3>
 
         <sect3 id="zend.memory.memory-objects.api.lock">
-
             <title>lock() method</title>
 
             <programlisting language="php"><![CDATA[
@@ -200,6 +191,7 @@ public function lock();
                 Locking objects in memory also guarantees that reference
                 returned by the <methodname>getRef()</methodname> method is valid until you
                 unlock the object:
+
                 <programlisting language="php"><![CDATA[
 $memObject1 = $memoryManager->create($data1);
 $memObject2 = $memoryManager->create($data2);
@@ -220,11 +212,9 @@ $memObject1->unlock();
 $memObject2->unlock();
 ]]></programlisting>
             </para>
-
         </sect3>
 
         <sect3 id="zend.memory.memory-objects.api.unlock">
-
             <title>unlock() method</title>
 
             <programlisting language="php"><![CDATA[
@@ -235,11 +225,9 @@ public function unlock();
                 <methodname>unlock()</methodname> method unlocks object when it's no longer
                 necessary to be locked. See the example above.
             </para>
-
         </sect3>
 
         <sect3 id="zend.memory.memory-objects.api.isLocked">
-
             <title>isLocked() method</title>
 
             <programlisting language="php"><![CDATA[
@@ -254,9 +242,6 @@ public function isLocked();
                 and may be either <constant>TRUE</constant> or <constant>FALSE</constant>
                 for "movable" objects.
             </para>
-
         </sect3>
-
     </sect2>
-
 </sect1>

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

@@ -1,14 +1,13 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect2 id="zend.validate.set.hostname">
-
     <title>Hostname</title>
 
     <para>
-        <classname>Zend_Validate_Hostname</classname> allows you to validate a hostname against a set of known
-        specifications. It is possible to check for three different types of hostnames: a DNS
-        Hostname (i.e. domain.com), IP address (i.e. 1.2.3.4), and Local hostnames (i.e. localhost).
-        By default only DNS hostnames are matched.
+        <classname>Zend_Validate_Hostname</classname> allows you to validate a hostname against a
+        set of known specifications. It is possible to check for three different types of hostnames:
+        a DNS Hostname (i.e. domain.com), IP address (i.e. 1.2.3.4), and Local hostnames (i.e.
+        localhost). By default only DNS hostnames are matched.
     </para>
 
     <para>
@@ -32,7 +31,6 @@ if ($validator->isValid($hostname)) {
 
         This will match the hostname <varname>$hostname</varname> and on failure populate
         <methodname>getMessages()</methodname> with useful error messages.
-
     </para>
 
     <para>
@@ -41,16 +39,19 @@ if ($validator->isValid($hostname)) {
 
     <para>
         You may find you also want to match IP addresses, Local hostnames, or a combination of all
-        allowed types. This can be done by passing a parameter to <classname>Zend_Validate_Hostname</classname> when you
-        instantiate it. The parameter should be an integer which determines what types of hostnames
-        are allowed. You are encouraged to use the <classname>Zend_Validate_Hostname</classname> constants to do this.
+        allowed types. This can be done by passing a parameter to
+        <classname>Zend_Validate_Hostname</classname> when you instantiate it. The parameter should
+        be an integer which determines what types of hostnames are allowed. You are encouraged to
+        use the <classname>Zend_Validate_Hostname</classname> constants to do this.
     </para>
 
     <para>
         The Zend_Validate_Hostname constants are: <constant>ALLOW_DNS</constant> to allow only DNS
-        hostnames, <constant>ALLOW_IP</constant> to allow IP addresses, <constant>ALLOW_LOCAL</constant> to allow
-        local network names, and <constant>ALLOW_ALL</constant> to allow all three types. To just check for
-        IP addresses you can use the example below:
+        hostnames, <constant>ALLOW_IP</constant> to allow IP addresses,
+        <constant>ALLOW_LOCAL</constant> to allow local network names, and
+        <constant>ALLOW_ALL</constant> to allow all three types. To just check for IP addresses you
+        can use the example below:
+
         <programlisting language="php"><![CDATA[
 $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_IP);
 if ($validator->isValid($hostname)) {
@@ -65,14 +66,14 @@ if ($validator->isValid($hostname)) {
     </para>
 
     <para>
-        As well as using <constant>ALLOW_ALL</constant> to accept all hostnames types you can combine
-        these types to allow for combinations. For example, to accept DNS and Local hostnames
-        instantiate your Zend_Validate_Hostname object as so:
+        As well as using <constant>ALLOW_ALL</constant> to accept all hostnames types you can
+        combine these types to allow for combinations. For example, to accept DNS and Local
+        hostnames instantiate your Zend_Validate_Hostname object as so:
+
         <programlisting language="php"><![CDATA[
 $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_DNS |
                                         Zend_Validate_Hostname::ALLOW_IP);
 ]]></programlisting>
-
     </para>
 
     <para>
@@ -82,8 +83,8 @@ $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_DNS |
     <para>
         Some Country Code Top Level Domains (ccTLDs), such as 'de' (Germany), support international
         characters in domain names. These are known as International Domain Names (IDN). These
-        domains can be matched by <classname>Zend_Validate_Hostname</classname> via extended characters that are used in
-        the validation process.
+        domains can be matched by <classname>Zend_Validate_Hostname</classname> via extended
+        characters that are used in the validation process.
     </para>
 
     <para>
@@ -151,7 +152,6 @@ $validator =
     <para>
         Please note TLDs are only validated if you allow DNS hostnames to be validated.
     </para>
-
 </sect2>
 <!--
 vim:se ts=4 sw=4 et:

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

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect2 id="zend.validate.set.identical">
-
     <title>Identical</title>
 
     <para>

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

@@ -180,7 +180,6 @@ if ($validator->isValid('value')) {
             </para>
         </note>
     </sect3>
-
 </sect2>
 <!--
 vim:se ts=4 sw=4 et:

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

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect2 id="zend.validate.set.ip">
-
     <title>Ip</title>
 
     <para>

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

@@ -112,15 +112,9 @@ if ($validator->isValid($isbn)) {
         </para>
 
         <itemizedlist>
-            <listitem>
-                <para>"" (empty) (default)</para>
-            </listitem>
-            <listitem>
-                <para>"-" (hyphen)</para>
-            </listitem>
-            <listitem>
-                <para>" " (space)</para>
-            </listitem>
+            <listitem><para>"" (empty) (default)</para></listitem>
+            <listitem><para>"-" (hyphen)</para></listitem>
+            <listitem><para>" " (space)</para></listitem>
         </itemizedlist>
     </sect3>
 </sect2>

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

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect2 id="zend.validate.set.post_code">
-
     <title>PostCode</title>
 
     <para>

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

@@ -17,6 +17,7 @@
             element in a Sitemap <acronym>XML</acronym> document. Valid values are: 'always',
             'hourly', 'daily', 'weekly', 'monthly', 'yearly', or 'never'.
         </para>
+
         <para>
             Returns <constant>TRUE</constant> if and only if the value is a string
             and is equal to one of the frequencies specified above.
@@ -32,6 +33,7 @@
             contain a <acronym>W3C</acronym> date string, optionally discarding information
             about time.
         </para>
+
         <para>
             Returns <constant>TRUE</constant> if and only if the given value is
             a string and is valid according to the protocol.
@@ -97,4 +99,4 @@ $validator->isValid('foo'); // false
 ]]></programlisting>
         </example>
     </sect3>
-</sect2>
+</sect2>

documentation/manual/en/module_specs/Zend_Version.xml

@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect1 id="zend.version.reading">
-
     <title>Getting the Zend Framework Version</title>
 
     <para>
@@ -23,12 +22,12 @@
 
     <example id="zend.version.reading.example">
         <title>Example of the compareVersion() Method</title>
+
         <programlisting language="php"><![CDATA[
 // returns -1, 0 or 1
 $cmp = Zend_Version::compareVersion('2.0.0');
 ]]></programlisting>
     </example>
-
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:

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

@@ -1,15 +1,13 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
 <sect3 id="zend.view.helpers.initial.cycle">
-
     <title>Cycle Helper</title>
 
     <para>
-      The <classname>Cycle</classname> helper is used to alternate a set of values.
+        The <classname>Cycle</classname> helper is used to alternate a set of values.
     </para>
 
     <example id="zend.view.helpers.initial.cycle.basicusage">
-
         <title>Cycle Helper Basic Usage</title>
 
         <para>
@@ -44,11 +42,9 @@ $this->cycle()->prev();
    <td>Second</td>
 </tr>
 ]]></programlisting>
-
     </example>
 
     <example id="zend.view.helpers.initial.cycle.advanceusage">
-
         <title>Working with two or more cycles</title>
 
        <para>
@@ -56,7 +52,6 @@ $this->cycle()->prev();
            cycle method. <command>$this->cycle(array("#F0F0F0","#FFFFFF"),'cycle2')</command>. You
            can also use setName($name) function.
         </para>
-
     </example>
 
     <programlisting language="php"><![CDATA[
@@ -69,7 +64,6 @@ $this->cycle()->prev();
 </tr>
 <?php endforeach;?>
 ]]></programlisting>
-
 </sect3>
 <!--
 vim:se ts=4 sw=4 et:

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

@@ -34,8 +34,7 @@
 
     <para>
         The <classname>Doctype</classname> helper is a concrete implementation of the
-        <link linkend="zend.view.helpers.initial.placeholder">Placeholder
-            helper</link>.
+        <link linkend="zend.view.helpers.initial.placeholder">Placeholder helper</link>.
     </para>
 
     <example id="zend.view.helpers.initial.doctype.basicusage">
@@ -60,7 +59,6 @@ $doctypeHelper->doctype('XHTML1_STRICT');
         <programlisting language="php"><![CDATA[
 <?php echo $this->doctype() ?>
 ]]></programlisting>
-
     </example>
 
     <example id="zend.view.helpers.initial.doctype.retrieving">

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

@@ -103,8 +103,7 @@
 
     <para>
         The <classname>HeadMeta</classname> helper is a concrete implementation of the
-        <link linkend="zend.view.helpers.initial.placeholder">Placeholder
-            helper</link>.
+        <link linkend="zend.view.helpers.initial.placeholder">Placeholder helper</link>.
     </para>
 
     <example id="zend.view.helpers.initial.headmeta.basicusage">
@@ -152,8 +151,7 @@ $this->headMeta()->appendHttpEquiv('Content-Type',
 ]]></programlisting>
 
         <para>
-            If you are serving an HTML5 document, you should provide the character
-            set like this:
+            If you are serving an HTML5 document, you should provide the character set like this:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -173,8 +171,7 @@ $this->headMeta()->appendHttpEquiv('Refresh',
 ]]></programlisting>
 
         <para>
-            When you're ready to place your meta tags in the layout, simply echo
-            the helper:
+            When you're ready to place your meta tags in the layout, simply echo the helper:
         </para>
 
         <programlisting language="php"><![CDATA[

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

@@ -129,8 +129,7 @@ $this->headScript()->appendFile(
 
     <para>
         The <classname>HeadScript</classname> helper is a concrete implementation of the
-        <link linkend="zend.view.helpers.initial.placeholder">Placeholder
-            helper</link>.
+        <link linkend="zend.view.helpers.initial.placeholder">Placeholder helper</link>.
     </para>
 
     <note>
@@ -232,24 +231,30 @@ $('foo_form').action = action;
         </para>
 
         <itemizedlist>
-            <listitem><para>
+            <listitem>
+                <para>
                     The script will be appended to the stack. If you wish for it
                     to replace the stack or be added to the top, you will need
                     to pass 'SET' or 'PREPEND', respectively, as the first
                     argument to <methodname>captureStart()</methodname>.
-            </para></listitem>
+                </para>
+            </listitem>
 
-            <listitem><para>
+            <listitem>
+                <para>
                     The script <acronym>MIME</acronym> type is assumed to be 'text/javascript'; if
                     you wish to specify a different type, you will need to pass it
                     as the second argument to <methodname>captureStart()</methodname>.
-            </para></listitem>
+                </para>
+            </listitem>
 
-            <listitem><para>
+            <listitem>
+                <para>
                     If you wish to specify any additional attributes for the
                     <emphasis>&lt;script&gt;</emphasis> tag, pass them in an array as
                     the third argument to <methodname>captureStart()</methodname>.
-            </para></listitem>
+                </para>
+            </listitem>
         </itemizedlist>
     </example>
 </sect3>

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

@@ -69,6 +69,7 @@
 
         <example id="zend.view.helpers.initial.headstyle.conditional">
             <title>Headstyle With Conditional Comments</title>
+
             <programlisting language="php"><![CDATA[
 // adding scripts
 $this->headStyle()->appendStyle($styles, array('conditional' => 'lt IE 7'));
@@ -194,18 +195,22 @@ body {
         </para>
 
         <itemizedlist>
-            <listitem><para>
+            <listitem>
+                <para>
                     The style declarations will be appended to the stack. If you
                     wish for them to replace the stack or be added to the top,
                     you will need to pass 'SET' or 'PREPEND', respectively, as
                     the first argument to <methodname>captureStart()</methodname>.
-            </para></listitem>
+                </para>
+            </listitem>
 
-            <listitem><para>
+            <listitem>
+                <para>
                     If you wish to specify any additional attributes for the
                     <emphasis>&lt;style&gt;</emphasis> tag, pass them in an array as
                     the second argument to <methodname>captureStart()</methodname>.
-            </para></listitem>
+                </para>
+            </listitem>
         </itemizedlist>
     </example>
 </sect3>

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

@@ -21,18 +21,21 @@
                 Generates markup for embedding Flash files.
             </para>
         </listitem>
+
         <listitem>
             <para>
                 <methodname>htmlObject()</methodname>
                 Generates markup for embedding a custom Object.
             </para>
         </listitem>
+
         <listitem>
             <para>
                 <methodname>htmlPage()</methodname>
                 Generates markup for embedding other (X)HTML pages.
             </para>
         </listitem>
+
         <listitem>
             <para>
                 <methodname>htmlQuicktime()</methodname>
@@ -47,7 +50,6 @@
     </para>
 
     <example id="zend.view.helpers.initial.object.flash">
-
         <title>Flash helper</title>
 
         <para>
@@ -70,7 +72,6 @@
         codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab">
 </object>
 ]]></programlisting>
-
     </example>
 
     <para>

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

@@ -19,13 +19,13 @@
 
     <note>
         <title>PartialLoop Counter</title>
+
         <para>
             The <classname>PartialLoop</classname> view helper assigns a variable to the view named
             <emphasis>partialCounter</emphasis> which passes the current position of the array to
             the view script. This provides an easy way to have alternating colors on table rows for
             example.
         </para>
-
     </note>
 
     <example id="zend.view.helpers.initial.partial.usage">
@@ -64,47 +64,52 @@
     <li>Subject: view partials</li>
 </ul>
 ]]></programlisting>
-
     </example>
-        <note>
-            <title>What is a model?</title>
-
-            <para>
-                A model used with the <classname>Partial</classname> view helper can be
-                one of the following:
-            </para>
-
-            <itemizedlist>
-                <listitem><para>
-                        <emphasis>Array</emphasis>. If an array is passed, it
-                        should be associative, as its key/value pairs are
-                        assigned to the view with keys as view variables.
-                </para></listitem>
-
-                <listitem><para>
-                        <emphasis>Object implementing toArray()
-                            method</emphasis>. If an object is passed an has a
-                        <methodname>toArray()</methodname> method, the results of
-                        <methodname>toArray()</methodname> will be assigned to the view
-                        object as view variables.
-                </para></listitem>
-
-                <listitem><para>
-                        <emphasis>Standard object</emphasis>. Any other object
-                        will assign the results of
-                        <methodname>object_get_vars()</methodname> (essentially all public
-                        properties of the object) to the view object.
-                </para></listitem>
-            </itemizedlist>
-
-            <para>
-                If your model is an object, you may want to have it passed
-                <emphasis>as an object</emphasis> to the partial script, instead
-                of serializing it to an array of variables. You can do this by
-                setting the 'objectKey' property of the appropriate helper:
-            </para>
-
-            <programlisting language="php"><![CDATA[
+
+    <note>
+        <title>What is a model?</title>
+
+        <para>
+            A model used with the <classname>Partial</classname> view helper can be
+            one of the following:
+        </para>
+
+        <itemizedlist>
+            <listitem>
+                <para>
+                    <emphasis>Array</emphasis>. If an array is passed, it
+                    should be associative, as its key/value pairs are
+                    assigned to the view with keys as view variables.
+                </para>
+            </listitem>
+
+            <listitem>
+                <para>
+                    <emphasis>Object implementing toArray() method</emphasis>. If an object is
+                    passed an has a <methodname>toArray()</methodname> method, the results of
+                    <methodname>toArray()</methodname> will be assigned to the view
+                    object as view variables.
+                </para>
+            </listitem>
+
+            <listitem>
+                <para>
+                    <emphasis>Standard object</emphasis>. Any other object
+                    will assign the results of
+                    <methodname>object_get_vars()</methodname> (essentially all public
+                    properties of the object) to the view object.
+                </para>
+            </listitem>
+        </itemizedlist>
+
+        <para>
+            If your model is an object, you may want to have it passed
+            <emphasis>as an object</emphasis> to the partial script, instead
+            of serializing it to an array of variables. You can do this by
+            setting the 'objectKey' property of the appropriate helper:
+        </para>
+
+        <programlisting language="php"><![CDATA[
 // Tell partial to pass objects as 'model' variable
 $view->partial()->setObjectKey('model');
 
@@ -113,15 +118,15 @@ $view->partial()->setObjectKey('model');
 $view->partialLoop()->setObjectKey('model');
 ]]></programlisting>
 
-            <para>
-                This technique is particularly useful when passing
-                <classname>Zend_Db_Table_Rowset</classname>s to
-                <methodname>partialLoop()</methodname>, as you then have full access to your
-                row objects within the view scripts, allowing you to call
-                methods on them (such as retrieving values from parent or
-                dependent rows).
-            </para>
-        </note>
+        <para>
+            This technique is particularly useful when passing
+            <classname>Zend_Db_Table_Rowset</classname>s to
+            <methodname>partialLoop()</methodname>, as you then have full access to your
+            row objects within the view scripts, allowing you to call
+            methods on them (such as retrieving values from parent or
+            dependent rows).
+        </para>
+    </note>
 
     <example id="zend.view.helpers.initial.partial.partialloop">
         <title>Using PartialLoop to Render Iterable Models</title>

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

@@ -23,6 +23,7 @@
 
     <note>
         <title>Watch the Case</title>
+
         <para>
             Helper names are always camelCased, i.e., they never begin with an
             uppercase character. The class name itself is MixedCased, but the

documentation/manual/en/module_specs/Zend_Wildfire.xml

@@ -16,22 +16,23 @@
         <acronym>PHP</acronym> code to inject logging messages into the
         <ulink url="http://www.getfirebug.com/">Firebug Console</ulink>.
   </para>
-  <para>
-    The
-    <link linkend="zend.log.writers.firebug"><classname>Zend_Log_Writer_Firebug</classname></link>
-    component is provided for the purpose of logging to Firebug, and a communication protocol has
-    been developed that uses <acronym>HTTP</acronym> request and response headers to send data
-    between the server and client components. It is great for logging intelligence data to the
-    browser that is generated during script execution, without interfering with the page content.
-    With this approach, it is possible to debug <acronym>AJAX</acronym> requests that require clean
-    <acronym>JSON</acronym> and <acronym>XML</acronym> responses.
-  </para>
-  <para>
-    There is also a <link linkend="zend.db.profiler.profilers.firebug">
-        <classname>Zend_Db_Profiler_Firebug</classname></link> component to log database profiling
-    information to Firebug.
-  </para>
 
+    <para>
+        The <link
+            linkend="zend.log.writers.firebug"><classname>Zend_Log_Writer_Firebug</classname></link>
+        component is provided for the purpose of logging to Firebug, and a communication protocol has
+        been developed that uses <acronym>HTTP</acronym> request and response headers to send data
+        between the server and client components. It is great for logging intelligence data to the
+        browser that is generated during script execution, without interfering with the page content.
+        With this approach, it is possible to debug <acronym>AJAX</acronym> requests that require clean
+        <acronym>JSON</acronym> and <acronym>XML</acronym> responses.
+    </para>
+
+    <para>
+        There is also a <link
+            linkend="zend.db.profiler.profilers.firebug"><classname>Zend_Db_Profiler_Firebug</classname></link>
+        component to log database profiling information to Firebug.
+    </para>
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:

documentation/manual/en/module_specs/Zend_XmlRpc_Client.xml

@@ -13,7 +13,6 @@
             between <acronym>PHP</acronym> and <acronym>XML-RPC</acronym>, a server proxy object,
             and access to server introspection capabilities.
         </para>
-
     </sect2>
 
     <sect2 id="zend.xmlrpc.client.method-calls">
@@ -36,6 +35,7 @@
 
         <example id="zend.xmlrpc.client.method-calls.example-1">
             <title>XML-RPC Method Call</title>
+
             <programlisting language="php"><![CDATA[
 $client = new Zend_XmlRpc_Client('http://framework.zend.com/xmlrpc');
 
@@ -62,6 +62,7 @@ echo $client->call('test.sayHello');
 
         <example id="zend.xmlrpc.client.method-calls.example-2">
             <title>XML-RPC Method Call with Parameters</title>
+
             <programlisting language="php"><![CDATA[
 $client = new Zend_XmlRpc_Client('http://framework.zend.com/xmlrpc');
 
@@ -93,6 +94,7 @@ $result = $client->call('test.sayHello', array($arg1, $arg2));
 
     <sect2 id="zend.xmlrpc.value.parameters">
         <title>Types and Conversions</title>
+
         <para>
             Some remote method calls require parameters. These are given to
             the <methodname>call()</methodname> method of <classname>Zend_XmlRpc_Client</classname>
@@ -104,6 +106,7 @@ $result = $client->call('test.sayHello', array($arg1, $arg2));
 
         <sect3 id="zend.xmlrpc.value.parameters.php-native">
             <title>PHP Native Types as Parameters</title>
+
             <para>
                 Parameters may be passed to <methodname>call()</methodname> as native
                 <acronym>PHP</acronym> variables, meaning as a <type>String</type>,
@@ -116,6 +119,7 @@ $result = $client->call('test.sayHello', array($arg1, $arg2));
 
             <table id="zend.xmlrpc.value.parameters.php-native.table-1">
                 <title>PHP and XML-RPC Type Conversions</title>
+
                 <tgroup cols="2">
                     <thead>
                         <row>
@@ -123,47 +127,58 @@ $result = $client->call('test.sayHello', array($arg1, $arg2));
                             <entry><acronym>XML-RPC</acronym> Type</entry>
                         </row>
                     </thead>
+
                     <tbody>
                         <row>
                             <entry>integer</entry>
                             <entry>int</entry>
                         </row>
+
                         <row>
                             <entry>Zend_Crypt_Math_BigInteger</entry>
                             <entry>i8</entry>
                         </row>
+
                         <row>
                             <entry>double</entry>
                             <entry>double</entry>
                         </row>
+
                         <row>
                             <entry>boolean</entry>
                             <entry>boolean</entry>
                         </row>
+
                         <row>
                             <entry>string</entry>
                             <entry>string</entry>
                         </row>
+
                         <row>
                             <entry>null</entry>
                             <entry>nil</entry>
                         </row>
+
                         <row>
                             <entry>array</entry>
                             <entry>array</entry>
                         </row>
+
                         <row>
                             <entry>associative array</entry>
                             <entry>struct</entry>
                         </row>
+
                         <row>
                             <entry>object</entry>
                             <entry>array</entry>
                         </row>
+
                         <row>
                             <entry>Zend_Date</entry>
                             <entry>dateTime.iso8601</entry>
                         </row>
+
                         <row>
                             <entry>DateTime</entry>
                             <entry>dateTime.iso8601</entry>
@@ -209,6 +224,7 @@ $result = $client->call('foo.bar', array(array()));
 
         <sect3 id="zend.xmlrpc.value.parameters.xmlrpc-value">
             <title>Zend_XmlRpc_Value Objects as Parameters</title>
+
             <para>
                 Parameters may also be created as <classname>Zend_XmlRpc_Value</classname>
                 instances to specify an exact <acronym>XML-RPC</acronym> type. The primary reasons
@@ -223,6 +239,7 @@ $result = $client->call('foo.bar', array(array()));
                             from a database as a string)
                         </para>
                     </listitem>
+
                     <listitem>
                         <para>
                             When the procedure requires <property>base64</property> or
@@ -230,6 +247,7 @@ $result = $client->call('foo.bar', array(array()));
                             <acronym>PHP</acronym> native type)
                         </para>
                     </listitem>
+
                     <listitem>
                         <para>
                             When auto-conversion may fail (i.e. you want to
@@ -252,6 +270,7 @@ $result = $client->call('foo.bar', array(array()));
 
             <table id="zend.xmlrpc.value.parameters.xmlrpc-value.table-1">
                 <title>Zend_XmlRpc_Value Objects for XML-RPC Types</title>
+
                 <tgroup cols="3">
                     <thead>
                         <row>
@@ -260,89 +279,125 @@ $result = $client->call('foo.bar', array(array()));
                             <entry><classname>Zend_XmlRpc_Value</classname> Object</entry>
                         </row>
                     </thead>
+
                     <tbody>
                         <row>
                             <entry>int</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_INTEGER</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Integer</classname></entry>
                         </row>
+
                         <row>
                             <entry>i8</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_I8</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_BigInteger</classname></entry>
                         </row>
+
                         <row>
                             <entry>ex:i8</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_APACHEI8</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_BigInteger</classname></entry>
                         </row>
+
                         <row>
                             <entry>double</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_DOUBLE</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Double</classname></entry>
                         </row>
+
                         <row>
                             <entry>boolean</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_BOOLEAN</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Boolean</classname></entry>
                         </row>
+
                         <row>
                             <entry>string</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_STRING</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_String</classname></entry>
                         </row>
+
                         <row>
                             <entry>nil</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_NIL</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Nil</classname></entry>
                         </row>
+
                         <row>
                             <entry>ex:nil</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_APACHENIL</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Nil</classname></entry>
                         </row>
+
                         <row>
                             <entry>base64</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_BASE64</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Base64</classname></entry>
                         </row>
+
                         <row>
                             <entry>dateTime.iso8601</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_DATETIME</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_DateTime</classname></entry>
                         </row>
+
                         <row>
                             <entry>array</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_ARRAY</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Array</classname></entry>
                         </row>
+
                         <row>
                             <entry>struct</entry>
+
                             <entry>
                                 <constant>Zend_XmlRpc_Value::XMLRPC_TYPE_STRUCT</constant>
                             </entry>
+
                             <entry><classname>Zend_XmlRpc_Value_Struct</classname></entry>
                         </row>
                     </tbody>
@@ -352,6 +407,7 @@ $result = $client->call('foo.bar', array(array()));
             <para>
                 <note>
                     <title>Automatic Conversion</title>
+
                     <para>
                         When building a new <classname>Zend_XmlRpc_Value</classname>
                         object, its value is set by a <acronym>PHP</acronym> type. The
@@ -368,6 +424,7 @@ $result = $client->call('foo.bar', array(array()));
 
     <sect2 id="zend.xmlrpc.client.requests-and-responses">
         <title>Server Proxy Object</title>
+
         <para>
             Another way to call remote methods with the <acronym>XML-RPC</acronym> client is to
             use the server proxy. This is a <acronym>PHP</acronym> object that proxies a remote
@@ -386,6 +443,7 @@ $result = $client->call('foo.bar', array(array()));
 
         <example id="zend.xmlrpc.client.requests-and-responses.example-1">
             <title>Proxy the Default Namespace</title>
+
             <programlisting language="php"><![CDATA[
 $client = new Zend_XmlRpc_Client('http://framework.zend.com/xmlrpc');
 
@@ -405,6 +463,7 @@ $hello = $service->test->sayHello(1, 2);  // test.Hello(1, 2) returns "hello"
 
         <example id="zend.xmlrpc.client.requests-and-responses.example-2">
             <title>Proxy Any Namespace</title>
+
             <programlisting language="php"><![CDATA[
 $client = new Zend_XmlRpc_Client('http://framework.zend.com/xmlrpc');
 
@@ -425,6 +484,7 @@ $hello = $test->sayHello(1, 2);         // test.Hello(1,2) returns "hello"
 
     <sect2 id="zend.xmlrpc.client.error-handling">
         <title>Error Handling</title>
+
         <para>
             Two kinds of errors can occur during an <acronym>XML-RPC</acronym> method call:
             <acronym>HTTP</acronym> errors and <acronym>XML-RPC</acronym> faults. The
@@ -523,11 +583,11 @@ try {
                 <classname>Zend_XmlRpc_Response</classname>.
             </para>
         </sect3>
-
     </sect2>
 
     <sect2 id="zend.xmlrpc.client.introspection">
         <title>Server Introspection</title>
+
         <para>
             Some <acronym>XML-RPC</acronym> servers support the de facto introspection methods
             under the <acronym>XML-RPC</acronym> <emphasis>system.</emphasis> namespace.
@@ -545,6 +605,7 @@ try {
 
     <sect2 id="zend.xmlrpc.client.request-to-response">
         <title>From Request to Response</title>
+
         <para>
             Under the hood, the <methodname>call()</methodname> instance method of
             <classname>Zend_XmlRpc_Client</classname> builds a request object
@@ -609,7 +670,6 @@ $client->doRequest($request);
             <classname>Zend_XmlRpc_Client</classname> for examples of how to do this.
         </para>
     </sect2>
-
 </sect1>
 <!--
 vim:se ts=4 sw=4 et: