[DOCUMENTATION] English:

 - wrap class names with <classname>

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

documentation/manual/en/module_specs/Zend_Application-AvailableResources-View.xml

@@ -6,7 +6,7 @@
     <para>
         <classname>Zend_Application_Resource_View</classname> can be used to configure
         a <classname>Zend_View</classname> instance. Configuration options are per <link
-            linkend="zend.view.introduction.options">the Zend_View
+            linkend="zend.view.introduction.options">the <classname>Zend_View</classname>
             options</link>.
     </para>
 

documentation/manual/en/module_specs/Zend_Application-CoreFunctionality-Bootstrap_BootstrapAbstract.xml

@@ -7,9 +7,9 @@
         <classname>Zend_Application_Bootstrap_BootstrapAbstract</classname> is an abstract class
         which provides the base functionality of a common bootstrap. It implements
         both <link linkend="zend.application.core-functionality.bootstrap-bootstrapper">
-            Zend_Application_Bootstrap_Bootstrapper</link> and <link
+            <classname>Zend_Application_Bootstrap_Bootstrapper</classname></link> and <link
             linkend="zend.application.core-functionality.bootstrap-resourcebootstrapper">
-            Zend_Application_Bootstrap_ResourceBootstrapper</link>.
+            <classname>Zend_Application_Bootstrap_ResourceBootstrapper</classname></link>.
     </para>
 
     <table id="zend.application.core-functionality.bootstrap-bootstrapabstract.api.table">

documentation/manual/en/module_specs/Zend_Currency-Usage.xml

@@ -84,7 +84,7 @@ $currency = new Zend_Currency();
             </para>
             <note>
                 <para>
-                    Note that Zend_Currency only accepts locales which include a region. This means
+                    Note that <classname>Zend_Currency</classname> only accepts locales which include a region. This means
                     that all locales that only include a language will result in an exception. For
                     example the locale <emphasis>en</emphasis> will cause an exception to be thrown
                     whereas the locale <emphasis>en_US</emphasis> will return
@@ -540,7 +540,7 @@ print $currency->toCurrency(1000);
             <classname>Zend_Cache</classname>. The static method
             <methodname>Zend_Currency::setCache($cache)</methodname> accepts one option: a
             <classname>Zend_Cache</classname> adapter. If the cache adapter is set, the localization
-            data that Zend_Currency uses are cached. There are some static methods for manipulating
+            data that <classname>Zend_Currency</classname> uses are cached. There are some static methods for manipulating
             the cache: <methodname>getCache()</methodname>, <methodname>hasCache()</methodname>,
             <methodname>clearCache()</methodname> and <methodname>removeCache()</methodname>.
         </para>

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

@@ -729,7 +729,7 @@
             you are more comfortable with it. However, not all formats defined in the ISO norm are
             supported with PHP's date format specifiers. Use the
             <methodname>Zend_Date::setOptions(array('format_type' => 'php'))</methodname> method to
-            switch Zend_Date methods from supporting ISO format specifiers to PHP date() type
+            switch <classname>Zend_Date</classname> methods from supporting ISO format specifiers to PHP date() type
             specifiers (see <xref linkend="zend.date.constants.phpformats" /> below).
         </para>
 
@@ -1167,7 +1167,7 @@ print $date->toString("'Era:GGGG='GGGG, ' Date:yy.MMMM.dd'yy.MMMM.dd");
             If you are more comfortable with PHP's date format specifier than with ISO format
             specifiers, then you can use the
             <methodname>Zend_Date::setOptions(array('format_type' => 'php'))</methodname> method to
-            switch Zend_Date methods from supporting ISO format specifiers to PHP date() type
+            switch <classname>Zend_Date</classname> methods from supporting ISO format specifiers to PHP 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 PHP date format lacks some of the formats supported by the
@@ -1195,10 +1195,10 @@ 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 PHP date format specifiers with their equivalent
-            Zend_Date constants and CLDR/ISO equivalent format specifiers. In most cases, when the
+            <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 PHP format specifier
             is not altered by <methodname>Zend_Locale_Format::convertPhpToIsoFormat()</methodname>,
-            and the Zend_Date methods then recognize these "peculiar" PHP format specifiers, even
+            and the <classname>Zend_Date</classname> methods then recognize these "peculiar" PHP format specifiers, even
             when in the default "ISO" format mode.
         </para>
 

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

@@ -105,7 +105,7 @@ date_default_timezone_set('Europe/Berlin');
                     Although PHP 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,"
                     <classname>Zend_Date</classname> supports a nearly unlimited range, with the
-                    help of the BCMath extension. If BCMath is not available, then Zend_Date will
+                    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
                     <code>float</code> type supported by your server. "The size of a float is
                     platform-dependent, although a maximum of ~1.8e308 with a precision of roughly
@@ -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 PHP date() format tokens, use Zend_Date's built-in support for ISO
+                    according to PHP date() format tokens, use <classname>Zend_Date</classname>'s built-in support for ISO
                     8601 formatted dates.
                 </para>
             </listitem>

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

@@ -48,7 +48,7 @@
                 <code>fix_dst</code> option. When crossing the Summer/Winter DST 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,
-                if the time part of the date was originally 00:00:00. Since Zend_Date is based on
+                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>,
@@ -119,7 +119,7 @@
                 is able to handle such problems with the help of <classname>Zend_TimeSync</classname>. You can set a
                 timeserver with <classname>Zend_Date::setOptions(array('timesync' => $timeserver));</classname> which
                 will set the offset between the own actual timestamp and the real actual timestamp for all
-                instances of Zend_Date. Using this option does not change the timestamp of existing instances.
+                instances of <classname>Zend_Date</classname>. Using this option does not change the timestamp of existing instances.
                 So best usage is to set it within the bootstrap file.
             </para>
 

documentation/manual/en/module_specs/Zend_Db_Adapter.xml

