Bladeren bron

[DOCUMENTATION] English:

- deleted multiple whitespaces

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@16443 44c647ce-9c0f-0410-b52a-842ac1e357ba
thomas 16 jaren geleden
bovenliggende
commit
ee11f69bf8

+ 2 - 2
documentation/manual/en/module_specs/Zend_Controller-Router-Route-Chain.xml

@@ -14,7 +14,7 @@
     <note>
     <note>
         <title>Parameter Priority</title>
         <title>Parameter Priority</title>
         <para>
         <para>
-            When chaining routes  together, the parameters of the outer route
+            When chaining routes together, the parameters of the outer route
             have a higher priority than the parameters of the inner route. Thus
             have a higher priority than the parameters of the inner route. Thus
             if you define a controller in the outer and in the inner route,
             if you define a controller in the outer and in the inner route,
             the controller of the outer route will be selected.
             the controller of the outer route will be selected.
@@ -70,7 +70,7 @@ echo $chainedRoute->assemble();
         <title>Chain Routes via Zend_Config</title>
         <title>Chain Routes via Zend_Config</title>
 
 
         <para>
         <para>
-            To chain routes together in a config file, there are  additional
+            To chain routes together in a config file, there are additional
             parameters for the configuration of those. The simpler approach is
             parameters for the configuration of those. The simpler approach is
             to use the <code>chains</code> parameters. This one is simply a list
             to use the <code>chains</code> parameters. This one is simply a list
             of routes, which will be chained with the parent route. Neither the
             of routes, which will be chained with the parent route. Neither the

+ 1 - 1
documentation/manual/en/module_specs/Zend_Gdata_AuthSub.xml

@@ -17,7 +17,7 @@
     <para>
     <para>
         The Google documentation says the ClientLogin mechanism is appropriate
         The Google documentation says the ClientLogin mechanism is appropriate
         for "installed applications" whereas the AuthSub mechanism is
         for "installed applications" whereas the AuthSub mechanism is
-        for "web applications."  The difference is that AuthSub requires
+        for "web applications." The difference is that AuthSub requires
         interaction from the user, and a browser interface that can react
         interaction from the user, and a browser interface that can react
         to redirection requests. The ClientLogin solution uses PHP code to
         to redirection requests. The ClientLogin solution uses PHP code to
         supply the account credentials; the user is not required to enter her
         supply the account credentials; the user is not required to enter her

+ 5 - 1
documentation/manual/en/module_specs/Zend_Gdata_Gbase.xml

@@ -197,7 +197,11 @@ $service = new Zend_Gdata_Gbase();
                 You can send a structured query to retrieve items from your own customer items feed or from the public snippets feed.
                 You can send a structured query to retrieve items from your own customer items feed or from the public snippets feed.
             </para>
             </para>
             <para>
             <para>
-                When retrieving items using the Base API, specially constructed query URLs are used to describe what events should be returned. The  <classname>Zend_Gdata_Gbase_ItemQuery</classname> and <classname>Zend_Gdata_Gbase_SnippetQuery</classname> classes simplify this task by automatically constructing a query URL based on provided parameters.
+                When retrieving items using the Base API, specially constructed query URLs are used
+                to describe what events should be returned. The
+                <classname>Zend_Gdata_Gbase_ItemQuery</classname> and
+                <classname>Zend_Gdata_Gbase_SnippetQuery</classname> classes simplify this task by
+                automatically constructing a query URL based on provided parameters.
             </para>
             </para>
             <sect4 id="zend.gdata.gbase.retrieve.query.customeritems">
             <sect4 id="zend.gdata.gbase.retrieve.query.customeritems">
                 <title>Query Customer Items Feed</title>
                 <title>Query Customer Items Feed</title>

+ 1 - 1
documentation/manual/en/module_specs/Zend_Gdata_YouTube.xml

