[DOCUMENTATION] English:

 - manual fixes: wrap acronym PDF|INI|IIS|GMT|RSS|CLDR|CET|ISO|DST|UTC|PECL|JSON with <acronym> inside <para>

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

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

@@ -171,7 +171,7 @@
             This (extended) backends stores cache records into a memcached server. <ulink
                 url="http://www.danga.com/memcached/">memcached</ulink> is a high-performance,
             distributed memory object caching system. To use this backend, you need a memcached
-            daemon and <ulink url="http://pecl.php.net/package/memcache">the memcache PECL
+            daemon and <ulink url="http://pecl.php.net/package/memcache">the memcache <acronym>PECL</acronym>
                 extension</ulink>.
         </para>
         <para>

documentation/manual/en/module_specs/Zend_Controller-Router.xml

@@ -45,7 +45,7 @@ RewriteRule ^.*$ index.php [NC,L]
 ]]></programlisting>
 
         <para>
-            The rewrite router can also be used with the IIS webserver (versions &lt;= 7.0) if
+            The rewrite router can also be used with the <acronym>IIS</acronym> webserver (versions &lt;= 7.0) if
             <ulink url="http://www.isapirewrite.com">Isapi_Rewrite</ulink> has been
             installed as an Isapi extension with the following rewrite rule:
         </para>
@@ -57,7 +57,7 @@ RewriteRule ^[\w/\%]*(?:\.(?!(?:js|ico|gif|jpg|png|css|html)$)[\w\%]*$)? /index.
         <note>
             <title>IIS Isapi_Rewrite</title>
             <para>
-                When using IIS, <varname>$_SERVER['REQUEST_URI']</varname> will either
+                When using <acronym>IIS</acronym>, <varname>$_SERVER['REQUEST_URI']</varname> will either
                 not exist, or be set as an empty string. In this case,
                 <classname>Zend_Controller_Request_Http</classname> will attempt to use
                 the <varname>$_SERVER['HTTP_X_REWRITE_URL']</varname> value set by the
@@ -66,7 +66,7 @@ RewriteRule ^[\w/\%]*(?:\.(?!(?:js|ico|gif|jpg|png|css|html)$)[\w\%]*$)? /index.
         </note>
 
         <para>
-            IIS 7.0 introduces a native <acronym>URL</acronym> rewriting module, and it can be
+            <acronym>IIS</acronym> 7.0 introduces a native <acronym>URL</acronym> rewriting module, and it can be
             configured as follows:
         </para>
 
@@ -408,7 +408,7 @@ $router->setGlobalParam('lang', 'en');
         </para>
 
         <para>
-            As an example, consider the following INI file:
+            As an example, consider the following <acronym>INI</acronym> file:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -433,7 +433,7 @@ routes.archive.map.1 = "year"
 ]]></programlisting>
 
         <para>
-            The above INI file can then be read into a <classname>Zend_Config</classname>
+            The above <acronym>INI</acronym> file can then be read into a <classname>Zend_Config</classname>
             object as follows:
         </para>
 
@@ -445,7 +445,7 @@ $router->addConfig($config, 'routes');
 
         <para>
             In the above example, we tell the router to use the 'routes' section
-            of the INI file to use for its routes. Each first-level key under
+            of the <acronym>INI</acronym> file to use for its routes. Each first-level key under
             that section will be used to define a route name; the above example
             defines the routes 'archive' and 'news'. Each route then requires,
             at minimum, a 'route' entry and one or more 'defaults' entries;

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

@@ -288,7 +288,7 @@ print $date->getIso();
             also has an effect to the date itself. Dates are always related to a timezone. Changing
             the timezone for a <classname>Zend_Date</classname> object does not change the time of
             <classname>Zend_Date</classname>. Remember that internally dates are always stored as
-            timestamps and in GMT. So the timezone means how much hours should be substracted or
+            timestamps and in <acronym>GMT</acronym>. So the timezone means how much hours should be substracted or
             added to get the actual global time for the own timezone and region.
         </para>
 

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

@@ -22,7 +22,7 @@
             of the world, the object's timezone will automatically be used to compute the correct
             value, even though the internal timestamp is the same for the same moment in time,
             regardless of the user's physical location in the world. Regardless of the units
-            involved, output must be expressed either as GMT/UTC or localized to a locale. The
+            involved, output must be expressed either as <acronym>GMT</acronym>/UTC or localized to a locale. The
             example output below reflects localization to Europe/GMT+1 hour (e.g. Germany, Austria,
             France).
         </para>
@@ -719,17 +719,17 @@
 
         <para>
             If you need a date format not shown above, then use a self-defined format composed from
-            the ISO format token specifiers below. The following examples illustrate the usage of
-            constants from the table below to create self-defined ISO formats. The format length is
+            the <acronym>ISO</acronym> format token specifiers below. The following examples illustrate the usage of
+            constants from the table below to create self-defined <acronym>ISO</acronym> formats. The format length is
             unlimited. Also, multiple usage of format constants is allowed.
         </para>
 
         <para>
-            The accepted format specifiers can be changed from ISO Format to <acronym>PHP</acronym>'s date format if
-            you are more comfortable with it. However, not all formats defined in the ISO norm are
+            The accepted format specifiers can be changed from <acronym>ISO</acronym> Format to <acronym>PHP</acronym>'s date format if
+            you are more comfortable with it. However, not all formats defined in the <acronym>ISO</acronym> norm are
             supported with <acronym>PHP</acronym>'s date format specifiers. Use the
             <methodname>Zend_Date::setOptions(array('format_type' => 'php'))</methodname> method to
-            switch <classname>Zend_Date</classname> methods from supporting ISO format specifiers to <acronym>PHP</acronym> date() type
+            switch <classname>Zend_Date</classname> methods from supporting <acronym>ISO</acronym> format specifiers to <acronym>PHP</acronym> date() type
             specifiers (see <xref linkend="zend.date.constants.phpformats" /> below).
         </para>
 
@@ -1131,7 +1131,7 @@ print $date->toString("'Era:GGGG='GGGG, ' Date:yy.MMMM.dd'yy.MMMM.dd");
 
         <note>
             <para>
-                Note that the default ISO format differs from <acronym>PHP</acronym>'s format which can be
+                Note that the default <acronym>ISO</acronym> format differs from <acronym>PHP</acronym>'s format which can be
                 irritating if you have not used in previous. Especially the format specifiers
                 for <emphasis>Year and Minute</emphasis> are often not used in the
                 intended way.
@@ -1140,9 +1140,9 @@ print $date->toString("'Era:GGGG='GGGG, ' Date:yy.MMMM.dd'yy.MMMM.dd");
             <para>
                 For <emphasis>year</emphasis> there are two specifiers available
                 which are often mistaken. The <emphasis>Y</emphasis> specifier
-                for the ISO year and the <emphasis>y</emphasis> specifier for the
+                for the <acronym>ISO</acronym> year and the <emphasis>y</emphasis> specifier for the
                 real year. The difference is small but significant.
-                <emphasis>Y</emphasis> calculates the ISO year, which is often used
+                <emphasis>Y</emphasis> calculates the <acronym>ISO</acronym> year, which is often used
                 for calendar formats. See for example the 31. December 2007. The real year is
                 2007, but it is the first day of the first week in the week 1 of the year 2008.
                 So, if you are using 'dd.MM.yyyy' you will get '31.December.2007' but if you use
@@ -1151,7 +1151,7 @@ print $date->toString("'Era:GGGG='GGGG, ' Date:yy.MMMM.dd'yy.MMMM.dd");
             </para>
 
             <para>
-                For <emphasis>minute</emphasis> the difference is not so big. ISO
+                For <emphasis>minute</emphasis> the difference is not so big. <acronym>ISO</acronym>
                 uses the specifier <emphasis>m</emphasis> for the minute, unlike
                 <acronym>PHP</acronym> which uses <emphasis>i</emphasis>. So if you are getting no
                 minute in your format check if you have used the right specifier.
@@ -1164,16 +1164,16 @@ print $date->toString("'Era:GGGG='GGGG, ' Date:yy.MMMM.dd'yy.MMMM.dd");
         <title>Self-Defined OUTPUT Formats Using PHP's date() Format Specifiers</title>
 
         <para>
-            If you are more comfortable with <acronym>PHP</acronym>'s date format specifier than with ISO format
+            If you are more comfortable with <acronym>PHP</acronym>'s date format specifier than with <acronym>ISO</acronym> format
             specifiers, then you can use the
             <methodname>Zend_Date::setOptions(array('format_type' => 'php'))</methodname> method to
-            switch <classname>Zend_Date</classname> methods from supporting ISO format specifiers to <acronym>PHP</acronym> date() type
+            switch <classname>Zend_Date</classname> methods from supporting <acronym>ISO</acronym> format specifiers to <acronym>PHP</acronym> date() type
             specifiers. Afterwards, all format parameters must be given with
             <ulink url="http://php.net/date">PHP's <methodname>date()</methodname> format
                 specifiers</ulink>. The <acronym>PHP</acronym> date format lacks some of the formats supported by the
-            ISO Format, and vice-versa. If you are not already comfortable with it, then use the
-            standard ISO format instead. Also, if you have legacy code using <acronym>PHP</acronym>'s date format,
-            then either manually convert it to the ISO format using <link
+            <acronym>ISO</acronym> Format, and vice-versa. If you are not already comfortable with it, then use the
+            standard <acronym>ISO</acronym> format instead. Also, if you have legacy code using <acronym>PHP</acronym>'s date format,
+            then either manually convert it to the <acronym>ISO</acronym> format using <link
                 linkend="zend.locale.date.normalize">Zend_Locale_Format::convertPhpToIsoFormat()</link>,
             or use <methodname>setOptions()</methodname>. The following examples illustrate the
             usage of constants from the table below to create self-defined formats.
@@ -1195,8 +1195,8 @@ print $date->toString("'Format:D M j G:i:s T Y='D M j G:i:s T Y");
 
         <para>
             The following table shows the list of <acronym>PHP</acronym> date format specifiers with their equivalent
-            <classname>Zend_Date</classname> constants and CLDR/ISO equivalent format specifiers. In most cases, when the
-            CLDR/ISO format does not have an equivalent format specifier, the <acronym>PHP</acronym> format specifier
+            <classname>Zend_Date</classname> constants and <acronym>CLDR</acronym>/ISO equivalent format specifiers. In most cases, when the
+            <acronym>CLDR</acronym>/ISO format does not have an equivalent format specifier, the <acronym>PHP</acronym> format specifier
             is not altered by <methodname>Zend_Locale_Format::convertPhpToIsoFormat()</methodname>,
             and the <classname>Zend_Date</classname> methods then recognize these "peculiar" <acronym>PHP</acronym> format specifiers, even
             when in the default "ISO" format mode.

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

@@ -60,9 +60,9 @@ date_default_timezone_set('Europe/Berlin');
         <para>
             Keep in mind that the timezones <emphasis>UTC</emphasis> and
             <emphasis>GMT</emphasis> do not include Daylight Saving Time. This means that even if
