[MANUAL] English:

- erasing endline spaces (no translations needed)

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

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

@@ -482,7 +482,7 @@ $cache = Zend_Cache::factory('Core', 'Zend_Cache_Backend_ZendServer_Disk',
             There is no option for this backend.
         </para>
     </sect2>
-    
+
     <sect2 id="zend.cache.backends.static">
         <title>Zend_Cache_Backend_Static</title>
         <para>
@@ -644,7 +644,7 @@ RewriteRule ^.*$ index.php [NC,L]
                               Umask for directories created within public_dir.
                         </entry>
                       </row>
-                      
+
                       <row>
                           <entry><emphasis>file_extension</emphasis></entry>
                           <entry><type>String</type></entry>
@@ -696,7 +696,7 @@ RewriteRule ^.*$ index.php [NC,L]
               </tgroup>
           </table>
     </sect2>
-    
+
 </sect1>
 <!--
 vim:se ts=4 sw=4 et:

documentation/manual/en/module_specs/Zend_Feed_Pubsubhubbub.xml

@@ -283,12 +283,12 @@ if (!$publisher->isSuccess()) {
                 resulting class implements the interface
                 <classname>Zend_Feed_Pubsubhubbub_Model_SubscriptionInterface</classname>.
             </para>
-            
+
             <para>
                 An example schema (MySQL) for a subscription table accessible by the provided model
                 may look similar to:
             </para>
-            
+
                     <programlisting language="sql"><![CDATA[
 CREATE TABLE IF NOT EXISTS `subscription` (
   `id` varchar(32) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',

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

@@ -34,14 +34,14 @@ $username = $filterChain->filter($_POST['username']);
 
     <sect2 id="zend.filter.filter_chains.order">
         <title>Changing filter chain order</title>
-        
+
         <para>
             Since 1.10, the <classname>Zend_Filter</classname> chain also
             supports altering the chain by prepending or appending filters. For
             example, the next piece of code does exactly the same as the other
             username filter chain example:
         </para>
-        
+
         <programlisting language="php"><![CDATA[
 // Create a filter chain and add filters to the chain
 $filterChain = new Zend_Filter();

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

@@ -107,7 +107,7 @@
             This filter returns the input string, with all HTML and <acronym>PHP</acronym> tags
             stripped from it, except those that have been explicitly allowed. In addition to the
             ability to specify which tags are allowed, developers can specify which attributes are
-            allowed across all allowed tags and for specific tags only. 
+            allowed across all allowed tags and for specific tags only.
         </para>
     </sect2>
 

documentation/manual/en/module_specs/Zend_Markup-Renderers.xml

@@ -47,29 +47,29 @@ echo $bbcode->render('my [foo]tag[/foo]');
             it with a tag structure. Currently, only BBCode supports this. Textile doesn't have
             support for custom tags.
         </para>
-        
+
         <para>
             Some renderers (like the HTML renderer) also have support for a
             'tag' parameter. This replaces the 'start' and 'end' parameters, and
             it renders the tags including some default attributes and the
-            closing tag. 
+            closing tag.
         </para>
-        
+
         <sect3 id="zend.markup.renderers.add.callback">
             <title>Add a callback tag</title>
-            
+
             <para>
                 By adding a callback tag, you can do a lot more then just a
                 simple replace of the tags. For instance, you can change the
                 contents, use the parameters to influence the output etc.
             </para>
-            
+
             <para>
                 A callback is a class that implements the
                 <classname>Zend_Markup_Renderer_TokenInterface</classname>
                 interface. An example of a callback class:
             </para>
-            
+
             <programlisting language="php"><![CDATA[
 class My_Markup_Renderer_Html_Upper extends Zend_Markup_Renderer_TokenConverterInterface
 {
@@ -87,7 +87,7 @@ class My_Markup_Renderer_Html_Upper extends Zend_Markup_Renderer_TokenConverterI
                 of the <classname>My_Markup_Renderer_Html_Upper</classname>
                 class. A simple example:
             </para>
-            
+
             <programlisting language="php"><![CDATA[
 // Creates instance of Zend_Markup_Renderer_Html,
 // with Zend_Markup_Parser_BbCode as its parser
@@ -112,7 +112,7 @@ echo $bbcode->render('my [upper]tag[/upper]');
 ]]></programlisting>
         </sect3>
     </sect2>
-    
+
     <sect2 id="zend.markup.renderers.list">
         <title>List of tags</title>
 

documentation/manual/en/module_specs/Zend_Oauth-GettingStarted.xml

@@ -10,14 +10,14 @@
         an OAuth Consumer Key and Consumer Secret. This are utilised to obtain
         an Access Token before we use the Twitter API to post a status message.
     </para>
-    
+
     <para>
         Assuming we have obtained a key and secret, we can start the OAuth workflow
         by setting up a <classname>Zend_Oauth_Consumer</classname> instance as
         follows passing it a configuration (either an array or <classname>
         Zend_Config</classname> object).
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 $config = array(
     'callbackUrl' => 'http://example.com/callback.php',
@@ -42,19 +42,19 @@ $consumer = new Zend_Oauth_Consumer($config);
         and <methodname>setAuthorizeUrl()</methodname> or the configuration fields requestTokenUrl,
         accessTokenUrl and authorizeUrl.
     </para>
-    
+
     <para>
         The consumerKey and consumerSecret are retrieved from Twitter when your
         application is registered for OAuth access. These also apply to any OAuth
         enabled service, so each one will provide a key and secret for your
         application.
     </para>
-    
+
     <para>
         All of these configuration options may be set using method calls simply
         by converting from, e.g. callbackUrl to setCallbackUrl().
     </para>
-    
+
     <para>
         In addition, you should note several other configuration values not
         explicitly used: requestMethod and requestScheme. By default, <classname>
@@ -69,7 +69,7 @@ $consumer = new Zend_Oauth_Consumer($config);
         fine apart from some exceptional cases. Please refer to the service provider's
         documentation for more details.
     </para>
-    
+
     <para>
         The second area of customisation is how <acronym>HMAC</acronym> operates
         when calculating/comparing them for all requests. This is configured using
@@ -80,12 +80,12 @@ $consumer = new Zend_Oauth_Consumer($config);
         fields or the <methodname>setRsaPrivateKey()</methodname> and
         <methodname>setRsaPublicKey()</methodname> methods.
     </para>
-    
+
     <para>
         The first part of the OAuth workflow is obtaining a request token. This
         is accomplished using:
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 $config = array(
     'callbackUrl' => 'http://example.com/callback.php',
@@ -106,7 +106,7 @@ $token = $consumer->getRequestToken();
         it. We accomplish this by redirecting the user to Twitter's authorize endpoint
         via:
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 $config = array(
     'callbackUrl' => 'http://example.com/callback.php',
@@ -133,14 +133,14 @@ $consumer->redirect();
         time to our Callback URL as previously set (note that the callback URL is
         also registered with Twitter when we registered our application).
     </para>
-    
+
     <para>
         Before redirecting the user, we should persist the request token to storage.
         For simplicity I'm just using the user's session, but you can easily use a
         database for the same purpose, so long as you tie the request token to the
         current user so it can be retrieved when they return to our application.
     </para>
-    
+
     <para>
         The redirect URI from Twitter will contain an authorized Access Token. We
         can include code to parse out this access token as follows - this source
@@ -150,7 +150,7 @@ $consumer->redirect();
         to the user session, but in reality an access token can have a long lifetime
         so it should really be stored to a database.
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 $config = array(
     'callbackUrl' => 'http://example.com/callback.php',
@@ -182,7 +182,7 @@ if (!empty($_GET) && isset($_SESSION['TWITTER_REQUEST_TOKEN'])) {
         from anywhere in your application, so long as you can access the OAuth
         configuration and retrieve the final authorized access token.
     </para>
-    
+
     <programlisting language="php"><![CDATA[
 $config = array(
     'callbackUrl' => 'http://example.com/callback.php',

documentation/manual/en/module_specs/Zend_Oauth-ProtocolWorkflow.xml

@@ -23,7 +23,7 @@
     <para>
         To use TweetExpress you are asked to register for a new account, and after your registration
         is confirmed you are informed that TweetExpress will seek to associate your Twitter account
-        with the service. 
+        with the service.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Oauth-SecurityArchitecture.xml

@@ -41,7 +41,7 @@
         (i.e. SHA1) in combination with a secret key known only to the message sender and receiver
         (i.e. the OAuth Consumer Secret and the authorized Access Key combined). This hashing
         mechanism is applied to the parameters and content of any OAuth requests which are
-        concatenated into a "base signature string" as defined by the OAuth specification. 
+        concatenated into a "base signature string" as defined by the OAuth specification.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Pdf-Drawing.xml

@@ -110,7 +110,7 @@ public function drawRectangle($x1, $y1, $x2, $y2,
  * @param integer $fillType
  * @return Zend_Pdf_Page
  */
-public function drawRoundedRectangle($x1, $y1, $x2, $y2, $radius, 
+public function drawRoundedRectangle($x1, $y1, $x2, $y2, $radius,
                        $fillType = Zend_Pdf_Page::SHAPE_DRAW_FILL_AND_STROKE);
 ]]></programlisting>
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Serializer-Adapter.xml

@@ -2,7 +2,7 @@
 <!-- Reviewed: no -->
 <sect1 id="zend.serializer.adapter">
     <title>Zend_Serializer_Adapter</title>
-    
+
     <para>
         <classname>Zend_Serializer</classname> adapters create a bridge for different methods of
         serializing with very little effort.
@@ -106,7 +106,7 @@
                           <entry></entry>
 
                           <entry>
-                            An optional comment that appears in the packet header. 
+                            An optional comment that appears in the packet header.
                           </entry>
                       </row>
                   </tbody>
@@ -412,7 +412,7 @@
              </tgroup>
         </table>
     </sect2>
-    
+
     <sect2 id="zend.serializer.adapter.phpcode">
         <title>Zend_Serializer_Adapter_PhpCode</title>
 

documentation/manual/en/module_specs/Zend_Serializer-Introduction.xml

@@ -21,15 +21,15 @@ $serializer = Zend_Serializer::factory('PhpSerialize');
 // Now $serializer is an instance of Zend_Serializer_Adapter_AdapterInterface,
 // specifically Zend_Serializer_Adapter_PhpSerialize
 
-try { 
+try {
     $serialized = $serializer->serialize($data);
     // now $serialized is a string
-    
+
     $unserialized = $serializer->unserialize($serialized);
     // now $data == $unserialized
-} catch (Zend_Serializer_Exception $e) { 
-    echo $e; 
-} 
+} catch (Zend_Serializer_Exception $e) {
+    echo $e;
+}
 ]]></programlisting>
     </example>
 
@@ -55,12 +55,12 @@ $serializer = Zend_Serializer::factory('Wddx', array(
     'comment' => 'serialized by Zend_Serializer',
 ));
 
-try { 
+try {
     $serialized = $serializer->serialize($data, array('comment' => 'change comment'));
     $unserialized = $serializer->unserialize($serialized, array(/* options for unserialize */));
-} catch (Zend_Serializer_Exception $e) { 
-    echo $e; 
-} 
+} catch (Zend_Serializer_Exception $e) {
+    echo $e;
+}
 ]]></programlisting>
 
     <para>
@@ -87,12 +87,12 @@ Zend_Serializer::setDefaultAdapter('PhpSerialize', $options);
 $serializer = Zend_Serializer::factory('PhpSerialize', $options);
 Zend_Serializer::setDefaultAdapter($serializer);
 
-try { 
-    $serialized   = Zend_Serializer::serialize($data, $options); 
-    $unserialized = Zend_Serializer::unserialize($serialized, $options); 
-} catch (Zend_Serializer_Exception $e) { 
-    echo $e; 
-} 
+try {
+    $serialized   = Zend_Serializer::serialize($data, $options);
+    $unserialized = Zend_Serializer::unserialize($serialized, $options);
+} catch (Zend_Serializer_Exception $e) {
+    echo $e;
+}
 ]]></programlisting>
     </example>
 </sect1>

documentation/manual/en/module_specs/Zend_Service_DeveloperGarden.xml

@@ -2,16 +2,16 @@
 <!-- Reviewed: no -->
 <sect1 id="zend.service.developergarden">
     <title>Zend_Service_DeveloperGarden</title>
-    
+
     <sect2 id="zend.service.developergarden.introduction">
         <title>Introduction to DeveloperGarden</title>
-        
+
         <para>
             DeveloperGarden is the name for the &quot;Open Development services&quot; of the German
             Telekom. The &quot;Open Development services&quot; are a set of <acronym>SOAP</acronym>
             API Services.
         </para>
-        
+
         <para>
             The family of <classname>Zend_Service_DeveloperGarden</classname> components provides a
             clean and simple interface to the <ulink
@@ -22,50 +22,50 @@
         <itemizedlist>
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.baseuserservice">BaseUserService</link>: 
+                    <link linkend="zend.service.developergarden.baseuserservice">BaseUserService</link>:
                     Class to manage API quota and user accounting details.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.iplocation">IpLocation</link>: 
-                    Locale the given IP and returns geo coordinates. Works only with IPs allocated 
+                    <link linkend="zend.service.developergarden.iplocation">IpLocation</link>:
+                    Locale the given IP and returns geo coordinates. Works only with IPs allocated
                     in the network of the german telekom.
                     </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.localsearch">LocalSearch</link>: 
+                    <link linkend="zend.service.developergarden.localsearch">LocalSearch</link>:
                     Allows you to search with options nearby or around a given geo coordinate or city.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.sendsms">SendSms</link>: Send a Sms 
+                    <link linkend="zend.service.developergarden.sendsms">SendSms</link>: Send a Sms
                     or Flash Sms to a given number.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.smsvalidation">SmsValidation</link>: 
+                    <link linkend="zend.service.developergarden.smsvalidation">SmsValidation</link>:
                     You can validate a number to use it with SendSms for also supply a back channel.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.voicecall">VoiceCall</link>: 
+                    <link linkend="zend.service.developergarden.voicecall">VoiceCall</link>:
                     Initiates a call between two numbers.
                  </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <link linkend="zend.service.developergarden.conferencecall">ConferenceCall</link>: 
+                    <link linkend="zend.service.developergarden.conferencecall">ConferenceCall</link>:
                     You can configure a whole conference room with participants for an adhoc
                     conference or you can also schedule your conference.
                 </para>
@@ -73,7 +73,7 @@
         </itemizedlist>
 
         <para>
-            The backend SOAP API is documented 
+            The backend SOAP API is documented
             <ulink url="http://www.developergarden.com/openapi/dokumentation/">here</ulink>.
         </para>
 
@@ -81,7 +81,7 @@
             <title>Sign Up for an Account</title>
 
             <para>
-                Before you can start using the DeveloperGarden API, you must first 
+                Before you can start using the DeveloperGarden API, you must first
                 <ulink url="http://www.developergarden.com/register">sign up</ulink> for an account.
             </para>
         </sect3>
@@ -172,9 +172,9 @@ $service = new Zend_Service_DeveloperGarden_SendSms($config);
 
     <sect2 id="zend.service.developergarden.baseuserservice">
         <title>BaseUserService</title>
-        
+
         <para>
-            The class can be used to set and get quota values for the services and to fetch 
+            The class can be used to set and get quota values for the services and to fetch
             account details.
         </para>
 
@@ -214,7 +214,7 @@ echo 'Max User Quota: ', $result->getMaxUserQuota(), '<br />';
 echo 'Quota Level: ', $result->getQuotaLevel(), '<br />';
 ]]></programlisting>
             </example>
-            
+
             <para>
                 You get a <classname>Result</classname> object that contains all information that
                 you need, optional you can pass to the <methodname>QuotaInformation</methodname>
@@ -257,7 +257,7 @@ echo 'Quota Level: ', $result->getQuotaLevel(), '<br />';
                 </listitem>
             </itemizedlist>
         </sect3>
-        
+
         <sect3 id="zend.service.developergarden.baseuserservice.changequotainformation">
             <title>Change quota information</title>
 
@@ -273,7 +273,7 @@ echo 'Quota Level: ', $result->getQuotaLevel(), '<br />';
                 <programlisting language="php"><![CDATA[
 $service = new Zend_Service_DeveloperGarden_BaseUserService($config);
 $result = $service->changeSmsQuotaPool(
-    1000, 
+    1000,
     Zend_Service_DeveloperGarden_BaseUserService::ENV_PRODUCTION
 );
 if (!$result->hasError()) {
@@ -281,7 +281,7 @@ if (!$result->hasError()) {
 }
 ]]></programlisting>
             </example>
-            
+
             <para>
                 Here a list of all <methodname>changeQuotaPool</methodname> methods:
             </para>
@@ -421,7 +421,7 @@ print_r($service->localSearch($search));
 
             <listitem>
                 <para>
-                    The following characters are counted twice: 
+                    The following characters are counted twice:
                     <literal>| ^ € { } [ ] ~ \ LF</literal> (line break)
                 </para>
             </listitem>
@@ -453,7 +453,7 @@ print_r($service->localSearch($search));
                         linkend="zend.service.developergarden.smsvalidation">SMS Validation</link>)
                 </para>
             </listitem>
-        </itemizedlist>      
+        </itemizedlist>
 
         <example id="zend.service.developergarden.sendsms.example">
             <title>Sending an SMS</title>
@@ -461,8 +461,8 @@ print_r($service->localSearch($search));
             <programlisting language="php"><![CDATA[
 $service = new Zend_Service_DeveloperGarden_SendSms($config);
 $sms = $service->createSms(
-    '+49-172-123456; +49-177-789012', 
-    'your test message', 
+    '+49-172-123456; +49-177-789012',
+    'your test message',
     'yourname'
 );
 print_r($service->send($sms));]]></programlisting>
@@ -595,7 +595,7 @@ $service->callStatus($sessionId, true); // extend the call
 
 sleep(10); // sleep 10s and then tearDown
 
-$service->tearDownCall($sessionId); 
+$service->tearDownCall($sessionId);
 ]]></programlisting>
         </example>
     </sect2>
@@ -606,7 +606,7 @@ $service->tearDownCall($sessionId);
         <para>
             Conference Call allows you to setup and start a phone conference.
         </para>
-        
+
         <para>
             The following features are available:
         </para>
@@ -642,15 +642,15 @@ $service->tearDownCall($sessionId);
                 </para>
             </listitem>
         </itemizedlist>
-        
+
         <para>
             Here is a list of currently implemented API methods:
         </para>
-        
+
         <itemizedlist>
             <listitem>
                 <para>
-                    <methodname>createConference()</methodname> creates a new conference                    
+                    <methodname>createConference()</methodname> creates a new conference
                 </para>
             </listitem>
 
@@ -663,7 +663,7 @@ $service->tearDownCall($sessionId);
             <listitem>
                 <para>
                     <methodname>commitConference()</methodname> saves the conference, and, if no date
-                    is configured, immediately starts the conference 
+                    is configured, immediately starts the conference
                 </para>
             </listitem>
 
@@ -696,7 +696,7 @@ $service->tearDownCall($sessionId);
 
             <listitem>
                 <para>
-                    <methodname>newParticipant()</methodname> creates a new participant                    
+                    <methodname>newParticipant()</methodname> creates a new participant
                 </para>
             </listitem>
 
@@ -722,14 +722,14 @@ $service->tearDownCall($sessionId);
 
             <listitem>
                 <para>
-                    <methodname>getRunningConference()</methodname> requests the running instance of 
+                    <methodname>getRunningConference()</methodname> requests the running instance of
                     a planned conference
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <methodname>createConferenceTemplate()</methodname> creates a new conference 
+                    <methodname>createConferenceTemplate()</methodname> creates a new conference
                     template
                 </para>
             </listitem>
@@ -744,7 +744,7 @@ $service->tearDownCall($sessionId);
             <listitem>
                 <para>
                     <methodname>updateConferenceTemplate()</methodname> updates existing conference
-                    template details                    
+                    template details
                 </para>
             </listitem>
 
@@ -777,7 +777,7 @@ $service->tearDownCall($sessionId);
 
             <listitem>
                 <para>
-                    <methodname>updateConferenceTemplateParticipant()</methodname> updates 
+                    <methodname>updateConferenceTemplateParticipant()</methodname> updates
                     participant details within a conference template
                 </para>
             </listitem>
@@ -789,7 +789,7 @@ $service->tearDownCall($sessionId);
                 </para>
             </listitem>
         </itemizedlist>
-        
+
         <example id="zend.service.developergarden.conferencecall.example">
             <title>Ad-Hoc conference</title>
 
@@ -831,7 +831,7 @@ $client->commitConference($conference->getConferenceId());
         <para>
             First of all, you can setup the internal SoapClient (PHP) caching values.
         </para>
-        
+
         <example id="zend.service.developergarden.performance.wsdlcache.example">
             <title>WSDL cache options</title>
 
@@ -872,7 +872,7 @@ Zend_Service_DeveloperGarden_SecurityTokenServer_Cache::setWsdlCache([PHP CONSTA
 
         <para>
             If you want also to cache the result for calls to the SecuritTokenServer
-            you can setup a <classname>Zend_Cache</classname> instance and pass it to the 
+            you can setup a <classname>Zend_Cache</classname> instance and pass it to the
             <methodname>setCache()</methodname>.
         </para>