@@ -609,7 +609,7 @@ if ($control instanceof Zend_Gdata_App_Extension_Control) {
       </para>
       </para>
       <para>
       <para>
         Please refer to the full documentation available in the
         Please refer to the full documentation available in the
-        <ulink url="http://code.google.com/apis/youtube/developers_guide_php.html">PHP Developer's  Guide</ulink> on code.google.com.
+        <ulink url="http://code.google.com/apis/youtube/developers_guide_php.html">PHP Developer's Guide</ulink> on code.google.com.
       </para>
       </para>
     </sect2>
     </sect2>
 </sect1>
 </sect1>

+ 1 - 1
documentation/manual/en/module_specs/Zend_Http_Cookie-Handling.xml

@@ -46,7 +46,7 @@
                         </listitem>
                         </listitem>
                         <listitem>
                         <listitem>
                             <para>
                             <para>
-                            <code>$value</code>: The value of the cookie  (required)
+                            <code>$value</code>: The value of the cookie (required)
                             </para>
                             </para>
                         </listitem>
                         </listitem>
                         <listitem>
                         <listitem>

+ 1 - 1
documentation/manual/en/module_specs/Zend_Mail_Read.xml

@@ -732,7 +732,7 @@ $quota = $mail->setQuota(array('size' => 10000, 'count' => 100));
 
 
             <para>
             <para>
             To add your own quota checks use single letters as keys, and they will be preserved (but obviously not checked).
             To add your own quota checks use single letters as keys, and they will be preserved (but obviously not checked).
-            It's also possible to extend  <classname>Zend_Mail_Storage_Writable_Maildir</classname> to define your own quota only
+            It's also possible to extend <classname>Zend_Mail_Storage_Writable_Maildir</classname> to define your own quota only
             if the maildirsize file is missing (which can happen in Maildir++):
             if the maildirsize file is missing (which can happen in Maildir++):
             </para>
             </para>
 
 

+ 1 - 1
documentation/manual/en/module_specs/Zend_Search_Lucene-BestPractice.xml

@@ -186,7 +186,7 @@ $index->optimize();
             This gives good approximation for the number of segments in the index:
             This gives good approximation for the number of segments in the index:
         </para>
         </para>
         <para>
         <para>
-            <emphasis>NumberOfSegments</emphasis>  &lt;= <emphasis>MaxBufferedDocs</emphasis> + <emphasis>MergeFactor</emphasis>*log
+            <emphasis>NumberOfSegments</emphasis> &lt;= <emphasis>MaxBufferedDocs</emphasis> + <emphasis>MergeFactor</emphasis>*log
             <subscript><emphasis>MergeFactor</emphasis></subscript> (<emphasis>NumberOfDocuments</emphasis>/<emphasis>MaxBufferedDocs</emphasis>)
             <subscript><emphasis>MergeFactor</emphasis></subscript> (<emphasis>NumberOfDocuments</emphasis>/<emphasis>MaxBufferedDocs</emphasis>)
         </para>
         </para>
 
 

+ 2 - 2
documentation/manual/en/module_specs/Zend_Search_Lucene-Extending.xml

@@ -229,7 +229,7 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
         </para>
         </para>
 
 
         <para>
         <para>
-            <code>score(q,d) = sum( tf(t in d) * idf(t) * getBoost(t.field in d) * lengthNorm(t.field in d)  ) *
+            <code>score(q,d) = sum( tf(t in d) * idf(t) * getBoost(t.field in d) * lengthNorm(t.field in d) ) *
             coord(q,d) * queryNorm(q)</code>
             coord(q,d) * queryNorm(q)</code>
         </para>
         </para>
 
 
@@ -269,7 +269,7 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
         </para>
         </para>
 
 
         <para>
         <para>
-            queryNorm(q) -  the normalization value for a query given the sum of the squared weights
+            queryNorm(q) - the normalization value for a query given the sum of the squared weights
             of each of the query terms. This value is then multiplied into the weight of each query
             of each of the query terms. This value is then multiplied into the weight of each query
             term.
             term.
         </para>
         </para>

+ 1 - 1
documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-Ebs.xml

@@ -7,7 +7,7 @@
         Amazon Elastic Block Store (Amazon EBS) is a new type of storage
         Amazon Elastic Block Store (Amazon EBS) is a new type of storage
         designed specifically for Amazon EC2 instances. Amazon EBS allows
         designed specifically for Amazon EC2 instances. Amazon EBS allows
         you to create volumes that can be mounted as devices by Amazon EC2
         you to create volumes that can be mounted as devices by Amazon EC2
-        instances. Amazon EBS  volumes behave like raw unformatted external
+        instances. Amazon EBS volumes behave like raw unformatted external
         block devices. They have user supplied device names and provide a block
         block devices. They have user supplied device names and provide a block
         device interface. You can load a file system on top of Amazon EBS volumes,
         device interface. You can load a file system on top of Amazon EBS volumes,
         or use them just as you would use a block device.
         or use them just as you would use a block device.

+ 2 - 2
documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-Instance.xml

@@ -476,7 +476,7 @@ $return = $ec2_instance->confirmProduct('productCode', 'instanceId');
             <title>Turn on CloudWatch Monitoring on an Instance(s)</title>
             <title>Turn on CloudWatch Monitoring on an Instance(s)</title>
             <para>
             <para>
                 <code>monitor</code> returns the list of instances and their
                 <code>monitor</code> returns the list of instances and their
-                current state of the CloudWatch Monitoring.  If the instance
+                current state of the CloudWatch Monitoring. If the instance
                 does not currently have Monitoring enabled it will be turned on.
                 does not currently have Monitoring enabled it will be turned on.
             </para>
             </para>
             <programlisting language="php"><![CDATA[
             <programlisting language="php"><![CDATA[
@@ -491,7 +491,7 @@ $return = $ec2_instance->monitor('instanceId');
             <title>Turn off CloudWatch Monitoring on an Instance(s)</title>
             <title>Turn off CloudWatch Monitoring on an Instance(s)</title>
             <para>
             <para>
                 <code>monitor</code> returns the list of instances and their
                 <code>monitor</code> returns the list of instances and their
-                current state of the CloudWatch Monitoring.  If the instance
+                current state of the CloudWatch Monitoring. If the instance
                 currently has Monitoring enabled it will be turned off.
                 currently has Monitoring enabled it will be turned off.
             </para>
             </para>
             <programlisting language="php"><![CDATA[
             <programlisting language="php"><![CDATA[

+ 3 - 3
documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2.xml

@@ -23,8 +23,8 @@
         <title>Static Methods</title>
         <title>Static Methods</title>
         <para>
         <para>
             To make using the Ec2 class easier to use there are two static methods that can be
             To make using the Ec2 class easier to use there are two static methods that can be
-            invoked from any of the Ec2 Elements.  The first static method is <code>setKeys</code>
-            which will defind you AWS Access Keys as default keys.  When you then create any new
+            invoked from any of the Ec2 Elements. The first static method is <code>setKeys</code>
+            which will defind you AWS Access Keys as default keys. When you then create any new
             object you don't need to pass in any keys to the constructor.
             object you don't need to pass in any keys to the constructor.
         </para>
         </para>
         <example id="zend.service.amazon.ec2.staticmethods.setkeys">
         <example id="zend.service.amazon.ec2.staticmethods.setkeys">
@@ -36,7 +36,7 @@ Zend_Service_Amazon_Ec2_Ebs::setKeys('aws_key','aws_secret_key');
         <para>
         <para>
             To set the region that you are working in you can call the <code>setRegion</code> to set which
             To set the region that you are working in you can call the <code>setRegion</code> to set which
             Amazon Ec2 Region you are working in. Currently there is only two region available us-east-1
             Amazon Ec2 Region you are working in. Currently there is only two region available us-east-1
-            and eu-west-1.  If an invalid value is passed it will throw an exception stating that.
+            and eu-west-1. If an invalid value is passed it will throw an exception stating that.
         </para>
         </para>
         <example id="zend.service.amazon.ec2.staticmethods.setregion">
         <example id="zend.service.amazon.ec2.staticmethods.setregion">
             <title>setRegion() Example</title>
             <title>setRegion() Example</title>

+ 1 - 1
documentation/manual/en/module_specs/Zend_Service_SlideShare.xml

@@ -46,7 +46,7 @@ $ss = new Zend_Service_SlideShare('APIKEY',
         <para>
         <para>
             All slide shows in the <classname>Zend_Service_SlideShare</classname> component are represented
             All slide shows in the <classname>Zend_Service_SlideShare</classname> component are represented
             using the <classname>Zend_Service_SlideShare_SlideShow</classname> object (both when retrieving
             using the <classname>Zend_Service_SlideShare_SlideShow</classname> object (both when retrieving
-            and uploading new    slide shows). For your reference a pseudo-code version of this class
+            and uploading new slide shows). For your reference a pseudo-code version of this class
             is provided below.
             is provided below.
         </para>
         </para>
 
 

+ 1 - 1
documentation/manual/en/module_specs/Zend_Service_Twitter.xml

@@ -15,7 +15,7 @@
         </para>
         </para>
 
 
         <para>
         <para>
-            <classname>Zend_Service_Twitter</classname> is implementing a REST service and  all methods return an instance of
+            <classname>Zend_Service_Twitter</classname> is implementing a REST service and all methods return an instance of
             <classname>Zend_Rest_Client_Result</classname>.
             <classname>Zend_Rest_Client_Result</classname>.
         </para>
         </para>
 
 

+ 7 - 6
documentation/manual/en/module_specs/Zend_Session-AdvancedUsage.xml

@@ -43,12 +43,13 @@ Zend_Session::start();
         <orderedlist>
         <orderedlist>
             <listitem>
             <listitem>
                 <para>
                 <para>
-                    Wrong: Do not enable PHP's
-                    <ulink url="http://www.php.net/manual/en/ref.session.php#ini.session.auto-start"><code>                    session.auto_start</code>
-                    setting</ulink>. If you do not have the ability to disable this setting in
-                    php.ini, you are using mod_php (or equivalent), and the setting is already enabled in
-                    <code>php.ini</code>, then add the following to your <code>.htaccess</code> file (usually in your
-                    HTML document root directory):
+                    Wrong: Do not enable PHP's <ulink
+                        url="http://www.php.net/manual/en/ref.session.php#ini.session.auto-start">
+                        <code>session.auto_start</code> setting</ulink>. If you do not have the
+                    ability to disable this setting in php.ini, you are using mod_php (or
+                    equivalent), and the setting is already enabled in <code>php.ini</code>, then
+                    add the following to your <code>.htaccess</code> file (usually in your HTML
+                    document root directory):
                     <programlisting language="httpd.conf"><![CDATA[
                     <programlisting language="httpd.conf"><![CDATA[
 php_value session.auto_start 0
 php_value session.auto_start 0
 ]]></programlisting>
 ]]></programlisting>

+ 2 - 2
documentation/manual/en/module_specs/Zend_Soap_AutoDiscovery.xml

@@ -102,7 +102,7 @@ $autodiscover->handle();
 
 
             <para>
             <para>
                 As the SOAP Endpoint Uri is uses the default
                 As the SOAP Endpoint Uri is uses the default
-                <code>'http://'  .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code>,
+                <code>'http://' .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code>,
                 but this can be changed with the <code>setUri()</code> function or the Constructor
                 but this can be changed with the <code>setUri()</code> function or the Constructor
                 parameter of <classname>Zend_Soap_AutoDiscover</classname> class. The endpoint has to provide
                 parameter of <classname>Zend_Soap_AutoDiscover</classname> class. The endpoint has to provide
                 a <classname>Zend_Soap_Server</classname> that listens to requests.
                 a <classname>Zend_Soap_Server</classname> that listens to requests.
@@ -149,7 +149,7 @@ $autodiscover->handle();
                 </listitem>
                 </listitem>
                 <listitem>
                 <listitem>
                     <para>
                     <para>
-                        <code>'http://'  .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code> is used
+                        <code>'http://' .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code> is used
                         as an URI where the WSDL is available by default but can be overwritten via <code>setUri()</code> method.
                         as an URI where the WSDL is available by default but can be overwritten via <code>setUri()</code> method.
                     </para>
                     </para>
                     <para>
                     <para>

+ 3 - 3
documentation/manual/en/module_specs/Zend_Soap_Wsdl.xml

@@ -242,7 +242,7 @@
                             <footnote>
                             <footnote>
                                 <para>
                                 <para>
                                     <code>'tns:' namespace</code> is defined as script URI
                                     <code>'tns:' namespace</code> is defined as script URI
-                                    (<code>'http://'  .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code>).
+                                    (<code>'http://' .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code>).
                                 </para>
                                 </para>
                             </footnote>
                             </footnote>
                             as binding name,
                             as binding name,
@@ -250,13 +250,13 @@
                 </listitem>
                 </listitem>
                 <listitem>
                 <listitem>
                     <para>
                     <para>
-                        script URI<footnote><para><code>'http://'  .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code></para></footnote>
+                        script URI<footnote><para><code>'http://' .$_SERVER['HTTP_HOST'] . $_SERVER['SCRIPT_NAME']</code></para></footnote>
                         as a service URI for Web Service definition using classes.
                         as a service URI for Web Service definition using classes.
                     </para>
                     </para>
                 </listitem>
                 </listitem>
             </itemizedlist>
             </itemizedlist>
             where <code>$name</code> is a class name for the Web Service definition mode using class and
             where <code>$name</code> is a class name for the Web Service definition mode using class and
-            script name for  the Web Service definition mode using set of functions.
+            script name for the Web Service definition mode using set of functions.
         </para>
         </para>
         <para>
         <para>
             See <ulink url="http://www.w3.org/TR/wsdl#_services"/> for the details.
             See <ulink url="http://www.w3.org/TR/wsdl#_services"/> for the details.