-            you define per hand that <classname>Zend_Date</classname> should work with DST, it would
+            you define per hand that <classname>Zend_Date</classname> should work with <acronym>DST</acronym>, it would
             automatically be switched back for the instances of <classname>Zend_Date</classname>
-            which have been set to UTC or GMT.
+            which have been set to <acronym>UTC</acronym> or <acronym>GMT</acronym>.
         </para>
     </sect2>
 
@@ -103,7 +103,7 @@ date_default_timezone_set('Europe/Berlin');
                 </para>
                 <para>
                     Although <acronym>PHP</acronym> 5.2 docs state, "The valid range of a timestamp is typically from
-                    Fri, 13 Dec 1901 20:45:54 GMT to Tue, 19 Jan 2038 03:14:07 GMT,"
+                    Fri, 13 Dec 1901 20:45:54 <acronym>GMT</acronym> to Tue, 19 Jan 2038 03:14:07 <acronym>GMT</acronym>,"
                     <classname>Zend_Date</classname> supports a nearly unlimited range, with the
                     help of the BCMath extension. If BCMath is not available, then <classname>Zend_Date</classname> will
                     have reduced support only for timestamps within the range of the
@@ -118,10 +118,10 @@ date_default_timezone_set('Europe/Berlin');
             </listitem>
             <listitem>
                 <para>
-                    Support for ISO_8601 date specifications
+                    Support for <acronym>ISO</acronym>_8601 date specifications
                 </para>
                 <para>
-                    ISO_8601 date specifications are supported. Even partially compliant ISO_8601
+                    <acronym>ISO</acronym>_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>
@@ -129,7 +129,7 @@ date_default_timezone_set('Europe/Berlin');
                     <classname>Zend_Date</classname> using the <link
                         linkend="zend.date.constants.list">Zend_Date::ISO_8601</link> format
                     specification constant. When date strings conform to "Y/m/d" or "Y-m-d H:i:s",
-                    according to <acronym>PHP</acronym> date() format tokens, use <classname>Zend_Date</classname>'s built-in support for ISO
+                    according to <acronym>PHP</acronym> date() format tokens, use <classname>Zend_Date</classname>'s built-in support for <acronym>ISO</acronym>
                     8601 formatted dates.
                 </para>
             </listitem>

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

@@ -20,12 +20,12 @@
             <para>
                 Several methods use date format strings, in a way similar to <acronym>PHP</acronym>'s
                 <methodname>date()</methodname>. If you are more comfortable with <acronym>PHP</acronym>'s date format
-                specifier than with ISO format specifiers, then you can use
+                specifier than with <acronym>ISO</acronym> format specifiers, then you can use
                 <methodname>Zend_Date::setOptions(array('format_type' => 'php'))</methodname>.
                 Afterward, use <acronym>PHP</acronym>'s date format specifiers for all functions which accept a
                 <varname>$format</varname> parameter. Use
                 <methodname>Zend_Date::setOptions(array('format_type' => 'iso'))</methodname> to
-                switch back to the default mode of supporting only ISO date format tokens. For a
+                switch back to the default mode of supporting only <acronym>ISO</acronym> date format tokens. For a
                 list of supported format codes, see
                 <xref linkend="zend.date.constants.phpformats" />
             </para>
@@ -37,34 +37,34 @@
             <title>DST and Date Math</title>
 
             <para>
-                When dates are manipulated, sometimes they cross over a DST change, normally
+                When dates are manipulated, sometimes they cross over a <acronym>DST</acronym> change, normally
                 resulting in the date losing or gaining an hour. For exmaple, when adding months to
-                a date before a DST change, if the resulting date is after the DST change, then the
+                a date before a <acronym>DST</acronym> change, if the resulting date is after the <acronym>DST</acronym> change, then the
                 resulting date will appear to lose or gain an hour, resulting in the time value of
                 the date changing. For boundary dates, such as midnight of the first or last day of
                 a month, adding enough months to cross a date boundary results in the date losing an
                 hour and becoming the last hour of the preceding month, giving the appearance of an
-                "off by 1" error. To avoid this situation, the DST change ignored by using the
-                <code>fix_dst</code> option. When crossing the Summer/Winter DST boundary, normally
+                "off by 1" error. To avoid this situation, the <acronym>DST</acronym> change ignored by using the
+                <code>fix_dst</code> option. When crossing the Summer/Winter <acronym>DST</acronym> boundary, normally
                 an hour is substracted or added depending on the date. For example, date math
-                crossing the Spring DST leads to a date having a day value one less than expected,
+                crossing the Spring <acronym>DST</acronym> leads to a date having a day value one less than expected,
                 if the time part of the date was originally 00:00:00. Since <classname>Zend_Date</classname> is based on
                 timestamps, and not calendar dates with a time component, the timestamp loses an
                 hour, resulting in the date having a calendar day value one less than expected. To
                 prevent such problems use the option <code>fix_dst</code>, which defaults to <constant>TRUE</constant>,
