[DOCUMENTATION] English:

 - manual fixes => only spaces (NO TRANSLATION NEEDED)

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

documentation/manual/en/module_specs/Zend_Filter-Compress.xml

@@ -158,7 +158,7 @@ $compressed = $filter->filter('Compressed string');
 
         <programlisting language="php"><![CDATA[
 $filter     = new Zend_Filter_Compress(array(
-    'adapter' => 'Bz2', 
+    'adapter' => 'Bz2',
     'options' => array(
         'archive' => 'filename.bz2',
     ),
@@ -187,7 +187,7 @@ $compressed = $filter->filter('Uncompressed string');
 
         <programlisting language="php"><![CDATA[
 $filter     = new Zend_Filter_Compress(array(
-    'adapter' => 'Bz2', 
+    'adapter' => 'Bz2',
     'options' => array(
         'archive' => 'filename.bz2'
     ),
@@ -203,7 +203,7 @@ $compressed = $filter->filter('C:\temp\compressme.txt');
 
         <programlisting language="php"><![CDATA[
 $filter     = new Zend_Filter_Compress(array(
-    'adapter' => 'Bz2', 
+    'adapter' => 'Bz2',
     'options' => array(
         'archive' => 'filename.bz2'
     ),
@@ -246,7 +246,7 @@ $compressed = $filter->filter('filename.bz2');
 
         <programlisting language="php"><![CDATA[
 $filter     = new Zend_Filter_Decompress(array(
-    'adapter' => 'Zip', 
+    'adapter' => 'Zip',
     'options' => array(
         'target' => 'C:\temp',
     )

documentation/manual/en/module_specs/Zend_Filter_Input.xml

@@ -504,7 +504,7 @@ $input->setDefaultEscapeFilter(new Zend_Filter_StringTrim());
 ]]></programlisting>
 
             <para>
-                In either usage, you  can specify the escape filter as a string
+                In either usage, you can specify the escape filter as a string
                 base name of the filter class, or as an object instance of a
                 filter class. The escape filter can be an instance of a filter
                 chain, an object of the class <classname>Zend_Filter</classname>.

documentation/manual/en/module_specs/Zend_Http_Client-Adapters.xml

@@ -552,10 +552,10 @@ $adapter->addResponse(
             and test its behavior.
         </para>
         <para>
-            If you need the adapter to fail on demand you can use 
-            <methodname>setNextRequestWillFail($flag)</methodname>. The method will cause the next 
-            call to <methodname>connect()</methodname> to throw an 
-            <classname>Zend_Http_Client_Adapter_Exception</classname> exception. This can be useful 
+            If you need the adapter to fail on demand you can use
+            <methodname>setNextRequestWillFail($flag)</methodname>. The method will cause the next
+            call to <methodname>connect()</methodname> to throw an
+            <classname>Zend_Http_Client_Adapter_Exception</classname> exception. This can be useful
             when your application caches content from an external site (in case the site goes down)
             and you want to test this feature.
         </para>
@@ -573,9 +573,9 @@ $adapter->nextRequestWillFail(true);
 
 try {
     // This call will result in a Zend_Http_Client_Adapter_Exception
-    $client->request(); 
+    $client->request();
 } catch (Zend_Http_Client_Adapter_Exception $e) {
-    // ... 
+    // ...
 }
 
 // Further requests will work as expected until you call setNextRequestWillFail(true) again

documentation/manual/en/module_specs/Zend_Http_Client-Advanced.xml

@@ -234,8 +234,8 @@ $client->setRawData($xml)->setEncType('text/xml')->request('POST');
         <title>HTTP Authentication</title>
         <para>
             Currently, Zend_Http_Client only supports basic HTTP authentication.
-            This feature is utilized using the <methodname>setAuth()</methodname> 
-            method, or by specifying a username and a password in the URI. The 
+            This feature is utilized using the <methodname>setAuth()</methodname>
+            method, or by specifying a username and a password in the URI. The
             <methodname>setAuth()</methodname> method
             takes 3 parameters: The user name, the password and an optional
             authentication type parameter. As mentioned, currently only basic

documentation/manual/en/module_specs/Zend_Loader-Autoloader.xml

@@ -286,7 +286,7 @@ autoloaderZfVersion = "latest"
             <para>
                 For best performance, either do not use this feature, or specify a specific Zend
                 Framework version (i.e., not "latest", a major revision such as "1", or a minor
-                revision such as "1.8").  Otherwise, the autoloader will need to scan the provided
+                revision such as "1.8"). Otherwise, the autoloader will need to scan the provided
                 path for directories matching the criteria -- a somewhat expensive operation to
                 perform on each request.
             </para>

documentation/manual/en/module_specs/Zend_Service-ReCaptcha.xml

@@ -95,19 +95,19 @@ if (!$result->isValid()) {
             validating the reCAPTCHA are automated for you.
         </para>
     </sect2>
-    
+
     <sect2 id="zend.service.recaptcha.mailhide">
         <title>Hiding email addresses</title>
-        
+
         <para>
-            <classname>Zend_Service_ReCaptcha_MailHide</classname> can be used to hide email 
-            addresses. It will replace a part of an email address with a link that opens a popup 
-            window with a reCAPTCHA challenge. Solving the challenge will reveal the complete 
-            email address. 
+            <classname>Zend_Service_ReCaptcha_MailHide</classname> can be used to hide email
+            addresses. It will replace a part of an email address with a link that opens a popup
+            window with a reCAPTCHA challenge. Solving the challenge will reveal the complete
+            email address.
         </para>
         <para>
-            In order to use this component you will need 
-            <ulink url="http://recaptcha.net/whyrecaptcha.html">an account</ulink> to generate 
+            In order to use this component you will need
+            <ulink url="http://recaptcha.net/whyrecaptcha.html">an account</ulink> to generate
             public and private keys for the mailhide API.
         </para>
         <example id="zend.service.recaptcha.mailhide.example-1">
@@ -128,11 +128,11 @@ print($mailHide);
 ]]></programlisting>
         </example>
         <para>
-            The example above will display "m...@example.com" where "..." has a link that opens up 
+            The example above will display "m...@example.com" where "..." has a link that opens up
             a popup window with a reCAPTCHA challenge.
         </para>
         <para>
-            The public key, private key, and the email address can also be specified in the 
+            The public key, private key, and the email address can also be specified in the
             constructor of the class. A fourth argument also exists that enables you to set some
             options for the component. The available options are listed in the following table:
             <table id="zend.service.recaptcha.mailhide.options.table">
@@ -176,8 +176,8 @@ print($mailHide);
             </table>
         </para>
         <para>
-            The configuration options can be set by sending them as the fourth argument to the 
-            constructor or by calling <methodname>setOptions($options)</methodname>, which takes 
+            The configuration options can be set by sending them as the fourth argument to the
+            constructor or by calling <methodname>setOptions($options)</methodname>, which takes
             an associative array or an instance of <link linkend="zend.config">Zend_Config</link>.
         </para>
         <example id="zend.service.recaptcha.mailhide.example-2">

documentation/manual/en/module_specs/Zend_Service_Twitter.xml

@@ -69,7 +69,7 @@
                     <code>favorite</code> lists, creates, and removes favorite tweets.
                 </para>
             </listitem>
-            
+
             <listitem>
                 <para>
                     <code>block</code> blocks and unblocks users from following you.
@@ -104,7 +104,7 @@ $twitter = new Zend_Service_Twitter('myusername', 'mysecretpassword');
 $response = $twitter->account->verifyCredentials();
 ]]></programlisting>
 
-			<para>
+            <para>
                 You can also pass in an array that contains the username and password as the
                 first argument.
             </para>
@@ -738,7 +738,7 @@ $response   = $twitter->favorite->destroy(12351);
             </listitem>
         </itemizedlist>
     </sect2>
-    
+
     <sect2 id="zend.service.twitter.block">
         <title>Block Methods</title>
 
@@ -801,7 +801,7 @@ $response   = $twitter->block->create('usertoblock);
                 <para>
                     <methodname>destroy()</methodname> un-blocks the user specified in the
                     <code>id</code> parameter for the authenticating user. Returns the un-blocked
-                    user in the requested format when successful. 
+                    user in the requested format when successful.
                 </para>
 
                 <example id="zend.service.twitter.block.destroy">
@@ -813,7 +813,7 @@ $response   = $twitter->block->destroy('blockeduser');
 ]]></programlisting>
                 </example>
             </listitem>
-            
+
             <listitem>
                 <para>
                     <methodname>blocking()</methodname> returns an array of user objects that the

documentation/manual/en/module_specs/Zend_Test-PHPUnit-Bootstrapping.xml

@@ -34,7 +34,7 @@ class UserControllerTest extends Zend_Test_PHPUnit_ControllerTestCase
     {
         // Assign and instantiate in one step:
         $this->bootstrap = new Zend_Application(
-            'testing', 
+            'testing',
             APPLICATION_PATH . '/configs/application.ini'
         );
         parent::setUp();

documentation/manual/en/module_specs/Zend_Tool_Framework-WritingProviders.xml

@@ -17,7 +17,7 @@
             By default Zend Tool uses the IncludePathLoader to find all
             the providers that you can run. It recursivly iterates all
             include path directories and opens all files that end
-            with "Manifest.php" or "Provider.php".  All classes in these
+            with "Manifest.php" or "Provider.php". All classes in these
             files are inspected if they implement either
             <classname>Zend_Tool_Framework_Provider_Interface</classname>
             or <classname>Zend_Tool_Framework_Manifest_ProviderManifestable</classname>.
@@ -165,7 +165,7 @@ class My_Component_HelloProvider
 
         <sect3 id="zend.tool.framework.writing-providers.advanced.variables">
             <title>Passing Variables to a Provider</title>
-            
+
             <para>
                 The above "Hello World" example is great for simple commands, but
                 what about something more advanced? As your scripting and tooling
@@ -295,7 +295,7 @@ I would say hello Ralph.
                 in the context of your provider. You can access debug or verbose modes
                 with:
             </para>
-            
+
             <programlisting language="php"><![CDATA[
 class My_Component_HelloProvider
     implements Zend_Tool_Framework_Provider_Interface

documentation/manual/en/module_specs/Zend_Uri.xml

@@ -7,7 +7,7 @@
         <title>Overview</title>
 
         <para>
-            <classname>Zend_Uri</classname> is a component that aids in manipulating and validating 
+            <classname>Zend_Uri</classname> is a component that aids in manipulating and validating
             <ulink url="http://www.w3.org/Addressing/">Uniform Resource Identifiers</ulink> (URIs).
             <classname>Zend_Uri</classname> exists primarily to service other components, such as
             <classname>Zend_Http_Client</classname>, but is also useful as a standalone utility.

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

@@ -47,7 +47,7 @@ if ($valid->isValid($input)) {
             PHP 5.3 introduces <ulink url="http://php.net/functions.anonymous">closures</ulink>,
             which are basically self-contained or <emphasis>anonymous</emphasis> functions. PHP
             considers closures another form of callback, and, as such, may be used with
-            <classname>Zend_Validate_Callback</classname>.  As an example:
+            <classname>Zend_Validate_Callback</classname>. As an example:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -182,7 +182,7 @@ class MyClass
 
         <programlisting language="php"><![CDATA[
 $valid = new Zend_Validate_Callback(array(
-    'callback' => array('MyClass', 'myMethod'), 
+    'callback' => array('MyClass', 'myMethod'),
     'options'  => $option,
 ));
 

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

@@ -10,12 +10,12 @@
 
     <para>
         A creditcard contains several items of metadata, including a hologram, account number, logo,
-        expiration date, security code and the card holder name.  The algorithms for verifying the
+        expiration date, security code and the card holder name. The algorithms for verifying the
         combination of metadata are only known to the issuing company, and should be verified with
         them for purposes of payment. However, it's often useful to know whether or not a given
         number actually falls within the ranges of possible numbers <emphasis>prior</emphasis> to
         performing such verification, and, as such, <classname>Zend_Validate_CreditCard</classname>
-        simply verifies that the credit card number provided is well-formed. 
+        simply verifies that the credit card number provided is well-formed.
     </para>
 
     <para>
@@ -126,7 +126,7 @@ if ($valid->isValid($input)) {
         <title>Accepting defined credit cards</title>
 
         <para>
-            Sometimes it is necessary to accept only defined credit card institutes instead of all; 
+            Sometimes it is necessary to accept only defined credit card institutes instead of all;
             e.g., when you have a webshop which accepts only Visa and American Express cards.
             <classname>Zend_Validate_CreditCard</classname> allows you to do exactly this by
             limiting it to exactly these institutes.