@@ -153,7 +153,7 @@ $db = new Zend_Db_Adapter_Pdo_Mysql(array(
             <para>
                 The first argument is a string that names the base name of the
                 adapter class. For example the string 'Pdo_Mysql' corresponds
-                to the class Zend_Db_Adapter_Pdo_Mysql. The second argument is
+                to the class <classname>Zend_Db_Adapter_Pdo_Mysql</classname>. The second argument is
                 the same array of parameters you would have given to the
                 adapter constructor.
             </para>
@@ -1752,7 +1752,7 @@ $db = Zend_Db::factory('Oracle', array(
             </para>
             <para>
                 Currently, only Oracle, DB2, and the PDO adapters (where
-                specified by PHP) support persistence in Zend_Db.
+                specified by PHP) support persistence in <classname>Zend_Db</classname>.
             </para>
         </note>
 
@@ -2138,7 +2138,7 @@ if (!is_null($version)) {
                         To connect to an SQLite2 database, specify
                         <code>'sqlite2'=>true</code> in the array of
                         parameters when creating an instance of the
-                        Pdo_Sqlite Adapter.
+                        <classname>Pdo_Sqlite</classname> Adapter.
                     </para>
                 </listitem>
                 <listitem>
@@ -2146,7 +2146,7 @@ if (!is_null($version)) {
                         To connect to an in-memory SQLite database,
                         specify <code>'dbname'=>':memory:'</code> in the
                         array of parameters when creating an instance of
-                        the Pdo_Sqlite Adapter.
+                        the <classname>Pdo_Sqlite</classname> Adapter.
                     </para>
                 </listitem>
                 <listitem>
@@ -2189,9 +2189,9 @@ if (!is_null($version)) {
                 </listitem>
 
                 <listitem>
-                    <para>Adapter name is ZendX_Db_Adapter_Firebird.</para>
+                    <para>Adapter name is <classname>ZendX_Db_Adapter_Firebird</classname>.</para>
                     <para>
-                        Remember to use the param adapterNamespace with value ZendX_Db_Adapter.
+                        Remember to use the param adapterNamespace with value <classname>ZendX_Db_Adapter</classname>.
                     </para>
                     <para>
                         We recommend to update the gds32.dll (or linux equivalent) bundled with php,

documentation/manual/en/module_specs/Zend_Db_Statement.xml

@@ -248,7 +248,7 @@ echo $rows[0]['bug_description'];
                 return rows, just as you can in the Adapter class. You can use
                 the <methodname>setFetchMode()</methodname> method of the statement object
                 to specify the fetch mode. Specify the fetch mode using
-                Zend_Db class constants FETCH_ASSOC, FETCH_NUM, FETCH_BOTH,
+                <classname>Zend_Db</classname> class constants FETCH_ASSOC, FETCH_NUM, FETCH_BOTH,
                 FETCH_COLUMN, and FETCH_OBJ.
                 See <xref linkend="zend.db.adapter.select.fetch-mode" />
                 for more information on these modes.

documentation/manual/en/module_specs/Zend_Db_Table.xml

@@ -28,7 +28,7 @@
         <title>Using Zend_Db_Table as a concrete class</title>
 
         <para>
-            As of ZF 1.9, you can instantiate Zend_Db_Table. This added benefit is that
+            As of ZF 1.9, you can instantiate <classname>Zend_Db_Table</classname>. This added benefit is that
             you do not have to extend a base class and configure it to do simple operations
             such as selecting, inserting, updating and deleteing on a single table. Below
             is an example of the simplest of use cases.
@@ -47,9 +47,9 @@ $bugTable = new Zend_Db_Table('bug');
 
         <para>
             The above example represents the simplest of use cases. Make not of all the
-            options describe below for configuring Zend_Db_Table tables. If you want to be
+            options describe below for configuring <classname>Zend_Db_Table</classname> tables. If you want to be
             able to use the concrete usage case, in addition to the more complex relationhip
-            features, see the Zend_Db_Table_Definition documentation.
+            features, see the <classname>Zend_Db_Table_Definition</classname> documentation.
         </para>
 
     </sect2>

documentation/manual/en/module_specs/Zend_Db_Table_Definition.xml

@@ -22,7 +22,7 @@
 
         <para>
             For all of the same options that are available when configuring an extended
-            Zend_Db_Table_Abstract class, those options are also available when describing
+            <classname>Zend_Db_Table_Abstract</classname> class, those options are also available when describing
             a definition file. This definition file should be passed to the class at
             instantiation time so that it can know the full definition of all tables
             in said definition.
@@ -77,8 +77,8 @@ $definition = new Zend_Db_Table_Definition(array(
 
         <para>
             As you can see, the same options you'd generally see inside of an
-            extended Zend_Db_Table_Abstract class are documented in this
-            array as well. When passed into Zend_Db_Table constructor, this
+            extended <classname>Zend_Db_Table_Abstract</classname> class are documented in this
+            array as well. When passed into <classname>Zend_Db_Table</classname> constructor, this
             definition is <emphasis>persisted</emphasis> to any tables it will need
             to create in order to return the proper rows.
         </para>
@@ -129,13 +129,13 @@ foreach ($authors as $author) {
             Sometimes you want to use both paradigms for defining and using the
             table gateway: both by extension and concrete instantiation. To do this
             simply leave out any table configurations out of the definition. This will
-            allow Zend_Db_Table to look for the actual refered class instead of the
+            allow <classname>Zend_Db_Table</classname> to look for the actual refered class instead of the
             definition key.
         </para>
 
         <para>
             Building on the example above, we will allow for one of the table configurations
-            to be a Zend_Db_Table_Abstract extended class, while keeping the rest of the tables
+            to be a <classname>Zend_Db_Table_Abstract</classname> extended class, while keeping the rest of the tables
             as part of the definition. We will also show how one would interact with this
             new definition.
         </para>

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

@@ -291,7 +291,7 @@ array(
             <title>Importing a custom data source</title>
 
             <para>
-                You can create a Zeed_Feed instance from any data source implementing
+                You can create a <classname>Zeed_Feed</classname> instance from any data source implementing
                 <classname>Zend_Feed_Builder_Interface</classname>. You just have to implement the
                 <methodname>getHeader()</methodname> and <methodname>getEntries()</methodname> methods to be able to use
                 your object with <methodname>Zend_Feed::importBuilder()</methodname>. As a simple

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

@@ -495,7 +495,7 @@ while (!$upload['done']) {
                 <listitem>
                     <para>
                         <emphasis>progress</emphasis>: This optional key takes a instance of
-                        Zend_ProgressBar_Adapter or Zend_ProgressBar and allows to get the actual
+                        <classname>Zend_ProgressBar_Adapter</classname> or <classname>Zend_ProgressBar</classname> and allows to get the actual
                         upload state within a progressbar.
                     </para>
                 </listitem>
@@ -503,7 +503,7 @@ while (!$upload['done']) {
                 <listitem>
                     <para>
                         <emphasis>session</emphasis>: This optional key takes the name of a session
-                        namespace which will be used within Zend_ProgressBar. When this key is not
+                        namespace which will be used within <classname>Zend_ProgressBar</classname>. When this key is not
                         given it defaults to
                         <classname>Zend_File_Transfer_Adapter_Http_ProgressBar</classname>.
                     </para>

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

@@ -82,7 +82,7 @@ $filtered = $inflector->filter(array('page' => $string));
             use with inflection. By default, any filter prefixed with
             <classname>Zend_Filter</classname> will be available. To access filters with
             that prefix but which occur deeper in the hierarchy, such as the
-            various Word filters, simply strip off the Zend_Filter prefix:
+            various Word filters, simply strip off the <classname>Zend_Filter</classname> prefix:
         </para>
 
         <programlisting language="php"><![CDATA[

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

@@ -19,7 +19,7 @@
             <para>
                 The alphabetic characters mean characters that makes up words in each language.
                 However, the english alphabet is treated as the alphabetic characters in following
-                languages: Chinese, Japanese, Korean. The language is specified by Zend_Locale.
+                languages: Chinese, Japanese, Korean. The language is specified by <classname>Zend_Locale</classname>.
             </para>
         </note>
 

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

@@ -5,7 +5,7 @@
     <title>Writing Filters</title>
 
     <para>
-        Zend_Filter supplies a set of commonly needed filters, but developers will often need to
+        <classname>Zend_Filter</classname> supplies a set of commonly needed filters, but developers will often need to
         write custom filters for their particular use cases. The task of writing a custom filter is
         facilitated by implementing <classname>Zend_Filter_Interface</classname>.
     </para>

documentation/manual/en/module_specs/Zend_Filter.xml

@@ -5,7 +5,7 @@
     <title>Introduction</title>
 
     <para>
-        The Zend_Filter component provides a set of commonly needed data
+        The <classname>Zend_Filter</classname> component provides a set of commonly needed data
         filters. It also provides a simple filter chaining mechanism by which
         multiple filters may be applied to a single datum in a user-defined
         order.
@@ -41,7 +41,7 @@
             (e.g., "<code>&amp;</code>" is transformed to
             "<code>&amp;amp;</code>"). Supporting such use cases for web
             developers is important, and "to filter," in the context of using
-            Zend_Filter, means to perform some transformations upon input data.
+            <classname>Zend_Filter</classname>, means to perform some transformations upon input data.
         </para>
 
     </sect2>
@@ -114,7 +114,7 @@ echo Zend_Filter::filterStatic('"', 'HtmlEntities', array(ENT_QUOTES));
         </para>
 
         <para>
-            Also, the Zend_Filter_Input class allows you to instantiate and run
+            Also, the <classname>Zend_Filter_Input</classname> class allows you to instantiate and run
             multiple filter and validator classes on demand to process
             sets of input data. See <xref linkend="zend.filter.input" />.
         </para>

documentation/manual/en/module_specs/Zend_Filter_Input.xml

@@ -4,7 +4,7 @@
     <title>Zend_Filter_Input</title>
 
     <para>
-        Zend_Filter_Input provides a declarative interface to associate
+        <classname>Zend_Filter_Input</classname> provides a declarative interface to associate
         multiple filters and validators, apply them to collections of data, and
         to retrieve input values after they have been processed by the filters
         and validators. Values are returned in escaped format by default for
@@ -63,7 +63,7 @@
     </itemizedlist>
 
     <para>
-        To use Zend_Filter_Input, perform the following steps:
+        To use <classname>Zend_Filter_Input</classname>, perform the following steps:
     </para>
 
     <orderedlist numeration="arabic">
@@ -98,7 +98,7 @@
         <title>Declaring Filter and Validator Rules</title>
 
         <para>
-            Before creating an instance of Zend_Filter_Input, declare an
+            Before creating an instance of <classname>Zend_Filter_Input</classname>, declare an
             array of filter rules and an array of validator rules.
             This associative array maps a rule name to a filter or
             validator or a chain of filters or validators.
@@ -106,8 +106,8 @@
 
         <para>
             The following example filter rule set that declares the field
-            'month' is filtered by Zend_Filter_Digits, and the field 'account'
-            is filtered by Zend_Filter_StringTrim. Then a validation rule set
+            'month' is filtered by <classname>Zend_Filter_Digits</classname>, and the field 'account'
+            is filtered by <classname>Zend_Filter_StringTrim</classname>. Then a validation rule set
             declares that the field 'account' is valid only if it contains only
             alphabetical characters.
         </para>
@@ -211,7 +211,7 @@ $filters = array(
 
         <para>
             After declaring the filters and validators arrays, use them as
-            arguments in the constructor of Zend_Filter_Input. This returns an
+            arguments in the constructor of <classname>Zend_Filter_Input</classname>. This returns an
             object that knows all your filtering and validating rules, and you
             can use this object to process one or more sets of input data.
         </para>
@@ -226,7 +226,7 @@ $input = new Zend_Filter_Input($filters, $validators);
             and the values are data values. The standard <varname>$_GET</varname>
             and <varname>$_POST</varname> superglobal variables in PHP are examples
             of this format. You can use either of these variables as input
-            data for Zend_Filter_Input.
+            data for <classname>Zend_Filter_Input</classname>.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -248,7 +248,7 @@ $input->setData($newData);
 
         <para>
             The <methodname>setData()</methodname> method redefines data in an existing
-            Zend_Filter_Input object without changing the filtering and
+            <classname>Zend_Filter_Input</classname> object without changing the filtering and
             validation rules. Using this method, you can run the same rules
             against different sets of input data.
         </para>
@@ -378,7 +378,7 @@ if ($input->hasUnknown()) {
             <para>
                 You can specify the message returned by
                 <methodname>getMissing()</methodname> using the 'missingMessage' option,
-                as an argument to the Zend_Filter_Input constructor or using
+                as an argument to the <classname>Zend_Filter_Input</classname> constructor or using
                 the <methodname>setOptions()</methodname> method.
             </para>
 
@@ -424,7 +424,7 @@ $m = $input->getUnescaped('month'); // not escaped
 
             <para>
                 By default, when retrieving a value, it is filtered with the
-                Zend_Filter_HtmlEntities. This is the default because it is
+                <classname>Zend_Filter_HtmlEntities</classname>. This is the default because it is
                 considered the most common usage to output the value of a field
                 in HTML. The HtmlEntities filter helps prevent unintentional
                 output of code, which can result in security problems.
@@ -463,7 +463,7 @@ $input->setDefaultEscapeFilter(new Zend_Filter_StringTrim());
                 In either usage, you can specify the escape filter as a string
                 base name of the filter class, or as an object instance of a
                 filter class. The escape filter can be an instance of a filter
-                chain, an object of the class Zend_Filter.
+                chain, an object of the class <classname>Zend_Filter</classname>.
             </para>
 
             <para>
@@ -482,9 +482,9 @@ $input->setDefaultEscapeFilter(new Zend_Filter_StringTrim());
                 There is only one method <methodname>getEscaped()</methodname>, and
                 therefore you can specify only one filter for escaping
                 (although this filter can be a filter chain). If you need a
-                single instance of Zend_Filter_Input to return escaped output
+                single instance of <classname>Zend_Filter_Input</classname> to return escaped output
                 using more than one filtering method, you should extend
-                Zend_Filter_Input and implement new methods in your subclass to
+                <classname>Zend_Filter_Input</classname> and implement new methods in your subclass to
                 get values in different ways.
             </para>
 
@@ -500,7 +500,7 @@ $input->setDefaultEscapeFilter(new Zend_Filter_StringTrim());
             In addition to declaring the mapping from fields to filters
             or validators, you can specify some "metacommands" in the array
             declarations, to control some optional behavior of
-            Zend_Filter_Input. Metacommands appear as string-indexed
+            <classname>Zend_Filter_Input</classname>. Metacommands appear as string-indexed
             entries in a given filter or validator array value.
         </para>
 
@@ -711,10 +711,10 @@ $validators = array(
                 In the uncommon case that you declare a validation rule with
                 no validators, but the 'allowEmpty' metacommand is
                 <constant>FALSE</constant> (that is, the field is considered invalid if
-                it is empty), Zend_Filter_Input returns a default error message
+                it is empty), <classname>Zend_Filter_Input</classname> returns a default error message
                 that you can retrieve with <methodname>getMessages()</methodname>. You can
                 specify this message using the 'notEmptyMessage' option, as an
-                argument to the Zend_Filter_Input constructor or using the
+                argument to the <classname>Zend_Filter_Input</classname> constructor or using the
                 <methodname>setOptions()</methodname> method.
             </para>
 
@@ -775,8 +775,8 @@ $input = new Zend_Filter_Input(null, $validators);
             </para>
 
             <para>
-                The validator chain class, Zend_Validate, is more flexible with
-                respect to breaking chain execution than Zend_Filter_Input.
+                The validator chain class, <classname>Zend_Validate</classname>, is more flexible with
+                respect to breaking chain execution than <classname>Zend_Filter_Input</classname>.
                 With the former class, you can set the option to break the
                 chain on failure independently for each validator in the chain.
                 With the latter class, the defined value of the
@@ -932,7 +932,7 @@ $validators = array(
                 The default value for 'allowEmpty', 'breakChainOnFailure', and
                 'presence' metacommands can be set for all rules using the
                 <varname>$options</varname> argument to the constructor of
-                Zend_Filter_Input. This allows you to set the default value
+                <classname>Zend_Filter_Input</classname>. This allows you to set the default value
                 for all rules, without requiring you to set the metacommand for
                 every rule.
             </para>
@@ -968,17 +968,17 @@ $input = new Zend_Filter_Input($filters, $validators, $data, $options);
 
         <para>
             By default, when you declare a filter or validator as a string,
-            Zend_Filter_Input searches for the corresponding classes under
-            the Zend_Filter or Zend_Validate namespaces. For example,
+            <classname>Zend_Filter_Input</classname> searches for the corresponding classes under
+            the <classname>Zend_Filter</classname> or <classname>Zend_Validate</classname> namespaces. For example,
             a filter named by the string 'digits' is found in the class
-            Zend_Filter_Digits.
+            <classname>Zend_Filter_Digits</classname>.
         </para>
 
         <para>
             If you write your own filter or validator classes, or use filters
             or validators provided by a third-party, the classes may exist in
-            different namespaces than Zend_Filter or Zend_Validate. You can
-            tell Zend_Filter_Input to search more namespaces. You can specify
+            different namespaces than <classname>Zend_Filter</classname> or <classname>Zend_Validate</classname>. You can
+            tell <classname>Zend_Filter_Input</classname> to search more namespaces. You can specify
             namespaces in the constructor options:
         </para>
 
@@ -991,7 +991,7 @@ $input = new Zend_Filter_Input($filters, $validators, $data, $options);
         <para>
             Alternatively, you can use the <methodname>addValidatorPrefixPath($prefix,
                 $path)</methodname> or <methodname>addFilterPrefixPath($prefix, $path)</methodname>
-            methods, which directly proxy to the plugin loader that is used by Zend_Filter_Input:
+            methods, which directly proxy to the plugin loader that is used by <classname>Zend_Filter_Input</classname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -1010,7 +1010,7 @@ $input->addFilterPrefixPath('Foo_Namespace', 'Foo/Namespace');
 ]]></programlisting>
 
         <para>
-            You cannot remove Zend_Filter and Zend_Validate as namespaces, you
+            You cannot remove <classname>Zend_Filter</classname> and <classname>Zend_Validate</classname> as namespaces, you
             only can add namespaces. User-defined namespaces are searched
             first, Zend namespaces are searched last.
         </para>

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

@@ -6,7 +6,7 @@
     <sect2 id="zend.http.client.adapters.overview">
         <title>Overview</title>
         <para>
-            Zend_Http_Client is based on a connection adapter design. The
+            <classname>Zend_Http_Client</classname> is based on a connection adapter design. The
             connection adapter is the object in charge of performing the
             actual connection to the server, as well as writing requests
             and reading responses.
@@ -16,7 +16,7 @@
             class, and with the same interface.
         </para>
         <para>
-            Currently, the Zend_Http_Client class provides four built-in
+            Currently, the <classname>Zend_Http_Client</classname> class provides four built-in
             connection adapters:
             <itemizedlist>
                 <listitem>
@@ -42,7 +42,7 @@
             </itemizedlist>
         </para>
         <para>
-            The Zend_Http_Client object's adapter connection adapter is set
+            The <classname>Zend_Http_Client</classname> object's adapter connection adapter is set
             using the 'adapter' configuration option. When instantiating the
             client object, you can set the 'adapter' configuration option to
             a string containing the adapter's name (eg. 'Zend_Http_Client_Adapter_Socket')
@@ -55,7 +55,7 @@
     <sect2 id="zend.http.client.adapters.socket">
         <title>The Socket Adapter</title>
         <para>
-            The default connection adapter is the Zend_Http_Client_Adapter_Socket
+            The default connection adapter is the <classname>Zend_Http_Client_Adapter_Socket</classname>
             adapter - this adapter will be used unless you explicitly set the
             connection adapter. The Socket adapter is based on PHP's built-in
             fsockopen() function, and does not require any special extensions or
@@ -263,10 +263,10 @@ echo $opts['ssl']['peer_certificate'];
     <sect2 id="zend.http.client.adapters.proxy">
         <title>The Proxy Adapter</title>
         <para>
-            The Zend_Http_Client_Adapter_Proxy adapter is similar to the default
+            The <classname>Zend_Http_Client_Adapter_Proxy</classname> adapter is similar to the default
             Socket adapter - only the connection is made through an HTTP proxy
             server instead of a direct connection to the target server. This
-            allows usage of Zend_Http_Client behind proxy servers - which is
+            allows usage of <classname>Zend_Http_Client</classname> behind proxy servers - which is
             sometimes needed for security or performance reasons.
         </para>
 
@@ -321,7 +321,7 @@ echo $opts['ssl']['peer_certificate'];
         </para>
         <para>
             proxy_host should always be set - if it is not set, the client will
-            fall back to a direct connection using Zend_Http_Client_Adapter_Socket.
+            fall back to a direct connection using <classname>Zend_Http_Client_Adapter_Socket</classname>.
             proxy_port defaults to '8080' - if your proxy listens on a different
             port you must set this one as well.
         </para>
@@ -436,17 +436,17 @@ $client->request("PUT");
             server will require a network connection, which is not always available.
         </para>
         <para>
-            For this reason, the Zend_Http_Client_Adapter_Test adapter is
-            provided. You can write your application to use Zend_Http_Client,
+            For this reason, the <classname>Zend_Http_Client_Adapter_Test</classname> adapter is
+            provided. You can write your application to use <classname>Zend_Http_Client</classname>,
             and just for testing purposes, for example in your unit testing
             suite, you can replace the default adapter with a Test adapter (a
             mock object), allowing you to run tests without actually
             performing server connections.
         </para>
         <para>
-            The Zend_Http_Client_Adapter_Test adapter provides an additional
+            The <classname>Zend_Http_Client_Adapter_Test</classname> adapter provides an additional
             method, setResponse() method. This method takes one parameter,
-            which represents an HTTP response as either text or a Zend_Http_Response
+            which represents an HTTP response as either text or a <classname>Zend_Http_Response</classname>
             object. Once set, your Test adapter will always return this response,
             without even performing an actual HTTP request.
         </para>
@@ -529,7 +529,7 @@ $adapter->addResponse(
         </example>
         <para>
             The setResponse() method clears any responses in the
-            Zend_Http_Client_Adapter_Test's buffer and sets the
+            <classname>Zend_Http_Client_Adapter_Test</classname>'s buffer and sets the
             first response that will be returned. The addResponse()
             method will add successive responses.
         </para>
@@ -563,7 +563,7 @@ $adapter->addResponse(
         </para>
         <para>
             In order to do so, you must create your own adapter class that implements
-            the Zend_Http_Client_Adapter_Interface interface. The following example
+            the <classname>Zend_Http_Client_Adapter_Interface</classname> interface. The following example
             shows the skeleton of a user-implemented adapter class. All the public
             functions defined in this example must be defined in your adapter as well:
         </para>

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

@@ -6,7 +6,7 @@
     <sect2 id="zend.http.client.redirections">
         <title>HTTP Redirections</title>
         <para>
-            By default, Zend_Http_Client automatically handles HTTP redirections,
+            By default, <classname>Zend_Http_Client</classname> automatically handles HTTP redirections,
             and will follow up to 5 redirections. This can be changed by setting
             the 'maxredirects' configuration parameter.
         </para>
@@ -255,7 +255,7 @@ $client->setAuth('shahar', 'myPassword!');
     <sect2 id="zend.http.client.multiple_requests">
         <title>Sending Multiple Requests With the Same Client</title>
         <para>
-            Zend_Http_Client was also designed specifically to handle several
+            <classname>Zend_Http_Client</classname> was also designed specifically to handle several
             consecutive requests with the same object. This is useful in cases
             where a script requires data to be fetched from several places, or
             when accessing a specific HTTP resource requires logging in and

documentation/manual/en/module_specs/Zend_Http_Client.xml

@@ -3,11 +3,11 @@
 <sect1 id="zend.http.client">
     <title>Introduction</title>
     <para>
-        Zend_Http_Client provides an easy interface for preforming Hyper-Text
-        Transfer Protocol (HTTP) requests. Zend_Http_Client supports most simple
+        <classname>Zend_Http_Client</classname> provides an easy interface for preforming Hyper-Text
+        Transfer Protocol (HTTP) requests. <classname>Zend_Http_Client</classname> supports most simple
         features expected from an HTTP client, as well as some more complex
         features such as HTTP authentication and file uploads. Successful
-        requests (and most unsuccessful ones too) return a Zend_Http_Response
+        requests (and most unsuccessful ones too) return a <classname>Zend_Http_Response</classname>
         object, which provides access to the response's headers and body (see
         <xref linkend="zend.http.response" />).
     </para>
@@ -53,7 +53,7 @@ $client->setConfig($config);
         <title>Configuration Parameters</title>
         <para>
             The constructor and setConfig() method accept an associative array
-            of configuration parameters, or a Zend_Config object. Setting these
+            of configuration parameters, or a <classname>Zend_Config</classname> object. Setting these
             parameters is optional, as they all have default values.
             <table id="zend.http.client.configuration.table">
                 <title>Zend_Http_Client configuration parameters</title>
@@ -230,7 +230,7 @@ $client->setParameterPost(array(
     <sect2 id="zend.http.client.accessing_last">
         <title>Accessing Last Request and Response</title>
         <para>
-            Zend_Http_Client provides methods of accessing the last request
+            <classname>Zend_Http_Client</classname> provides methods of accessing the last request
             sent and last response received by the client object.
             <classname>Zend_Http_Client->getLastRequest()</classname> takes no parameters
             and returns the last HTTP request sent by the client as a string.

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

@@ -6,16 +6,16 @@
     <sect2 id="zend.http.cookies.introduction">
         <title>Introduction</title>
         <para>
-            Zend_Http_Cookie, as expected, is a class that represents an HTTP
+            <classname>Zend_Http_Cookie</classname>, as expected, is a class that represents an HTTP
             cookie. It provides methods for parsing HTTP response strings,
             collecting cookies, and easily accessing their properties. It also
             allows checking if a cookie matches against a specific scenario, IE
             a request URL, expiration time, secure connection, etc.
         </para>
         <para>
-            Zend_Http_CookieJar is an object usually used by Zend_Http_Client to
-            hold a set of Zend_Http_Cookie objects. The idea is that if a
-            Zend_Http_CookieJar object is attached to a Zend_Http_Client object,
+            <classname>Zend_Http_CookieJar</classname> is an object usually used by <classname>Zend_Http_Client</classname> to
+            hold a set of <classname>Zend_Http_Cookie</classname> objects. The idea is that if a
+            <classname>Zend_Http_CookieJar</classname> object is attached to a <classname>Zend_Http_Client</classname> object,
             all cookies going from and into the client through HTTP requests and
             responses will be stored by the CookieJar object. Then, when the client
             will send another request, it will first ask the CookieJar object for
@@ -23,7 +23,7 @@
             headers automatically. This is highly useful in cases where you need to
             maintain a user session over consecutive HTTP requests, automatically
             sending the session ID cookies when required. Additionally, the
-            Zend_Http_CookieJar object can be serialized and stored in $_SESSION
+            <classname>Zend_Http_CookieJar</classname> object can be serialized and stored in $_SESSION
             when needed.
         </para>
     </sect2>
@@ -36,7 +36,7 @@
                 <listitem>
                     <para>
                     Through the constructor, using the following syntax:
-                    <code>new Zend_Http_Cookie(string $name, string $value, string $domain, [int $expires, [string $path, [boolean $secure]]]);</code>
+                    <code>new <classname>Zend_Http_Cookie</classname>(string $name, string $value, string $domain, [int $expires, [string $path, [boolean $secure]]]);</code>
                     </para>
                     <itemizedlist>
                         <listitem>
@@ -106,7 +106,7 @@ $cookie = Zend_Http_Cookie::fromString('foo=bar; secure;',
             </example>
             <note>
                 <para>
-                When instantiating a cookie object using the Zend_Http_Cookie::fromString() method, the
+                When instantiating a cookie object using the <classname>Zend_Http_Cookie</classname>::fromString() method, the
                 cookie value is expected to be URL encoded, as cookie strings should be. However, when
                 using the constructor, the cookie value string is expected to be the real, decoded value.
                 </para>
@@ -143,7 +143,7 @@ echo $cookie;
     <sect2 id="zend.http.cookies.cookie.accessors">
         <title>Zend_Http_Cookie getter methods</title>
         <para>
-            Once a Zend_Http_Cookie object is instantiated, it provides several getter methods to get
+            Once a <classname>Zend_Http_Cookie</classname> object is instantiated, it provides several getter methods to get
             the different properties of the HTTP cookie:
             <itemizedlist>
                 <listitem>
@@ -234,7 +234,7 @@ echo ($cookie->isSessionCookie() ? 'Yes' : 'No');
     <sect2 id="zend.http.cookies.cookie.matching">
         <title>Zend_Http_Cookie: Matching against a scenario</title>
         <para>
-            The only real logic contained in a Zend_Http_Cookie object, is in the match() method.
+            The only real logic contained in a <classname>Zend_Http_Cookie</classname> object, is in the match() method.
             This method is used to test a cookie against a given HTTP request scenario, in order
             to tell whether the cookie should be sent in this request or not. The method has
             the following syntax and parameters:
@@ -242,7 +242,7 @@ echo ($cookie->isSessionCookie() ? 'Yes' : 'No');
             <itemizedlist>
                 <listitem>
                     <para>
-                    <code>mixed $uri</code>: A Zend_Uri_Http object with a domain name and path to be checked.
+                    <code>mixed $uri</code>: A <classname>Zend_Uri_Http</classname> object with a domain name and path to be checked.
                     Optionally, a string representing a valid HTTP URL can be passed instead. The cookie will
                     match if the URL's scheme (HTTP or HTTPS), domain and path all match.
                     </para>
@@ -316,8 +316,8 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
         <title>The Zend_Http_CookieJar Class: Instantiation</title>
         <para>
             In most cases, there is no need to directly instantiate a
-            Zend_Http_CookieJar object. If you want to attach a new cookie jar
-            to your Zend_Http_Client object, just call the
+            <classname>Zend_Http_CookieJar</classname> object. If you want to attach a new cookie jar
+            to your <classname>Zend_Http_Client</classname> object, just call the
             Zend_Http_Client->setCookieJar() method, and a new, empty cookie jar
             will be attached to your client. You could later get this cookie jar
             using Zend_Http_Client->getCookieJar().
@@ -327,9 +327,9 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
             can do so by calling "new Zend_Http_CookieJar()" directly - the
             constructor method does not take any parameters. Another way to
             instantiate a CookieJar object is to use the static Zend_Http_CookieJar::fromResponse()
-            method. This method takes two parameters: a Zend_Http_Response object,
-            and a reference URI, as either a string or a Zend_Uri_Http object.
-            This method will return a new Zend_Http_CookieJar object, already
+            method. This method takes two parameters: a <classname>Zend_Http_Response</classname> object,
+            and a reference URI, as either a string or a <classname>Zend_Uri_Http</classname> object.
+            This method will return a new <classname>Zend_Http_CookieJar</classname> object, already
             containing the cookies set by the passed HTTP response. The reference
             URI will be used to set the cookie's domain and path, if they are
             not defined in the Set-Cookie headers.
@@ -339,7 +339,7 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
     <sect2 id="zend.http.cookies.cookiejar.adding_cookies">
         <title>Adding Cookies to a Zend_Http_CookieJar object</title>
         <para>
-            Usually, the Zend_Http_Client object you attached your CookieJar object
+            Usually, the <classname>Zend_Http_Client</classname> object you attached your CookieJar object
             to will automatically add cookies set by HTTP responses to your jar. If
             you wish to manually add cookies to your jar, this can be done by using
             two methods:
@@ -347,19 +347,19 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
                 <listitem>
                     <para>
                     <classname>Zend_Http_CookieJar->addCookie($cookie[, $ref_uri])</classname>: Add a
-                    single cookie to the jar. $cookie can be either a Zend_Http_Cookie
+                    single cookie to the jar. $cookie can be either a <classname>Zend_Http_Cookie</classname>
                     object or a string, which will be converted automatically into a
                     Cookie object. If a string is provided, you should also provide
                     $ref_uri - which is a reference URI either as a string or
-                    Zend_Uri_Http object, to use as the cookie's default domain and path.
+                    <classname>Zend_Uri_Http</classname> object, to use as the cookie's default domain and path.
                     </para>
                 </listitem>
                 <listitem>
                     <para>
                     <classname>Zend_Http_CookieJar->addCookiesFromResponse($response, $ref_uri)</classname>:
                     Add all cookies set in a single HTTP response to the jar. $response is
-                    expected to be a Zend_Http_Response object with Set-Cookie headers. $ref_uri
-                    is the request URI, either as a string or a Zend_Uri_Http object, according
+                    expected to be a <classname>Zend_Http_Response</classname> object with Set-Cookie headers. $ref_uri
+                    is the request URI, either as a string or a <classname>Zend_Uri_Http</classname> object, according
                     to which the cookies' default domain and path will be set.
                     </para>
                 </listitem>
@@ -371,13 +371,13 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
         <title>Retrieving Cookies From a Zend_Http_CookieJar object</title>
         <para>
             Just like with adding cookies, there is usually no need to manually
-            fetch cookies from a CookieJar object. Your Zend_Http_Client object
+            fetch cookies from a CookieJar object. Your <classname>Zend_Http_Client</classname> object
             will automatically fetch the cookies required for an HTTP request
             for you. However, you can still use 3 provided methods to fetch
             cookies from the jar object: <methodname>getCookie()</methodname>,
             <methodname>getAllCookies()</methodname>, and <methodname>getMatchingCookies()</methodname>.
             Additionnaly, iterating over the CookieJar will let you
-            retrieve all the Zend_Http_Cookie objects from it.
+            retrieve all the <classname>Zend_Http_Cookie</classname> objects from it.
         </para>
         <para>
             It is important to note that each one of these methods takes a
@@ -387,7 +387,7 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
                 <listitem>
                     <para>
                     <classname>Zend_Http_CookieJar::COOKIE_OBJECT</classname>: Return
-                    a Zend_Http_Cookie object. If the method returns more than
+                    a <classname>Zend_Http_Cookie</classname> object. If the method returns more than
                     one cookie, an array of objects will be returned.
                     </para>
                 </listitem>
@@ -418,7 +418,7 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
                     <para>
                     <classname>Zend_Http_CookieJar->getCookie($uri, $cookie_name[, $ret_as])</classname>:
                     Get a single cookie from the jar, according to its URI (domain and path)
-                    and name. $uri is either a string or a Zend_Uri_Http object representing the
+                    and name. $uri is either a string or a <classname>Zend_Uri_Http</classname> object representing the
                     URI. $cookie_name is a string identifying the cookie name. $ret_as
                     specifies the return type as described above. $ret_type is optional, and
                     defaults to COOKIE_OBJECT.
@@ -438,7 +438,7 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
                     <itemizedlist>
                         <listitem>
                             <para>
-                            <varname>$uri</varname> is either a Zend_Uri_Http object or a string specifying the
+                            <varname>$uri</varname> is either a <classname>Zend_Uri_Http</classname> object or a string specifying the
                             connection type (secure or non-secure), domain and path to match against.
                             </para>
                         </listitem>

documentation/manual/en/module_specs/Zend_Http_Response.xml

@@ -6,10 +6,10 @@
     <sect2 id="zend.http.response.introduction">
         <title>Introduction</title>
         <para>
-            Zend_Http_Response provides easy access to an HTTP responses
+            <classname>Zend_Http_Response</classname> provides easy access to an HTTP responses
             message, as well as a set of static methods for parsing HTTP
-            response messages. Usually, Zend_Http_Response is used as an object
-            returned by a Zend_Http_Client request.
+            response messages. Usually, <classname>Zend_Http_Response</classname> is used as an object
+            returned by a <classname>Zend_Http_Client</classname> request.
         </para>
         <para>
             In most cases, a Zend_Http_Response object will be instantiated
@@ -74,7 +74,7 @@ $response = Zend_Http_Response::factory($str);
     <sect2 id="zend.http.response.testers">
         <title>Boolean Tester Methods</title>
         <para>
-            Once a Zend_Http_Response object is instantiated, it provides several
+            Once a <classname>Zend_Http_Response</classname> object is instantiated, it provides several
             methods that can be used to test the type of the response. These all
             return Boolean true or false:
             <itemizedlist>
@@ -208,7 +208,7 @@ echo $body;
     <sect2 id="zend.http.response.static_parsers">
         <title>Static HTTP Response Parsers</title>
         <para>
-            The Zend_Http_Response class also includes several internally-used
+            The <classname>Zend_Http_Response</classname> class also includes several internally-used
             methods for processing and parsing HTTP response messages. These
             methods are all exposed as static methods, which means they can be
             used externally, even if you do not need to instantiate a response

documentation/manual/en/module_specs/Zend_InfoCard-Basics.xml

@@ -161,9 +161,9 @@ if (isset($_POST['xmlToken'])) {
         <title>Using the Zend_InfoCard component standalone</title>
 
         <para>
-            It is also possible to use the Zend_InfoCard component as a
+            It is also possible to use the <classname>Zend_InfoCard</classname> component as a
             standalone component by interacting with the
-            <classname>Zend_InfoCard</classname> class directly. Using the Zend_InfoCard
+            <classname>Zend_InfoCard</classname> class directly. Using the <classname>Zend_InfoCard</classname>
             class is very similar to its use with the <classname>Zend_Auth</classname>
             component. An example of its use is shown below:
         </para>

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

@@ -63,7 +63,7 @@ $phpNative = Zend_Json::decode($encodedValue, Zend_Json::TYPE_OBJECT);
         <title>Internal Encoder/Decoder</title>
 
         <para>
-            Zend_Json has two different modes depending if ext/json is enabled in
+            <classname>Zend_Json</classname> has two different modes depending if ext/json is enabled in
             your PHP 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
@@ -89,7 +89,7 @@ Zend_Json::$useBuiltinEncoderDecoder = true:
             Javascript makes heavy use of anonymnous function callbacks, which
             can be saved within JSON object variables. Still they only work if not
             returned inside double qoutes, which <classname>Zend_Json</classname> naturally does.
-            With the Expression support for Zend_Json support you can encode JSON
+            With the Expression support for <classname>Zend_Json</classname> support you can encode JSON
             objects with valid javascript callbacks. This works for both <methodname>json_encode()</methodname>
             or the internal encoder.
         </para>

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

@@ -13,7 +13,7 @@
 
         <para>
             In both cases, however, you'll need to create a layout script.
-            Layout scripts simply utilize Zend_View (or whatever view
+            Layout scripts simply utilize <classname>Zend_View</classname> (or whatever view
             implementation you are using). Layout variables are registered with
             a <classname>Zend_Layout</classname> <link linkend="zend.view.helpers.initial.placeholder">placeholder</link>,
             and may be accessed via the placeholder helper or by fetching them
@@ -111,7 +111,7 @@
         </para>
 
         <para>
-            First, let's look at how to initialize Zend_Layout for use with the
+            First, let's look at how to initialize <classname>Zend_Layout</classname> for use with the
             MVC:
         </para>
 
@@ -216,7 +216,7 @@ $layout = Zend_Layout::getMvcInstance();
         <title>Using Zend_Layout as a Standalone Component</title>
 
         <para>
-            As a standalone component, Zend_Layout does not offer nearly as many
+            As a standalone component, <classname>Zend_Layout</classname> does not offer nearly as many
             features or as much convenience as when used with the MVC. However,
             it still has two chief benefits:
         </para>

documentation/manual/en/module_specs/Zend_Loader.xml

@@ -5,7 +5,7 @@
     <title>Loading Files and Classes Dynamically</title>
 
     <para>
-        The Zend_Loader class includes methods to help you load files dynamically.
+        The <classname>Zend_Loader</classname> class includes methods to help you load files dynamically.
     </para>
 
     <tip>

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

@@ -82,7 +82,7 @@
                 As with Zend Framework 1.8 a default caching was added. The reason behind this
                 change was, that most users had performance problems but did not add caching at
                 all. As the I18n core is a bottleneck when no caching is used we decided to add
-                a default caching when no cache has been set to Zend_Locale.
+                a default caching when no cache has been set to <classname>Zend_Locale</classname>.
             </para>
 
             <para>

documentation/manual/en/module_specs/Zend_Mail-Encoding.xml

@@ -11,7 +11,7 @@
     </para>
 
     <para>
-        Header Encoding, especially the encoding of the subject, is a tricky topic. Zend_Mime currently implements
+        Header Encoding, especially the encoding of the subject, is a tricky topic. <classname>Zend_Mime</classname> currently implements
         its own algorithm to encode quoted printable headers according to RFC-2045.
         This due to the problems of <code>iconv_mime_encode</code> and <code>mb_encode_mimeheader</code>
         with regards to certain charsets. This algorithm only breaks the header at spaces, which might lead to headers

documentation/manual/en/module_specs/Zend_Mime_Message.xml

@@ -32,7 +32,7 @@
 
     <para>An array with all <link linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>
     objects in the <classname>Zend_Mime_Message</classname> is returned
-        from the method <code>-&gt;getParts()</code>. The Zend_Mime_Part objects
+        from the method <code>-&gt;getParts()</code>. The <classname>Zend_Mime_Part</classname> objects
         can then be changed since they are stored in the array as references. If
         parts are added to the array or the sequence is changed, the array needs
         to be given back to the <link linkend="zend.mime.part"><classname>Zend_Mime_Part</classname></link>

documentation/manual/en/module_specs/Zend_Navigation-Migration.xml

@@ -5,7 +5,7 @@
 
     <para>
         This chapter documents primarily backwards compatibility breaks made in
-        Zend_Navigation and Zend_View_Helper_Navigation, and should serve to aid
+        <classname>Zend_Navigation</classname> and <classname>Zend_View_Helper_Navigation</classname>, and should serve to aid
         in migration from previous versions.
     </para>
 

documentation/manual/en/module_specs/Zend_Navigation-Pages-Common.xml

@@ -19,7 +19,7 @@
     </para>
 
     <para>
-        Read more on extending Zend_Navigation_Page in
+        Read more on extending <classname>Zend_Navigation_Page</classname> in
         <link linkend="zend.navigation.pages.custom">Creating custom page types</link>.
     </para>
 

documentation/manual/en/module_specs/Zend_Rest_Server.xml

@@ -7,7 +7,7 @@
         <title>Introduction</title>
 
         <para>
-            Zend_Rest_Server is intended as a fully-featured REST server.
+            <classname>Zend_Rest_Server</classname> is intended as a fully-featured REST server.
         </para>
     </sect2>
 

documentation/manual/en/module_specs/Zend_Search_Lucene-Searching.xml

@@ -328,7 +328,7 @@ $index->find($query, 'name', SORT_STRING, 'quantity', SORT_NUMERIC, SORT_DESC);
     <sect2 id="zend.search.lucene.searching.highlighting">
         <title>Search Results Highlighting</title>
         <para>
-            Zend_Search_Lucene provides two options for search results highlighting.
+            <classname>Zend_Search_Lucene</classname> provides two options for search results highlighting.
         </para>
         <para>
             The first one is utilizing <classname>Zend_Search_Lucene_Document_Html</classname> class

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

@@ -7,7 +7,7 @@
     <para>
         While the basic usage examples are a perfectly acceptable way to utilize Zend Framework sessions, there are some
         best practices to consider. This section discusses the finer details of session handling and illustrates more
-        advanced usage of the Zend_Session component.
+        advanced usage of the <classname>Zend_Session</classname> component.
     </para>
 
     <sect2 id="zend.session.advanced_usage.starting_a_session">
@@ -15,7 +15,7 @@
         <title>Starting a Session</title>
 
         <para>
-            If you want all requests to have a session facilitated by Zend_Session, then start the session in the
+            If you want all requests to have a session facilitated by <classname>Zend_Session</classname>, then start the session in the
             bootstrap file:
         </para>
 
@@ -37,7 +37,7 @@ Zend_Session::start();
         </para>
 
         <para>
-            There are four ways to start a session, when using Zend_Session. Two are wrong.
+            There are four ways to start a session, when using <classname>Zend_Session</classname>. Two are wrong.
         </para>
 
         <orderedlist>
@@ -432,7 +432,7 @@ echo $myNamespace->someArray['foo']; // prints "bar"
             suite of unit tests to cover the code in their applications. The exception
             "<emphasis>Zend_Session is currently marked as read-only</emphasis>" is thrown while
             performing unit tests, if any write-related methods are used after ending the session. However, unit tests
-            using Zend_Session require extra attention, because closing (<methodname>Zend_Session::writeClose()</methodname>), or
+            using <classname>Zend_Session</classname> require extra attention, because closing (<methodname>Zend_Session::writeClose()</methodname>), or
             destroying a session (<methodname>Zend_Session::destroy()</methodname>) prevents any further setting or unsetting of
             keys in any instance of <classname>Zend_Session_Namespace</classname>. This behavior is a direct result of the
             underlying ext/session mechanism and PHP's <methodname>session_destroy()</methodname> and

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

@@ -5,8 +5,8 @@
     <title>Global Session Management</title>
 
     <para>
-        The default behavior of sessions can be modified using the static methods of Zend_Session. All management and
-        manipulation of global session management occurs using Zend_Session, including configuration of the
+        The default behavior of sessions can be modified using the static methods of <classname>Zend_Session</classname>. All management and
+        manipulation of global session management occurs using <classname>Zend_Session</classname>, including configuration of the
         <ulink url="http://www.php.net/session#session.configuration">usual options provided by ext/session</ulink>,
         using <methodname>Zend_Session::setOptions()</methodname>. For example, failure to insure the use of a safe
         <code>save_path</code> or a unique cookie name by ext/session using <methodname>Zend_Session::setOptions()</methodname> may
@@ -18,10 +18,10 @@
         <title>Configuration Options</title>
 
         <para>
-            When the first session namespace is requested, Zend_Session will automatically start the PHP session, unless
+            When the first session namespace is requested, <classname>Zend_Session</classname> will automatically start the PHP session, unless
             already started with
             <link linkend="zend.session.advanced_usage.starting_a_session"><methodname>Zend_Session::start()</methodname></link>.
-            The underlying PHP session will use defaults from Zend_Session, unless modified first by
+            The underlying PHP session will use defaults from <classname>Zend_Session</classname>, unless modified first by
             <methodname>Zend_Session::setOptions()</methodname>.
         </para>
 
@@ -29,7 +29,7 @@
             To set a session configuration option, include the basename (the part of the name after
             "<code>session.</code>") as a key of an array passed to <methodname>Zend_Session::setOptions()</methodname>. The
             corresponding value in the array is used to set the session option value. If no options are set by the
-            developer, Zend_Session will utilize recommended default options first, then the default php.ini settings.
+            developer, <classname>Zend_Session</classname> will utilize recommended default options first, then the default php.ini settings.
             Community feedback about best practices for these options should be sent to
             <ulink url="mailto:fw-auth@lists.zend.com">fw-auth@lists.zend.com</ulink>.
         </para>
@@ -220,7 +220,7 @@ Zend_Session::setOptions($config->toArray());
             </listitem>
             <listitem>
                 <para>
-                    If a Zend_Session method is involved in causing the error message, examine the method carefully, and
+                    If a <classname>Zend_Session</classname> method is involved in causing the error message, examine the method carefully, and
                     make sure its use really is needed in the application. For example, the default usage of
                     <methodname>destroy()</methodname> also sends an HTTP header to expire the client-side session cookie. If this
                     is not needed, then use <methodname>destroy(false)</methodname>, since the instructions to set cookies are sent
@@ -254,7 +254,7 @@ Zend_Session::setOptions($config->toArray());
             a means to track individual users. By default this component uses only cookies to maintain session
             identifiers. The cookie's value is the unique identifier of your browser's session. PHP's ext/session
             uses this identifier to maintain a unique one-to-one relationship between website visitors, and
-            persistent session data storage unique to each visitor. Zend_Session* wraps this storage mechanism
+            persistent session data storage unique to each visitor. <classname>Zend_Session</classname>* wraps this storage mechanism
             (<varname>$_SESSION</varname>) with an object-oriented interface. Unfortunately, if an attacker gains access
             to the value of the cookie (the session id), an attacker might be able to hijack a visitor's session.
             This problem is not unique to PHP, or Zend Framework. The <methodname>regenerateId()</methodname> method allows
@@ -446,7 +446,7 @@ if (!isset($defaultNamespace->initialized)) {
         <title>stop()</title>
 
         <para>
-            This method does absolutely nothing more than toggle a flag in Zend_Session to prevent further writing to
+            This method does absolutely nothing more than toggle a flag in <classname>Zend_Session</classname> to prevent further writing to
             the session data store. We are specifically requesting feedback on this feature. Potential uses/abuses might
             include temporarily disabling the use of <classname>Zend_Session_Namespace</classname> instances or
             <classname>Zend_Session</classname> methods to write to the session data store, while execution is transferred to view-
@@ -514,8 +514,8 @@ if (!isset($defaultNamespace->initialized)) {
         <note>
             <title>Throws</title>
             <para>
-                An exception will be thrown if <classname>Zend_Session</classname> is not marked as readable (e.g., before <code>
-                Zend_Session</code> has been started).
+                An exception will be thrown if <classname>Zend_Session</classname> is not marked as readable (e.g., before
+                <classname>Zend_Session</classname> has been started).
             </para>
         </note>
 

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

@@ -48,7 +48,7 @@
         a different server than the one where the session data are located, then the responding server has no access to
         the session data (if they are not available from a networked filesystem). A list of additional, appropriate
         save handlers will be provided, when available. Community members are encouraged to suggest and submit save
-        handlers to the <ulink url="mailto:fw-auth@lists.zend.com">fw-auth@lists.zend.com</ulink> list. A Zend_Db
+        handlers to the <ulink url="mailto:fw-auth@lists.zend.com">fw-auth@lists.zend.com</ulink> list. A <classname>Zend_Db</classname>
         compatible save handler has been posted to the list.
     </para>
 

documentation/manual/en/module_specs/Zend_Soap_Client.xml

@@ -12,14 +12,14 @@
     </para>
 
     <para>
-        Under the WSDL mode, the Zend_Soap_Client component uses a WSDL document to define transport
+        Under the WSDL mode, the <classname>Zend_Soap_Client</classname> component uses a WSDL document to define transport
         layer options.
     </para>
 
     <para>
         The WSDL description is usually provided by the web service the client will access. If the WSDL description is not
-        made available, you may want to use Zend_Soap_Client in non-WSDL mode.
-        Under this mode, all SOAP protocol options have to be set explicitly on the Zend_Soap_Client class.
+        made available, you may want to use <classname>Zend_Soap_Client</classname> in non-WSDL mode.
+        Under this mode, all SOAP protocol options have to be set explicitly on the <classname>Zend_Soap_Client</classname> class.
     </para>
 
     <sect2 id="zend.soap.client.constructor">
@@ -46,7 +46,7 @@
         <note>
             <title>Important!</title>
             <para>
-                If you use Zend_Soap_Client component in non-WSDL mode, you <emphasis>must</emphasis> set
+                If you use <classname>Zend_Soap_Client</classname> component in non-WSDL mode, you <emphasis>must</emphasis> set
                 the 'location' and 'uri' options.
             </para>
         </note>
@@ -77,7 +77,7 @@
                         'wsdl' which is equivalent to <methodname>setWsdl($wsdlValue)</methodname> call.
                     </para>
                     <para>
-                        Changing this option may switch Zend_Soap_Client object to or from WSDL mode.
+                        Changing this option may switch <classname>Zend_Soap_Client</classname> object to or from WSDL mode.
                     </para>
                 </listitem>
                 <listitem>

documentation/manual/en/module_specs/Zend_Soap_Server.xml

@@ -12,7 +12,7 @@
     </para>
 
     <para>
-        When Zend_Soap_Server component works in the WSDL mode, it uses already prepared WSDL document to define
+        When <classname>Zend_Soap_Server</classname> component works in the WSDL mode, it uses already prepared WSDL document to define
         server object behavior and transport layer options.
     </para>
 
@@ -246,7 +246,7 @@ $server->handle();
         </note>
 
         <para>
-            Zend_Soap_Server component performs request/response processing automatically,
+            <classname>Zend_Soap_Server</classname> component performs request/response processing automatically,
             but allows to catch it and do some pre- and post-processing.
         </para>
 

documentation/manual/en/module_specs/Zend_Soap_Wsdl.xml

@@ -5,9 +5,9 @@
 
     <note>
         <para>
-            <classname>Zend_Soap_Wsdl</classname> class is used by Zend_Soap_Server component internally to operate with WSDL
+            <classname>Zend_Soap_Wsdl</classname> class is used by <classname>Zend_Soap_Server</classname> component internally to operate with WSDL
             documents. Nevertheless, you could also use functionality provided by this class for your own needs.
-            The Zend_Soap_Wsdl package contains both a parser and a builder of WSDL documents.
+            The <classname>Zend_Soap_Wsdl</classname> package contains both a parser and a builder of WSDL documents.
         </para>
         <para>
             If you don't plan to do this, you can skip this documentation section.
@@ -92,7 +92,7 @@
             (/definitions/portType) with the specified port type name.
         </para>
         <para>
-            It joins a set of Web Service methods defined in terms of Zend_Soap_Server implementation.
+            It joins a set of Web Service methods defined in terms of <classname>Zend_Soap_Server</classname> implementation.
         </para>
         <para>
             See <ulink url="http://www.w3.org/TR/wsdl#_porttypes"/> for the details.
@@ -108,7 +108,7 @@
         </para>
         <para>
             Each port operation corresponds to a class method (if Web Service is based on a class) or function
-            (if Web Service is based on a set of methods) in terms of Zend_Soap_Server implementation.
+            (if Web Service is based on a set of methods) in terms of <classname>Zend_Soap_Server</classname> implementation.
         </para>
         <para>
             It also adds corresponding port operation messages depending on specified
@@ -116,7 +116,7 @@
 
             <note>
                 <para>
-                    Zend_Soap_Server component generates two messages for each port operation while describing service based on
+                    <classname>Zend_Soap_Server</classname> component generates two messages for each port operation while describing service based on
                     <classname>Zend_Soap_Server</classname> class:
                     <itemizedlist>
                         <listitem>
@@ -152,7 +152,7 @@
         </para>
 
         <para>
-            Zend_Soap_Server implementation uses <code>$serviceName . 'Binding'</code> name for 'binding' element of WSDL document.
+            <classname>Zend_Soap_Server</classname> implementation uses <code>$serviceName . 'Binding'</code> name for 'binding' element of WSDL document.
         </para>
     </sect2>
 
@@ -168,7 +168,7 @@
             specified parameters
         </para>
         <para>
-            Zend_Soap_Server implementation adds corresponding binding entry for each Web Service method with input and output
+            <classname>Zend_Soap_Server</classname> implementation adds corresponding binding entry for each Web Service method with input and output
             entries defining 'soap:body' element as
             '&lt;soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/&gt;
         </para>
@@ -206,7 +206,7 @@
             specified for other transports.
         </para>
         <para>
-            Zend_Soap_Server implementation uses <code>$serviceUri . '#' . $methodName</code> for SOAP operation action name.
+            <classname>Zend_Soap_Server</classname> implementation uses <code>$serviceUri . '#' . $methodName</code> for SOAP operation action name.
         </para>
         <para>
             See <ulink url="http://www.w3.org/TR/wsdl#_soap:operation"/> for the details.
@@ -221,10 +221,10 @@
         </para>
         <para>
             WSDL 1.1 allows to have several port types (sets of operations) per service. This ability is not used by
-            Zend_Soap_Server implementation and not supported by <classname>Zend_Soap_Wsdl</classname> class.
+            <classname>Zend_Soap_Server</classname> implementation and not supported by <classname>Zend_Soap_Wsdl</classname> class.
         </para>
         <para>
-            Zend_Soap_Server implementation uses:
+            <classname>Zend_Soap_Server</classname> implementation uses:
             <itemizedlist>
                 <listitem>
                     <para>
@@ -266,7 +266,7 @@
     <sect2 id="zend.soap.wsdl.types">
         <title>Type mapping</title>
         <para>
-            Zend_Soap WSDL accessor implementation uses the following type mapping between PHP and SOAP types:
+            <classname>Zend_Soap</classname> WSDL accessor implementation uses the following type mapping between PHP and SOAP types:
 
             <itemizedlist>
                 <listitem>
@@ -353,7 +353,7 @@ $soapMyClassType = $wsdl->getType('MyClass');
                 active detection strategy for complex types. You can set the detection strategy either by
                 specifying the class name as string or instance of a <classname>Zend_Soap_Wsdl_Strategy_Interface</classname>
                 implementation as the third parameter of the constructor or using the <methodname>setComplexTypeStrategy($strategy)</methodname>
-                function of Zend_Soap_Wsdl. The following detection strategies currently exist:
+                function of <classname>Zend_Soap_Wsdl</classname>. The following detection strategies currently exist:
             </para>
 
             <itemizedlist>
@@ -443,7 +443,7 @@ $soapMyClassType = $wsdl->getType('MyClass');
         <title>Parsing WSDL documents</title>
 
         <para>
-            Zend_Soap_Wsdl also contains a parser for WSDL documents that has its main application in unit-testing and code-generation
+            <classname>Zend_Soap_Wsdl</classname> also contains a parser for WSDL documents that has its main application in unit-testing and code-generation
             for SOAP Webservices (Client and Server). The following example will show how the Parser can be used:
         </para>
 

documentation/manual/en/module_specs/Zend_Uri.xml

@@ -48,7 +48,7 @@ $uri = Zend_Uri::factory('http');
     <para>
       To create a new URI from scratch, pass only the scheme to
       <methodname>Zend_Uri::factory()</methodname><footnote><para>At the time of writing,
-      Zend_Uri only supports the HTTP and HTTPS schemes.</para></footnote> .
+      <classname>Zend_Uri</classname> only supports the HTTP and HTTPS schemes.</para></footnote> .
       If an unsupported scheme is passed, a <classname>Zend_Uri_Exception</classname>
       will be thrown.
     </para>
@@ -116,14 +116,14 @@ $valid = Zend_Uri::check('http://uri.in.question');
         <title>Allowing "Unwise" characters in URIs</title>
 
         <para>
-            By default, Zend_Uri will not accept the following characters, defined by
+            By default, <classname>Zend_Uri</classname> will not accept the following characters, defined by
             the RFC as "unwise" and invalid: <code>"{", "}", "|", "\", "^", "`"</code>.
             However, many implementations do accept these characters as valid.
         </para>
 
         <para>
-            Zend_Uri can be set to accept these "unwise" characters by setting the
-            'allow_unwise' option to boolean TRUE using the Zend_Uri::setConfig()
+            <classname>Zend_Uri</classname> can be set to accept these "unwise" characters by setting the
+            'allow_unwise' option to boolean TRUE using the <classname>Zend_Uri</classname>::setConfig()
             method:
         </para>
 

documentation/manual/en/module_specs/Zend_Validate-Hostname.xml

@@ -5,7 +5,7 @@
     <title>Hostname</title>
 
     <para>
-        Zend_Validate_Hostname allows you to validate a hostname against a set of known
+        <classname>Zend_Validate_Hostname</classname> allows you to validate a hostname against a set of known
         specifications. It is possible to check for three different types of hostnames: a DNS
         Hostname (i.e. domain.com), IP address (i.e. 1.2.3.4), and Local hostnames (i.e. localhost).
         By default only DNS hostnames are matched.
@@ -41,9 +41,9 @@ if ($validator->isValid($hostname)) {
 
     <para>
         You may find you also want to match IP addresses, Local hostnames, or a combination of all
-        allowed types. This can be done by passing a parameter to Zend_Validate_Hostname when you
+        allowed types. This can be done by passing a parameter to <classname>Zend_Validate_Hostname</classname> when you
         instantiate it. The parameter should be an integer which determines what types of hostnames
-        are allowed. You are encouraged to use the Zend_Validate_Hostname constants to do this.
+        are allowed. You are encouraged to use the <classname>Zend_Validate_Hostname</classname> constants to do this.
     </para>
 
     <para>
@@ -82,7 +82,7 @@ $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_DNS |
     <para>
         Some Country Code Top Level Domains (ccTLDs), such as 'de' (Germany), support international
         characters in domain names. These are known as International Domain Names (IDN). These
-        domains can be matched by Zend_Validate_Hostname via extended characters that are used in
+        domains can be matched by <classname>Zend_Validate_Hostname</classname> via extended characters that are used in
         the validation process.
     </para>
 
@@ -121,7 +121,7 @@ $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_DNS |
     <para>
         To match an IDN domain it's as simple as just using the standard Hostname validator since
         IDN matching is enabled by default. If you wish to disable IDN validation this can be done
-        by either passing a parameter to the Zend_Validate_Hostname constructor or via the
+        by either passing a parameter to the <classname>Zend_Validate_Hostname</classname> constructor or via the
         <code>$validator->setValidateIdn()</code> method.
     </para>
 

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

@@ -21,7 +21,7 @@
             <para>
                 The alphabetic characters mean characters that makes up words in each language.
                 However, the English alphabet is treated as the alphabetic characters in following
-                languages: Chinese, Japanese, Korean. The language is specified by Zend_Locale.
+                languages: Chinese, Japanese, Korean. The language is specified by <classname>Zend_Locale</classname>.
             </para>
         </note>
 

documentation/manual/en/module_specs/Zend_Validate-WritingValidators.xml

@@ -5,7 +5,7 @@
     <title>Writing Validators</title>
 
     <para>
-        Zend_Validate supplies a set of commonly needed validators, but inevitably, developers will
+        <classname>Zend_Validate</classname> supplies a set of commonly needed validators, but inevitably, developers will
         wish to write custom validators for their particular needs. The task of writing a custom
         validator is described in this section.
     </para>

documentation/manual/en/module_specs/Zend_Validate.xml

@@ -5,7 +5,7 @@
     <title>Introduction</title>
 
     <para>
-        The Zend_Validate component provides a set of commonly needed
+        The <classname>Zend_Validate</classname> component provides a set of commonly needed
         validators. It also provides a simple validator chaining mechanism by
         which multiple validators may be applied to a single datum in a
         user-defined order.

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

@@ -5,7 +5,7 @@
 
     <para>
         This chapter documents primarily backwards compatibility breaks made in
-        Zend_View, and should serve to aid in migration from previous versions.
+        <classname>Zend_View</classname>, and should serve to aid in migration from previous versions.
     </para>
 
     <sect2 id="zend.view.migration.zf5748">

documentation/manual/en/module_specs/Zend_XmlRpc_Server.xml

@@ -374,7 +374,7 @@ echo $server->handle();
             <title>Specifying exceptions to use as valid fault responses</title>
 
             <para>
-                The example below allows any Services_Exception-derived class to
+                The example below allows any <classname>Services_Exception</classname>-derived class to
                 report its code and message in the fault response.
             </para>