[MANUAL] English:

- unified "XML" with acronym

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

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

@@ -156,7 +156,7 @@ class NewsController extends Zend_Controller_Action
 
         <para>
             By default, two contexts are available to the
-            <emphasis>ContextSwitch</emphasis> helper: json and xml.
+            <emphasis>ContextSwitch</emphasis> helper: json and <acronym>XML</acronym>.
         </para>
 
         <itemizedlist>

documentation/manual/en/module_specs/Zend_Feed_Writer.xml

@@ -455,10 +455,13 @@ $out = $feed->export('atom');
 
                     <row>
                         <entry><methodname>export()</methodname></entry>
-                        <entry>Exports the entire data hierarchy to an XML feed. The method
-                        has two parameters. The first is the feed type, one of "atom"
-                        or "rss". The second is an optional boolean to set whether
-                        Exceptions are thrown. The default is TRUE.</entry>
+
+                        <entry>
+                            Exports the entire data hierarchy to an <acronym>XML</acronym> feed. The
+                            method has two parameters. The first is the feed type, one of "atom"
+                            or "rss". The second is an optional boolean to set whether
+                            Exceptions are thrown. The default is <constant>TRUE</constant>.
+                        </entry>
                     </row>
                 </tbody>
             </tgroup>
@@ -642,9 +645,9 @@ $out = $feed->export('atom');
                         <entry><methodname>setCommentFeedLink()</methodname></entry>
 
                         <entry>
-                            Sets a link to a XML feed containing comments associated with this
-                            entry. The parameter is an array containing the keys "uri" and "type",
-                            where the type is one of "rdf", "rss" or "atom".
+                            Sets a link to a <acronym>XML</acronym> feed containing comments
+                            associated with this entry. The parameter is an array containing the
+                            keys "uri" and "type", where the type is one of "rdf", "rss" or "atom".
                         </entry>
                     </row>
 

documentation/manual/en/module_specs/Zend_Log-Formatters.xml

@@ -61,8 +61,9 @@ $logger->info('there');
         <title>Formatting to XML</title>
 
         <para>
-            <classname>Zend_Log_Formatter_Xml</classname> formats log data into XML strings.
-            By default, it automatically logs all items in the event data array:
+            <classname>Zend_Log_Formatter_Xml</classname> formats log data into
+            <acronym>XML</acronym> strings. By default, it automatically logs all items in the event
+            data array:
 
             <programlisting language="php"><![CDATA[
 $writer = new Zend_Log_Writer_Stream('php://output');
@@ -77,7 +78,7 @@ $logger->info('informational message');
         </para>
 
         <para>
-            The code above outputs the following XML (space added for clarity):
+            The code above outputs the following <acronym>XML</acronym> (space added for clarity):
 
             <programlisting language="xml"><![CDATA[
 <logEntry>
@@ -91,7 +92,7 @@ $logger->info('informational message');
 
         <para>
             It's possible to customize the root element as well as specify a mapping
-            of XML elements to the items in the event data array. The constructor
+            of <acronym>XML</acronym> elements to the items in the event data array. The constructor
             of <classname>Zend_Log_Formatter_Xml</classname> accepts a string with the name of
             the root element as the first parameter and an associative array with
             the element mapping as the second parameter:

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

@@ -203,7 +203,7 @@ $pdf->save($pdfPath);
     </para>
 
     <para>
-        This XML document can be retrieved and attached to the PDF with
+        This <acronym>XML</acronym> document can be retrieved and attached to the PDF with
         <methodname>Zend_Pdf::getMetadata()</methodname> and
         <methodname>Zend_Pdf::setMetadata($metadata)</methodname> methods:
 

documentation/manual/en/module_specs/Zend_Soap_Server.xml

@@ -368,7 +368,8 @@ $server->handle();
 
             <para>
                 Last processed request may be retrieved using
-                <methodname>getLastRequest()</methodname> method as an XML string:
+                <methodname>getLastRequest()</methodname> method as an <acronym>XML</acronym>
+                string:
 
                 <programlisting language="php"><![CDATA[
 ...

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

@@ -126,8 +126,8 @@
                 <constant>ZF_CONFIG_FILE</constant> is set, then its value will be used as the
                 location of the configuration file to use with the Console Client. The
                 <constant>ZF_CONFIG_FILE</constant> can point to any
-                <classname>Zend_Config</classname> readable <acronym>INI</acronym>, XML or
-                <acronym>PHP</acronym> File.
+                <classname>Zend_Config</classname> readable <acronym>INI</acronym>,
+                <acronym>XML</acronym> or <acronym>PHP</acronym> File.
             </para>
 
             <para>
@@ -171,7 +171,7 @@ php.error_reporting = 1
                 <para>
                     The reserved prefix "php" only works with <acronym>INI</acronym> files. You
                     can't set <acronym>PHP</acronym> <acronym>INI</acronym> values with
-                    <acronym>PHP</acronym> or XML config.
+                    <acronym>PHP</acronym> or <acronym>XML</acronym> config.
                 </para>
             </important>
         </sect3>

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

@@ -135,12 +135,12 @@
             </para>
 
             <para>
-                When you use a xml based source format like TMX or XLIFF you must
-                define the encoding within the xml files header because xml files
-                without defined encoding will be treated as UTF-8 by any xml parser
-                by default. You should also be aware that actually the encoding of
-                xml files is limited to the encodings supported by <acronym>PHP</acronym> which are
-                UTF-8, ISO-8859-1 and US-ASCII.
+                When you use a <acronym>XML</acronym> based source format like TMX or XLIFF you must
+                define the encoding within the <acronym>XML</acronym> files header because
+                <acronym>XML</acronym> files without defined encoding will be treated as UTF-8 by
+                any <acronym>XML</acronym> parser by default. You should also be aware that actually
+                the encoding of <acronym>XML</acronym> files is limited to the encodings supported
+                by <acronym>PHP</acronym> which are UTF-8, ISO-8859-1 and US-ASCII.
             </para>
         </note>