[DOCUMENTATION] English:

 - manual fixes: <acronym>ISO</acronym>* => ISO* where * doesn't begin with a space

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

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

@@ -118,10 +118,10 @@ date_default_timezone_set('Europe/Berlin');
             </listitem>
             <listitem>
                 <para>
-                    Support for <acronym>ISO</acronym>_8601 date specifications
+                    Support for ISO_8601 date specifications
                 </para>
                 <para>
-                    <acronym>ISO</acronym>_8601 date specifications are supported. Even partially compliant <acronym>ISO</acronym>_8601
+                    ISO_8601 date specifications are supported. Even partially compliant <acronym>ISO</acronym>_8601
                     date specifications will be identified. These date formats are particularly
                     useful when working with databases. for example, even though MsSQL and <ulink
                         url="http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html">MySQL</ulink>

documentation/manual/en/module_specs/Zend_Dojo-Form-Elements.xml

@@ -1273,14 +1273,14 @@ $form->addElement(
             <listitem><para>
                 <methodname>setVisibleIncrement($format)</methodname> and
                 <methodname>getVisibleIncrement()</methodname>: set the increment visible
-                in the time chooser; must follow <acronym>ISO</acronym>-8601 formats.
+                in the time chooser; must follow ISO-8601 formats.
             </para></listitem>
 
             <listitem><para>
                 <methodname>setVisibleRange($format)</methodname> and
                 <methodname>getVisibleRange()</methodname>: set and retrieve the range of
                 time visible in the time chooser at any given moment; must
-                follow <acronym>ISO</acronym>-8601 formats.
+                follow ISO-8601 formats.
             </para></listitem>
         </itemizedlist>
 

documentation/manual/en/module_specs/Zend_Locale-DatesTimes.xml

@@ -330,7 +330,7 @@ print_r ($date);
         <note>
             <title>Database date format</title>
             <para>
-                To parse a database date value (f.e. MySql or MsSql), use <classname>Zend_Date</classname>'s <acronym>ISO</acronym>_8601 format instead of
+                To parse a database date value (f.e. MySql or MsSql), use <classname>Zend_Date</classname>'s ISO_8601 format instead of
                 getDate().
             </para>
         </note>

documentation/manual/en/module_specs/Zend_OpenId-Consumer.xml

@@ -546,13 +546,13 @@ $consumer = new Zend_OpenId_Consumer($storage);
             <listitem>
                 <para>
                     <emphasis>country</emphasis>
-                    - the user's country of residence as specified by <acronym>ISO</acronym>3166
+                    - the user's country of residence as specified by ISO3166
                 </para>
             </listitem>
             <listitem>
                 <para>
                     <emphasis>language</emphasis>
-                    - the user's preferred language as specified by <acronym>ISO</acronym>639
+                    - the user's preferred language as specified by ISO639
                 </para>
             </listitem>
             <listitem>

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

@@ -95,7 +95,7 @@
                 encoding you will sometimes be in the need of other encoding.
                 <classname>Zend_Translate</classname> will not change any encoding which is defined
                 within the source file which means that if your Gettext source
-                is build upon <acronym>ISO</acronym>-8859-1 it will also return strings in this encoding
+                is build upon ISO-8859-1 it will also return strings in this encoding
                 without converting them. There is only one restriction:
             </para>
 
@@ -105,7 +105,7 @@
                 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, <acronym>ISO</acronym>-8859-1 and US-ASCII.
+                UTF-8, ISO-8859-1 and US-ASCII.
             </para>
         </note>
 

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

@@ -110,7 +110,7 @@ $translate->addTranslation('/path/to/german.mo', 'de');
                  Otherwise you will have problems when using two
                  different source encodings.
                  E.g. one of your source files is encoded
-                 with <acronym>ISO</acronym>-8815-11 and another one with CP815.
+                 with ISO-8815-11 and another one with CP815.
                  You can set only one encoding for your source file,
                  so one of your languages probably will not display correctly.
             </para>

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

@@ -148,7 +148,7 @@ base/path/
                 <code>encoding</code>: indicate the character encoding to use
                 with <methodname>htmlentities()</methodname>,
                 <methodname>htmlspecialchars()</methodname>, and other operations. Defaults
-                to <acronym>ISO</acronym>-8859-1 (latin1). May be set via
+                to ISO-8859-1 (latin1). May be set via
                 <methodname>setEncoding()</methodname> or the <code>encoding</code> option
                 to the constructor.
             </para></listitem>