-                causing DST to have no effect on date "math" (<methodname>addMonth()</methodname>,
+                causing <acronym>DST</acronym> to have no effect on date "math" (<methodname>addMonth()</methodname>,
                 <methodname>subMonth()</methodname>). Use
                 <methodname>Zend_Date::setOptions(array('fix_dst' => false))</methodname> to
-                enable the subtraction or addition of the DST adjustment when performing date
+                enable the subtraction or addition of the <acronym>DST</acronym> adjustment when performing date
                 "math".
             </para>
 
             <para>
                 <emphasis>If your actual timezone within the instance of
-                <classname>Zend_Date</classname> is set to UTC or GMT the option
+                <classname>Zend_Date</classname> is set to <acronym>UTC</acronym> or <acronym>GMT</acronym> the option
                 <code>'fix_dst'</code> will not be used</emphasis> because these two timezones do
-                not work with DST. When you change the timezone for this instance again to a
-                timezone which is not UTC or GMT the previous set 'fix_dst' option will be used
+                not work with <acronym>DST</acronym>. When you change the timezone for this instance again to a
+                timezone which is not <acronym>UTC</acronym> or <acronym>GMT</acronym> the previous set 'fix_dst' option will be used
                 again for date "math".
             </para>
         </sect3>
@@ -136,7 +136,7 @@
             object, it will have an associated timezone, but an internal representation using
             standard <ulink url="http://en.wikipedia.org/wiki/Unix_Time">UNIX timestamps</ulink>.
             In order for a date to be rendered in a localized manner, a timezone must be known
-            first. The default timezone is always GMT/UTC. To examine an object's timezone use
+            first. The default timezone is always <acronym>GMT</acronym>/UTC. To examine an object's timezone use
             <methodname>getTimeZone()</methodname>. To change an object's timezone, use
             <methodname>setTimeZone()</methodname>. All manipulations of these objects are assumed to be
             relative to this timezone.
@@ -823,7 +823,7 @@ print $date;
                                     </listitem>
                                     <listitem>
                                         <para>
-                                            Delay of timezone to GMT as
+                                            Delay of timezone to <acronym>GMT</acronym> as
                                             '<emphasis>gmtsecs</emphasis>'
                                             (<constant>Zend_Date::GMT_SECS</constant>)
                                         </para>

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

@@ -37,11 +37,11 @@
                         All dates and times, even ambiguous ones (e.g. no year), are represented
                         internally as absolute moments in time, represented as a UNIX timestamp
                         expressing the difference between the desired time and January 1st, 1970
-                        00:00:00 GMT/UTC. This was only possible, because
+                        00:00:00 <acronym>GMT</acronym>/UTC. This was only possible, because
                         <classname>Zend_Date</classname> is not limited to UNIX timestamps nor
                         integer values. The BCMath extension is required to support extremely large
-                        dates outside of the range Fri, 13 Dec 1901 20:45:54 GMT to Tue, 19 Jan 2038
-                        03:14:07 GMT. Additional, tiny math errors may arise due to the inherent
+                        dates outside of the range Fri, 13 Dec 1901 20:45:54 <acronym>GMT</acronym> to Tue, 19 Jan 2038
+                        03:14:07 <acronym>GMT</acronym>. Additional, tiny math errors may arise due to the inherent
                         limitations of float data types and rounding, unless using the BCMath
                         extension.
                     </para>
@@ -52,7 +52,7 @@
                     </para>
                     <para>
                         Thus, an instance object representing three hours would be expressed as
-                        three hours after January 1st, 1970 00:00:00 GMT/UTC -i.e. 0 + 3 * 60 * 60 =
+                        three hours after January 1st, 1970 00:00:00 <acronym>GMT</acronym>/UTC -i.e. 0 + 3 * 60 * 60 =
                         10800.
                     </para>
                 </listitem>

documentation/manual/en/module_specs/Zend_Db_Adapter.xml

@@ -2025,7 +2025,7 @@ if (!is_null($version)) {
                     <para>
                         You must use at least <acronym>PDO</acronym>_IBM extension version 1.2.2.
                         If you have an earlier version of this extension, you
-                        must upgrade the <acronym>PDO</acronym>_IBM extension from PECL.
+                        must upgrade the <acronym>PDO</acronym>_IBM extension from <acronym>PECL</acronym>.
                     </para>
                 </listitem>
             </itemizedlist>

documentation/manual/en/module_specs/Zend_Db_Profiler-Firebug.xml

@@ -12,7 +12,7 @@
     <para>
         All data is sent via the <classname>Zend_Wildfire_Channel_HttpHeaders</classname>
         component which uses <acronym>HTTP</acronym> headers to ensure the page content is not
-        disturbed. Debugging <acronym>AJAX</acronym> requests that require clean JSON and <acronym>XML</acronym>
+        disturbed. Debugging <acronym>AJAX</acronym> requests that require clean <acronym>JSON</acronym> and <acronym>XML</acronym>
         responses is possible with this approach.
     </para>
 

documentation/manual/en/module_specs/Zend_Dojo-Data.xml

@@ -15,7 +15,7 @@
         dojo.data is often used with XmlHttpRequest to pull dynamic data from
         the server. The primary mechanism for this is to extend the
         QueryReadStore to point at a <acronym>URL</acronym> and specify the query information. The
-        server side then returns data in the following JSON format:
+        server side then returns data in the following <acronym>JSON</acronym> format:
     </para>
 
     <programlisting language="javascript"><![CDATA[
@@ -32,7 +32,7 @@
     <para>
         <classname>Zend_Dojo_Data</classname> provides a simple interface for building
         such structures programmatically, interacting with them, and serializing
-        them to an array or JSON.
+        them to an array or <acronym>JSON</acronym>.
     </para>
 
     <sect2 id="zend.dojo.data.usage">
@@ -140,7 +140,7 @@ $data->setLabel('name');
 
         <para>
             Finally, you can also load a <classname>Zend_Dojo_Data</classname> item from a
-            dojo.data JSON array, using the <methodname>fromJson()</methodname> method.
+            dojo.data <acronym>JSON</acronym> array, using the <methodname>fromJson()</methodname> method.
         </para>
 
         <example id="zend.dojo.data.usage.populate">
@@ -267,7 +267,7 @@ echo count($data), " items found!";
 
         <para>
             Finally, as the class implements <methodname>__toString()</methodname>, you can
-            also cast it to JSON simply by echoing it or casting to string:
+            also cast it to <acronym>JSON</acronym> simply by echoing it or casting to string:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -373,7 +373,7 @@ $json = (string) $data; // cast to string == cast to JSON
                 </para></listitem>
 
                 <listitem><para>
-                    <methodname>toJson()</methodname>: cast the object to a JSON
+                    <methodname>toJson()</methodname>: cast the object to a <acronym>JSON</acronym>
                     representation.
                 </para></listitem>
             </itemizedlist>

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 ISO-8601 formats.
+                in the time chooser; must follow <acronym>ISO</acronym>-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 ISO-8601 formats.
+                follow <acronym>ISO</acronym>-8601 formats.
             </para></listitem>
         </itemizedlist>
 

documentation/manual/en/module_specs/Zend_Feed-ConsumingAtom.xml

@@ -7,9 +7,9 @@
         <classname>Zend_Feed_Atom</classname> is used in much the same way as
         <classname>Zend_Feed_Rss</classname>. It provides the same access to feed-level properties
         and iteration over entries in the feed. The main difference is in the structure of the Atom
-        protocol itself. Atom is a successor to RSS; it is more generalized protocol and it is
+        protocol itself. Atom is a successor to <acronym>RSS</acronym>; it is more generalized protocol and it is
         designed to deal more easily with feeds that provide their full content inside the feed,
-        splitting RSS' <code>description</code> tag into two elements, <code>summary</code> and
+        splitting <acronym>RSS</acronym>' <code>description</code> tag into two elements, <code>summary</code> and
         <code>content</code>, for that purpose.
     </para>
 
@@ -36,7 +36,7 @@ foreach ($feed as $entry) {
     <para>
         <itemizedlist>
             <listitem>
-                <para><code>title</code> - The feed's title, same as RSS's channel title</para>
+                <para><code>title</code> - The feed's title, same as <acronym>RSS</acronym>'s channel title</para>
             </listitem>
             <listitem>
                 <para><code>id</code> - Every feed and entry in Atom has a unique identifier</para>
@@ -47,14 +47,14 @@ foreach ($feed as $entry) {
                     <code>type</code> attribute
                 </para>
                 <para>
-                    The equivalent to RSS's channel link would be <code>type="text/html"</code>. If
+                    The equivalent to <acronym>RSS</acronym>'s channel link would be <code>type="text/html"</code>. If
                     the link is to an alternate version of the same content that's in the feed, it
                     would have a <code>rel="alternate"</code> attribute.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <code>subtitle</code> - The feed's description, equivalent to RSS' channel
+                    <code>subtitle</code> - The feed's description, equivalent to <acronym>RSS</acronym>' channel
                     description
                 </para>
                 <para><code>author->name()</code> - The feed author's name</para>
@@ -73,7 +73,7 @@ foreach ($feed as $entry) {
                 <para><code>id</code> - The entry's unique identifier</para>
             </listitem>
             <listitem>
-                <para><code>title</code> - The entry's title, same as RSS item titles</para>
+                <para><code>title</code> - The entry's title, same as <acronym>RSS</acronym> item titles</para>
             </listitem>
             <listitem>
                 <para>

documentation/manual/en/module_specs/Zend_Feed-ConsumingRss.xml

@@ -3,7 +3,7 @@
 <sect1 id="zend.feed.consuming-rss">
     <title>Consuming an RSS Feed</title>
     <para>
-        Reading an RSS feed is as simple as instantiating a <classname>Zend_Feed_Rss</classname>
+        Reading an <acronym>RSS</acronym> feed is as simple as instantiating a <classname>Zend_Feed_Rss</classname>
         object with the <acronym>URL</acronym> of the feed:
     </para>
     <programlisting language="php"><![CDATA[
@@ -15,7 +15,7 @@ $channel = new Zend_Feed_Rss('http://rss.example.com/channelName');
     </para>
 
     <para>
-        Once you have a feed object, you can access any of the standard RSS "channel" properties
+        Once you have a feed object, you can access any of the standard <acronym>RSS</acronym> "channel" properties
         directly on the object:
     </para>
     <programlisting language="php"><![CDATA[
@@ -51,8 +51,8 @@ foreach ($channel as $item) {
 }
 ]]></programlisting>
     <para>
-        If you are not familiar with RSS, here are the standard elements you can expect to be
-        available in an RSS channel and in individual RSS items (entries).
+        If you are not familiar with <acronym>RSS</acronym>, here are the standard elements you can expect to be
+        available in an <acronym>RSS</acronym> channel and in individual <acronym>RSS</acronym> items (entries).
     </para>
 
     <para>
@@ -100,7 +100,7 @@ foreach ($channel as $item) {
     </para>
 
     <para>
-        RSS <code>&lt;item&gt;</code> elements do not have any strictly required elements. However,
+        <acronym>RSS</acronym> <code>&lt;item&gt;</code> elements do not have any strictly required elements. However,
         either <code>title</code> or <code>description</code> must be present.
     </para>
 
@@ -153,7 +153,7 @@ if ($item->propname()) {
     </para>
 
     <para>
-        For further information, the official RSS 2.0 specification is available at: <ulink
+        For further information, the official <acronym>RSS</acronym> 2.0 specification is available at: <ulink
             url="http://blogs.law.harvard.edu/tech/rss">http://blogs.law.harvard.edu/tech/rss</ulink>
     </para>
 </sect1>

documentation/manual/en/module_specs/Zend_Feed-Importing.xml

@@ -29,7 +29,7 @@ $feedFromPHP = Zend_Feed::importString($feedString);
     <para>
         In each of the examples above, an object of a class that extends
         <classname>Zend_Feed_Abstract</classname> is returned upon success, depending on the type of
-        the feed. If an RSS feed were retrieved via one of the import methods above, then a
+        the feed. If an <acronym>RSS</acronym> feed were retrieved via one of the import methods above, then a
         <classname>Zend_Feed_Rss</classname> object would be returned. On the other hand, if an Atom
         feed were imported, then a <classname>Zend_Feed_Atom</classname> object is returned. The
         import methods will also throw a <classname>Zend_Feed_Exception</classname> object upon
@@ -257,7 +257,7 @@ array(
                 <itemizedlist>
                     <listitem>
                         <para>
-                            RSS 2.0 specification: <ulink
+                            <acronym>RSS</acronym> 2.0 specification: <ulink
                                 url="http://blogs.law.harvard.edu/tech/rss">RSS 2.0</ulink>
                         </para>
                     </listitem>

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

@@ -3,7 +3,7 @@
 <sect1 id="zend.feed.introduction">
     <title>Introduction</title>
     <para>
-        <classname>Zend_Feed</classname> provides functionality for consuming RSS and Atom feeds.
+        <classname>Zend_Feed</classname> provides functionality for consuming <acronym>RSS</acronym> and Atom feeds.
         It provides a natural syntax for accessing elements of feeds, feed attributes, and entry
         attributes. <classname>Zend_Feed</classname> also has extensive support for modifying feed
         and entry structure with the same natural syntax, and turning the result back into <acronym>XML</acronym>. In
@@ -15,12 +15,12 @@
         Programmatically, <classname>Zend_Feed</classname> consists of a base
         <classname>Zend_Feed</classname> class, abstract <classname>Zend_Feed_Abstract</classname>
         and <classname>Zend_Feed_Entry_Abstract</classname> base classes for representing Feeds and
-        Entries, specific implementations of feeds and entries for RSS and Atom, and a
+        Entries, specific implementations of feeds and entries for <acronym>RSS</acronym> and Atom, and a
         behind-the-scenes helper for making the natural syntax magic work.
     </para>
 
     <para>
-        In the example below, we demonstrate a simple use case of retrieving an RSS feed and
+        In the example below, we demonstrate a simple use case of retrieving an <acronym>RSS</acronym> feed and
         saving relevant portions of the feed data to a simple <acronym>PHP</acronym> array, which could then be used
         for printing the data, storing to a database, etc.
     </para>
@@ -28,9 +28,9 @@
     <note>
         <title>Be aware</title>
         <para>
-            Many RSS feeds have different channel and item properties available. The RSS
+            Many <acronym>RSS</acronym> feeds have different channel and item properties available. The <acronym>RSS</acronym>
             specification provides for many optional properties, so be aware of this when writing
-            code to work with RSS data.
+            code to work with <acronym>RSS</acronym> data.
         </para>
     </note>
 

documentation/manual/en/module_specs/Zend_Form-Forms.xml

@@ -1405,7 +1405,7 @@ if (!$form->isValidPartial($data)) {
         <para>
             When validating elements or groups of elements for an <acronym>AJAX</acronym> request,
             you will typically be validating a subset of the form, and want the
-            response back in JSON. <methodname>processAjax()</methodname> does precisely
+            response back in <acronym>JSON</acronym>. <methodname>processAjax()</methodname> does precisely
             that:
         </para>
 
@@ -1414,7 +1414,7 @@ $json = $form->processAjax($data);
 ]]></programlisting>
 
         <para>
-            You can then simply send the JSON response to the client. If the
+            You can then simply send the <acronym>JSON</acronym> response to the client. If the
             form is valid, this will be a boolean true response. If not, it will
             be a javascript object containing key/message pairs, where each
             'message' is an array of validation error messages.

documentation/manual/en/module_specs/Zend_Form-QuickStart.xml

@@ -395,7 +395,7 @@ if ($form->isValidPartial($_POST)) {
         <para>
             An additional method, <methodname>processAjax()</methodname>, can be used
             for validating partial forms. Unlike <methodname>isValidPartial()</methodname>,
-            it returns a JSON-formatted string containing error messages on
+            it returns a <acronym>JSON</acronym>-formatted string containing error messages on
             failure.
         </para>
 
@@ -562,7 +562,7 @@ class UserController extends Zend_Controller_Action
             <classname>Zend_Config</classname>; you can either pass a
             <classname>Zend_Config</classname> object to the constructor or pass it in
             with <methodname>setConfig()</methodname>. Let's look at how we might create the
-            above form using an INI file. First, let's follow the
+            above form using an <acronym>INI</acronym> file. First, let's follow the
             recommendations, and place our configurations into sections
             reflecting the release location, and focus on the 'development'
             section. Next, we'll setup a section for the given controller

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

@@ -432,7 +432,7 @@ $client->request("PUT");
         <title>The Test Adapter</title>
         <para>
             Sometimes, it is very hard to test code that relies on <acronym>HTTP</acronym> connections.
-            For example, testing an application that pulls an RSS feed from a remote
+            For example, testing an application that pulls an <acronym>RSS</acronym> feed from a remote
             server will require a network connection, which is not always available.
         </para>
         <para>

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

@@ -4,22 +4,22 @@
     <title>Introduction</title>
     <para>
         <classname>Zend_Json</classname> provides convenience methods for serializing
-        native <acronym>PHP</acronym> to JSON and decoding JSON to native <acronym>PHP</acronym>. For more information
-        on JSON, <ulink url="http://www.json.org/">visit the JSON project
+        native <acronym>PHP</acronym> to <acronym>JSON</acronym> and decoding <acronym>JSON</acronym> to native <acronym>PHP</acronym>. For more information
+        on <acronym>JSON</acronym>, <ulink url="http://www.json.org/">visit the <acronym>JSON</acronym> project
         site</ulink>.
     </para>
     <para>
-        JSON, JavaScript Object Notation, can be used for data
-        interchange between JavaScript and other languages. Since JSON can be
+        <acronym>JSON</acronym>, JavaScript Object Notation, can be used for data
+        interchange between JavaScript and other languages. Since <acronym>JSON</acronym> can be
         directly evaluated by JavaScript, it is a more efficient and lightweight
         format than <acronym>XML</acronym> for exchanging data with JavaScript clients.
     </para>
 
     <para>
         In addition, <classname>Zend_Json</classname> provides a useful way to convert any
-        arbitrary <acronym>XML</acronym> formatted string into a JSON formatted string. This built-in
+        arbitrary <acronym>XML</acronym> formatted string into a <acronym>JSON</acronym> formatted string. This built-in
         feature will enable <acronym>PHP</acronym> developers to transform the enterprise data
-        encoded in <acronym>XML</acronym> format into JSON format before sending it to browser-based
+        encoded in <acronym>XML</acronym> format into <acronym>JSON</acronym> format before sending it to browser-based
         Ajax client applications. It provides an easy way to do dynamic data
         conversion on the server-side code thereby avoiding unnecessary <acronym>XML</acronym>
         parsing in the browser-side applications. It offers a nice utility

documentation/manual/en/module_specs/Zend_Json-Objects.xml

@@ -6,11 +6,11 @@
     <sect2 id="zend.json.advanced.objects1">
         <title>JSON Objects</title>
         <para>
-            When encoding <acronym>PHP</acronym> objects as JSON, all public properties of that object
-            will be encoded in a JSON object.
+            When encoding <acronym>PHP</acronym> objects as <acronym>JSON</acronym>, all public properties of that object
+            will be encoded in a <acronym>JSON</acronym> object.
         </para>
         <para>
-            JSON does not allow object references, so care should be taken not to
+            <acronym>JSON</acronym> does not allow object references, so care should be taken not to
             encode objects with recursive references. If you have issues with
             recursion, <methodname>Zend_Json::encode()</methodname> and
             <methodname>Zend_Json_Encoder::encode()</methodname> allow an optional second
@@ -18,15 +18,15 @@
             exception will be thrown.
         </para>
         <para>
-            Decoding JSON objects poses an additional difficulty, however, since
+            Decoding <acronym>JSON</acronym> objects poses an additional difficulty, however, since
             Javascript objects correspond most closely to <acronym>PHP</acronym>'s associative array.
             Some suggest that a class identifier should be passed, and an object
             instance of that class should be created and populated with the
-            key/value pairs of the JSON object; others feel this could pose a
+            key/value pairs of the <acronym>JSON</acronym> object; others feel this could pose a
             substantial security risk.
         </para>
         <para>
-            By default, <classname>Zend_Json</classname> will decode JSON objects as
+            By default, <classname>Zend_Json</classname> will decode <acronym>JSON</acronym> objects as
             associative arrays. However, if you desire an object returned, you can
             specify this:
         </para>
@@ -36,12 +36,12 @@ $phpNative = Zend_Json::decode($encodedValue, Zend_Json::TYPE_OBJECT);
 ]]></programlisting>
         <para>
             Any objects thus decoded are returned as <code>StdClass</code> objects
-            with properties corresponding to the key/value pairs in the JSON
+            with properties corresponding to the key/value pairs in the <acronym>JSON</acronym>
             notation.
         </para>
         <para>
             The recommendation of Zend Framework is that the individual
-            developer should decide how to decode JSON objects. If an object of a
+            developer should decide how to decode <acronym>JSON</acronym> objects. If an object of a
             specified type should be created, it can be created in the developer
             code and populated with the values decoded using <classname>Zend_Json</classname>.
         </para>
@@ -54,7 +54,7 @@ $phpNative = Zend_Json::decode($encodedValue, Zend_Json::TYPE_OBJECT);
             If you are encoding <acronym>PHP</acronym> objects by default the encoding mechanism
             can only access public properties of these objects. When a method
             <methodname>toJson()</methodname> is implemented on an object to encode, <classname>Zend_Json</classname>
-            calls this method and expects the object to return a JSON representation
+            calls this method and expects the object to return a <acronym>JSON</acronym> representation
             of its internal state.
         </para>
     </sect2>
@@ -66,7 +66,7 @@ $phpNative = Zend_Json::decode($encodedValue, Zend_Json::TYPE_OBJECT);
             <classname>Zend_Json</classname> has two different modes depending if ext/json is enabled in
             your <acronym>PHP</acronym> installation or not. If ext/json is installed by default
             <methodname>json_encode()</methodname> and <methodname>json_decode()</methodname> functions
-            are used for encoding and decoding JSON. If ext/json is not installed
+            are used for encoding and decoding <acronym>JSON</acronym>. If ext/json is not installed
             a Zend Framework implementation in <acronym>PHP</acronym> code is used for en-/decoding.
             This is considerably slower than using the php extension, but behaves
             exactly the same.
@@ -87,9 +87,9 @@ Zend_Json::$useBuiltinEncoderDecoder = true:
 
         <para>
             Javascript makes heavy use of anonymnous function callbacks, which
-            can be saved within JSON object variables. Still they only work if not
+            can be saved within <acronym>JSON</acronym> object variables. Still they only work if not
             returned inside double qoutes, which <classname>Zend_Json</classname> naturally does.
-            With the Expression support for <classname>Zend_Json</classname> support you can encode JSON
+            With the Expression support for <classname>Zend_Json</classname> support you can encode <acronym>JSON</acronym>
             objects with valid javascript callbacks. This works for both <methodname>json_encode()</methodname>
             or the internal encoder.
         </para>

documentation/manual/en/module_specs/Zend_Json-Server.xml

@@ -17,8 +17,8 @@
     </para>
 
     <para>
-        JSON-RPC is a lightweight Remote Procedure Call protocol that utilizes
-        JSON for its messaging envelopes. This JSON-RPC implementation follows
+        <acronym>JSON</acronym>-RPC is a lightweight Remote Procedure Call protocol that utilizes
+        <acronym>JSON</acronym> for its messaging envelopes. This <acronym>JSON</acronym>-RPC implementation follows
         <acronym>PHP</acronym>'s <ulink
             url="http://us.php.net/manual/en/function.soap-soapserver-construct.php">SoapServer</ulink>
         <acronym>API</acronym>. This means that in a typical situation, you will simply:
@@ -46,7 +46,7 @@
 
     <para>
         <classname>Zend_Json_Server</classname> listens for POST requests only at this
-        time; fortunately, most JSON-RPC client implementations in the wild at
+        time; fortunately, most <acronym>JSON</acronym>-RPC client implementations in the wild at
         the time of this writing will only POST requests as it is. This makes it
         simple to utilize the same server end point to both handle requests as
         well as to deliver the service SMD, as is shown in the next example.
@@ -56,7 +56,7 @@
         <title>Zend_Json_Server Usage</title>
 
         <para>
-            First, let's define a class we wish to expose via the JSON-RPC
+            First, let's define a class we wish to expose via the <acronym>JSON</acronym>-RPC
             server. We'll call the class 'Calculator', and define methods for
             'add', 'subtract', 'multiply', and 'divide':
         </para>
@@ -141,7 +141,7 @@ $server->handle();
 
         <para>
             However, this will not address the issue of returning an SMD so that
-            the JSON-RPC client can autodiscover methods. That can be
+            the <acronym>JSON</acronym>-RPC client can autodiscover methods. That can be
             accomplished by determining the <acronym>HTTP</acronym> request method, and then
             specifying some server metadata:
         </para>
@@ -168,7 +168,7 @@ $server->handle();
 ]]></programlisting>
 
         <para>
-            If utilizing the JSON-RPC server with Dojo toolkit, you will also
+            If utilizing the <acronym>JSON</acronym>-RPC server with Dojo toolkit, you will also
             need to set a special compatibility flag to ensure that the two
             interoperate properly:
         </para>
@@ -207,7 +207,7 @@ $server->handle();
             <title>Zend_Json_Server</title>
 
             <para>
-                <classname>Zend_Json_Server</classname> is the core class in the JSON-RPC
+                <classname>Zend_Json_Server</classname> is the core class in the <acronym>JSON</acronym>-RPC
                 offering; it handles all requests and returns the response
                 payload. It has the following methods:
             </para>
@@ -217,12 +217,12 @@ $server->handle();
                         userland function to attach to the server.</para></listitem>
                 <listitem><para><methodname>setClass($class)</methodname>: Specify a class
                         or object to attach to the server; all public methods of
-                        that item will be exposed as JSON-RPC methods.</para></listitem>
+                        that item will be exposed as <acronym>JSON</acronym>-RPC methods.</para></listitem>
                 <listitem><para><code>fault($fault = null, $code = 404, $data =
                         null)</code>: Create and return a
                         <classname>Zend_Json_Server_Error</classname> object.</para></listitem>
                 <listitem><para><methodname>handle($request = false)</methodname>: Handle a
-                        JSON-RPC request; optionally, pass a
+                        <acronym>JSON</acronym>-RPC request; optionally, pass a
                         <classname>Zend_Json_Server_Request</classname> object to utilize
                         (creates one by default).</para></listitem>
                 <listitem><para><methodname>getFunctions()</methodname>: Return a list of
@@ -253,12 +253,12 @@ $server->handle();
             <title>Zend_Json_Server_Request</title>
 
             <para>
-                The JSON-RPC request environment is encapsulated in the
+                The <acronym>JSON</acronym>-RPC request environment is encapsulated in the
                 <classname>Zend_Json_Server_Request</classname> object. This object allows
-                you to set necessary portions of the JSON-RPC request, including
-                the request ID, parameters, and JSON-RPC specification version.
-                It has the ability to load itself via JSON or a set of options,
-                and can render itself as JSON via the <methodname>toJson()</methodname>
+                you to set necessary portions of the <acronym>JSON</acronym>-RPC request, including
+                the request ID, parameters, and <acronym>JSON</acronym>-RPC specification version.
+                It has the ability to load itself via <acronym>JSON</acronym> or a set of options,
+                and can render itself as <acronym>JSON</acronym> via the <methodname>toJson()</methodname>
                 method.
             </para>
 
@@ -300,22 +300,22 @@ $server->handle();
                 <listitem><para><methodname>getId()</methodname>: Retrieve the request
                         identifier.</para></listitem>
                 <listitem><para><methodname>setVersion($version)</methodname>: Set the
-                        JSON-RPC specification version the request conforms to.
+                        <acronym>JSON</acronym>-RPC specification version the request conforms to.
                         May be either '1.0' or '2.0'.</para></listitem>
-                <listitem><para><methodname>getVersion()</methodname>: Retrieve the JSON-RPC
+                <listitem><para><methodname>getVersion()</methodname>: Retrieve the <acronym>JSON</acronym>-RPC
                         specification version used by the
                         request.</para></listitem>
                 <listitem><para><methodname>loadJson($json)</methodname>: Load the request
-                        object from a JSON string.</para></listitem>
+                        object from a <acronym>JSON</acronym> string.</para></listitem>
                 <listitem><para><methodname>toJson()</methodname>: Render the request as
-                        a JSON string.</para></listitem>
+                        a <acronym>JSON</acronym> string.</para></listitem>
             </itemizedlist>
 
             <para>
                 An <acronym>HTTP</acronym> specific version is available via
                 <classname>Zend_Json_Server_Request_Http</classname>. This class will
                 retrieve the request via <code>php://input</code>, and allows
-                access to the raw JSON via the <methodname>getRawJson()</methodname> method.
+                access to the raw <acronym>JSON</acronym> via the <methodname>getRawJson()</methodname> method.
             </para>
         </sect3>
 
@@ -323,10 +323,10 @@ $server->handle();
             <title>Zend_Json_Server_Response</title>
 
             <para>
-                The JSON-RPC response payload is encapsulated in the
+                The <acronym>JSON</acronym>-RPC response payload is encapsulated in the
                 <classname>Zend_Json_Server_Response</classname> object. This object allows
                 you to set the return value of the request, whether or not the
-                response is an error, the request identifier, the JSON-RPC
+                response is an error, the request identifier, the <acronym>JSON</acronym>-RPC
                 specification version the response conforms to, and optionally
                 the service map.
             </para>
@@ -342,7 +342,7 @@ $server->handle();
                     result.</para></listitem>
                 <listitem><para><code>setError(Zend_Json_Server_Error
                     $error)</code>: Set an error object. If set, this will be
-                    used as the response when serializing to JSON.</para></listitem>
+                    used as the response when serializing to <acronym>JSON</acronym>.</para></listitem>
                 <listitem><para><methodname>getError()</methodname>: Retrieve the error
                     object, if any.</para></listitem>
                 <listitem><para><methodname>isError()</methodname>: Whether or not the
@@ -353,11 +353,11 @@ $server->handle();
                 <listitem><para><methodname>getId()</methodname>: Retrieve the request
                     identifier.</para></listitem>
                 <listitem><para><methodname>setVersion($version)</methodname>: Set the
-                    JSON-RPC version the response conforms to.</para></listitem>
-                <listitem><para><methodname>getVersion()</methodname>: Retrieve the JSON-RPC
+                    <acronym>JSON</acronym>-RPC version the response conforms to.</para></listitem>
+                <listitem><para><methodname>getVersion()</methodname>: Retrieve the <acronym>JSON</acronym>-RPC
                     version the response conforms to.</para></listitem>
                 <listitem><para><methodname>toJson()</methodname>: Serialize the response to
-                    JSON. If the response is an error response, serializes the
+                    <acronym>JSON</acronym>. If the response is an error response, serializes the
                     error object.</para></listitem>
                 <listitem><para><methodname>setServiceMap($serviceMap)</methodname>: Set the
                     service map object for the response.</para></listitem>
@@ -369,7 +369,7 @@ $server->handle();
                 An <acronym>HTTP</acronym> specific version is available via
                 <classname>Zend_Json_Server_Response_Http</classname>. This class will
                 send the appropriate <acronym>HTTP</acronym> headers as well as serialize the
-                response as JSON.
+                response as <acronym>JSON</acronym>.
             </para>
         </sect3>
 
@@ -377,7 +377,7 @@ $server->handle();
             <title>Zend_Json_Server_Error</title>
 
             <para>
-                JSON-RPC has a special format for reporting error conditions.
+                <acronym>JSON</acronym>-RPC has a special format for reporting error conditions.
                 All errors need to provide, minimally, an error message and error
                 code; optionally, they can provide additional data, such as a
                 backtrace.
@@ -415,7 +415,7 @@ $server->handle();
                     array. The array will contain the keys 'code', 'message',
                     and 'data'.</para></listitem>
                 <listitem><para><methodname>toJson()</methodname>: Cast the error to a
-                    JSON-RPC error representation.</para></listitem>
+                    <acronym>JSON</acronym>-RPC error representation.</para></listitem>
             </itemizedlist>
         </sect3>
 
@@ -423,12 +423,12 @@ $server->handle();
             <title>Zend_Json_Server_Smd</title>
 
             <para>
-                SMD stands for Service Mapping Description, a JSON schema that
+                SMD stands for Service Mapping Description, a <acronym>JSON</acronym> schema that
                 defines how a client can interact with a particular web service.
                 At the time of this writing, the <ulink
                     url="http://groups.google.com/group/json-schema/web/service-mapping-description-proposal">specification</ulink>
                 has not yet been formally ratified, but it is in use already
-                within Dojo toolkit as well as other JSON-RPC consumer clients.
+                within Dojo toolkit as well as other <acronym>JSON</acronym>-RPC consumer clients.
             </para>
 
             <para>
@@ -436,7 +436,7 @@ $server->handle();
                 method of transport (POST, GET, TCP/IP, etc), the request
                 envelope type (usually based on the protocol of the server), the
                 target <acronym>URL</acronym> of the service provider, and a map of services
-                available. In the case of JSON-RPC, the service map is a list of
+                available. In the case of <acronym>JSON</acronym>-RPC, the service map is a list of
                 available methods, which each method documenting the available
                 parameters and their types, as well as the expected return value
                 type.
@@ -512,9 +512,9 @@ $server->handle();
                         description.</para></listitem>
                 <listitem><para><methodname>setDojoCompatible($flag)</methodname>: Set a
                         flag indicating whether or not the SMD is compatible
-                        with Dojo toolkit. When true, the generated JSON SMD
+                        with Dojo toolkit. When true, the generated <acronym>JSON</acronym> SMD
                         will be formatted to comply with the format that Dojo's
-                        JSON-RPC client expects.</para></listitem>
+                        <acronym>JSON</acronym>-RPC client expects.</para></listitem>
                 <listitem><para><methodname>isDojoCompatible()</methodname>: Returns the
                         value of the Dojo compatibility flag (false, by
                         default).</para></listitem>
@@ -539,7 +539,7 @@ $server->handle();
                 <listitem><para><methodname>toDojoArray()</methodname>: Cast the service map
                         to an array compatible with Dojo Toolkit.</para></listitem>
                 <listitem><para><methodname>toJson()</methodname>: Cast the service map to a
-                        JSON representation.</para></listitem>
+                        <acronym>JSON</acronym> representation.</para></listitem>
             </itemizedlist>
 
             <para>
@@ -606,7 +606,7 @@ $server->handle();
                 <listitem><para><methodname>toArray()</methodname>: Cast the service to an
                     array.</para></listitem>
                 <listitem><para><methodname>toJson()</methodname>: Cast the service to a
-                    JSON representation.</para></listitem>
+                    <acronym>JSON</acronym> representation.</para></listitem>
             </itemizedlist>
         </sect3>
     </sect2>

documentation/manual/en/module_specs/Zend_Json-xml2json.xml

@@ -4,14 +4,14 @@
     <title>XML to JSON conversion</title>
     <para>
         <classname>Zend_Json</classname> provides a convenience method for transforming
-        <acronym>XML</acronym> formatted data into JSON format. This feature was inspired from an
+        <acronym>XML</acronym> formatted data into <acronym>JSON</acronym> format. This feature was inspired from an
         <ulink url="http://www.ibm.com/developerworks/xml/library/x-xml2jsonphp/">
         IBM developerWorks article</ulink>.
     </para>
 
     <para>
         <classname>Zend_Json</classname> includes a static function called <methodname>Zend_Json::fromXml()</methodname>.
-        This function will generate JSON from a given <acronym>XML</acronym> input. This function takes any arbitrary
+        This function will generate <acronym>JSON</acronym> from a given <acronym>XML</acronym> input. This function takes any arbitrary
         <acronym>XML</acronym> string as an input parameter. It also takes an optional boolean input parameter to instruct the
         conversion logic to ignore or not ignore the <acronym>XML</acronym> attributes during the conversion process. If this
         optional input parameter is not given, then the default behavior is to ignore the <acronym>XML</acronym> attributes.
@@ -25,7 +25,7 @@ $jsonContents = Zend_Json::fromXml($xmlStringContents, true);
 
     <para>
         <methodname>Zend_Json::fromXml()</methodname> function does the conversion of the <acronym>XML</acronym> formatted string input
-        parameter and returns the equivalent JSON formatted string output. In case of any <acronym>XML</acronym> input format
+        parameter and returns the equivalent <acronym>JSON</acronym> formatted string output. In case of any <acronym>XML</acronym> input format
         error or conversion logic error, this function will throw an exception. The conversion logic also
         uses recursive techniques to traverse the <acronym>XML</acronym> tree. It supports recursion upto 25 levels deep.
         Beyond that depth, it will throw a <classname>Zend_Json_Exception</classname>. There are several <acronym>XML</acronym> files with varying
@@ -35,10 +35,10 @@ $jsonContents = Zend_Json::fromXml($xmlStringContents, true);
 
     <para>
         The following is a simple example that shows both the <acronym>XML</acronym> input string passed to
-        and the JSON output string returned as a result from the
+        and the <acronym>JSON</acronym> output string returned as a result from the
         <methodname>Zend_Json::fromXml()</methodname> function. This example used the optional function parameter as
         not to ignore the <acronym>XML</acronym> attributes during the conversion. Hence, you can notice that the
-        resulting JSON string includes a representation of the <acronym>XML</acronym> attributes present in the <acronym>XML</acronym> input string.
+        resulting <acronym>JSON</acronym> string includes a representation of the <acronym>XML</acronym> attributes present in the <acronym>XML</acronym> input string.
     </para>
 
     <para>
@@ -69,7 +69,7 @@ $jsonContents = Zend_Json::fromXml($xmlStringContents, true);
 ]]></programlisting>
 
     <para>
-        JSON output string returned from <methodname>Zend_Json::fromXml()</methodname> function:
+        <acronym>JSON</acronym> output string returned from <methodname>Zend_Json::fromXml()</methodname> function:
     </para>
 
     <programlisting language="php"><![CDATA[

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

@@ -72,7 +72,7 @@
 
         <para>
             For those needing to specify explicitly the format of the date string, the following format token specifiers
-            are supported. If an invalid format specifier is used, such as the <acronym>PHP</acronym> 'i' specifier when in ISO format
+            are supported. If an invalid format specifier is used, such as the <acronym>PHP</acronym> 'i' specifier when in <acronym>ISO</acronym> format
             mode, then an error will be thrown by the methods in <classname>Zend_Locale_Format</classname> that support user-defined formats.
         </para>
 
@@ -81,7 +81,7 @@
             <methodname>toString()</methodname>. If you need to use <acronym>PHP</acronym> <methodname>date()</methodname> compatible format specifiers, then first
             call <methodname>setOptions(array('format_type' => 'php'))</methodname>. And if you want to convert only one special format
             string from <acronym>PHP</acronym> <methodname>date()</methodname> compatible format to "ISO" format use <methodname>convertPhpToIsoFormat()</methodname>.
-            Currently, the only practical difference relates to the specifier for minutes ('m' using the ISO default,
+            Currently, the only practical difference relates to the specifier for minutes ('m' using the <acronym>ISO</acronym> default,
             and 'i' using the <acronym>PHP</acronym> date format).
         </para>
 
@@ -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 ISO_8601 format instead of
+                To parse a database date value (f.e. MySql or MsSql), use <classname>Zend_Date</classname>'s <acronym>ISO</acronym>_8601 format instead of
                 getDate().
             </para>
         </note>

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

@@ -88,7 +88,7 @@
                 <para>
                     <classname>Zend_Locale_Data</classname> - Retrieve localized standard strings as country names, language names
                     and
-                    <ulink url="http://unicode.org/cldr/">more from the CLDR</ulink>
+                    <ulink url="http://unicode.org/cldr/">more from the <acronym>CLDR</acronym></ulink>
                     .
                 </para>
             </listitem>
@@ -176,7 +176,7 @@ $locale = new Zend_Locale('de_DE'); // German language _ Germany
             particular region observes Daylight Savings Time, and even which timezone a particular
             geographic area belongs. Thus, when performing date math, the math performed by Zend
             Framework components will not adjust for these changes, but instead will give the
-            correct time for the timezone using current, modern rules for DST and timezone
+            correct time for the timezone using current, modern rules for <acronym>DST</acronym> and timezone
             assignment for geographic regions.
         </para>
 
@@ -465,7 +465,7 @@ echo $date->getDate();
             The 'precision' option of a value is used to truncate or stretch extra digits. A value of '-1' disables
             modification of the number of digits in the fractional part of the value. The 'locale' option helps when
             parsing numbers and dates using separators and month names. The date format 'format_type' option selects between
-            CLDR/ISO date format specifier tokens and <acronym>PHP</acronym>'s date() tokens. The 'fix_date' option enables or disables
+            <acronym>CLDR</acronym>/ISO date format specifier tokens and <acronym>PHP</acronym>'s date() tokens. The 'fix_date' option enables or disables
             heuristics that attempt to correct invalid dates. The 'number_format' option specifies a default number
             format for use with <methodname>toNumber()</methodname> (see
             <xref

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

@@ -159,7 +159,7 @@ print $number;
 
         <para>
             Using the option 'number_format' a self defined format for generating a number can be defined.
-            The format itself has to be given in CLDR format as described below. The locale is used to get
+            The format itself has to be given in <acronym>CLDR</acronym> format as described below. The locale is used to get
             separation, precision and other number formatting signs from it. German for example defines
             ',' as precision separation and in English the '.' sign is used.
         </para>
@@ -412,15 +412,15 @@ if (Zend_Locale_Format::isInteger('13.445', array('locale' => $locale)) {
             will result in an exception, to avoid accidentally performing an incorrect conversion due to a spelling
             error. All characters in the input, which are not numerals for the selected numeral system, are copied to
             the output with no conversion provided for unit separator characters. <classname>Zend_Locale</classname>* components
-            rely on the data provided by CLDR (see their
+            rely on the data provided by <acronym>CLDR</acronym> (see their
             <ulink url="http://unicode.org/cldr/data/diff/supplemental/languages_and_scripts.html?sortby=date">
                 list of scripts grouped by language</ulink>).
         </para>
 
         <para>
-            In CLDR and hereafter, the Europena/Latin numerals will
+            In <acronym>CLDR</acronym> and hereafter, the Europena/Latin numerals will
             be referred to as "Latin" or by the assigned 4-letter code "Latn".
-            Also, the CLDR refers to this numeral systems as "scripts".
+            Also, the <acronym>CLDR</acronym> refers to this numeral systems as "scripts".
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Log-Writers-Firebug.xml

@@ -13,7 +13,7 @@
     <para>
       All data is sent via the <classname>Zend_Wildfire_Channel_HttpHeaders</classname> component
       which uses <acronym>HTTP</acronym> headers to ensure the page content is not disturbed.
-      Debugging <acronym>AJAX</acronym> requests that require clean JSON and <acronym>XML</acronym> responses is possible with this approach.
+      Debugging <acronym>AJAX</acronym> requests that require clean <acronym>JSON</acronym> and <acronym>XML</acronym> responses is possible with this approach.
     </para>
     <para>
       Requirements:

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 ISO3166
+                    - the user's country of residence as specified by <acronym>ISO</acronym>3166
                 </para>
             </listitem>
             <listitem>
                 <para>
                     <emphasis>language</emphasis>
-                    - the user's preferred language as specified by ISO639
+                    - the user's preferred language as specified by <acronym>ISO</acronym>639
                 </para>
             </listitem>
             <listitem>

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

@@ -3,7 +3,7 @@
 <sect1 id="zend.pdf.create">
     <title>Creating and Loading PDF Documents</title>
     <para>
-    The <classname>Zend_Pdf</classname> class represents PDF documents and provides document-level
+    The <classname>Zend_Pdf</classname> class represents <acronym>PDF</acronym> documents and provides document-level
     operations.
     </para>
 
@@ -12,7 +12,7 @@
     </para>
 
     <para>
-    <classname>Zend_Pdf</classname> class also provides two static methods to load an existing PDF document.
+    <classname>Zend_Pdf</classname> class also provides two static methods to load an existing <acronym>PDF</acronym> document.
     These are the <methodname>Zend_Pdf::load()</methodname> and <methodname>Zend_Pdf::parse()</methodname> methods.
     Both of them return <classname>Zend_Pdf</classname> objects as a result or throw an exception if an error occurs.
     </para>
@@ -34,7 +34,7 @@ $pdf3 = Zend_Pdf::parse($pdfString);
     </example>
 
     <para>
-    The PDF file format supports incremental document update. Thus each time a document
+    The <acronym>PDF</acronym> file format supports incremental document update. Thus each time a document
     is updated, then a new revision of the document is created.
     <classname>Zend_Pdf</classname> component supports the retrieval of a specified revision.
     </para>

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

@@ -6,7 +6,7 @@
     <sect2 id="zend.pdf.drawing.geometry">
         <title>Geometry</title>
         <para>
-        PDF uses the same geometry as PostScript. It starts from bottom-left corner of page
+        <acronym>PDF</acronym> uses the same geometry as PostScript. It starts from bottom-left corner of page
         and by default is measured in points (1/72 of an inch).
         </para>
         <para>
@@ -23,7 +23,7 @@ $height = $pdfPage->getHeight();
     <sect2 id="zend.pdf.drawing.color">
         <title>Colors</title>
         <para>
-        PDF has a powerful capabilities for colors representation. <classname>Zend_Pdf</classname> module supports Gray Scale,
+        <acronym>PDF</acronym> has a powerful capabilities for colors representation. <classname>Zend_Pdf</classname> module supports Gray Scale,
         RGB and CMYK color spaces. Any of them can be used in any place, where <classname>Zend_Pdf_Color</classname>
         object is required. <classname>Zend_Pdf_Color_GrayScale</classname>, <classname>Zend_Pdf_Color_Rgb</classname> and
         <classname>Zend_Pdf_Color_Cmyk</classname> classes provide this functionality:
@@ -52,7 +52,7 @@ $color3 = new Zend_Pdf_Color_Html('forestgreen');
     <sect2 id="zend.pdf.drawing.shape-drawing">
         <title>Shape Drawing</title>
         <para>
-        All drawing operations can be done in a context of PDF page.
+        All drawing operations can be done in a context of <acronym>PDF</acronym> page.
         </para>
         <para>
         <classname>Zend_Pdf_Page</classname> class provides a set of drawing primitives:
@@ -179,7 +179,7 @@ public function drawEllipse($x1,
     <sect2 id="zend.pdf.drawing.text-drawing">
         <title>Text Drawing</title>
         <para>
-        Text drawing operations also exist in the context of a PDF page. You can draw a single line of text
+        Text drawing operations also exist in the context of a <acronym>PDF</acronym> page. You can draw a single line of text
         at any position on the page by supplying the x and y coordinates of the baseline. Current font and
         current font size are used for text drawing operations (see detailed description below).
         </para>
@@ -243,14 +243,14 @@ $pdfPage->drawText($unicodeString, 72, 720, 'UTF-8');
 public function setFont(Zend_Pdf_Resource_Font $font, $fontSize);
 ]]></programlisting>
         <para>
-        PDF documents support PostScript Type 1 and TrueType fonts, as well as two specialized PDF types, Type 3
-        and composite fonts. There are also 14 standard Type 1 fonts built-in to every PDF viewer: Courier (4
+        <acronym>PDF</acronym> documents support PostScript Type 1 and TrueType fonts, as well as two specialized <acronym>PDF</acronym> types, Type 3
+        and composite fonts. There are also 14 standard Type 1 fonts built-in to every <acronym>PDF</acronym> viewer: Courier (4
         styles), Helvetica (4 styles), Times (4 styles), Symbol, and Zapf Dingbats.
         </para>
         <para>
-        <classname>Zend_Pdf</classname> currently supports the standard 14 PDF fonts as well as your own custom TrueType fonts. Font
+        <classname>Zend_Pdf</classname> currently supports the standard 14 <acronym>PDF</acronym> fonts as well as your own custom TrueType fonts. Font
         objects are obtained via one of two factory methods: <methodname>Zend_Pdf_Font::fontWithName($fontName)</methodname>
-        for the standard 14 PDF fonts or <methodname>Zend_Pdf_Font::fontWithPath($filePath)</methodname> for custom fonts.
+        for the standard 14 <acronym>PDF</acronym> fonts or <methodname>Zend_Pdf_Font::fontWithPath($filePath)</methodname> for custom fonts.
         </para>
         <example id="zend.pdf.drawing.using-fonts.example-1">
             <title>Create a standard font</title>
@@ -265,7 +265,7 @@ $pdfPage->setFont($font, 36);
 ]]></programlisting>
         </example>
         <para>
-        Constants for the standard 14 PDF font names are defined in the <classname>Zend_Pdf_Font</classname> class:
+        Constants for the standard 14 <acronym>PDF</acronym> font names are defined in the <classname>Zend_Pdf_Font</classname> class:
         <itemizedlist>
             <listitem>
                 <para>Zend_Pdf_Font::FONT_COURIER</para>
@@ -335,7 +335,7 @@ $pdfPage->setFont($goodDogCoolFont, 36);
 ]]></programlisting>
         </example>
         <para>
-        By default, custom fonts will be embedded in the resulting PDF document. This allows recipients
+        By default, custom fonts will be embedded in the resulting <acronym>PDF</acronym> document. This allows recipients
         to view the page as intended, even if they don't have the proper fonts installed on their system.
         If you are concerned about file size, you can request that the font program not be embedded by
         passing a 'do not embed' option to the factory method:
@@ -354,12 +354,12 @@ $pdfPage->setFont($goodDogCoolFont, 36);
 ]]></programlisting>
         </example>
         <para>
-        If the font program is not embedded but the recipient of the PDF file has the font installed on
+        If the font program is not embedded but the recipient of the <acronym>PDF</acronym> file has the font installed on
         their system, they will see the document as intended. If they do not have the correct font
-        installed, the PDF viewer application will do its best to synthesize a replacement.
+        installed, the <acronym>PDF</acronym> viewer application will do its best to synthesize a replacement.
         </para>
         <para>
-        Some fonts have very specific licensing rules which prevent them from being embedded in PDF
+        Some fonts have very specific licensing rules which prevent them from being embedded in <acronym>PDF</acronym>
         documents. So you are not caught off-guard by this, if you try to use a font that cannot be
         embedded, the factory method will throw an exception.
         </para>
@@ -380,7 +380,7 @@ $font = Zend_Pdf_Font::fontWithPath(
         </example>
         <para>
         This suppression technique is preferred if you allow an end-user to choose their own fonts. Fonts
-        which can be embedded in the PDF document will be; those that cannot, won't.
+        which can be embedded in the <acronym>PDF</acronym> document will be; those that cannot, won't.
         </para>
         <para>
         Font programs can be rather large, some reaching into the tens of megabytes. By default, all embedded
@@ -415,7 +415,7 @@ $font = Zend_Pdf_Font::fontWithPath(
     <sect2 id="zend.pdf.drawing.standard-fonts-limitations">
         <title>Standard PDF fonts limitations</title>
         <para>
-            Standard PDF fonts use several single byte encodings internally
+            Standard <acronym>PDF</acronym> fonts use several single byte encodings internally
             (see <ulink url="http://www.adobe.com/devnet/acrobat/pdfs/pdf_reference_1-7.pdf">PDF Reference, Sixth Edition, version 1.7</ulink>
              Appendix D for details). They are generally equal to Latin1 character set (except Symbol and ZapfDingbats fonts).
         </para>
@@ -670,7 +670,7 @@ public function setLineDashingPattern($pattern, $phase = 0);
                         For simple convex paths, the nonzero winding number rule defines the inside
                         and outside as one would intuitively expect. The more interesting cases are those
                         involving complex or self-intersecting paths like the ones shown in Figure 4.10
-                        (in a PDF Reference).
+                        (in a <acronym>PDF</acronym> Reference).
 
                         For a path consisting of a five-pointed star, drawn with five connected straight
                         line segments intersecting each other, the rule considers the inside to be the entire
@@ -697,7 +697,7 @@ public function setLineDashingPattern($pattern, $phase = 0);
                         paths with simple shapes, but produces different results for more complex
                         shapes.
 
-                        Figure 4.11 (in a PDF Reference) shows the effects of applying the even-odd rule
+                        Figure 4.11 (in a <acronym>PDF</acronym> Reference) shows the effects of applying the even-odd rule
                         to complex paths. For the five-pointed star, the rule considers the triangular
                         points to be inside the path, but not the pentagon in the center. For the two
                         concentric circles, only the "doughnut" shape between the two circles is considered inside,
@@ -714,7 +714,7 @@ public function setLineDashingPattern($pattern, $phase = 0);
         <sect3 id="zend.pdf.drawing.linear-transformations.rotations">
             <title>Rotations</title>
             <para>
-            PDF page can be rotated before applying any draw operation.
+            <acronym>PDF</acronym> page can be rotated before applying any draw operation.
             It can be done by <methodname>Zend_Pdf_Page::rotate()</methodname> method:
             </para>
             <programlisting language="php"><![CDATA[
@@ -818,7 +818,7 @@ public function restoreGS();
     <sect2 id="zend.pdf.drawing.clipping">
         <title>Clipping draw area</title>
         <para>
-        PDF and <classname>Zend_Pdf</classname> module support clipping of draw area.
+        <acronym>PDF</acronym> and <classname>Zend_Pdf</classname> module support clipping of draw area.
         Current clip area limits the regions of the page affected by painting operators. It's a whole page initially.
         </para>
         <para>
@@ -900,7 +900,7 @@ public function clipEllipse($x1,
         <classname>Zend_Pdf_Style</classname> class provides styles functionality.
         </para>
         <para>
-        Styles can be used to store a set of graphic state parameters and apply it to a PDF page by one operation:
+        Styles can be used to store a set of graphic state parameters and apply it to a <acronym>PDF</acronym> page by one operation:
         </para>
         <programlisting language="php"><![CDATA[
 /**

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

@@ -4,9 +4,9 @@
     <!-- @todo review and revise upon completion of refactoring -->
     <title>Introduction</title>
     <para>
-    The <classname>Zend_Pdf</classname> component is a PDF (Portable Document Format) manipulation engine.
+    The <classname>Zend_Pdf</classname> component is a <acronym>PDF</acronym> (Portable Document Format) manipulation engine.
     It can load, create, modify and save documents.
-    Thus it can help any <acronym>PHP</acronym> application dynamically create PDF documents by modifying existing documents or generating new ones from scratch.
+    Thus it can help any <acronym>PHP</acronym> application dynamically create <acronym>PDF</acronym> documents by modifying existing documents or generating new ones from scratch.
 
     <classname>Zend_Pdf</classname> offers the following features:
     <itemizedlist>
@@ -15,7 +15,7 @@
             Create a new document or load existing one.
             <footnote>
                 <para>
-                Loading PDF V1.4 (Acrobat 5) documents is now supported.
+                Loading <acronym>PDF</acronym> V1.4 (Acrobat 5) documents is now supported.
                 </para>
             </footnote>
             </para>
@@ -58,7 +58,7 @@
         </listitem>
         <listitem>
             <para>
-            Incremental PDF file update.
+            Incremental <acronym>PDF</acronym> file update.
             </para>
         </listitem>
     </itemizedlist>

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

@@ -5,18 +5,18 @@
     <sect2 id="zend.pdf.pages.creation">
         <title>Page Creation</title>
         <para>
-            The pages in a PDF document are represented as <classname>Zend_Pdf_Page</classname> instances in <classname>Zend_Pdf</classname>.
+            The pages in a <acronym>PDF</acronym> document are represented as <classname>Zend_Pdf_Page</classname> instances in <classname>Zend_Pdf</classname>.
         </para>
 
         <para>
-            PDF pages either are loaded from an existing PDF or created using the <classname>Zend_Pdf</classname> <acronym>API</acronym>.
+            <acronym>PDF</acronym> pages either are loaded from an existing <acronym>PDF</acronym> or created using the <classname>Zend_Pdf</classname> <acronym>API</acronym>.
         </para>
 
         <para>
             New pages can be created by instantiating new <classname>Zend_Pdf_Page</classname> objects directly or by calling
             the <methodname>Zend_Pdf::newPage()</methodname> method, which returns a <classname>Zend_Pdf_Page</classname> object.
             <methodname>Zend_Pdf::newPage()</methodname> creates a page that is already attached to
-            a document. Unattached pages can't be used with multiple PDF documents,
+            a document. Unattached pages can't be used with multiple <acronym>PDF</acronym> documents,
             but they are somewhat more performant.
             <footnote>
                 <para>
@@ -75,7 +75,7 @@ unset($pdf->pages[$id]);
     <sect2 id="zend.pdf.pages.cloning">
         <title>Page cloning</title>
         <para>
-            Existing PDF page can be cloned by creating new <classname>Zend_Pdf_Page</classname> object with existing page as a parameter:
+            Existing <acronym>PDF</acronym> page can be cloned by creating new <classname>Zend_Pdf_Page</classname> object with existing page as a parameter:
         </para>
 
         <example id="zend.pdf.pages.example-2">
@@ -108,7 +108,7 @@ unset($pdf->pages[$templatePageIndex]);
 
         <caution>
             <para>
-                Important! Cloned page shares some PDF resources with a template page, so it can be used only within the same document
+                Important! Cloned page shares some <acronym>PDF</acronym> resources with a template page, so it can be used only within the same document
                 as a template page. Modified document can be saved as new one.
             </para>
         </caution>

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

@@ -4,7 +4,7 @@
     <!-- @todo review and revise upon completion of refactoring -->
     <title>Document Info and Metadata</title>
     <para>
-        A PDF document may include general information such as the document's title,
+        A <acronym>PDF</acronym> document may include general information such as the document's title,
         author, and creation and modification dates.
     </para>
     <para>
@@ -23,7 +23,7 @@ $pdf->save($pdfPath);
 
     </para>
     <para>
-        The following keys are defined by PDF v1.4 (Acrobat 5) standard:
+        The following keys are defined by <acronym>PDF</acronym> v1.4 (Acrobat 5) standard:
 
         <itemizedlist>
             <listitem>
@@ -48,15 +48,15 @@ $pdf->save($pdfPath);
             </listitem>
             <listitem>
                 <para>
-                    <emphasis>Creator</emphasis> - string, optional, if the document was converted to PDF from another format,
+                    <emphasis>Creator</emphasis> - string, optional, if the document was converted to <acronym>PDF</acronym> from another format,
                     the name of the application (for example, Adobe FrameMaker®) that created the original document from which
                     it was converted.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis>Producer</emphasis> - string, optional, if the document was converted to PDF from another format, the
-                    name of the application (for example, Acrobat Distiller) that converted it to PDF..
+                    <emphasis>Producer</emphasis> - string, optional, if the document was converted to <acronym>PDF</acronym> from another format, the
+                    name of the application (for example, Acrobat Distiller) that converted it to <acronym>PDF</acronym>..
                 </para>
             </listitem>
             <listitem>
@@ -160,7 +160,7 @@ $pdf->save($pdfPath);
     </para>
 
     <para>
-        Since PDF v 1.6 metadata can be stored in the special <acronym>XML</acronym> document attached to the PDF
+        Since <acronym>PDF</acronym> v 1.6 metadata can be stored in the special <acronym>XML</acronym> document attached to the <acronym>PDF</acronym>
         (XMP - <ulink url="http://www.adobe.com/products/xmp/">Extensible Metadata Platform</ulink>).
     </para>
 

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

@@ -3,18 +3,18 @@
 <sect1 id="zend.pdf.save">
     <title>Save Changes to PDF Documents</title>
     <para>
-    There are two methods that save changes to PDF documents: the <methodname>Zend_Pdf::save()</methodname> and
+    There are two methods that save changes to <acronym>PDF</acronym> documents: the <methodname>Zend_Pdf::save()</methodname> and
     <methodname>Zend_Pdf::render()</methodname> methods.
     </para>
 
     <para>
-    <methodname>Zend_Pdf::save($filename, $updateOnly = false)</methodname> saves the PDF document to a file. If $updateOnly
-    is true, then only the new PDF file segment is appended to a file. Otherwise, the file is overwritten.
+    <methodname>Zend_Pdf::save($filename, $updateOnly = false)</methodname> saves the <acronym>PDF</acronym> document to a file. If $updateOnly
+    is true, then only the new <acronym>PDF</acronym> file segment is appended to a file. Otherwise, the file is overwritten.
     </para>
 
     <para>
-    <methodname>Zend_Pdf::render($newSegmentOnly = false)</methodname> returns the PDF document as a string. If
-    $newSegmentOnly is true, then only the new PDF file segment is returned.
+    <methodname>Zend_Pdf::render($newSegmentOnly = false)</methodname> returns the <acronym>PDF</acronym> document as a string. If
+    $newSegmentOnly is true, then only the new <acronym>PDF</acronym> file segment is returned.
     </para>
 
     <example id="zend.pdf.save.example-1">

documentation/manual/en/module_specs/Zend_ProgressBar_Adapter_JsPull.xml

@@ -7,8 +7,8 @@
         as it requires to pull for new updates, instead of pushing updates out
         to the browsers. Generally you should use the adapter with the
         persistence option of the <classname>Zend_ProgressBar</classname>. On notify,
-        the adapter sends a JSON string to the browser, which looks exactly
-        like the JSON string which is send by the jsPush adapter. The only
+        the adapter sends a <acronym>JSON</acronym> string to the browser, which looks exactly
+        like the <acronym>JSON</acronym> string which is send by the jsPush adapter. The only
         difference is, that it contains an additional parameter,
         <code>finished</code>, which is either <constant>FALSE</constant> when
         <methodname>update()</methodname> is called or <constant>TRUE</constant>, when

documentation/manual/en/module_specs/Zend_Service_Amazon_Ec2-CloudWatch.xml

@@ -106,14 +106,14 @@ $return = $ec2_ebs->listMetrics();
                         return, inclusive. For example, 2008-02-26T19:00:00+00:00. We round your
                         value down to the nearest minute. You can set your start time for more than
                         two weeks in the past. However, you will only get data for the past two
-                        weeks. (in ISO 8601 format). Constraints: Must be before EndTime.
+                        weeks. (in <acronym>ISO</acronym> 8601 format). Constraints: Must be before EndTime.
                     </para>
                 </listitem>
                 <listitem>
                     <para>
                         <emphasis>EndTime</emphasis> The timestamp to use for determining the last
                         datapoint to return. This is the last datapoint to fetch, exclusive. For
-                        example, 2008-02-26T20:00:00+00:00 (in ISO 8601 format).
+                        example, 2008-02-26T20:00:00+00:00 (in <acronym>ISO</acronym> 8601 format).
                     </para>
                 </listitem>
             </itemizedlist>

documentation/manual/en/module_specs/Zend_Service_Delicious.xml

@@ -7,7 +7,7 @@
         <para>
             <classname>Zend_Service_Delicious</classname> is simple <acronym>API</acronym> for using
             <ulink url="http://del.icio.us">del.icio.us</ulink>
-            <acronym>XML</acronym> and JSON web services. This component gives you read-write access to posts at del.icio.us
+            <acronym>XML</acronym> and <acronym>JSON</acronym> web services. This component gives you read-write access to posts at del.icio.us
             if you provide credentials. It also allows read-only access to public data of all users.
         </para>
         <example id="zend.service.delicious.introduction.getAllPosts">

documentation/manual/en/module_specs/Zend_Service_Twitter_Search.xml

@@ -10,7 +10,7 @@
             <classname>Zend_Service_Twitter_Search</classname> provides a client for the <ulink
                 url="http://apiwiki.twitter.com/Search+API+Documentation">Twitter Search <acronym>API</acronym></ulink>.
             The Twitter Search service is use to search Twitter. Currently it only
-            returns data in Atom or JSON format but a full REST service is in the future
+            returns data in Atom or <acronym>JSON</acronym> format but a full REST service is in the future
             which will support <acronym>XML</acronym> responses.
         </para>
     </sect3>
@@ -22,7 +22,7 @@
             Returns the top ten queries that are currently trending on Twitter.
             The response includes the time of the request, the name of each trending topic,
             and the url to the Twitter Search results page for that topic.
-            Currently the search <acronym>API</acronym> for trends only supports a JSON return so the function returns
+            Currently the search <acronym>API</acronym> for trends only supports a <acronym>JSON</acronym> return so the function returns
             an array.
         </para>
 
@@ -154,7 +154,7 @@ $search_results = $twitter_search->search('zend', array('lang' => 'en'));
                 <para>
                     <methodname>getResponseType()</methodname> and <methodname>setResponseType()</methodname>
                     allow you to retrieve and modify the response type of the search
-                    between JSON and ATOM.
+                    between <acronym>JSON</acronym> and ATOM.
                 </para>
             </listitem>
         </itemizedlist>

documentation/manual/en/module_specs/Zend_Session-GlobalSessionManagement.xml

@@ -41,7 +41,7 @@
             <para>
                 To configure this component using
                 <link linkend="zend.config.adapters.ini"><classname>Zend_Config_Ini</classname></link>, first add the
-                configuration options to the INI file:
+                configuration options to the <acronym>INI</acronym> file:
             </para>
 
             <programlisting language="ini"><![CDATA[

documentation/manual/en/module_specs/Zend_Tag_Cloud.xml

@@ -9,7 +9,7 @@
         <classname>Zend_Tag</classname>. By default it comes with a set of HTML
         decorators, which allow you to create tag clouds for a website, but
         also supplies you with two abstract classes to create your own
-        decorators, to create tag clouds in PDF documents for example.
+        decorators, to create tag clouds in <acronym>PDF</acronym> documents for example.
     </para>
 
     <para>

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

@@ -200,7 +200,7 @@
             In addition to checking for redirect headers, you will often need
             to check for specific <acronym>HTTP</acronym> response codes and headers -- for
             instance, to determine whether an action results in a 404 or 500
-            response, or to ensure that JSON responses contain the appropriate
+            response, or to ensure that <acronym>JSON</acronym> responses contain the appropriate
             Content-Type header. The following assertions are available.
         </para>
 

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 ISO-8859-1 it will also return strings in this encoding
+                is build upon <acronym>ISO</acronym>-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, ISO-8859-1 and US-ASCII.
+                UTF-8, <acronym>ISO</acronym>-8859-1 and US-ASCII.
             </para>
         </note>
 
@@ -188,7 +188,7 @@
             <para>
                 The Ini Adapter is a very simple Adapter which can even be used
                 directly by customers.
-                INI files are readable by standard text editors, but
+                <acronym>INI</acronym> files are readable by standard text editors, but
                 text editors often do not support utf8 character sets.
             </para>
 
@@ -203,10 +203,10 @@
                 <para>
                     Prior to <acronym>PHP</acronym> 5.3, <function>parse_ini_file()</function> and
                     <function>parse_ini_string()</function> handled non-ASCII characters
-                    within INI option keys worked without an issue. However, starting with <acronym>PHP</acronym> 5.3,
+                    within <acronym>INI</acronym> option keys worked without an issue. However, starting with <acronym>PHP</acronym> 5.3,
                     any such keys will now be silently dropped in the returned array from either
                     function. If you had keys utilizing UTF-8 or Latin-1 characters, you may find
-                    your translations no longer work when using the INI adapter. If this is the
+                    your translations no longer work when using the <acronym>INI</acronym> adapter. If this is the
                     case, we recommend utilizing a different adapter.
                 </para>
             </warning>

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 ISO-8815-11 and another one with CP815.
+                 with <acronym>ISO</acronym>-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>
@@ -277,9 +277,9 @@ $translate->addTranslation('/path/to/other.csv', 'fr');
         <title>Creating INI source files</title>
 
         <para>
-            INI source files are human readable but normally not very small as they also
+            <acronym>INI</acronym> source files are human readable but normally not very small as they also
             include other data beside translations. If you have data which shall be
-            editable by your customers you can use the INI adapter.
+            editable by your customers you can use the <acronym>INI</acronym> adapter.
         </para>
 
         <example id="zend.translate.sourcecreation.ini.example">
@@ -299,7 +299,7 @@ $translate->addTranslation('/path/to/other.ini', 'it');
         </example>
 
         <para>
-            INI files have several restrictions. If a value in the ini file contains any
+            <acronym>INI</acronym> files have several restrictions. If a value in the ini file contains any
             non-alphanumeric characters it needs to be enclosed in double-quotes (<code>"</code>).
             There are also reserved words which must not be used as keys for ini files.
             These include: <constant>NULL</constant>, <code>yes</code>, <code>no</code>, <constant>TRUE</constant>,

documentation/manual/en/module_specs/Zend_View-Helpers-Json.xml

@@ -4,14 +4,14 @@
     <title>JSON Helper</title>
 
     <para>
-        When creating views that return JSON, it's important to also set the
-        appropriate response header. The JSON view helper does exactly that. In
+        When creating views that return <acronym>JSON</acronym>, it's important to also set the
+        appropriate response header. The <acronym>JSON</acronym> view helper does exactly that. In
         addition, by default, it disables layouts (if currently enabled), as
-        layouts generally aren't used with JSON responses.
+        layouts generally aren't used with <acronym>JSON</acronym> responses.
     </para>
 
     <para>
-        The JSON helper sets the following header:
+        The <acronym>JSON</acronym> helper sets the following header:
     </para>
 
     <programlisting language="text"><![CDATA[
@@ -24,7 +24,7 @@ Content-Type: application/json
     </para>
 
     <para>
-        Usage of the JSON helper is very straightforward:
+        Usage of the <acronym>JSON</acronym> helper is very straightforward:
     </para>
 
     <programlisting language="php"><![CDATA[
@@ -35,7 +35,7 @@ Content-Type: application/json
         <title>Keeping layouts and enabling encoding using Zend_Json_Expr</title>
 
         <para>
-            Each method in the JSON helper accepts a second, optional argument.
+            Each method in the <acronym>JSON</acronym> helper accepts a second, optional argument.
             This second argument can be a boolean flag to enable or disable
             layouts, or an array of options that will be passed to
             <methodname>Zend_Json::encode()</methodname> and used internally to encode data.
@@ -57,7 +57,7 @@ echo $this->json($this->data, array('keepLayouts' => true));
 ]]></programlisting>
 
         <para>
-            <classname>Zend_Json::encode</classname> allows the encoding of native JSON
+            <classname>Zend_Json::encode</classname> allows the encoding of native <acronym>JSON</acronym>
             expressions using <classname>Zend_Json_Expr</classname> objects. This option
             is disabled by default. To enable this option, pass a boolean
             <constant>TRUE</constant> to the <code>enableJsonExprFinder</code> key of

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 ISO-8859-1 (latin1). May be set via
+                to <acronym>ISO</acronym>-8859-1 (latin1). May be set via
                 <methodname>setEncoding()</methodname> or the <code>encoding</code> option
                 to the constructor.
             </para></listitem>