[DOCUMENTATION] English:

 - manual fixes: <code>method name</code> => <methodname>method name</methodname>

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

documentation/manual/en/module_specs/Zend_Db_Table-Relationships.xml

@@ -316,7 +316,7 @@ $bugsAssignedToUser = $user1234->findDependentRowset('Bugs',
 
             Alternatively, you can query rows from a dependent table using a special mechanism
             called a "magic method". <classname>Zend_Db_Table_Row_Abstract</classname> invokes the
-            method: <code>findDependentRowset('&lt;TableClass&gt;', '&lt;Rule&gt;')</code> if you
+            method: <methodname>findDependentRowset('&lt;TableClass&gt;', '&lt;Rule&gt;')</methodname> if you
             invoke a method on the Row object matching either of the following patterns:
         </para>
 
@@ -458,7 +458,7 @@ $engineer = $bug1->findParentRow('Accounts', 'Engineer');
         <para>
             Alternatively, you can query rows from a parent table using a "magic method".
             <classname>Zend_Db_Table_Row_Abstract</classname> invokes the method:
-            <code>findParentRow('&lt;TableClass&gt;', '&lt;Rule&gt;')</code> if you invoke a method
+            <methodname>findParentRow('&lt;TableClass&gt;', '&lt;Rule&gt;')</methodname> if you invoke a method
             on the Row object matching either of the following patterns:
         </para>
 
@@ -876,10 +876,10 @@ class BugsProducts extends Zend_Db_Table_Abstract
 
             <para>
                 Cascading deletes and updates defined in your <classname>Zend_Db_Table</classname>
-                classes are applied if you execute the <code>save()</code> or <code>delete()</code>
+                classes are applied if you execute the <methodname>save()</methodname> or <methodname>delete()</methodname>
                 methods on the Row class. However, if you update or delete data using another
                 interface, such as a query tool or another application, the cascading operations are
-                not applied. Even when using <code>update()</code> and <code>delete()</code> methods
+                not applied. Even when using <methodname>update()</methodname> and <methodname>delete()</methodname> methods
                 in the <classname>Zend_Db_Adapter</classname> class, cascading operations defined in
                 your <classname>Zend_Db_Table</classname> classes are not executed.
             </para>

documentation/manual/en/module_specs/Zend_Db_Table.xml

@@ -213,7 +213,7 @@ class Bugs extends Zend_Db_Table_Abstract
             <para>
                 If you don't specify the primary key, <classname>Zend_Db_Table_Abstract</classname>
                 tries to discover the primary key based on the information provided by the
-                <code>describeTable()</code>´ method.
+                <methodname>describeTable()</methodname>´ method.
             </para>
 
             <note>
@@ -222,7 +222,7 @@ class Bugs extends Zend_Db_Table_Abstract
                     Every table class must know which column(s) can be used to address rows
                     uniquely. If no primary key column(s) are specified in the table class
                     definition or the table constructor arguments, or discovered in the table
-                    metadata provided by <code>describeTable()</code>, then the table cannot be
+                    metadata provided by <methodname>describeTable()</methodname>, then the table cannot be
                     used with <classname>Zend_Db_Table</classname>.
                 </para>
 
@@ -265,7 +265,7 @@ class Bugs extends Zend_Db_Table_Abstract
             <itemizedlist>
                 <listitem>
                     <para>
-                        <code>_setupDatabaseAdapter()</code> checks that an adapter has been
+                        <methodname>_setupDatabaseAdapter()</methodname> checks that an adapter has been
                         provided; gets a default adapter from the registry if needed. By overriding
                         this method, you can set a database adapter from some other source.
                     </para>
@@ -273,7 +273,7 @@ class Bugs extends Zend_Db_Table_Abstract
 
                 <listitem>
                     <para>
-                        <code>_setupTableName()</code> defaults the table name to the name of the
+                        <methodname>_setupTableName()</methodname> defaults the table name to the name of the
                         class. By overriding this method, you can set the table name before this
                         default behavior runs.
                     </para>
@@ -281,18 +281,18 @@ class Bugs extends Zend_Db_Table_Abstract
 
                 <listitem>
                     <para>
-                        <code>_setupMetadata()</code> sets the schema if the table name contains
-                        the pattern "schema.table"; calls <code>describeTable()</code> to get
+                        <methodname>_setupMetadata()</methodname> sets the schema if the table name contains
+                        the pattern "schema.table"; calls <methodname>describeTable()</methodname> to get
                         metadata information; defaults the <varname>$_cols</varname> array to the
-                        columns reported by <code>describeTable()</code>. By overriding this method,
+                        columns reported by <methodname>describeTable()</methodname>. By overriding this method,
                         you can specify the columns.
                     </para>
                 </listitem>
 
                 <listitem>
                     <para>
-                        <code>_setupPrimaryKey()</code> defaults the primary key columns to those
-                        reported by <code>describeTable()</code>; checks that the primary key
+                        <methodname>_setupPrimaryKey()</methodname> defaults the primary key columns to those
+                        reported by <methodname>describeTable()</methodname>; checks that the primary key
                         columns are included in the <varname>$_cols</varname> array. By overriding
                         this method, you can specify the primary key columns.
                     </para>
@@ -307,7 +307,7 @@ class Bugs extends Zend_Db_Table_Abstract
 
             <para>
                 If application-specific logic needs to be initialized when a Table class is
-                constructed, you can select to move your tasks to the <code>init()</code> method,
+                constructed, you can select to move your tasks to the <methodname>init()</methodname> method,
                 which is called after all Table metadata has been processed. This is recommended
                 over the <code>__construct</code> method if you do not need to alter the metadata
                 in any programmatic way.
@@ -455,7 +455,7 @@ $table = new Bugs(array('db' => 'my_db'));
 
         <para>
             You can use the Table object to insert rows into the database table on which the Table
-            object is based. Use the <code>insert()</code> method of your Table object. The
+            object is based. Use the <methodname>insert()</methodname> method of your Table object. The
             argument is an associative array, mapping column names to values.
         </para>
 
@@ -616,7 +616,7 @@ class Bugs extends Zend_Db_Table_Abstract
                 If you define the <varname>$_sequence</varname> to be the Boolean value
                 <constant>FALSE</constant>, then <classname>Zend_Db_Table_Abstract</classname>
                 assumes that the table has a natural primary key. You must provide values for the
-                primary key columns in the array of data to the <code>insert()</code> method, or
+                primary key columns in the array of data to the <methodname>insert()</methodname> method, or
                 else this method throws a <classname>Zend_Db_Table_Exception</classname>.
             </para>
 
@@ -681,8 +681,8 @@ $table->update($data, $where);
         </example>
 
         <para>
-            Since the table <code>update()</code> method proxies to the database adapter
-            <link linkend="zend.db.adapter.write.update"><code>update()</code></link> method, the
+            Since the table <methodname>update()</methodname> method proxies to the database adapter
+            <link linkend="zend.db.adapter.write.update"><methodname>update()</methodname></link> method, the
             second argument can be an array of SQL expressions. The expressions are combined as
             Boolean terms using an <code>AND</code> operator.
         </para>
@@ -692,8 +692,8 @@ $table->update($data, $where);
             <para>
                 The values and identifiers in the SQL expression are not quoted for you. If you
                 have values or identifiers that require quoting, you are responsible for doing
-                this. Use the <code>quote()</code>, <code>quoteInto()</code>, and
-                <code>quoteIdentifier()</code> methods of the database adapter.
+                this. Use the <methodname>quote()</methodname>, <methodname>quoteInto()</methodname>, and
+                <methodname>quoteIdentifier()</methodname> methods of the database adapter.
             </para>
 
         </note>
@@ -705,7 +705,7 @@ $table->update($data, $where);
         <title>Deleting Rows from a Table</title>
 
         <para>
-            You can delete rows from a database table using the <code>delete()</code> method. This
+            You can delete rows from a database table using the <methodname>delete()</methodname> method. This
             method takes one argument, which is an SQL expression that is used in a
             <code>WHERE</code> clause, as criteria for the rows to delete.
         </para>
@@ -725,8 +725,8 @@ $table->delete($where);
         </example>
 
         <para>
-            Since the table <code>delete()</code> method proxies to the database adapter
-            <link linkend="zend.db.adapter.write.delete"><code>delete()</code></link> method, the
+            Since the table <methodname>delete()</methodname> method proxies to the database adapter
+            <link linkend="zend.db.adapter.write.delete"><methodname>delete()</methodname></link> method, the
             argument can also be an array of SQL expressions. The expressions are combined as
             Boolean terms using an <code>AND</code> operator.
         </para>
@@ -736,8 +736,8 @@ $table->delete($where);
             <para>
                 The values and identifiers in the SQL expression are not quoted for you. If you
                 have values or identifiers that require quoting, you are responsible for doing
-                this. Use the <code>quote()</code>, <code>quoteInto()</code>, and
-                <code>quoteIdentifier()</code> methods of the database adapter.
+                this. Use the <methodname>quote()</methodname>, <methodname>quoteInto()</methodname>, and
+                <methodname>quoteIdentifier()</methodname> methods of the database adapter.
             </para>
 
         </note>
@@ -750,7 +750,7 @@ $table->delete($where);
 
         <para>
             You can query the database table for rows matching specific values in the primary key,
-            using the <code>find()</code> method. The first argument of this method is either a
+            using the <methodname>find()</methodname> method. The first argument of this method is either a
             single value or an array of values to match against the primary key of the table.
         </para>
 
@@ -780,16 +780,16 @@ $rows = $table->find(array(1234, 5678));
         </para>
 
         <para>
-            The <code>find()</code> method might return fewer rows than the number of values you
+            The <methodname>find()</methodname> method might return fewer rows than the number of values you
             specify for the primary key, if some of the values don't match any rows in the database
             table. The method even may return zero rows. Because the number of rows returned is
-            variable, the <code>find()</code> method returns an object of type
+            variable, the <methodname>find()</methodname> method returns an object of type
             <classname>Zend_Db_Table_Rowset_Abstract</classname>.
         </para>
 
         <para>
             If the primary key is a compound key, that is, it consists of multiple columns, you can
-            specify the additional columns as additional arguments to the <code>find()</code>
+            specify the additional columns as additional arguments to the <methodname>find()</methodname>
             method. You must provide as many arguments as the number of columns in the table's
             primary key.
         </para>
@@ -807,7 +807,7 @@ $rows = $table->find(array(1234, 5678));
             <title>Example of finding rows by compound primary key values</title>
 
             <para>
-                The call to <code>find()</code> below to match multiple rows can match two rows in
+                The call to <methodname>find()</methodname> below to match multiple rows can match two rows in
                 the database. The first row must have primary key value (1234, 'ABC'), and the
                 second row must have primary key value (5678, 'DEF').
             </para>
@@ -849,8 +849,8 @@ $rows = $table->find(array(1234, 5678), array('ABC', 'DEF'));
                     <para>
                         The API for fetch operations has been superseded to allow a
                         <classname>Zend_Db_Table_Select</classname> object to modify the query.
-                        However, the deprecated usage of the <code>fetchRow()</code> and
-                        <code>fetchAll()</code> methods will continue to work without modification.
+                        However, the deprecated usage of the <methodname>fetchRow()</methodname> and
+                        <methodname>fetchAll()</methodname> methods will continue to work without modification.
                     </para>
 
                     <para>
@@ -916,7 +916,7 @@ $row = $table->fetchRow(
                         rowset will be <property>readOnly</property> and cannot be used for save()
                         operations. A <classname>Zend_Db_Table_Row</classname> with
                         <property>readOnly</property> status will throw an exception if a
-                        <code>save()</code> operation is attempted.
+                        <methodname>save()</methodname> operation is attempted.
                     </para>
                 </listitem>
 
@@ -987,7 +987,7 @@ $rows =
 
             <para>
                 You can query for a set of rows using any criteria other than the primary key
-                values, using the <code>fetchAll()</code> method of the Table class. This method
+                values, using the <methodname>fetchAll()</methodname> method of the Table class. This method
                 returns an object of type <classname>Zend_Db_Table_Rowset_Abstract</classname>.
             </para>
 
@@ -1186,7 +1186,7 @@ $rows = $table->fetchAll($select);
 
         <para>
             You can query for a single row using criteria similar to that of the
-            <code>fetchAll()</code> method.
+            <methodname>fetchAll()</methodname> method.
         </para>
 
         <example id="zend.db.table.fetch-row.example1">
@@ -1207,7 +1207,7 @@ $row = $table->fetchRow($select);
         <para>
             This method returns an object of type <classname>Zend_Db_Table_Row_Abstract</classname>.
             If the search criteria you specified match no rows in the database table, then
-            <code>fetchRow()</code> returns PHP's <constant>NULL</constant> value.
+            <methodname>fetchRow()</methodname> returns PHP's <constant>NULL</constant> value.
         </para>
 
     </sect2>
@@ -1218,7 +1218,7 @@ $row = $table->fetchRow($select);
 
         <para>
             The <classname>Zend_Db_Table_Abstract</classname> class provides some information about
-            its metadata. The <code>info()</code> method returns an array structure with information
+            its metadata. The <methodname>info()</methodname> method returns an array structure with information
             about the table, its columns and primary key, and other metadata.
         </para>
 
@@ -1237,7 +1237,7 @@ echo "The table name is " . $info['name'] . "\n";
         </example>
 
         <para>
-            The keys of the array returned by the <code>info()</code> method are described below:
+            The keys of the array returned by the <methodname>info()</methodname> method are described below:
         </para>
 
         <itemizedlist>
@@ -1265,7 +1265,7 @@ echo "The table name is " . $info['name'] . "\n";
                 <para>
                     <emphasis>metadata</emphasis> => an associative array, mapping
                     column names to information about the columns. This is the information returned
-                    by the <code>describeTable()</code> method.
+                    by the <methodname>describeTable()</methodname> method.
                 </para>
             </listitem>
 
@@ -1320,16 +1320,16 @@ echo "The table name is " . $info['name'] . "\n";
             underlying database for <link linkend="zend.db.table.info">table
                 metadata</link> whenever that data is needed to perform table
             operations. The table object fetches the table metadata from the
-            database using the adapter's <code>describeTable()</code> method.
+            database using the adapter's <methodname>describeTable()</methodname> method.
             Operations requiring this introspection include:
         </para>
 
         <itemizedlist>
-            <listitem><para><code>insert()</code></para></listitem>
+            <listitem><para><methodname>insert()</methodname></para></listitem>
 
-            <listitem><para><code>find()</code></para></listitem>
+            <listitem><para><methodname>find()</methodname></para></listitem>
 
-            <listitem><para><code>info()</code></para></listitem>
+            <listitem><para><methodname>info()</methodname></para></listitem>
         </itemizedlist>
 
         <para>
@@ -1581,8 +1581,8 @@ $rows = $table->fetchAll($where);
             </example>
 
             <para>
-                You can change the classes by specifying them with the <code>setRowClass()</code>
-                and <code>setRowsetClass()</code> methods. This applies to rows and rowsets created
+                You can change the classes by specifying them with the <methodname>setRowClass()</methodname>
+                and <methodname>setRowsetClass()</methodname> methods. This applies to rows and rowsets created
                 subsequently; it does not change the class of any row or rowset objects you have
                 created previously.
             </para>
@@ -1624,7 +1624,7 @@ $rowsCustom = $table->fetchAll($where);
             <title>Defining Custom Logic for Insert, Update, and Delete</title>
 
             <para>
-                You can override the <code>insert()</code> and <code>update()</code> methods in
+                You can override the <methodname>insert()</methodname> and <methodname>update()</methodname> methods in
                 your Table class. This gives you the opportunity to implement custom code that is
                 executed before performing the database operation. Be sure to call the parent class
                 method when you are done.
@@ -1662,7 +1662,7 @@ class Bugs extends Zend_Db_Table_Abstract
             </example>
 
             <para>
-                You can also override the <code>delete()</code> method.
+                You can also override the <methodname>delete()</methodname> method.
             </para>
 
         </sect3>
@@ -1674,7 +1674,7 @@ class Bugs extends Zend_Db_Table_Abstract
             <para>
                 You can implement custom query methods in your Table class, if you have frequent
                 need to do queries against this table with specific criteria. Most queries can be
-                written using <code>fetchAll()</code>, but this requires that you duplicate code to
+                written using <methodname>fetchAll()</methodname>, but this requires that you duplicate code to
                 form the query conditions if you need to run the query in several places in your
                 application. Therefore it can be convenient to implement a method in the Table
                 class to perform frequently-used queries against this table.
@@ -1740,7 +1740,7 @@ class Bugs extends Zend_Db_Table_Abstract
 
             <para>
                 If you prefer to use inflection, then you must implement the transformation
-                yourself, by overriding the <code>_setupTableName()</code> method in your Table
+                yourself, by overriding the <methodname>_setupTableName()</methodname> method in your Table
                 classes. One way to do this is to define an abstract class that extends
                 <classname>Zend_Db_Table_Abstract</classname>, and then the rest of your tables
                 extend your new abstract class.

documentation/manual/en/module_specs/Zend_Db_Table_Row.xml

@@ -28,9 +28,9 @@
         <title>Fetching a Row</title>
 
         <para>
-            <classname>Zend_Db_Table_Abstract</classname> provides methods <code>find()</code> and
-            <code>fetchAll()</code>, which each return an object of type
-            <classname>Zend_Db_Table_Rowset</classname>, and the method <code>fetchRow()</code>,
+            <classname>Zend_Db_Table_Abstract</classname> provides methods <methodname>find()</methodname> and
+            <methodname>fetchAll()</methodname>, which each return an object of type
+            <classname>Zend_Db_Table_Rowset</classname>, and the method <methodname>fetchRow()</methodname>,
             which returns an object of type <classname>Zend_Db_Table_Row</classname>.
         </para>
 
@@ -109,7 +109,7 @@ echo $row->bug_description;
             <title>Retrieving Row Data as an Array</title>
 
             <para>
-                You can access the row's data as an array using the <code>toArray()</code> method
+                You can access the row's data as an array using the <methodname>toArray()</methodname> method
                 of the Row object. This returns an associative array of the column names to the
                 column values.
             </para>
@@ -135,7 +135,7 @@ foreach ($rowArray as $column => $value) {
             </example>
 
             <para>
-                The array returned from <code>toArray()</code> is not updateable. You can modify
+                The array returned from <methodname>toArray()</methodname> is not updateable. You can modify
                 values in the array as you can with any array, but you cannot save changes to this
                 array to the database directly.
             </para>
@@ -173,7 +173,7 @@ foreach ($rowArray as $column => $value) {
             <para>
                 Using a column accessor to set a value changes the column value of the row object
                 in your application, but it does not commit the change to the database yet. You can
-                do that with the <code>save()</code> method.
+                do that with the <methodname>save()</methodname> method.
             </para>
 
             <example id="zend.db.table.row.write.set.example">
@@ -200,10 +200,10 @@ $row->save();
             <title>Inserting a new row</title>
 
             <para>
-                You can create a new row for a given table with the <code>createRow()</code> method
+                You can create a new row for a given table with the <methodname>createRow()</methodname> method
                 of the table class. You can access fields of this row with the object-oriented
                 interface, but the row is not stored in the database until you call the
-                <code>save()</code> method.
+                <methodname>save()</methodname> method.
             </para>
 
             <example id="zend.db.table.row.write.insert.example">
@@ -251,7 +251,7 @@ $newRow->save();
             <note>
 
                 <para>
-                    The <code>createRow()</code> method was called <code>fetchNew()</code> in
+                    The <methodname>createRow()</methodname> method was called <methodname>fetchNew()</methodname> in
                     earlier releases of <classname>Zend_Db_Table</classname>. You are encouraged to
                     use the new method name, even though the old name continues to work for the sake
                     of backward compatibility.
@@ -267,7 +267,7 @@ $newRow->save();
 
             <para>
                 <classname>Zend_Db_Table_Row_Abstract</classname> provides the
-                <code>setFromArray()</code> method to enable you to set several columns in a single
+                <methodname>setFromArray()</methodname> method to enable you to set several columns in a single
                 row at once, specified in an associative array that maps the column names to values.
                 You may find this method convenient for setting values both for new rows and for
                 rows you need to update.
@@ -303,7 +303,7 @@ $newRow->save();
             <title>Deleting a row</title>
 
             <para>
-                You can call the <code>delete()</code> method on a Row object. This deletes rows in
+                You can call the <methodname>delete()</methodname> method on a Row object. This deletes rows in
                 the database matching the primary key in the Row object.
             </para>
 
@@ -322,7 +322,7 @@ $row->delete();
             </example>
 
             <para>
-                You do not have to call <code>save()</code> to apply the delete; it is executed
+                You do not have to call <methodname>save()</methodname> to apply the delete; it is executed
                 against the database immediately.
             </para>
 
@@ -346,7 +346,7 @@ $row->delete();
             <title>Serializing a Row</title>
 
             <para>
-                Simply use PHP's <code>serialize()</code> function to create a string containing a
+                Simply use PHP's <methodname>serialize()</methodname> function to create a string containing a
                 byte-stream representation of the Row object argument.
             </para>
 
@@ -373,7 +373,7 @@ $serializedRow = serialize($row);
             <title>Unserializing Row Data</title>
 
             <para>
-                Use PHP's <code>unserialize()</code> function to restore a string containing a
+                Use PHP's <methodname>unserialize()</methodname> function to restore a string containing a
                 byte-stream representation of an object. The function returns the original object.
             </para>
 
@@ -420,7 +420,7 @@ echo $rowClone->bug_description;
             <title>Reactivating a Row as Live Data</title>
 
             <para>
-                You can reactivate a disconnected Row, using the <code>setTable()</code> method.
+                You can reactivate a disconnected Row, using the <methodname>setTable()</methodname> method.
                 The argument to this method is a valid object of type
                 <classname>Zend_Db_Table_Abstract</classname>, which you create. Creating a Table
                 object requires a live connection to the database, so by reassociating the Table
@@ -497,7 +497,7 @@ $bugs = new Bugs(array('rowClass' => 'MyRow'));
 
             <para>
                 If application-specific logic needs to be initialized when a row is constructed,
-                you can select to move your tasks to the <code>init()</code> method, which is
+                you can select to move your tasks to the <methodname>init()</methodname> method, which is
                 called after all row metadata has been processed. This is recommended over the
                 <code>__construct</code> method if you do not need to alter the metadata in any
                 programmatic way.
@@ -529,8 +529,8 @@ class MyApplicationRow extends Zend_Db_Table_Row_Abstract
             <title>Defining Custom Logic for Insert, Update, and Delete in Zend_Db_Table_Row</title>
 
             <para>
-                The Row class calls protected methods <code>_insert()</code>,
-                <code>_update()</code>, and <code>_delete()</code> before performing the
+                The Row class calls protected methods <methodname>_insert()</methodname>,
+                <methodname>_update()</methodname>, and <methodname>_delete()</methodname> before performing the
                 corresponding operations <code>INSERT</code>, <code>UPDATE</code>, and
                 <code>DELETE</code>. You can add logic to these methods in your custom Row
                 subclass.
@@ -539,7 +539,7 @@ class MyApplicationRow extends Zend_Db_Table_Row_Abstract
             <para>
                 If you need to do custom logic in a specific table, and the custom logic must occur
                 for every operation on that table, it may make more sense to implement your custom
-                code in the <code>insert()</code>, <code>update()</code> and <code>delete()</code>
+                code in the <methodname>insert()</methodname>, <methodname>update()</methodname> and <methodname>delete()</methodname>
                 methods of your Table class. However, sometimes it may be necessary to do custom
                 logic in the Row class.
             </para>
@@ -652,7 +652,7 @@ class Products extends Zend_Db_Table_Abstract
 
             <para>
                 If you prefer to use inflection, then you must implement the transformation
-                yourself, by overriding the <code>_transformColumn()</code> method in a custom Row
+                yourself, by overriding the <methodname>_transformColumn()</methodname> method in a custom Row
                 class, and using that custom Row class when you perform queries against your Table
                 class.
             </para>
@@ -663,7 +663,7 @@ class Products extends Zend_Db_Table_Abstract
 
                 <para>
                     This allows you to use an inflected version of the column name in the
-                    accessors. The Row class uses the <code>_transformColumn()</code> method to
+                    accessors. The Row class uses the <methodname>_transformColumn()</methodname> method to
                     change the name you use to the native column name in the database table.
                 </para>
 

documentation/manual/en/module_specs/Zend_Db_Table_Rowset.xml

@@ -9,8 +9,8 @@
         <title>Introduction</title>
 
         <para>
-            When you run a query against a Table class using the <code>find()</code> or
-            <code>fetchAll()</code> methods, the result is returned in an object of type
+            When you run a query against a Table class using the <methodname>find()</methodname> or
+            <methodname>fetchAll()</methodname> methods, the result is returned in an object of type
             <classname>Zend_Db_Table_Rowset_Abstract</classname>. A Rowset contains a collection of
             objects descending from <classname>Zend_Db_Table_Row_Abstract</classname>. You can
             iterate through the Rowset and access individual Row objects, reading or modifying data
@@ -24,8 +24,8 @@
         <title>Fetching a Rowset</title>
 
         <para>
-            <classname>Zend_Db_Table_Abstract</classname> provides methods <code>find()</code> and
-            <code>fetchAll()</code>, each of which returns an object of type
+            <classname>Zend_Db_Table_Abstract</classname> provides methods <methodname>find()</methodname> and
+            <methodname>fetchAll()</methodname>, each of which returns an object of type
             <classname>Zend_Db_Table_Rowset_Abstract</classname>.
         </para>
 
@@ -55,7 +55,7 @@ $rowset = $bugs->fetchAll("bug_status = 'NEW'");
             A legitimate query returns zero rows when no rows in the database match the query
             conditions. Therefore, a Rowset object might contain zero Row objects. Since
             <classname>Zend_Db_Table_Rowset_Abstract</classname> implements the
-            <code>Countable</code> interface, you can use <code>count()</code> to determine the
+            <code>Countable</code> interface, you can use <methodname>count()</methodname> to determine the
             number of Rows in the Rowset.
         </para>
 
@@ -82,7 +82,7 @@ if ($rowCount > 0) {
             <title>Reading a Single Row from a Rowset</title>
 
             <para>
-                The simplest way to access a Row from a Rowset is to use the <code>current()</code>
+                The simplest way to access a Row from a Rowset is to use the <methodname>current()</methodname>
                 method. This is particularly appropriate when the Rowset contains exactly one Row.
             </para>
 
@@ -95,7 +95,7 @@ $row    = $rowset->current();
         </example>
 
         <para>
-            If the Rowset contains zero rows, <code>current()</code> returns
+            If the Rowset contains zero rows, <methodname>current()</methodname> returns
             PHP's <constant>NULL</constant> value.
         </para>
 
@@ -141,10 +141,10 @@ foreach ($rowset as $row) {
 
             <para>
                 <code>SeekableIterator</code> allows you to seek to a position that you would like
-                the iterator to jump to. Simply use the <code>seek()</code> method for that. Pass it
+                the iterator to jump to. Simply use the <methodname>seek()</methodname> method for that. Pass it
                 an integer representing the number of the Row you would like your Rowset to point to
                 next, don't forget that it starts with index 0. If the index is wrong, ie doesn't
-                exist, an exception will be thrown. You should use <code>count()</code> to check the
+                exist, an exception will be thrown. You should use <methodname>count()</methodname> to check the
                 number of results before seeking to a position.
             </para>
 
@@ -168,9 +168,9 @@ $row9->save();
         </example>
 
             <para>
-                <code>getRow()</code> allows you to get a specific row in the Rowset, knowing its
+                <methodname>getRow()</methodname> allows you to get a specific row in the Rowset, knowing its
                 position; don't forget however that positions start with index zero. The first
-                parameter for <code>getRow()</code> is an integer for the position asked. The second
+                parameter for <methodname>getRow()</methodname> is an integer for the position asked. The second
                 optional parameter is a boolean; it tells the Rowset iterator if it must seek to
                 that position in the same time, or not (default is false). This method returns a
                 <classname>Zend_Db_Table_Row</classname> object by default. If the position
@@ -203,7 +203,7 @@ $row9->save();
         <title>Retrieving a Rowset as an Array</title>
 
         <para>
-            You can access all the data in the Rowset as an array using the <code>toArray()</code>
+            You can access all the data in the Rowset as an array using the <methodname>toArray()</methodname>
             method of the Rowset object. This returns an array containing one entry per Row. Each
             entry is an associative array having keys that correspond to column names and elements
             that correspond to the respective column values.
@@ -232,7 +232,7 @@ foreach ($rowsetArray as $rowArray) {
         </example>
 
         <para>
-            The array returned from <code>toArray()</code> is not updateable. That is, you can
+            The array returned from <methodname>toArray()</methodname> is not updateable. That is, you can
             modify values in the array as you can with any array, but changes to the array data are
             not propagated to the database.
         </para>
@@ -254,7 +254,7 @@ foreach ($rowsetArray as $rowArray) {
             <title>Serializing a Rowset</title>
 
             <para>
-                Simply use PHP's <code>serialize()</code> function to create a string containing a
+                Simply use PHP's <methodname>serialize()</methodname> function to create a string containing a
                 byte-stream representation of the Rowset object argument.
             </para>
 
@@ -275,7 +275,7 @@ $serializedRowset = serialize($rowset);
             <title>Unserializing a Serialized Rowset</title>
 
             <para>
-                Use PHP's <code>unserialize()</code> function to restore a string containing a
+                Use PHP's <methodname>unserialize()</methodname> function to restore a string containing a
                 byte-stream representation of an object. The function returns the original object.
             </para>
 
@@ -310,7 +310,7 @@ echo $row->bug_description;
         </note>
 
         <para>
-            You can reactivate a disconnected Rowset using the <code>setTable()</code> method. The
+            You can reactivate a disconnected Rowset using the <methodname>setTable()</methodname> method. The
             argument to this method is a valid object of type
             <classname>Zend_Db_Table_Abstract</classname>, which you create. Creating a Table object
             requires a live connection to the database, so by reassociating the Table with the
@@ -341,7 +341,7 @@ $row->save();
         </example>
 
         <para>
-            Reactivating a Rowset with <code>setTable()</code> also reactivates all the Row objects
+            Reactivating a Rowset with <methodname>setTable()</methodname> also reactivates all the Row objects
             contained in that Rowset.
         </para>
 

documentation/manual/en/module_specs/Zend_Debug.xml

@@ -42,10 +42,10 @@ Zend_Debug::dump($var, $label=null, $echo=true);
     <para>
         It may be helpful to understand that internally,
         <classname>Zend_Debug::dump()</classname> method wraps the PHP function
-        <ulink url="http://php.net/var_dump"><code>var_dump()</code></ulink>.
+        <ulink url="http://php.net/var_dump"><methodname>var_dump()</methodname></ulink>.
         If the output stream is detected as a web presentation,
-        the output of <code>var_dump()</code> is escaped using
-        <ulink url="http://php.net/htmlspecialchars"><code>htmlspecialchars()</code></ulink>
+        the output of <methodname>var_dump()</methodname> is escaped using
+        <ulink url="http://php.net/htmlspecialchars"><methodname>htmlspecialchars()</methodname></ulink>
         and wrapped with (X)HTML <code>&lt;pre&gt;</code> tags.
     </para>
 

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

@@ -64,7 +64,7 @@ $data->setIdentifier('id')
 
         <para>
             You can also add a single item at a time, or append items, using
-            <code>addItem()</code> and <code>addItems()</code>.
+            <methodname>addItem()</methodname> and <methodname>addItems()</methodname>.
         </para>
 
         <example id="zend.dojo.data.usage.append">
@@ -98,7 +98,7 @@ $data->addItems($someMoreItems);
             </para></listitem>
 
             <listitem><para>
-                Objects implementing a <code>toArray()</code> method
+                Objects implementing a <methodname>toArray()</methodname> method
             </para></listitem>
 
             <listitem><para>
@@ -108,7 +108,7 @@ $data->addItems($someMoreItems);
 
         <para>
             You can attach collections of the above items via
-            <code>addItems()</code> or <code>setItems()</code> (overwrites all
+            <methodname>addItems()</methodname> or <methodname>setItems()</methodname> (overwrites all
             previously set items); when doing so, you may pass a single
             argument:
         </para>
@@ -127,7 +127,7 @@ $data->addItems($someMoreItems);
 
         <para>
             If you want to specify a field that will act as a label for the
-            item, call <code>setLabel()</code>:
+            item, call <methodname>setLabel()</methodname>:
         </para>
 
         <example id="zend.dojo.data.usage.label">
@@ -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 <code>fromJson()</code> method.
+            dojo.data JSON array, using the <methodname>fromJson()</methodname> method.
         </para>
 
         <example id="zend.dojo.data.usage.populate">
@@ -218,7 +218,7 @@ $data->clearMetadata();
             All items are referenced by the identifier field. Since identifiers
             must be unique, you can use the values of this field to pull
             individual records. There are two ways to do this: with the
-            <code>getItem()</code> method, or via array notation.
+            <methodname>getItem()</methodname> method, or via array notation.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -266,7 +266,7 @@ echo count($data), " items found!";
 ]]></programlisting>
 
         <para>
-            Finally, as the class implements <code>__toString()</code>, you can
+            Finally, as the class implements <methodname>__toString()</methodname>, you can
             also cast it to JSON simply by echoing it or casting to string:
         </para>
 
@@ -286,32 +286,32 @@ $json = (string) $data; // cast to string == cast to JSON
 
             <itemizedlist>
                 <listitem><para>
-                    <code>setItems($items)</code>: set multiple items at once,
+                    <methodname>setItems($items)</methodname>: set multiple items at once,
                     overwriting any items that were previously set in the
                     object. <code>$items</code> should be an array or a
                     <code>Traversable</code> object.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setItem($item, $id = null)</code>: set an individual
+                    <methodname>setItem($item, $id = null)</methodname>: set an individual
                     item, optionally passing an explicit identifier. Overwrites
                     the item if it is already in the collection. Valid items
                     include associative arrays, objects implementing
-                    <code>toArray()</code>, or any object with public
+                    <methodname>toArray()</methodname>, or any object with public
                     properties.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>addItem($item, $id = null)</code>: add an individual
+                    <methodname>addItem($item, $id = null)</methodname>: add an individual
                     item, optionally passing an explicit identifier. Will raise
                     an exception if the item already exists in the collection.
                     Valid items include associative arrays, objects implementing
-                    <code>toArray()</code>, or any object with public
+                    <methodname>toArray()</methodname>, or any object with public
                     properties.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>addItems($items)</code>: add multiple items at once,
+                    <methodname>addItems($items)</methodname>: add multiple items at once,
                     appending them to any current items. Will raise an exception
                     if any of the new items have an identifier matching an
                     identifier already in the collection. <code>$items</code>
@@ -319,61 +319,61 @@ $json = (string) $data; // cast to string == cast to JSON
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getItems()</code>: retrieve all items as an array of
+                    <methodname>getItems()</methodname>: retrieve all items as an array of
                     arrays.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>hasItem($id)</code>: determine whether an item with
+                    <methodname>hasItem($id)</methodname>: determine whether an item with
                     the given identifier exists in the collection.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getItem($id)</code>: retrieve an item with the given
+                    <methodname>getItem($id)</methodname>: retrieve an item with the given
                     identifier from the collection; the item returned will be an
                     associative array. If no item matches, a null value is
                     returned.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>removeItem($id)</code>: remove an item with the given
+                    <methodname>removeItem($id)</methodname>: remove an item with the given
                     identifier from the collection.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>clearItems()</code>: remove all items from the
+                    <methodname>clearItems()</methodname>: remove all items from the
                     collection.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setIdentifier($identifier)</code>: set the name of the
+                    <methodname>setIdentifier($identifier)</methodname>: set the name of the
                     field that represents the unique identifier for each item in
                     the collection.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getIdentifier()</code>: retrieve the name of the
+                    <methodname>getIdentifier()</methodname>: retrieve the name of the
                     identifier field.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setLabel($label)</code>: set the name of a field
+                    <methodname>setLabel($label)</methodname>: set the name of a field
                     to be used as a display label for an item.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getLabel()</code>: retrieve the label field name.
+                    <methodname>getLabel()</methodname>: retrieve the label field name.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>toArray()</code>: cast the object to an array. At a minimum, the
+                    <methodname>toArray()</methodname>: cast the object to an array. At a minimum, the
                     array will contain the keys 'identifier',
                     'items', and 'label' if a label field has been set
                     in the object.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>toJson()</code>: cast the object to a JSON
+                    <methodname>toJson()</methodname>: cast the object to a JSON
                     representation.
                 </para></listitem>
             </itemizedlist>

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

@@ -34,10 +34,10 @@
 
         <para>
             It is important that each element have a unique ID (as fetched from
-            the element's <code>getId()</code> method). If duplicates are
-            detected within the <code>dojo()</code> view helper, the decorator
+            the element's <methodname>getId()</methodname> method). If duplicates are
+            detected within the <methodname>dojo()</methodname> view helper, the decorator
             will trigger a notice, but then create a unique ID by appending the
-            return of <code>uniqid()</code> to the identifier.
+            return of <methodname>uniqid()</methodname> to the identifier.
         </para>
 
         <para>

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

@@ -11,38 +11,38 @@
 
     <itemizedlist>
         <listitem><para>
-                <code>setDijitParam($key, $value)</code>: set a single dijit
+                <methodname>setDijitParam($key, $value)</methodname>: set a single dijit
                 parameter. If the dijit parameter already exists, it will be
                 overwritten.
         </para></listitem>
 
         <listitem><para>
-                <code>setDijitParams(array $params)</code>: set several dijit
+                <methodname>setDijitParams(array $params)</methodname>: set several dijit
                 parameters at once. Any passed parameters matching those
                 already present will overwrite.
         </para></listitem>
 
         <listitem><para>
-                <code>hasDijitParam($key)</code>: If a given dijit parameter
+                <methodname>hasDijitParam($key)</methodname>: If a given dijit parameter
                 is defined and present, return TRUE, otherwise return FALSE.
         </para></listitem>
 
         <listitem><para>
-                <code>getDijitParam($key)</code>: retrieve the given dijit
+                <methodname>getDijitParam($key)</methodname>: retrieve the given dijit
                 parameter. If not available, a null value is returned.
         </para></listitem>
 
         <listitem><para>
-                <code>getDijitParams()</code>: retrieve all dijit parameters.
+                <methodname>getDijitParams()</methodname>: retrieve all dijit parameters.
         </para></listitem>
 
         <listitem><para>
-                <code>removeDijitParam($key)</code>: remove the given dijit
+                <methodname>removeDijitParam($key)</methodname>: remove the given dijit
                 parameter.
         </para></listitem>
 
         <listitem><para>
-                <code>clearDijitParams()</code>: clear all currently defined
+                <methodname>clearDijitParams()</methodname>: clear all currently defined
                 dijit parameters.
         </para></listitem>
     </itemizedlist>
@@ -100,14 +100,14 @@ $element->addDecorator('DijitElement')
 
         <itemizedlist>
             <listitem><para>
-                <code>getLabel()</code> will utilize the element name as the
+                <methodname>getLabel()</methodname> will utilize the element name as the
                 button label if no name is provided. Additionally, it will
                 translate the name if a translation adapter with a matching
                 translation message is available.
             </para></listitem>
 
             <listitem><para>
-                <code>isChecked()</code> determines if the value submitted
+                <methodname>isChecked()</methodname> determines if the value submitted
                 matches the label; if so, it returns true. This is useful for
                 determining which button was used when a form was submitted.
             </para></listitem>
@@ -145,32 +145,32 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setCheckedValue($value)</code>: set the value to use when
+                <methodname>setCheckedValue($value)</methodname>: set the value to use when
                 the element is checked.
             </para></listitem>
 
             <listitem><para>
-                <code>getCheckedValue()</code>: get the value of the item to
+                <methodname>getCheckedValue()</methodname>: get the value of the item to
                 use when checked.
             </para></listitem>
 
             <listitem><para>
-                <code>setUncheckedValue($value)</code>: set the value of the
+                <methodname>setUncheckedValue($value)</methodname>: set the value of the
                 item to use when it is unchecked.
             </para></listitem>
 
             <listitem><para>
-                <code>getUncheckedValue()</code>: get the value of the item to
+                <methodname>getUncheckedValue()</methodname>: get the value of the item to
                 use when it is unchecked.
             </para></listitem>
 
             <listitem><para>
-                <code>setChecked($flag)</code>: mark the element as checked or
+                <methodname>setChecked($flag)</methodname>: mark the element as checked or
                 unchecked.
             </para></listitem>
 
             <listitem><para>
-                <code>isChecked()</code>: determine if the element is currently
+                <methodname>isChecked()</methodname>: determine if the element is currently
                 checked.
             </para></listitem>
         </itemizedlist>
@@ -221,40 +221,40 @@ $form->addElement(
             examining and setting the select options as well as specifying a
             dojo.data datastore (if used). They extend from DijitMulti, which
             allows you to specify select options via the
-            <code>setMultiOptions()</code> and <code>setMultiOption()</code>
+            <methodname>setMultiOptions()</methodname> and <methodname>setMultiOption()</methodname>
             methods. In addition, the following methods are available:
         </para>
 
         <itemizedlist>
             <listitem><para>
-                <code>getStoreInfo()</code>: get all datastore information
+                <methodname>getStoreInfo()</methodname>: get all datastore information
                 currently set. Returns an empty array if no data is currently
                 set.
             </para></listitem>
 
             <listitem><para>
-                <code>setStoreId($identifier)</code>: set the store identifier
+                <methodname>setStoreId($identifier)</methodname>: set the store identifier
                 variable (usually referred to by the attribute 'jsId' in Dojo).
                 This should be a valid javascript variable name.
             </para></listitem>
 
             <listitem><para>
-                <code>getStoreId()</code>: retrieve the store identifier
+                <methodname>getStoreId()</methodname>: retrieve the store identifier
                 variable name.
             </para></listitem>
 
             <listitem><para>
-                <code>setStoreType($dojoType)</code>: set the datastore class
+                <methodname>setStoreType($dojoType)</methodname>: set the datastore class
                 to use; e.g., "dojo.data.ItemFileReadStore".
             </para></listitem>
 
             <listitem><para>
-                <code>getStoreType()</code>: get the dojo datastore class to
+                <methodname>getStoreType()</methodname>: get the dojo datastore class to
                 use.
             </para></listitem>
 
             <listitem><para>
-                <code>setStoreParams(array $params)</code>: set any parameters
+                <methodname>setStoreParams(array $params)</methodname>: set any parameters
                 used to configure the datastore object. As an example,
                 dojo.data.ItemFileReadStore datastore would expect a 'url'
                 parameter pointing to a location that would return the
@@ -262,18 +262,18 @@ $form->addElement(
             </para></listitem>
 
             <listitem><para>
-                <code>getStoreParams()</code>: get any datastore parameters
+                <methodname>getStoreParams()</methodname>: get any datastore parameters
                 currently set; if none, an empty array is returned.
             </para></listitem>
 
             <listitem><para>
-                <code>setAutocomplete($flag)</code>: indicate whether or not
+                <methodname>setAutocomplete($flag)</methodname>: indicate whether or not
                 the selected item will be used when the user leaves the
                 element.
             </para></listitem>
 
             <listitem><para>
-                <code>getAutocomplete()</code>: get the value of the
+                <methodname>getAutocomplete()</methodname>: get the value of the
                 autocomplete flag.
             </para></listitem>
         </itemizedlist>
@@ -283,7 +283,7 @@ $form->addElement(
             this element registers an <code>InArray</code> validator which
             validates against the array keys of registered options. You can
             disable this behavior by either calling
-            <code>setRegisterInArrayValidator(false)</code>, or by passing a
+            <methodname>setRegisterInArrayValidator(false)</methodname>, or by passing a
             false value to the <code>registerInArrayValidator</code>
             configuration key.
         </para>
@@ -361,33 +361,33 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setCurrency($currency)</code>: set the currency type to
+                <methodname>setCurrency($currency)</methodname>: set the currency type to
                 use; should follow the <ulink
                     url="http://en.wikipedia.org/wiki/ISO_4217">ISO-4217</ulink>
                 specification.
             </para></listitem>
 
             <listitem><para>
-                <code>getCurrency()</code>: retrieve the current currency type.
+                <methodname>getCurrency()</methodname>: retrieve the current currency type.
             </para></listitem>
 
             <listitem><para>
-                <code>setSymbol($symbol)</code>: set the 3-letter <ulink
+                <methodname>setSymbol($symbol)</methodname>: set the 3-letter <ulink
                     url="http://en.wikipedia.org/wiki/ISO_4217">ISO-4217</ulink>
                 currency symbol to use.
             </para></listitem>
 
             <listitem><para>
-                <code>getSymbol()</code>: get the current currency symbol.
+                <methodname>getSymbol()</methodname>: get the current currency symbol.
             </para></listitem>
 
             <listitem><para>
-                <code>setFractional($flag)</code>: set whether or not the
+                <methodname>setFractional($flag)</methodname>: set whether or not the
                 currency should allow for fractional values.
             </para></listitem>
 
             <listitem><para>
-                <code>getFractional()</code>: retrieve the status of the
+                <methodname>getFractional()</methodname>: retrieve the status of the
                 fractional flag.
             </para></listitem>
         </itemizedlist>
@@ -430,39 +430,39 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setAmPm($flag)</code> and <code>getAmPm()</code>: Whether
+                <methodname>setAmPm($flag)</methodname> and <methodname>getAmPm()</methodname>: Whether
                 or not to use AM/PM strings in times.
             </para></listitem>
 
             <listitem><para>
-                <code>setStrict($flag)</code> and <code>getStrict()</code>:
+                <methodname>setStrict($flag)</methodname> and <methodname>getStrict()</methodname>:
                 whether or not to use strict regular expression matching when
                 validating input. If false, which is the default, it will be
                 lenient about whitespace and some abbreviations.
             </para></listitem>
 
             <listitem><para>
-                <code>setLocale($locale)</code> and <code>getLocale()</code>:
+                <methodname>setLocale($locale)</methodname> and <methodname>getLocale()</methodname>:
                 Set and retrieve the locale to use with this specific element.
             </para></listitem>
 
             <listitem><para>
-                <code>setDatePattern($pattern)</code> and
-                <code>getDatePattern()</code>: provide and retrieve the <ulink
+                <methodname>setDatePattern($pattern)</methodname> and
+                <methodname>getDatePattern()</methodname>: provide and retrieve the <ulink
                     url="http://www.unicode.org/reports/tr35/#Date_Format_Patterns">unicode
                     date format pattern</ulink> for formatting the date.
             </para></listitem>
 
             <listitem><para>
-                <code>setFormatLength($formatLength)</code> and
-                <code>getFormatLength()</code>: provide and retrieve the format
+                <methodname>setFormatLength($formatLength)</methodname> and
+                <methodname>getFormatLength()</methodname>: provide and retrieve the format
                 length type to use; should be one of "long", "short", "medium"
                 or "full".
             </para></listitem>
 
             <listitem><para>
-                <code>setSelector($selector)</code> and
-                <code>getSelector()</code>: provide and retrieve the style of
+                <methodname>setSelector($selector)</methodname> and
+                <methodname>getSelector()</methodname>: provide and retrieve the style of
                 selector; should be either "date" or "time".
             </para></listitem>
         </itemizedlist>
@@ -510,13 +510,13 @@ $form->addElement(
                 </para>
 
                 <itemizedlist>
-                    <listitem><para><code>addCaptureEvent($event)</code></para></listitem>
-                    <listitem><para><code>addCaptureEvents(array $events)</code></para></listitem>
-                    <listitem><para><code>setCaptureEvents(array $events)</code></para></listitem>
-                    <listitem><para><code>getCaptureEvents()</code></para></listitem>
-                    <listitem><para><code>hasCaptureEvent($event)</code></para></listitem>
-                    <listitem><para><code>removeCaptureEvent($event)</code></para></listitem>
-                    <listitem><para><code>clearCaptureEvents()</code></para></listitem>
+                    <listitem><para><methodname>addCaptureEvent($event)</methodname></para></listitem>
+                    <listitem><para><methodname>addCaptureEvents(array $events)</methodname></para></listitem>
+                    <listitem><para><methodname>setCaptureEvents(array $events)</methodname></para></listitem>
+                    <listitem><para><methodname>getCaptureEvents()</methodname></para></listitem>
+                    <listitem><para><methodname>hasCaptureEvent($event)</methodname></para></listitem>
+                    <listitem><para><methodname>removeCaptureEvent($event)</methodname></para></listitem>
+                    <listitem><para><methodname>clearCaptureEvents()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
@@ -528,13 +528,13 @@ $form->addElement(
                 </para>
 
                 <itemizedlist>
-                    <listitem><para><code>addEvent($event)</code></para></listitem>
-                    <listitem><para><code>addEvents(array $events)</code></para></listitem>
-                    <listitem><para><code>setEvents(array $events)</code></para></listitem>
-                    <listitem><para><code>getEvents()</code></para></listitem>
-                    <listitem><para><code>hasEvent($event)</code></para></listitem>
-                    <listitem><para><code>removeEvent($event)</code></para></listitem>
-                    <listitem><para><code>clearEvents()</code></para></listitem>
+                    <listitem><para><methodname>addEvent($event)</methodname></para></listitem>
+                    <listitem><para><methodname>addEvents(array $events)</methodname></para></listitem>
+                    <listitem><para><methodname>setEvents(array $events)</methodname></para></listitem>
+                    <listitem><para><methodname>getEvents()</methodname></para></listitem>
+                    <listitem><para><methodname>hasEvent($event)</methodname></para></listitem>
+                    <listitem><para><methodname>removeEvent($event)</methodname></para></listitem>
+                    <listitem><para><methodname>clearEvents()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
@@ -547,13 +547,13 @@ $form->addElement(
                 </para>
 
                 <itemizedlist>
-                    <listitem><para><code>addPlugin($plugin)</code></para></listitem>
-                    <listitem><para><code>addPlugins(array $plugins)</code></para></listitem>
-                    <listitem><para><code>setPlugins(array $plugins)</code></para></listitem>
-                    <listitem><para><code>getPlugins()</code></para></listitem>
-                    <listitem><para><code>hasPlugin($plugin)</code></para></listitem>
-                    <listitem><para><code>removePlugin($plugin)</code></para></listitem>
-                    <listitem><para><code>clearPlugins()</code></para></listitem>
+                    <listitem><para><methodname>addPlugin($plugin)</methodname></para></listitem>
+                    <listitem><para><methodname>addPlugins(array $plugins)</methodname></para></listitem>
+                    <listitem><para><methodname>setPlugins(array $plugins)</methodname></para></listitem>
+                    <listitem><para><methodname>getPlugins()</methodname></para></listitem>
+                    <listitem><para><methodname>hasPlugin($plugin)</methodname></para></listitem>
+                    <listitem><para><methodname>removePlugin($plugin)</methodname></para></listitem>
+                    <listitem><para><methodname>clearPlugins()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
@@ -562,8 +562,8 @@ $form->addElement(
                     <emphasis>editActionInterval</emphasis> is used to group
                     events for undo operations. By default, this value is 3
                     seconds. The method
-                    <code>setEditActionInterval($interval)</code> may be used to
-                    set the value, while <code>getEditActionInterval()</code>
+                    <methodname>setEditActionInterval($interval)</methodname> may be used to
+                    set the value, while <methodname>getEditActionInterval()</methodname>
                     will retrieve it.
                 </para>
             </listitem>
@@ -573,8 +573,8 @@ $form->addElement(
                     <emphasis>focusOnLoad</emphasis> is used to determine
                     whether this particular editor will receive focus when the
                     page has loaded. By default, this is false. The method
-                    <code>setFocusOnLoad($flag)</code> may be used to
-                    set the value, while <code>getFocusOnLoad()</code>
+                    <methodname>setFocusOnLoad($flag)</methodname> may be used to
+                    set the value, while <methodname>getFocusOnLoad()</methodname>
                     will retrieve it.
                 </para>
             </listitem>
@@ -583,8 +583,8 @@ $form->addElement(
                 <para>
                     <emphasis>height</emphasis> specifies the height of the
                     editor; by default, this is 300px. The method
-                    <code>setHeight($height)</code> may be used to set the
-                    value, while <code>getHeight()</code> will retrieve it.
+                    <methodname>setHeight($height)</methodname> may be used to set the
+                    value, while <methodname>getHeight()</methodname> will retrieve it.
                 </para>
             </listitem>
 
@@ -594,8 +594,8 @@ $form->addElement(
                     whether the editor will use the parent container's width or
                     simply default to 100% width. By default, this is false
                     (i.e., it will fill the width of the window). The method
-                    <code>setInheritWidth($flag)</code> may be used to set the
-                    value, while <code>getInheritWidth()</code> will retrieve
+                    <methodname>setInheritWidth($flag)</methodname> may be used to set the
+                    value, while <methodname>getInheritWidth()</methodname> will retrieve
                     it.
                 </para>
             </listitem>
@@ -604,8 +604,8 @@ $form->addElement(
                 <para>
                     <emphasis>minHeight</emphasis> indicates the minimum height
                     of the editor; by default, this is 1em. The method
-                    <code>setMinHeight($height)</code> may be used to set the
-                    value, while <code>getMinHeight()</code> will retrieve it.
+                    <methodname>setMinHeight($height)</methodname> may be used to set the
+                    value, while <methodname>getMinHeight()</methodname> will retrieve it.
                 </para>
             </listitem>
 
@@ -619,17 +619,17 @@ $form->addElement(
                 </para>
 
                 <itemizedlist>
-                    <listitem><para><code>addStyleSheet($styleSheet)</code></para></listitem>
+                    <listitem><para><methodname>addStyleSheet($styleSheet)</methodname></para></listitem>
                     <listitem>
-                        <para><code>addStyleSheets(array $styleSheets)</code></para>
+                        <para><methodname>addStyleSheets(array $styleSheets)</methodname></para>
                     </listitem>
                     <listitem>
-                        <para><code>setStyleSheets(array $styleSheets)</code></para>
+                        <para><methodname>setStyleSheets(array $styleSheets)</methodname></para>
                     </listitem>
-                    <listitem><para><code>getStyleSheets()</code></para></listitem>
-                    <listitem><para><code>hasStyleSheet($styleSheet)</code></para></listitem>
-                    <listitem><para><code>removeStyleSheet($styleSheet)</code></para></listitem>
-                    <listitem><para><code>clearStyleSheets()</code></para></listitem>
+                    <listitem><para><methodname>getStyleSheets()</methodname></para></listitem>
+                    <listitem><para><methodname>hasStyleSheet($styleSheet)</methodname></para></listitem>
+                    <listitem><para><methodname>removeStyleSheet($styleSheet)</methodname></para></listitem>
+                    <listitem><para><methodname>clearStyleSheets()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
         </itemizedlist>
@@ -669,8 +669,8 @@ $form->addElement('editor', 'content', array(
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>setTopDecorationDijit($dijit)</code> and
-                    <code>setBottomDecorationDijit($dijit)</code>: set the name
+                    <methodname>setTopDecorationDijit($dijit)</methodname> and
+                    <methodname>setBottomDecorationDijit($dijit)</methodname>: set the name
                     of the dijit to use for either the top or bottom of the
                     slider. This should not include the "dijit.form." prefix,
                     but rather only the final name -- one of "HorizontalRule"
@@ -680,8 +680,8 @@ $form->addElement('editor', 'content', array(
 
             <listitem>
                 <para>
-                    <code>setTopDecorationContainer($container)</code> and
-                    <code>setBottomDecorationContainer($container)</code>:
+                    <methodname>setTopDecorationContainer($container)</methodname> and
+                    <methodname>setBottomDecorationContainer($container)</methodname>:
                     specify the name to use for the container element of the
                     rules; e.g. 'topRule', 'topContainer', etc.
                 </para>
@@ -689,8 +689,8 @@ $form->addElement('editor', 'content', array(
 
             <listitem>
                 <para>
-                    <code>setTopDecorationLabels(array $labels)</code> and
-                    <code>setBottomDecorationLabels(array $labels)</code>: set
+                    <methodname>setTopDecorationLabels(array $labels)</methodname> and
+                    <methodname>setBottomDecorationLabels(array $labels)</methodname>: set
                     the labels to use for one of the RuleLabels dijit types.
                     These should be an indexed array; specify a single empty
                     space to skip a given label position (such as the beginning
@@ -700,8 +700,8 @@ $form->addElement('editor', 'content', array(
 
             <listitem>
                 <para>
-                    <code>setTopDecorationParams(array $params)</code> and
-                    <code>setBottomDecorationParams(array $params)</code>:
+                    <methodname>setTopDecorationParams(array $params)</methodname> and
+                    <methodname>setBottomDecorationParams(array $params)</methodname>:
                     dijit parameters to use when configuring the given Rule or
                     RuleLabels dijit.
                 </para>
@@ -709,8 +709,8 @@ $form->addElement('editor', 'content', array(
 
             <listitem>
                 <para>
-                    <code>setTopDecorationAttribs(array $attribs)</code> and
-                    <code>setBottomDecorationAttribs(array $attribs)</code>:
+                    <methodname>setTopDecorationAttribs(array $attribs)</methodname> and
+                    <methodname>setBottomDecorationAttribs(array $attribs)</methodname>:
                     HTML attributes to specify for the given Rule or RuleLabels
                     HTML element container.
                 </para>
@@ -718,8 +718,8 @@ $form->addElement('editor', 'content', array(
 
             <listitem>
                 <para>
-                    <code>getTopDecoration()</code> and
-                    <code>getBottomDecoration()</code>: retrieve all metadata
+                    <methodname>getTopDecoration()</methodname> and
+                    <methodname>getBottomDecoration()</methodname>: retrieve all metadata
                     for a given Rule or RuleLabels definition, as provided by
                     the above mutators.
                 </para>
@@ -800,52 +800,52 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setDefaultTimeout($timeout)</code> and
-                <code>getDefaultTimeout()</code>: set and retrieve the default
+                <methodname>setDefaultTimeout($timeout)</methodname> and
+                <methodname>getDefaultTimeout()</methodname>: set and retrieve the default
                 timeout, in milliseconds, between when the button is held
                 pressed and the value is changed.
             </para></listitem>
 
             <listitem><para>
-                <code>setTimeoutChangeRate($rate)</code> and
-                <code>getTimeoutChangeRate()</code>: set and retrieve the
+                <methodname>setTimeoutChangeRate($rate)</methodname> and
+                <methodname>getTimeoutChangeRate()</methodname>: set and retrieve the
                 rate, in milliseconds, at which changes will be made when a
                 button is held pressed.
             </para></listitem>
 
             <listitem><para>
-                <code>setLargeDelta($delta)</code> and
-                <code>getLargeDelta()</code>: set and retrieve the amount by
+                <methodname>setLargeDelta($delta)</methodname> and
+                <methodname>getLargeDelta()</methodname>: set and retrieve the amount by
                 which the numeric value should change when a button is held
                 pressed.
             </para></listitem>
 
             <listitem><para>
-                <code>setSmallDelta($delta)</code> and
-                <code>getSmallDelta()</code>: set and retrieve the delta by
+                <methodname>setSmallDelta($delta)</methodname> and
+                <methodname>getSmallDelta()</methodname>: set and retrieve the delta by
                 which the number should change when a button is pressed once.
             </para></listitem>
 
             <listitem><para>
-                <code>setIntermediateChanges($flag)</code> and
-                <code>getIntermediateChanges()</code>: set and retrieve the
+                <methodname>setIntermediateChanges($flag)</methodname> and
+                <methodname>getIntermediateChanges()</methodname>: set and retrieve the
                 flag indicating whether or not each value change should be
                 shown when a button is held pressed.
             </para></listitem>
 
             <listitem><para>
-                <code>setRangeMessage($message)</code> and
-                <code>getRangeMessage()</code>: set and retrieve the message
+                <methodname>setRangeMessage($message)</methodname> and
+                <methodname>getRangeMessage()</methodname>: set and retrieve the message
                 indicating the range of values available.
             </para></listitem>
 
             <listitem><para>
-                <code>setMin($value)</code> and <code>getMin()</code>: set and
+                <methodname>setMin($value)</methodname> and <methodname>getMin()</methodname>: set and
                 retrieve the minimum value possible.
             </para></listitem>
 
             <listitem><para>
-                <code>setMax($value)</code> and <code>getMax()</code>: set and
+                <methodname>setMax($value)</methodname> and <methodname>getMax()</methodname>: set and
                 retrieve the maximum value possible.
             </para></listitem>
         </itemizedlist>
@@ -894,31 +894,31 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setLocale($locale)</code> and <code>getLocale()</code>:
+                <methodname>setLocale($locale)</methodname> and <methodname>getLocale()</methodname>:
                 specify and retrieve a specific or alternate locale to use with
                 this dijit.
             </para></listitem>
 
             <listitem><para>
-                <code>setPattern($pattern)</code> and
-                <code>getPattern()</code>: set and retrieve a <ulink
+                <methodname>setPattern($pattern)</methodname> and
+                <methodname>getPattern()</methodname>: set and retrieve a <ulink
                     url="http://www.unicode.org/reports/tr35/#Number_Format_Patterns">number
                     pattern format</ulink> to use to format the number.
             </para></listitem>
 
             <listitem><para>
-                <code>setType($type)</code> and <code>getType()</code>: set and
+                <methodname>setType($type)</methodname> and <methodname>getType()</methodname>: set and
                 retrieve the numeric format type to use (should be one of
                 'decimal', 'percent', or 'currency').
             </para></listitem>
 
             <listitem><para>
-                <code>setPlaces($places)</code> and <code>getPlaces()</code>:
+                <methodname>setPlaces($places)</methodname> and <methodname>getPlaces()</methodname>:
                 set and retrieve the number of decimal places to support.
             </para></listitem>
 
             <listitem><para>
-                <code>setStrict($flag)</code> and <code>getStrict()</code>: set
+                <methodname>setStrict($flag)</methodname> and <methodname>getStrict()</methodname>: set
                 and retrieve the value of the strict flag, which indicates how
                 much leniency is allowed in relation to whitespace and
                 non-numeric characters.
@@ -995,7 +995,7 @@ $form->addElement(
         <para>
             RadioButton extends from DijitMulti, which
             allows you to specify select options via the
-            <code>setMultiOptions()</code> and <code>setMultiOption()</code>
+            <methodname>setMultiOptions()</methodname> and <methodname>setMultiOption()</methodname>
             methods.
         </para>
 
@@ -1003,7 +1003,7 @@ $form->addElement(
             By default, this element registers an <code>InArray</code> validator
             which validates against the array keys of registered options. You
             can disable this behavior by either calling
-            <code>setRegisterInArrayValidator(false)</code>, or by passing a
+            <methodname>setRegisterInArrayValidator(false)</methodname>, or by passing a
             false value to the <code>registerInArrayValidator</code>
             configuration key.
         </para>
@@ -1070,46 +1070,46 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setClickSelect($flag)</code> and
-                <code>getClickSelect()</code>: set and retrieve the flag
+                <methodname>setClickSelect($flag)</methodname> and
+                <methodname>getClickSelect()</methodname>: set and retrieve the flag
                 indicating whether or not clicking the slider changes the
                 value.
             </para></listitem>
 
             <listitem><para>
-                <code>setIntermediateChanges($flag)</code> and
-                <code>getIntermediateChanges()</code>: set and retrieve the
+                <methodname>setIntermediateChanges($flag)</methodname> and
+                <methodname>getIntermediateChanges()</methodname>: set and retrieve the
                 flag indicating whether or not the dijit will send a
                 notification on each slider change event.
             </para></listitem>
 
             <listitem><para>
-                <code>setShowButtons($flag)</code> and
-                <code>getShowButtons()</code>: set and retrieve the flag
+                <methodname>setShowButtons($flag)</methodname> and
+                <methodname>getShowButtons()</methodname>: set and retrieve the flag
                 indicating whether or not buttons on either end will be
                 displayed; if so, the user can click on these to change the
                 value of the slider.
             </para></listitem>
 
             <listitem><para>
-                <code>setDiscreteValues($value)</code> and
-                <code>getDiscreteValues()</code>: set and retrieve the number
+                <methodname>setDiscreteValues($value)</methodname> and
+                <methodname>getDiscreteValues()</methodname>: set and retrieve the number
                 of discrete values represented by the slider.
             </para></listitem>
 
             <listitem><para>
-                <code>setMaximum($value)</code> and <code>getMaximum()</code>:
+                <methodname>setMaximum($value)</methodname> and <methodname>getMaximum()</methodname>:
                 set the maximum value of the slider.
             </para></listitem>
 
             <listitem><para>
-                <code>setMinimum($value)</code> and <code>getMinimum()</code>:
+                <methodname>setMinimum($value)</methodname> and <methodname>getMinimum()</methodname>:
                 set the minimum value of the slider.
             </para></listitem>
 
             <listitem><para>
-                <code>setPageIncrement($value)</code> and
-                <code>getPageIncrement()</code>: set the amount by which the
+                <methodname>setPageIncrement($value)</methodname> and
+                <methodname>getPageIncrement()</methodname>: set the amount by which the
                 slider will change on keyboard events.
             </para></listitem>
         </itemizedlist>
@@ -1159,32 +1159,32 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setLowercase($flag)</code> and
-                <code>getLowercase()</code>: set and retrieve the flag
+                <methodname>setLowercase($flag)</methodname> and
+                <methodname>getLowercase()</methodname>: set and retrieve the flag
                 indicating whether or not input should be cast to lowercase.
             </para></listitem>
 
             <listitem><para>
-                <code>setPropercase($flag)</code> and
-                <code>getPropercase()</code>: set and retrieve the flag
+                <methodname>setPropercase($flag)</methodname> and
+                <methodname>getPropercase()</methodname>: set and retrieve the flag
                 indicating whether or not the input should be cast to Proper
                 Case.
             </para></listitem>
 
             <listitem><para>
-                <code>setUppercase($flag)</code> and <code>getUppercase()</code>: set and retrieve
+                <methodname>setUppercase($flag)</methodname> and <methodname>getUppercase()</methodname>: set and retrieve
                 the flag indicating whether or not the input should be cast to UPPERCASE.
             </para></listitem>
 
             <listitem><para>
-                <code>setTrim($flag)</code> and <code>getTrim()</code>: set and
+                <methodname>setTrim($flag)</methodname> and <methodname>getTrim()</methodname>: set and
                 retrieve the flag indicating whether or not leading or trailing
                 whitespace should be stripped.
             </para></listitem>
 
             <listitem><para>
-                <code>setMaxLength($length)</code> and
-                <code>getMaxLength()</code>: set and retrieve the maximum
+                <methodname>setMaxLength($length)</methodname> and
+                <methodname>getMaxLength()</methodname>: set and retrieve the maximum
                 length of input.
             </para></listitem>
         </itemizedlist>
@@ -1256,29 +1256,29 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setTimePattern($pattern)</code> and
-                <code>getTimePattern()</code>: set and retrieve the <ulink
+                <methodname>setTimePattern($pattern)</methodname> and
+                <methodname>getTimePattern()</methodname>: set and retrieve the <ulink
                     url="http://www.unicode.org/reports/tr35/#Date_Format_Patterns">unicode
                     time format pattern</ulink> for formatting the time.
             </para></listitem>
 
             <listitem><para>
-                <code>setClickableIncrement($format)</code> and
-                <code>getClickableIncrement()</code>: set the <ulink
+                <methodname>setClickableIncrement($format)</methodname> and
+                <methodname>getClickableIncrement()</methodname>: set the <ulink
                     url="http://en.wikipedia.org/wiki/ISO_8601">ISO-8601</ulink>
                 string representing the amount by which every clickable element
                 in the time picker increases.
             </para></listitem>
 
             <listitem><para>
-                <code>setVisibleIncrement($format)</code> and
-                <code>getVisibleIncrement()</code>: set the increment visible
+                <methodname>setVisibleIncrement($format)</methodname> and
+                <methodname>getVisibleIncrement()</methodname>: set the increment visible
                 in the time chooser; must follow ISO-8601 formats.
             </para></listitem>
 
             <listitem><para>
-                <code>setVisibleRange($format)</code> and
-                <code>getVisibleRange()</code>: set and retrieve the range of
+                <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.
             </para></listitem>
@@ -1320,47 +1320,47 @@ $form->addElement(
 
         <itemizedlist>
             <listitem><para>
-                <code>setInvalidMessage($message)</code> and
-                <code>getInvalidMessage()</code>: set and retrieve the tooltip
+                <methodname>setInvalidMessage($message)</methodname> and
+                <methodname>getInvalidMessage()</methodname>: set and retrieve the tooltip
                 message to display when the value does not validate.
             </para></listitem>
 
             <listitem><para>
-                <code>setPromptMessage($message)</code> and
-                <code>getPromptMessage()</code>: set and retrieve the tooltip
+                <methodname>setPromptMessage($message)</methodname> and
+                <methodname>getPromptMessage()</methodname>: set and retrieve the tooltip
                 message to display for element usage.
             </para></listitem>
 
             <listitem><para>
-                <code>setRegExp($regexp)</code> and <code>getRegExp()</code>:
+                <methodname>setRegExp($regexp)</methodname> and <methodname>getRegExp()</methodname>:
                 set and retrieve the regular expression to use for validating
                 the element. The regular expression does not need boundaries
                 (unlike PHP's preg* family of functions).
             </para></listitem>
 
             <listitem><para>
-                <code>setConstraint($key, $value)</code> and
-                <code>getConstraint($key)</code>: set and retrieve additional
+                <methodname>setConstraint($key, $value)</methodname> and
+                <methodname>getConstraint($key)</methodname>: set and retrieve additional
                 constraints to use when validating the element; used primarily
                 with subclasses. Constraints are stored in the 'constraints'
                 key of the dijit parameters.
             </para></listitem>
 
             <listitem><para>
-                <code>setConstraints(array $constraints)</code> and
-                <code>getConstraints()</code>: set and retrieve individual
+                <methodname>setConstraints(array $constraints)</methodname> and
+                <methodname>getConstraints()</methodname>: set and retrieve individual
                 constraints to use when validating the element; used primarily
                 with subclasses.
             </para></listitem>
 
             <listitem><para>
-                <code>hasConstraint($key)</code>: test whether a given
+                <methodname>hasConstraint($key)</methodname>: test whether a given
                 constraint exists.
             </para></listitem>
 
             <listitem><para>
-                <code>removeConstraint($key)</code> and
-                <code>clearConstraints()</code>: remove an individual or all
+                <methodname>removeConstraint($key)</methodname> and
+                <methodname>clearConstraints()</methodname>: remove an individual or all
                 constraints for the element.
             </para></listitem>
         </itemizedlist>

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

@@ -67,7 +67,7 @@
 
         <para>
             A second approach is to call <classname>Zend_Dojo::enableForm()</classname>
-            within your custom form's <code>init()</code> method; when the form
+            within your custom form's <methodname>init()</methodname> method; when the form
             definition is complete, loop through all SubForms to dojo-enable
             them:
         </para>

documentation/manual/en/module_specs/Zend_Dojo-View-Dojo.xml

@@ -4,7 +4,7 @@
     <title>dojo() View Helper</title>
 
     <para>
-        The <code>dojo()</code> view helper is intended to simplify setting up
+        The <methodname>dojo()</methodname> view helper is intended to simplify setting up
         the Dojo environment, including the following responsibilities:
     </para>
 
@@ -18,7 +18,7 @@
     </itemizedlist>
 
     <para>
-        The <code>dojo()</code> view helper implementation is an example of a
+        The <methodname>dojo()</methodname> view helper implementation is an example of a
         placeholder implementation. The data set in it persists between view
         objects and may be directly echoed from your layout script.
     </para>
@@ -136,7 +136,7 @@ $this->dojo()->enable()
             unreachable. To promote standards and document validation,
             Zend Framework uses programmatic usage by default; the various view
             helpers will generate javascript and push it to the
-            <code>dojo()</code> view helper for inclusion when rendered.
+            <methodname>dojo()</methodname> view helper for inclusion when rendered.
         </para>
 
         <para>
@@ -156,7 +156,7 @@ $this->dojo()->enable()
 
             <para>
                 To specify declarative usage, simply call the static
-                <code>setUseDeclarative()</code> method:
+                <methodname>setUseDeclarative()</methodname> method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -165,7 +165,7 @@ Zend_Dojo_View_Helper_Dojo::setUseDeclarative();
 
             <para>
                 If you decide instead to use programmatic usage, call the static
-                <code>setUseProgrammatic()</code> method:
+                <methodname>setUseProgrammatic()</methodname> method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -258,8 +258,8 @@ $view->dojo()->addStylesheetModule('dijit.themes.tundra');
         </para>
 
         <para>
-            To use a layer, the <code>dojo()</code> view helper has a
-            <code>addLayer()</code> method for adding paths to required layers:
+            To use a layer, the <methodname>dojo()</methodname> view helper has a
+            <methodname>addLayer()</methodname> method for adding paths to required layers:
         </para>
 
         <programlisting language="html"><![CDATA[
@@ -277,108 +277,108 @@ $view->dojo()->addLayer('/js/foo/foo.js');
         <title>Methods Available</title>
 
         <para>
-            The <code>dojo()</code> view helper always returns an instance of
+            The <methodname>dojo()</methodname> view helper always returns an instance of
             the dojo placeholder container. That container object has the
             following methods available:
         </para>
 
         <itemizedlist>
-            <listitem><para><code>setView(Zend_View_Interface $view)</code>: set
+            <listitem><para><methodname>setView(Zend_View_Interface $view)</methodname>: set
                     a view instance in the container.</para></listitem>
-            <listitem><para><code>enable()</code>: explicitly enable Dojo
+            <listitem><para><methodname>enable()</methodname>: explicitly enable Dojo
                     integration.</para></listitem>
-            <listitem><para><code>disable()</code>: disable Dojo
+            <listitem><para><methodname>disable()</methodname>: disable Dojo
                     integration.</para></listitem>
-            <listitem><para><code>isEnabled()</code>: determine whether or not
+            <listitem><para><methodname>isEnabled()</methodname>: determine whether or not
                     Dojo integration is enabled.</para></listitem>
-            <listitem><para><code>requireModule($module)</code>: setup a
+            <listitem><para><methodname>requireModule($module)</methodname>: setup a
                     <code>dojo.require</code> statement.</para></listitem>
-            <listitem><para><code>getModules()</code>: determine what modules
+            <listitem><para><methodname>getModules()</methodname>: determine what modules
                     have been required.</para></listitem>
-            <listitem><para><code>registerModulePath($module, $path)</code>:
+            <listitem><para><methodname>registerModulePath($module, $path)</methodname>:
                     register a custom Dojo module path.</para></listitem>
-            <listitem><para><code>getModulePaths()</code>: get list of
+            <listitem><para><methodname>getModulePaths()</methodname>: get list of
                     registered module paths.</para></listitem>
-            <listitem><para><code>addLayer($path)</code>: add a layer (custom
+            <listitem><para><methodname>addLayer($path)</methodname>: add a layer (custom
                     build) path to use.</para></listitem>
-            <listitem><para><code>getLayers()</code>: get a list of all
+            <listitem><para><methodname>getLayers()</methodname>: get a list of all
                     registered layer paths (custom builds).</para></listitem>
-            <listitem><para><code>removeLayer($path)</code>: remove the layer
+            <listitem><para><methodname>removeLayer($path)</methodname>: remove the layer
                     that matches <code>$path</code> from the list of registered
                     layers (custom builds).</para></listitem>
-            <listitem><para><code>setCdnBase($url)</code>: set the base URL for
+            <listitem><para><methodname>setCdnBase($url)</methodname>: set the base URL for
                     a CDN; typically, one of the
                     <classname>Zend_Dojo::CDN_BASE_AOL</classname> or
                     <classname>Zend_Dojo::CDN_BASE_GOOGLE</classname>, but it only needs
                     to be the URL string prior to the version number.</para></listitem>
-            <listitem><para><code>getCdnBase()</code>: retrieve the base CDN url
+            <listitem><para><methodname>getCdnBase()</methodname>: retrieve the base CDN url
                     to utilize.</para></listitem>
-            <listitem><para><code>setCdnVersion($version = null)</code>: set
+            <listitem><para><methodname>setCdnVersion($version = null)</methodname>: set
                     which version of Dojo to utilize from the CDN.</para></listitem>
-            <listitem><para><code>getCdnVersion()</code>: retrieve what
+            <listitem><para><methodname>getCdnVersion()</methodname>: retrieve what
                     version of Dojo from the CDN will be used.</para></listitem>
-            <listitem><para><code>setCdnDojoPath($path)</code>: set the relative
+            <listitem><para><methodname>setCdnDojoPath($path)</methodname>: set the relative
                     path to the dojo.js or dojo.xd.js file on a CDN; typically,
                     one of the <classname>Zend_Dojo::CDN_DOJO_PATH_AOL</classname> or
                     <classname>Zend_Dojo::CDN_DOJO_PATH_GOOGLE</classname>, but it only
                     needs to be the path string following the version
                     number.</para></listitem>
-            <listitem><para><code>getCdnDojoPath()</code>: retrieve the last
+            <listitem><para><methodname>getCdnDojoPath()</methodname>: retrieve the last
                     path segment of the CDN url pointing to the dojo.js
                     file.</para></listitem>
-            <listitem><para><code>useCdn()</code>: tell the container to
+            <listitem><para><methodname>useCdn()</methodname>: tell the container to
                     utilize the CDN; implicitly enables integration.</para></listitem>
-            <listitem><para><code>setLocalPath($path)</code>: tell the container
+            <listitem><para><methodname>setLocalPath($path)</methodname>: tell the container
                     the path to a local Dojo install (should be a path relative
                     to the server, and contain the dojo.js file itself);
                     implicitly enables integration.</para></listitem>
-            <listitem><para><code>getLocalPath()</code>: determine what local
+            <listitem><para><methodname>getLocalPath()</methodname>: determine what local
                     path to Dojo is being used.</para></listitem>
-            <listitem><para><code>useLocalPath()</code>: is the integration
+            <listitem><para><methodname>useLocalPath()</methodname>: is the integration
                     utilizing a Dojo local path?</para></listitem>
-            <listitem><para><code>setDjConfig(array $config)</code>: set
+            <listitem><para><methodname>setDjConfig(array $config)</methodname>: set
                     dojo/dijit configuration values (expects assoc
                     array).</para></listitem>
-            <listitem><para><code>setDjConfigOption($option, $value)</code>: set
+            <listitem><para><methodname>setDjConfigOption($option, $value)</methodname>: set
                     a single dojo/dijit configuration value.</para></listitem>
-            <listitem><para><code>getDjConfig()</code>: get all dojo/dijit
+            <listitem><para><methodname>getDjConfig()</methodname>: get all dojo/dijit
                     configuration values.</para></listitem>
             <listitem><para><code>getDjConfigOption($option, $default =
                     null)</code>: get a single dojo/dijit configuration
                     value.</para></listitem>
-            <listitem><para><code>addStylesheetModule($module)</code>: add a
+            <listitem><para><methodname>addStylesheetModule($module)</methodname>: add a
                     stylesheet based on a module theme.</para></listitem>
-            <listitem><para><code>getStylesheetModules()</code>: get stylesheets
+            <listitem><para><methodname>getStylesheetModules()</methodname>: get stylesheets
                     registered as module themes.</para></listitem>
-            <listitem><para><code>addStylesheet($path)</code>: add a local
+            <listitem><para><methodname>addStylesheet($path)</methodname>: add a local
                     stylesheet for use with Dojo.</para></listitem>
-            <listitem><para><code>getStylesheets()</code>: get local Dojo
+            <listitem><para><methodname>getStylesheets()</methodname>: get local Dojo
                     stylesheets.</para></listitem>
-            <listitem><para><code>addOnLoad($spec, $function = null)</code>: add
+            <listitem><para><methodname>addOnLoad($spec, $function = null)</methodname>: add
                     a lambda for dojo.onLoad to call. If one argument is passed,
                     it is assumed to be either a function name or a javascript
                     closure. If two arguments are passed, the first is assumed
                     to be the name of an object instance variable and the second
                     either a method name in that object or a closure to utilize
                     with that object.</para></listitem>
-            <listitem><para><code>prependOnLoad($spec, $function = null)</code>:
-                    exactly like <code>addOnLoad()</code>, excepts prepends to
+            <listitem><para><methodname>prependOnLoad($spec, $function = null)</methodname>:
+                    exactly like <methodname>addOnLoad()</methodname>, excepts prepends to
                     beginning of onLoad stack.</para></listitem>
-            <listitem><para><code>getOnLoadActions()</code>: retrieve all
+            <listitem><para><methodname>getOnLoadActions()</methodname>: retrieve all
                     dojo.onLoad actions registered with the container. This will
                     be an array of arrays.</para></listitem>
-            <listitem><para><code>onLoadCaptureStart($obj = null)</code>:
+            <listitem><para><methodname>onLoadCaptureStart($obj = null)</methodname>:
                     capture data to be used as a lambda for dojo.onLoad(). If
                     $obj is provided, the captured JS code will be considered a
                     closure to use with that Javascript object.</para></listitem>
-            <listitem><para><code>onLoadCaptureEnd($obj = null)</code>: finish
+            <listitem><para><methodname>onLoadCaptureEnd($obj = null)</methodname>: finish
                     capturing data for use with dojo.onLoad().</para></listitem>
-            <listitem><para><code>javascriptCaptureStart()</code>:
+            <listitem><para><methodname>javascriptCaptureStart()</methodname>:
                     capture arbitrary javascript to be included with Dojo JS
                     (onLoad, require, etc. statements).</para></listitem>
-            <listitem><para><code>javascriptCaptureEnd()</code>: finish
+            <listitem><para><methodname>javascriptCaptureEnd()</methodname>: finish
                     capturing javascript.</para></listitem>
-            <listitem><para><code>__toString()</code>: cast the container to a
+            <listitem><para><methodname>__toString()</methodname>: cast the container to a
                     string; renders all HTML style and script elements.</para></listitem>
         </itemizedlist>
     </sect3>

documentation/manual/en/module_specs/Zend_Dojo-View-Helpers.xml

@@ -90,7 +90,7 @@
 
             <para>
                 The argument order varies from the other dijits in order to
-                keep compatibility with the standard <code>form()</code> view
+                keep compatibility with the standard <methodname>form()</methodname> view
                 helper.
             </para>
         </listitem>
@@ -164,8 +164,8 @@ $view->addHelperPath('Zend/Dojo/View/Helper', 'Zend_Dojo_View_Helper');
             signature <code>string ($id = null, $content = '', array $params =
                 array(), array $attribs = array())</code>. In all caess, if you
             pass no arguments, the helper object itself will be returned. This
-            gives you access to the <code>captureStart()</code> and
-            <code>captureEnd()</code> methods, which allow you to capture
+            gives you access to the <methodname>captureStart()</methodname> and
+            <methodname>captureEnd()</methodname> methods, which allow you to capture
             content instead of passing it to the layout container.
         </para>
 
@@ -342,10 +342,10 @@ $view->addHelperPath('Zend/Dojo/View/Helper', 'Zend_Dojo_View_Helper');
 
             <listitem>
                 <para>
-                    <code>captureEnd($id)</code>:
+                    <methodname>captureEnd($id)</methodname>:
                     finish capturing content to include in a container.
                     <code>$id</code> should refer to an id previously used with
-                    a <code>captureStart()</code> call. Returns a string
+                    a <methodname>captureStart()</methodname> call. Returns a string
                     representing the container and its contents, just as if
                     you'd simply passed content to the helper itself.
                 </para>
@@ -619,7 +619,7 @@ $view->headMeta()->appendHttpEquiv('Content-Type',
 
                     <para>
                         This will mean, of course, that you will need to ensure
-                        that the <code>headMeta()</code> placeholder is echoed
+                        that the <methodname>headMeta()</methodname> placeholder is echoed
                         in your layout script.
                     </para>
                 </note>
@@ -1122,8 +1122,8 @@ echo $view->validationTextBox(
             <code>CustomDijit</code> extends the base
             <code>DijitContainer</code> view helper, which also allows it to
             capture content (using the
-            <code>captureStart()</code>/<code>captureEnd()</code> pair of
-            methods). <code>captureStart()</code> also expects that you pass the
+            <methodname>captureStart()</methodname>/<methodname>captureEnd()</methodname> pair of
+            methods). <methodname>captureStart()</methodname> also expects that you pass the
             "dojoType" attribute to its "params" argument.
         </para>
 
@@ -1157,7 +1157,7 @@ echo $view->validationTextBox(
 
             <para>
                 If you wanted to capture content instead, simply use the
-                <code>captureStart()</code> method, and pass the "dojoType" to
+                <methodname>captureStart()</methodname> method, and pass the "dojoType" to
                 the "params" argument:
             </para>
 

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

@@ -21,7 +21,7 @@
         <para>
             To use Dojo view helpers, you will need to tell your view object
             where to find them. You can do this by calling
-            <code>addHelperPath()</code>:
+            <methodname>addHelperPath()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -30,7 +30,7 @@ $view->addHelperPath('Zend/Dojo/View/Helper/', 'Zend_Dojo_View_Helper');
 
         <para>
             Alternately, you can use <classname>Zend_Dojo</classname>'s
-            <code>enableView()</code> method to do the work for you:
+            <methodname>enableView()</methodname> method to do the work for you:
         </para>
 
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Dom-Query.xml

@@ -29,7 +29,7 @@
             To use <classname>Zend_Dom_Query</classname>, you instantiate a
             <classname>Zend_Dom_Query</classname> object, optionally passing a document to
             query (a string). Once you have a document, you can use either the
-            <code>query()</code> or <code>queryXpath()</code> methods; each
+            <methodname>query()</methodname> or <methodname>queryXpath()</methodname> methods; each
             method will return a <classname>Zend_Dom_Query_Result</classname> object with
             any matching nodes.
         </para>
@@ -153,7 +153,7 @@ foreach ($results as $result) {
 
         <para>
             <classname>Zend_Dom_Query</classname> also allows straight XPath queries
-            utilizing the <code>queryXpath()</code> method; you can pass any
+            utilizing the <methodname>queryXpath()</methodname> method; you can pass any
             valid XPath query to this method, and it will return a
             <classname>Zend_Dom_Query_Result</classname> object.
         </para>
@@ -177,45 +177,45 @@ foreach ($results as $result) {
 
             <itemizedlist>
                 <listitem><para>
-                    <code>setDocumentXml($document)</code>: specify an XML
+                    <methodname>setDocumentXml($document)</methodname>: specify an XML
                     string to query against.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setDocumentXhtml($document)</code>: specify an XHTML
+                    <methodname>setDocumentXhtml($document)</methodname>: specify an XHTML
                     string to query against.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setDocumentHtml($document)</code>: specify an HTML
+                    <methodname>setDocumentHtml($document)</methodname>: specify an HTML
                     string to query against.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setDocument($document)</code>: specify a
+                    <methodname>setDocument($document)</methodname>: specify a
                     string to query against; <classname>Zend_Dom_Query</classname> will
                     then attempt to autodetect the document type.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getDocument()</code>: retrieve the original document
+                    <methodname>getDocument()</methodname>: retrieve the original document
                     string provided to the object.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getDocumentType()</code>: retrieve the document
+                    <methodname>getDocumentType()</methodname>: retrieve the document
                     type of the document provided to the object; will be one of
                     the <code>DOC_XML</code>, <code>DOC_XHTML</code>, or
                     <code>DOC_HTML</code> class constants.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>query($query)</code>: query the document using CSS
+                    <methodname>query($query)</methodname>: query the document using CSS
                     selector notation.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>queryXpath($xPathQuery)</code>: query the document
+                    <methodname>queryXpath($xPathQuery)</methodname>: query the document
                     using XPath notation.
                 </para></listitem>
             </itemizedlist>
@@ -229,25 +229,25 @@ foreach ($results as $result) {
                 implements both <code>Iterator</code> and
                 <code>Countable</code>, and as such can be used in a
                 <code>foreach</code> loop as well as with the
-                <code>count()</code> function. Additionally, it exposes the
+                <methodname>count()</methodname> function. Additionally, it exposes the
                 following methods:
             </para>
 
             <itemizedlist>
                 <listitem><para>
-                    <code>getCssQuery()</code>: return the CSS selector query
+                    <methodname>getCssQuery()</methodname>: return the CSS selector query
                     used to produce the result (if any).
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getXpathQuery()</code>: return the XPath query
+                    <methodname>getXpathQuery()</methodname>: return the XPath query
                     used to produce the result. Internally,
                     <classname>Zend_Dom_Query</classname> converts CSS selector queries to
                     XPath, so this value will always be populated.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getDocument()</code>: retrieve the DOMDocument the
+                    <methodname>getDocument()</methodname>: retrieve the DOMDocument the
                     selection was made against.
                 </para></listitem>
             </itemizedlist>

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

@@ -11,7 +11,7 @@
 
     <para>
         Here is an example of a custom Atom entry class that handles its own <code>myns:</code>
-        namespace entries. Note that it also makes the <code>registerNamespace()</code> call for
+        namespace entries. Note that it also makes the <methodname>registerNamespace()</methodname> call for
         you, so the end user doesn't need to worry about namespaces at all.
     </para>
 

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

@@ -11,7 +11,7 @@
 $feedArray = Zend_Feed::findFeeds('http://www.example.com/news.html');
 ]]></programlisting>
     <para>
-        Here the <code>findFeeds()</code> method returns an array of
+        Here the <methodname>findFeeds()</methodname> method returns an array of
         <classname>Zend_Feed_Abstract</classname> objects that are referenced by
         <code>&lt;link&gt;</code> tags on the news.html web page. Depending on the type of each
         feed, each respective entry in the <code>$feedArray</code> array may be a

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

@@ -293,13 +293,13 @@ array(
             <para>
                 You can create a Zeed_Feed instance from any data source implementing
                 <classname>Zend_Feed_Builder_Interface</classname>. You just have to implement the
-                <code>getHeader()</code> and <code>getEntries()</code> methods to be able to use
+                <methodname>getHeader()</methodname> and <methodname>getEntries()</methodname> methods to be able to use
                 your object with <classname>Zend_Feed::importBuilder()</classname>. As a simple
                 reference implementation, you can use <classname>Zend_Feed_Builder</classname>,
                 which takes an array in its constructor, performs some minor validation, and then
-                can be used in the <code>importBuilder()</code> method. The <code>getHeader()</code>
+                can be used in the <methodname>importBuilder()</methodname> method. The <methodname>getHeader()</methodname>
                 method must return an instance of <classname>Zend_Feed_Builder_Header</classname>,
-                and <code>getEntries()</code> must return an array of
+                and <methodname>getEntries()</methodname> must return an array of
                 <classname>Zend_Feed_Builder_Entry</classname> instances.
             </para>
 
@@ -338,7 +338,7 @@ $rssFeedFromArray =
 
             <para>
                 To dump the contents of a <classname>Zend_Feed_Abstract</classname> instance, you
-                may use <code>send()</code> or <code>saveXml()</code> methods.
+                may use <methodname>send()</methodname> or <methodname>saveXml()</methodname> methods.
             </para>
 
             <programlisting language="php"><![CDATA[

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

@@ -80,27 +80,27 @@
                     <code>setFilters(array $filters, $files =
                         null)</code>: Overwrites any existing filters with
                     the filters specified. The filters should follow the
-                    syntax for <code>addFilters()</code>.
+                    syntax for <methodname>addFilters()</methodname>.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>hasFilter($name)</code>: Indicates if a
+                    <methodname>hasFilter($name)</methodname>: Indicates if a
                     filter has been registered.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>getFilter($name)</code>: Returns a previously
+                    <methodname>getFilter($name)</methodname>: Returns a previously
                     registered filter.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>getFilters($files = null)</code>: Returns
+                    <methodname>getFilters($files = null)</methodname>: Returns
                     registered filters; if <code>$files</code> is passed,
                     returns filters for that particular file or set of
                     files.
@@ -109,14 +109,14 @@
 
             <listitem>
                 <para>
-                    <code>removeFilter($name)</code>: Removes a previously
+                    <methodname>removeFilter($name)</methodname>: Removes a previously
                     registered filter.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>clearFilters()</code>: Clears all
+                    <methodname>clearFilters()</methodname>: Clears all
                     registered filters.
                 </para>
             </listitem>
@@ -142,8 +142,8 @@ $upload->addFilter('Rename',
             <title>Limit filters to single files</title>
 
             <para>
-                <code>addFilter()</code>, <code>addFilters()</code>, and
-                <code>setFilters()</code> each accept a final
+                <methodname>addFilter()</methodname>, <methodname>addFilters()</methodname>, and
+                <methodname>setFilters()</methodname> each accept a final
                 <code>$files</code> argument. This argument can be used to
                 specify a particular file or array of files on which to set the
                 given filter.
@@ -158,7 +158,7 @@ $upload->addFilter('Rename', 'C:\picture\uploads', 'file2');
         </example>
 
         <para>
-            Generally you should simply use the <code>addFilters()</code> method, which can be
+            Generally you should simply use the <methodname>addFilters()</methodname> method, which can be
             called multiple times.
         </para>
 
@@ -166,7 +166,7 @@ $upload->addFilter('Rename', 'C:\picture\uploads', 'file2');
             <title>Add multiple filters</title>
 
             <para>
-                Often it's simpler just to call <code>addFilter()</code> multiple times. One call
+                Often it's simpler just to call <methodname>addFilter()</methodname> multiple times. One call
                 for each filter. This also increases the readability and makes your code more
                 maintainable. As all methods provide a fluent interface you can couple the calls as
                 shown below:
@@ -305,7 +305,7 @@ $upload->addFilter('Encrypt',
 
         <para>
             At initiation you can give a string which will then be used as encoding. Or you can use
-            the <code>setEncoding()</code> method to set it afterwards.
+            the <methodname>setEncoding()</methodname> method to set it afterwards.
         </para>
 
         <example id="zend.file.transfer.filters.lowercase.example">
@@ -368,9 +368,9 @@ $upload->addFilter('LowerCase', 'ISO-8859-1');
         </itemizedlist>
 
         <para>
-            Additionally you can also use the method <code>setFile()</code> to set files, which
-            erases all previous set, <code>addFile()</code> to add a new file to existing ones, and
-            <code>getFile()</code> to get all actually set files. To simplify things, this filter
+            Additionally you can also use the method <methodname>setFile()</methodname> to set files, which
+            erases all previous set, <methodname>addFile()</methodname> to add a new file to existing ones, and
+            <methodname>getFile()</methodname> to get all actually set files. To simplify things, this filter
             understands several notations and that methods and constructor understand the same
             notations.
         </para>
@@ -482,7 +482,7 @@ $upload->addFilter('Rename', 'C:\mypics\newgifs', 'uploadfile1');
 
         <para>
             At initiation you can give a string which will then be used as encoding. Or you can use
-            the <code>setEncoding()</code> method to set it afterwards.
+            the <methodname>setEncoding()</methodname> method to set it afterwards.
         </para>
 
         <example id="zend.file.transfer.filters.uppercase.example">

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

@@ -77,7 +77,7 @@ if (!$adapter->receive()) {
         <para>
             This code listing demonstrates the simplest usage of
             <classname>Zend_File_Transfer</classname>. A local destination is set with the
-            <code>setDestination</code> method, then the <code>receive()</code> method is called. If
+            <code>setDestination</code> method, then the <methodname>receive()</methodname> method is called. If
             there are any upload errors, an error will be returned.
         </para>
 
@@ -112,7 +112,7 @@ if (!$adapter->receive()) {
         <para>
             <classname>Zend_File_Transfer</classname> and its adapters support different options.
             You can set all options either by passing them to the constructor or by calling
-            <code>setOptions($options)</code>. <code>getOptions()</code> will return the options
+            <methodname>setOptions($options)</methodname>. <methodname>getOptions()</methodname> will return the options
             that are currently set. The following is a list of all supported options.
         </para>
 
@@ -143,8 +143,8 @@ if (!$adapter->receive()) {
                     <emphasis>isValid($files = null)</emphasis>: This method will check if the
                     given files are valid, based on the validators that are attached to the files.
                     If no files are specified, all files will be checked. You can call
-                    <code>isValid()</code> before calling <code>receive()</code>; in this case,
-                    <code>receive()</code> will not call <code>isValid</code> internally again when
+                    <methodname>isValid()</methodname> before calling <methodname>receive()</methodname>; in this case,
+                    <methodname>receive()</methodname> will not call <code>isValid</code> internally again when
                     receiving the file.
                 </para>
             </listitem>
@@ -243,7 +243,7 @@ $upload->receive();
         </itemizedlist>
 
         <para>
-            <code>getFileName()</code> accepts the name of the element as first parameter. If no
+            <methodname>getFileName()</methodname> accepts the name of the element as first parameter. If no
             name is given, all known filenames will be returned in an array. If the file is a
             multifile, you will also get an array. If there is only a single file a string will be
             returned.
@@ -275,12 +275,12 @@ $names = $upload->getFileName('foo');
             <para>
                 Note that the file name can change after you receive the file, because all filters
                 will be applied once the file is received. So you should always call
-                <code>getFileName()</code> after the files have been received.
+                <methodname>getFileName()</methodname> after the files have been received.
             </para>
         </note>
 
         <para>
-            <code>getFileSize()</code> returns per default the real filesize in SI notation which
+            <methodname>getFileSize()</methodname> returns per default the real filesize in SI notation which
             means you will get <code>2kB</code> instead of <code>2048</code>. If you need only the
             plain size set the <code>useByteString</code> option to false.
         </para>
@@ -303,7 +303,7 @@ $size = $upload->getFileSize();
         </example>
 
         <para>
-            <code>getHash()</code> accepts the name of a hash algorithm as first parameter. For a
+            <methodname>getHash()</methodname> accepts the name of a hash algorithm as first parameter. For a
             list of known algorithms refer to
             <ulink url="http://php.net/hash_algos">PHP's hash_algos method</ulink>. If you don't
             specify an algorithm, the <code>crc32</code> algorithm will be used by default.
@@ -333,7 +333,7 @@ $names = $upload->getHash('crc32', 'foo');
         </note>
 
         <para>
-            <code>getMimeType()</code> returns the mimetype of a file. If more than one file was
+            <methodname>getMimeType()</methodname> returns the mimetype of a file. If more than one file was
             uploaded it returns an array, otherwise a string.
         </para>
 
@@ -401,7 +401,7 @@ $names = $upload->getMimeType('foo');
 
             <para>
                 To archive this, you have to add the wished
-                <emphasis>Zend_ProgressBar_Adapter</emphasis> to <code>getProgress()</code> when you
+                <emphasis>Zend_ProgressBar_Adapter</emphasis> to <methodname>getProgress()</methodname> when you
                 are calling it the first time. For details about the right adapter to use, look into
                 the chapter <link linkend="zend.progressbar.adapters">Zend_ProgressBar Standard
                     Adapters</link>.
@@ -424,7 +424,7 @@ while (!$upload['done']) {
             </example>
 
             <para>
-                The complete handling is done by <code>getProgress()</code> for you in the
+                The complete handling is done by <methodname>getProgress()</methodname> for you in the
                 background.
             </para>
 
@@ -435,12 +435,12 @@ while (!$upload['done']) {
             <title>Using getProgress() manually</title>
 
             <para>
-                You can also work manually with <code>getProgress()</code> without the usage of
+                You can also work manually with <methodname>getProgress()</methodname> without the usage of
                 <classname>Zend_ProgressBar</classname>.
             </para>
 
             <para>
-                Call <code>getProgress()</code> without settings. It will return you an array with
+                Call <methodname>getProgress()</methodname> without settings. It will return you an array with
                 several keys. They differ according to the used PHP extension. But the following
                 keys are given independently of the extension:
             </para>

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

@@ -163,11 +163,11 @@ $upload->addValidator('Extension',
                 </itemizedlist>
 
                 <para>
-                    Additionally, the <code>useByteString()</code> method
+                    Additionally, the <methodname>useByteString()</methodname> method
                     signature has changed. It can only be used to test if the
                     validator is expecting to use byte strings in generated
                     messages. To set the value of the flag, use the
-                    <code>setUseByteString()</code> method.
+                    <methodname>setUseByteString()</methodname> method.
                 </para>
 
                 <example id="zend.file.transfer.migration.fromonesixonetooneseven.validators.filessize.example">
@@ -332,7 +332,7 @@ $upload->addValidator('Size',
 
             <itemizedlist>
                 <listitem><para>
-                    Old method API: <code>addValidator($validator, $options, $files)</code>.
+                    Old method API: <methodname>addValidator($validator, $options, $files)</methodname>.
                 </para></listitem>
 
                 <listitem><para>

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

@@ -166,7 +166,7 @@
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>isValid($files = null)</code>: Checks the specified files using all
+                    <methodname>isValid($files = null)</methodname>: Checks the specified files using all
                     validators. <code>$files</code> may be either a real filename, the element's
                     name or the name of the temporary file.
                 </para>
@@ -198,27 +198,27 @@
                     <code>setValidators(array $validators, $files =
                         null)</code>: Overwrites any existing validators with
                     the validators specified. The validators should follow the
-                    syntax for <code>addValidators()</code>.
+                    syntax for <methodname>addValidators()</methodname>.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>hasValidator($name)</code>: Indicates whether a
+                    <methodname>hasValidator($name)</methodname>: Indicates whether a
                     validator has been registered.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>getValidator($name)</code>: Returns a previously
+                    <methodname>getValidator($name)</methodname>: Returns a previously
                     registered validator.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>getValidators($files = null)</code>: Returns
+                    <methodname>getValidators($files = null)</methodname>: Returns
                     registered validators. If <code>$files</code> is specified,
                     returns validators for that particular file or set of
                     files.
@@ -227,14 +227,14 @@
 
             <listitem>
                 <para>
-                    <code>removeValidator($name)</code>: Removes a previously
+                    <methodname>removeValidator($name)</methodname>: Removes a previously
                     registered validator.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>clearValidators()</code>: Clears all
+                    <methodname>clearValidators()</methodname>: Clears all
                     registered validators.
                 </para>
             </listitem>
@@ -265,8 +265,8 @@ $upload->setValidators(array(
             <title>Limit Validators to Single Files</title>
 
             <para>
-                <code>addValidator()</code>, <code>addValidators()</code>, and
-                <code>setValidators()</code> each accept a final
+                <methodname>addValidator()</methodname>, <methodname>addValidators()</methodname>, and
+                <methodname>setValidators()</methodname> each accept a final
                 <code>$files</code> argument. This argument can be used to
                 specify a particular file or array of files on which to set the
                 given validator.
@@ -281,7 +281,7 @@ $upload->addValidator('Size', false, 20000, 'file2');
         </example>
 
         <para>
-            Normally, you should use the <code>addValidators()</code> method, which can be called
+            Normally, you should use the <methodname>addValidators()</methodname> method, which can be called
             multiple times.
         </para>
 
@@ -289,7 +289,7 @@ $upload->addValidator('Size', false, 20000, 'file2');
             <title>Add Multiple Validators</title>
 
             <para>
-                Often it's simpler just to call <code>addValidator()</code> multiple times with one
+                Often it's simpler just to call <methodname>addValidator()</methodname> multiple times with one
                 call for each validator. This also increases readability and makes your code more
                 maintainable. All methods provide a fluent interface, so you can couple the calls as
                 shown below:
@@ -315,14 +315,14 @@ $upload->addValidator('Size', false, 20000)
         </note>
 
         <para>
-            Last but not least, you can simply check the files using <code>isValid()</code>.
+            Last but not least, you can simply check the files using <methodname>isValid()</methodname>.
         </para>
 
         <example id="zend.file.transfer.validators.usage.exampleisvalid">
             <title>Validate the Files</title>
 
             <para>
-                <code>isValid()</code> accepts the file name of the uploaded or downloaded file, the
+                <methodname>isValid()</methodname> accepts the file name of the uploaded or downloaded file, the
                 temporary file name and or the name of the form element. If no parameter or null is
                 given all files will be validated
             </para>
@@ -344,7 +344,7 @@ if ($upload->isValid()) {
 
         <note>
             <para>
-                Note that <code>isValid()</code> will be called automatically when you receive the
+                Note that <methodname>isValid()</methodname> will be called automatically when you receive the
                 files and have not called it previously.
             </para>
         </note>
@@ -352,8 +352,8 @@ if ($upload->isValid()) {
         <para>
             When validation has failed it is a good idea to get information about the
             problems found. To get this information, you can use the methods
-            <code>getMessages()</code> which returns all validation messages as array,
-            <code>getErrors()</code> which returns all error codes, and <code>hasErrors()</code>
+            <methodname>getMessages()</methodname> which returns all validation messages as array,
+            <methodname>getErrors()</methodname> which returns all error codes, and <methodname>hasErrors()</methodname>
             which returns true as soon as a validation error has been found.
         </para>
 
@@ -401,9 +401,9 @@ if ($upload->isValid()) {
 
         <para>
             If you initiate this validator with a string or integer, the value will be used as
-            <code>max</code>. Or you can also use the methods <code>setMin()</code> and
-            <code>setMax()</code> to set both options afterwards and <code>getMin()</code> and
-            <code>getMax()</code> to retrieve the actual set values.
+            <code>max</code>. Or you can also use the methods <methodname>setMin()</methodname> and
+            <methodname>setMax()</methodname> to set both options afterwards and <methodname>getMin()</methodname> and
+            <methodname>getMax()</methodname> to retrieve the actual set values.
         </para>
 
         <example id="zend.file.transfer.validators.count.example">
@@ -493,8 +493,8 @@ $upload->addValidator('Crc32', false, array('3b3652f', 'e612b69'));
 
         <para>
             This validator accepts multiple extensions, either as a comma-delimited string, or as an
-            array. You may also use the methods <code>setExtension()</code>,
-            <code>addExtension()</code>, and <code>getExtension()</code> to set and retrieve
+            array. You may also use the methods <methodname>setExtension()</methodname>,
+            <methodname>addExtension()</methodname>, and <methodname>getExtension()</methodname> to set and retrieve
             extensions.
         </para>
 
@@ -558,8 +558,8 @@ $upload->addValidator('ExcludeExtension',
 
         <para>
             This validator accepts multiple MIME types, either as a comma-delimited string, or as an
-            array. You may also use the methods <code>setMimeType()</code>,
-            <code>addMimeType()</code>, and <code>getMimeType()</code> to set and retrieve the MIME
+            array. You may also use the methods <methodname>setMimeType()</methodname>,
+            <methodname>addMimeType()</methodname>, and <methodname>getMimeType()</methodname> to set and retrieve the MIME
             types.
         </para>
 
@@ -617,8 +617,8 @@ $upload->addValidator('ExcludeMimeType', false, 'image');
 
         <para>
             This validator accepts multiple directories, either as a comma-delimited string, or as
-            an array. You may also use the methods <code>setDirectory()</code>,
-            <code>addDirectory()</code>, and <code>getDirectory()</code> to set and retrieve
+            an array. You may also use the methods <methodname>setDirectory()</methodname>,
+            <methodname>addDirectory()</methodname>, and <methodname>getDirectory()</methodname> to set and retrieve
             directories.
         </para>
 
@@ -674,8 +674,8 @@ $upload->addValidator('Exists',
 
         <para>
             This validator accepts multiple extensions, either as a comma-delimited string, or as an
-            array. You may also use the methods <code>setExtension()</code>,
-            <code>addExtension()</code>, and <code>getExtension()</code> to set and retrieve
+            array. You may also use the methods <methodname>setExtension()</methodname>,
+            <methodname>addExtension()</methodname>, and <methodname>getExtension()</methodname> to set and retrieve
             extension values.
         </para>
 
@@ -755,9 +755,9 @@ if (!$upload->isValid('C:\temp\myfile.MO')) {
 
         <para>
             You can initialize this validator with a string, which will then be used to set the
-            <code>max</code> option. You can also use the methods <code>setMin()</code> and
-            <code>setMax()</code> to set both options after construction, along with
-            <code>getMin()</code> and <code>getMax()</code> to retrieve the values that have been
+            <code>max</code> option. You can also use the methods <methodname>setMin()</methodname> and
+            <methodname>setMax()</methodname> to set both options after construction, along with
+            <methodname>getMin()</methodname> and <methodname>getMax()</methodname> to retrieve the values that have been
             set previously.
         </para>
 
@@ -836,16 +836,16 @@ $upload->addValidator('FilesSize',
         </itemizedlist>
 
         <para>
-            The methods <code>setImageMin()</code> and <code>setImageMax()</code> also set
-            both minimum and maximum values, while the methods <code>getMin()</code> and
-            <code>getMax()</code> return the currently set values.
+            The methods <methodname>setImageMin()</methodname> and <methodname>setImageMax()</methodname> also set
+            both minimum and maximum values, while the methods <methodname>getMin()</methodname> and
+            <methodname>getMax()</methodname> return the currently set values.
         </para>
 
         <para>
-            For your convenience there are also the <code>setImageWidth()</code> and
-            <code>setImageHeight()</code> methods, which set the minimum and maximum height and
-            width of the image file. They, too, have corresponding <code>getImageWidth()</code> and
-            <code>getImageHeight()</code> methods to retrieve the currently set values.
+            For your convenience there are also the <methodname>setImageWidth()</methodname> and
+            <methodname>setImageHeight()</methodname> methods, which set the minimum and maximum height and
+            width of the image file. They, too, have corresponding <methodname>getImageWidth()</methodname> and
+            <methodname>getImageHeight()</methodname> methods to retrieve the currently set values.
         </para>
 
         <para>
@@ -975,7 +975,7 @@ $upload->addValidator('IsImage', false, 'jpeg');
                 </para>
 
                 <para>
-                    You can set multiple algorithm by calling the <code>addHash()</code> method
+                    You can set multiple algorithm by calling the <methodname>addHash()</methodname> method
                     multiple times.
                 </para>
             </listitem>
@@ -1086,15 +1086,15 @@ $upload->addValidator('Md5',
 
         <para>
             This validator accepts multiple MIME type, either as a comma-delimited string, or as an
-            array. You may also use the methods <code>setMimeType()</code>,
-            <code>addMimeType()</code>, and <code>getMimeType()</code> to set and retrieve MIME
+            array. You may also use the methods <methodname>setMimeType()</methodname>,
+            <methodname>addMimeType()</methodname>, and <methodname>getMimeType()</methodname> to set and retrieve MIME
             type.
         </para>
 
         <para>
             You can also set the magicfile which shall be used by fileinfo with the 'magicfile'
-            option. Additionally there are convenient <code>setMagicFile()</code> and
-            <code>getMagicFile()</code> methods which allow later setting and retrieving of the
+            option. Additionally there are convenient <methodname>setMagicFile()</methodname> and
+            <methodname>getMagicFile()</methodname> methods which allow later setting and retrieving of the
             magicfile parameter. This methods are available since Zend Framework 1.7.1.
         </para>
 
@@ -1171,8 +1171,8 @@ $upload->addValidator('MimeType',
 
         <para>
             This validator accepts multiple directories either as a comma-delimited string, or as an
-            array. You may also use the methods <code>setDirectory()</code>,
-            <code>addDirectory()</code>, and <code>getDirectory()</code> to set and retrieve
+            array. You may also use the methods <methodname>setDirectory()</methodname>,
+            <methodname>addDirectory()</methodname>, and <methodname>getDirectory()</methodname> to set and retrieve
             directories.
         </para>
 
@@ -1277,9 +1277,9 @@ $upload->addValidator('Sha1',
 
         <para>
             You can initialize this validator with a string, which will then be used to set the
-            <code>max</code> option. You can also use the methods <code>setMin()</code> and
-            <code>setMax()</code> to set both options after construction, along with
-            <code>getMin()</code> and <code>getMax()</code> to retrieve the values that have been
+            <code>max</code> option. You can also use the methods <methodname>setMin()</methodname> and
+            <methodname>setMax()</methodname> to set both options after construction, along with
+            <methodname>getMin()</methodname> and <methodname>getMax()</methodname> to retrieve the values that have been
             set previously.
         </para>
 
@@ -1337,9 +1337,9 @@ $upload->addValidator('Size',
 
         <para>
             If you initiate this validator with a string or integer, the value will be used as
-            <code>max</code>. Or you can also use the methods <code>setMin()</code> and
-            <code>setMax()</code> to set both options afterwards and <code>getMin()</code> and
-            <code>getMax()</code> to retrieve the actual set values.
+            <code>max</code>. Or you can also use the methods <methodname>setMin()</methodname> and
+            <methodname>setMax()</methodname> to set both options afterwards and <methodname>getMin()</methodname> and
+            <methodname>getMax()</methodname> to retrieve the actual set values.
         </para>
 
         <example id="zend.file.transfer.validators.wordcount.example">

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

@@ -37,8 +37,8 @@ print $filter->filter('Hello!');
 ]]></programlisting>
 
     <para>
-        To get the actual set callback use <code>getCallback()</code> and to set another callback
-        use <code>setCallback()</code>.
+        To get the actual set callback use <methodname>getCallback()</methodname> and to set another callback
+        use <methodname>setCallback()</methodname>.
     </para>
 
     <para>

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

@@ -24,7 +24,7 @@
         <para>
             There is one emminent difference for you. When you did not provide a vector at
             encryption you need to get it after you encrypted the content by using the
-            <code>getVector()</code> method on the encryption filter. Without the correct vector you
+            <methodname>getVector()</methodname> method on the encryption filter. Without the correct vector you
             will not be able to decrypt the content.
         </para>
 
@@ -111,7 +111,7 @@ $filter->setEnvelopeKey(array(
 
         <para>
             Optionally it could be necessary to provide the passphrase for decrypting the keys
-            themself by using the <code>setPassphrase()</code> method.
+            themself by using the <methodname>setPassphrase()</methodname> method.
         </para>
 
         <programlisting language="php"><![CDATA[

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

@@ -22,8 +22,8 @@ $filter2 = new Zend_Filter_Encrypt(array('adapter' => 'openssl'));
 ]]></programlisting>
 
     <para>
-        To set another adapter you can also use <code>setAdapter()</code>, and the
-        <code>getAdapter()</code> method to receive the actual set adapter.
+        To set another adapter you can also use <methodname>setAdapter()</methodname>, and the
+        <methodname>getAdapter()</methodname> method to receive the actual set adapter.
     </para>
 
     <programlisting language="php"><![CDATA[
@@ -107,7 +107,7 @@ $filter->setAdapter('openssl');
 
         <para>
             You can get/set the encryption values also afterwards with the
-            <code>getEncryption()</code> and <code>setEncryption()</code> methods.
+            <methodname>getEncryption()</methodname> and <methodname>setEncryption()</methodname> methods.
         </para>
 
         <note>
@@ -126,8 +126,8 @@ $filter->setAdapter('openssl');
         </note>
 
         <para>
-            You can get/set the encryption vector by calling <code>getVector()</code> and
-            <code>setVector()</code>. A given string will be truncated or padded to the needed
+            You can get/set the encryption vector by calling <methodname>getVector()</methodname> and
+            <methodname>setVector()</methodname>. A given string will be truncated or padded to the needed
             vector size of the used algorithm.
         </para>
 
@@ -181,9 +181,9 @@ print $encrypted;
         </itemizedlist>
 
         <para>
-            You can get/set the public keys also afterwards with the <code>getPublicKey()</code>
-            and <code>setPublicKey()</code> methods. The private key can also be get and set with
-            the related <code>getPrivateKey()</code> and <code>setPrivateKey()</code> methods.
+            You can get/set the public keys also afterwards with the <methodname>getPublicKey()</methodname>
+            and <methodname>setPublicKey()</methodname> methods. The private key can also be get and set with
+            the related <methodname>getPrivateKey()</methodname> and <methodname>setPrivateKey()</methodname> methods.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -209,7 +209,7 @@ $filter->setPublicKey(array(
 
         <para>
             When you want to encode also the keys, then you have to provide a passphrase with the
-            <code>setPassphrase()</code> method. When you want to decode content which was encoded
+            <methodname>setPassphrase()</methodname> method. When you want to decode content which was encoded
             with a passphrase you will not only need the public key, but also the passphrase to
             decode the encrypted key.
         </para>
@@ -236,7 +236,7 @@ $filter->setPassphrase('mypassphrase');
 
         <para>
             This means for you, that you have to get the envelope keys after the encryption with the
-            <code>getEnvelopeKey()</code> method.
+            <methodname>getEnvelopeKey()</methodname> method.
         </para>
 
         <para>

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

@@ -18,7 +18,7 @@
     <para>
         <classname>Zend_Filter_Inflector</classname> implements
         <classname>Zend_Filter_Interface</classname>; you perform inflection by calling
-        <code>filter()</code> on the object instance.
+        <methodname>filter()</methodname> on the object instance.
     </para>
 
     <example id="zend.filter.inflector.camel_case_example">
@@ -52,7 +52,7 @@ $filtered = $inflector->filter(array('page' => $string));
         </para>
 
         <para>
-            When calling <code>filter()</code>, you then pass in an array of
+            When calling <methodname>filter()</methodname>, you then pass in an array of
             key/value pairs corresponding to the variables in the target.
         </para>
 
@@ -93,7 +93,7 @@ $inflector->addRules(array('script' => 'Word_CamelCaseToDash'));
         <para>
             To set alternate paths, <classname>Zend_Filter_Inflector</classname> has a
             utility method that proxies to the plugin loader,
-            <code>addFilterPrefixPath()</code>:
+            <methodname>addFilterPrefixPath()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -124,13 +124,13 @@ $loader->addPrefixPath('My_Filter', 'My/Filter/');
             The inflector target is a string with some placeholders for
             variables. Placeholders take the form of an identifier, a colon
             (':') by default, followed by a variable name: ':script', ':path',
-            etc. The <code>filter()</code> method looks for the identifier
+            etc. The <methodname>filter()</methodname> method looks for the identifier
             followed by the variable name being replaced.
         </para>
 
         <para>
             You can change the identifier using the
-            <code>setTargetReplacementIdentifier()</code> method, or passing it
+            <methodname>setTargetReplacementIdentifier()</methodname> method, or passing it
             as the third argument to the constructor:
         </para>
 
@@ -147,7 +147,7 @@ $inflector->setTargetReplacementIdentifier('#');
             may want to re-set the target later (for instance, to modify the
             default inflector in core components, such as the
             <code>ViewRenderer</code> or <classname>Zend_Layout</classname>).
-            <code>setTarget()</code> can be used for this purpose:
+            <methodname>setTarget()</methodname> can be used for this purpose:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -159,7 +159,7 @@ $inflector->setTarget('layouts/:script.phtml');
             Additionally, you may wish to have a class member for your class
             that you can use to keep the inflector target updated -- without
             needing to directly update the target each time (thus saving on
-            method calls). <code>setTargetReference()</code> allows you to do
+            method calls). <methodname>setTargetReference()</methodname> allows you to do
             this:
         </para>
 
@@ -224,7 +224,7 @@ class Foo
                 Static rules do simple string substitution; use them when you
                 have a segment in the target that will typically be static, but
                 which you want to allow the developer to modify. Use the
-                <code>setStaticRule()</code> method to set or modify the rule:
+                <methodname>setStaticRule()</methodname> method to set or modify the rule:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -241,7 +241,7 @@ $inflector->setStaticRule('suffix', 'php');
                 require a method call; this is often useful when your class uses
                 an inflector internally, and you don't want your users to need
                 to fetch the inflector in order to update it. The
-                <code>setStaticRuleReference()</code> method is used to
+                <methodname>setStaticRuleReference()</methodname> method is used to
                 accomplish this:
             </para>
 
@@ -291,9 +291,9 @@ class Foo
             </para>
 
             <para>
-                Rules may be added using <code>setFilterRule()</code> (which
+                Rules may be added using <methodname>setFilterRule()</methodname> (which
                 overwrites any previous rules for that variable) or
-                <code>addFilterRule()</code> (which appends the new rule to any
+                <methodname>addFilterRule()</methodname> (which appends the new rule to any
                 existing rule for that variable). Filters are specified in one
                 of the following ways:
             </para>
@@ -341,8 +341,8 @@ $inflector->setFilterRule('script', array(
             <para>
                 Typically, it's easier to set many rules at once than to
                 configure a single variable and its inflection rules at a time.
-                <classname>Zend_Filter_Inflector</classname>'s <code>addRules()</code> and
-                <code>setRules()</code> method allow this.
+                <classname>Zend_Filter_Inflector</classname>'s <methodname>addRules()</methodname> and
+                <methodname>setRules()</methodname> method allow this.
             </para>
 
             <para>
@@ -392,37 +392,37 @@ $inflector->addRules(array(
 
         <itemizedlist>
             <listitem><para>
-                    <code>setPluginLoader()</code> can be used when you have
+                    <methodname>setPluginLoader()</methodname> can be used when you have
                     configured your own plugin loader and wish to use it with
                     <classname>Zend_Filter_Inflector</classname>;
-                    <code>getPluginLoader()</code> retrieves the currently set
+                    <methodname>getPluginLoader()</methodname> retrieves the currently set
                     one.
             </para></listitem>
 
             <listitem><para>
-                    <code>setThrowTargetExceptionsOn()</code> can be used to
-                    control whether or not <code>filter()</code> throws an
+                    <methodname>setThrowTargetExceptionsOn()</methodname> can be used to
+                    control whether or not <methodname>filter()</methodname> throws an
                     exception when a given replacement identifier passed to it
                     is not found in the target. By default, no exceptions are
-                    thrown. <code>isThrowTargetExceptionsOn()</code> will tell
+                    thrown. <methodname>isThrowTargetExceptionsOn()</methodname> will tell
                     you what the current value is.
             </para></listitem>
 
             <listitem><para>
-                    <code>getRules($spec = null)</code> can be used to retrieve all
+                    <methodname>getRules($spec = null)</methodname> can be used to retrieve all
                     registered rules for all variables, or just the rules for a
                     single variable.
             </para></listitem>
 
             <listitem><para>
-                    <code>getRule($spec, $index)</code> fetches a single rule
+                    <methodname>getRule($spec, $index)</methodname> fetches a single rule
                     for a given variable; this can be useful for fetching a
                     specific filter rule for a variable that has a filter chain.
                     <code>$index</code> must be passed.
             </para></listitem>
 
             <listitem><para>
-                    <code>clearRules()</code> will clear all currently
+                    <methodname>clearRules()</methodname> will clear all currently
                     registered rules.
             </para></listitem>
         </itemizedlist>
@@ -435,7 +435,7 @@ $inflector->addRules(array(
             You can use <classname>Zend_Config</classname> to set rules, filter prefix
             paths, and other object state in your inflectors, either by passing
             a <classname>Zend_Config</classname> object to the constructor or
-            <code>setConfig()</code>. The following settings may be specified:
+            <methodname>setConfig()</methodname>. The following settings may be specified:
         </para>
 
         <itemizedlist>
@@ -463,7 +463,7 @@ $inflector->addRules(array(
             <listitem><para>
                     <code>rules</code> specifies an array of inflection rules;
                     it should consist of keys that specify either values or
-                    arrays of values, consistent with <code>addRules()</code>.
+                    arrays of values, consistent with <methodname>addRules()</methodname>.
             </para></listitem>
         </itemizedlist>
 

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

@@ -11,7 +11,7 @@
     </para>
 
     <para>
-        <classname>Zend_Filter_Interface</classname> defines a single method, <code>filter()</code>,
+        <classname>Zend_Filter_Interface</classname> defines a single method, <methodname>filter()</methodname>,
         that may be implemented by user classes. An object that implements this interface may be
         added to a filter chain with <classname>Zend_Filter::addFilter()</classname>.
     </para>

documentation/manual/en/module_specs/Zend_Filter.xml

@@ -53,7 +53,7 @@
         <para>
             Having this filter definition established provides the foundation
             for <classname>Zend_Filter_Interface</classname>, which requires a single
-            method named <code>filter()</code> to be implemented by a filter
+            method named <methodname>filter()</methodname> to be implemented by a filter
             class.
         </para>
 
@@ -82,11 +82,11 @@ echo $htmlEntities->filter('"'); // &quot;
             instance of the filter, you can use the static method
             <classname>Zend_Filter::filterStatic()</classname> as an alternative invocation style.
             The first argument of this method is a data input value, that you
-            would pass to the <code>filter()</code> method. The second
+            would pass to the <methodname>filter()</methodname> method. The second
             argument is a string, which corresponds to the basename of the
             filter class, relative to the Zend_Filter namespace. The
-            <code>get()</code> method automatically loads the class, creates an
-            instance, and applies the <code>filter()</code> method to the data
+            <methodname>get()</methodname> method automatically loads the class, creates an
+            instance, and applies the <methodname>filter()</methodname> method to the data
             input.
 
             <programlisting language="php"><![CDATA[
@@ -110,7 +110,7 @@ echo Zend_Filter::filterStatic('"', 'HtmlEntities', array(ENT_QUOTES));
             but if you have the need to run a filter for multiple inputs,
             it's more efficient to follow the first example above,
             creating an instance of the filter object and calling its
-            <code>filter()</code> method.
+            <methodname>filter()</methodname> method.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Filter_Input.xml

@@ -237,7 +237,7 @@ $input = new Zend_Filter_Input($filters, $validators, $data);
 ]]></programlisting>
 
         <para>
-            Alternatively, use the <code>setData()</code> method, passing
+            Alternatively, use the <methodname>setData()</methodname> method, passing
             an associative array of key/value pairs the same format as
             described above.
         </para>
@@ -248,7 +248,7 @@ $input->setData($newData);
 ]]></programlisting>
 
         <para>
-            The <code>setData()</code> method redefines data in an existing
+            The <methodname>setData()</methodname> method redefines data in an existing
             Zend_Filter_Input object without changing the filtering and
             validation rules. Using this method, you can run the same rules
             against different sets of input data.
@@ -273,9 +273,9 @@ $input->setData($newData);
 
             <para>
                 If all input data pass the validation rules, the
-                <code>isValid()</code> method returns <constant>TRUE</constant>.
+                <methodname>isValid()</methodname> method returns <constant>TRUE</constant>.
                 If any field is invalid or any required field is missing,
-                <code>isValid()</code> returns <constant>FALSE</constant>.
+                <methodname>isValid()</methodname> returns <constant>FALSE</constant>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -287,7 +287,7 @@ if ($input->isValid()) {
             <para>
                 This method accepts an optional string argument, naming
                 an individual field. If the specified field passed validation
-                and is ready for fetching, <code>isValid('fieldName')</code>
+                and is ready for fetching, <methodname>isValid('fieldName')</methodname>
                 returns <constant>TRUE</constant>.
             </para>
 
@@ -352,7 +352,7 @@ if ($input->hasUnknown()) {
 ]]></programlisting>
 
             <para>
-                The results of the <code>getMessages()</code> method is an
+                The results of the <methodname>getMessages()</methodname> method is an
                 associative array, mapping a rule name to an array of error
                 messages related to that rule. Note that the index of this
                 array is the rule name used in the rule declaration, which may
@@ -360,15 +360,15 @@ if ($input->hasUnknown()) {
             </para>
 
             <para>
-                The <code>getMessages()</code> method returns the merge of the
-                arrays returned by the <code>getInvalid()</code> and
-                <code>getMissing()</code>. These methods return subsets of the
+                The <methodname>getMessages()</methodname> method returns the merge of the
+                arrays returned by the <methodname>getInvalid()</methodname> and
+                <methodname>getMissing()</methodname>. These methods return subsets of the
                 messages, related to validation failures, or fields that were
                 declared as required but missing from the input.
             </para>
 
             <para>
-                The <code>getErrors()</code> method returns an associative array,
+                The <methodname>getErrors()</methodname> method returns an associative array,
                 mapping a rule name to an array of error identifiers. Error
                 identifiers are fixed strings, to identify the reason for a
                 validation failure, while messages can be customized.
@@ -378,9 +378,9 @@ if ($input->hasUnknown()) {
 
             <para>
                 You can specify the message returned by
-                <code>getMissing()</code> using the 'missingMessage' option,
+                <methodname>getMissing()</methodname> using the 'missingMessage' option,
                 as an argument to the Zend_Filter_Input constructor or using
-                the <code>setOptions()</code> method.
+                the <methodname>setOptions()</methodname> method.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -397,7 +397,7 @@ $input->setOptions($options);
 ]]></programlisting>
 
             <para>
-                The results of the <code>getUnknown()</code> method is an
+                The results of the <methodname>getUnknown()</methodname> method is an
                 associative array, mapping field names to field values. Field
                 names are used as the array keys in this case, instead of rule
                 names, because no rule mentions the fields considered to be
@@ -414,7 +414,7 @@ $input->setOptions($options);
                 All fields that are neither invalid, missing, nor unknown are
                 considered valid. You can get values for valid fields using a
                 magic accessor. There are also non-magic accessor methods
-                <code>getEscaped()</code> and <code>getUnescaped()</code>.
+                <methodname>getEscaped()</methodname> and <methodname>getUnescaped()</methodname>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -434,7 +434,7 @@ $m = $input->getUnescaped('month'); // not escaped
             <note>
                 <para>
                     As shown above, you can retrieve the unescaped value using
-                    the <code>getUnescaped()</code> method, but you must write
+                    the <methodname>getUnescaped()</methodname> method, but you must write
                     code to use the value safely, and avoid security issues
                     such as vulnerability to cross-site scripting attacks.
                 </para>
@@ -452,7 +452,7 @@ $input = new Zend_Filter_Input($filters, $validators, $data, $options);
 
             <para>
                 Alternatively, you can use the
-                <code>setDefaultEscapeFilter()</code> method:
+                <methodname>setDefaultEscapeFilter()</methodname> method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -475,12 +475,12 @@ $input->setDefaultEscapeFilter(new Zend_Filter_StringTrim());
                 the process of validation would be more complex, and it would
                 be harder to provide both escaped and unescaped versions of the
                 data. So it is recommended to declare filters to escape output
-                using <code>setDefaultEscapeFilter()</code>, not in the
+                using <methodname>setDefaultEscapeFilter()</methodname>, not in the
                 <code>$filters</code> array.
             </para>
 
             <para>
-                There is only one method <code>getEscaped()</code>, and
+                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
@@ -573,7 +573,7 @@ $validators = array(
             <para>
                 If the validation of this rule fails, the rule key
                 (<code>'password'</code>) is used in the return value of
-                <code>getInvalid()</code>, not any of the fields named in
+                <methodname>getInvalid()</methodname>, not any of the fields named in
                 the 'fields' metacommand.
             </para>
 
@@ -713,10 +713,10 @@ $validators = array(
                 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
-                that you can retrieve with <code>getMessages()</code>. You can
+                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
-                <code>setOptions()</code> method.
+                <methodname>setOptions()</methodname> method.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -990,8 +990,8 @@ $input = new Zend_Filter_Input($filters, $validators, $data, $options);
 ]]></programlisting>
 
         <para>
-            Alternatively, you can use the <code>addValidatorPrefixPath($prefix, $path)</code>
-            or <code>addFilterPrefixPath($prefix, $path)</code> methods, which directly
+            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:
         </para>
 
@@ -1018,7 +1018,7 @@ $input->addFilterPrefixPath('Foo_Namespace', 'Foo/Namespace');
 
         <note>
             <para>
-                As of version 1.5 the function <code>addNamespace($namespace)</code> was deprecated
+                As of version 1.5 the function <methodname>addNamespace($namespace)</methodname> was deprecated
                 and exchanged with the plugin loader and the <code>addFilterPrefixPath</code> and
                 <code>addValidatorPrefixPath</code> were added. Also the constant
                 <classname>Zend_Filter_Input::INPUT_NAMESPACE</classname> is now deprecated. The

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

@@ -176,16 +176,16 @@
                     flag true, you can indicate that an entire form should be
                     treated as an array. By default, the form's name will be
                     used as the name of the array, unless
-                    <code>setElementsBelongTo()</code> has been called. If the
+                    <methodname>setElementsBelongTo()</methodname> has been called. If the
                     form has no specified name, or if
-                    <code>setElementsBelongTo()</code> has not been set, this
+                    <methodname>setElementsBelongTo()</methodname> has not been set, this
                     flag will be ignored (as there is no array name to which
                     the elements may belong).
                 </para>
 
                 <para>
                     You may determine if a form is being treated as an array
-                    using the <code>isArray()</code> accessor.
+                    using the <methodname>isArray()</methodname> accessor.
                 </para>
             </listitem>
 
@@ -193,7 +193,7 @@
                     <classname>Zend_Form::setElementsBelongTo($array)</classname>:
                     Using this method, you can specify the name of an array to
                     which all elements of the form belong. You can determine the
-                    name using the <code>getElementsBelongTo()</code> accessor.
+                    name using the <methodname>getElementsBelongTo()</methodname> accessor.
             </para></listitem>
         </itemizedlist>
 
@@ -203,7 +203,7 @@
             <classname>Zend_Form_Element::setBelongsTo()</classname> method.
             To discover what this value is -- whether set explicitly or
             implicitly via the form -- you may use the
-            <code>getBelongsTo()</code> accessor.
+            <methodname>getBelongsTo()</methodname> accessor.
         </para>
     </sect2>
 
@@ -572,11 +572,11 @@ class RegistrationController extends Zend_Controller_Action
 
             <para>
                 Now, let's figure out how to process and display the various sub
-                forms. We can use <code>getCurrentSubForm()</code> to determine
+                forms. We can use <methodname>getCurrentSubForm()</methodname> to determine
                 if any sub forms have been submitted (false return values
                 indicate none have been displayed or submitted), and
-                <code>getNextSubForm()</code> to retrieve a form to display. We
-                can then use the form's <code>prepareSubForm()</code> method to
+                <methodname>getNextSubForm()</methodname> to retrieve a form to display. We
+                can then use the form's <methodname>prepareSubForm()</methodname> method to
                 ensure the form is ready for display.
             </para>
 

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

@@ -20,16 +20,16 @@
 
     <para>
         Object state is set via configuration options passed to the constructor
-        or the decorator's <code>setOptions()</code> method. When creating
-        decorators via an item's <code>addDecorator()</code> or related methods,
+        or the decorator's <methodname>setOptions()</methodname> method. When creating
+        decorators via an item's <methodname>addDecorator()</methodname> or related methods,
         options may be passed as an argument to the method. These can be used to
         specify placement, a separator to use between passed in content and
         newly generated content, and whatever options the decorator supports.
     </para>
 
     <para>
-        Before each decorator's <code>render()</code> method is called, the
-        current item is set in the decorator using <code>setElement()</code>,
+        Before each decorator's <methodname>render()</methodname> method is called, the
+        current item is set in the decorator using <methodname>setElement()</methodname>,
         giving the decorator awareness of the item being rendered. This allows
         you to create decorators that only render specific portions of the item
         -- such as the label, the value, error messages, etc. By stringing
@@ -43,8 +43,8 @@
         <para>
             To configure a decorator, pass an array of options or a
             <classname>Zend_Config</classname> object to its constructor, an array to
-            <code>setOptions()</code>, or a <classname>Zend_Config</classname> object to
-            <code>setConfig()</code>.
+            <methodname>setOptions()</methodname>, or a <classname>Zend_Config</classname> object to
+            <methodname>setConfig()</methodname>.
         </para>
 
         <para>
@@ -55,7 +55,7 @@
             <listitem><para>
                     <code>placement</code>: Placement can be either 'append' or
                     'prepend' (case insensitive), and indicates whether content
-                    passed to <code>render()</code> will be appended or
+                    passed to <methodname>render()</methodname> will be appended or
                     prepended, respectively. In the case that a decorator
                     replaces the content, this setting is ignored. The default
                     setting is to append.
@@ -63,7 +63,7 @@
 
             <listitem><para>
                     <code>separator</code>: The separator is used between the
-                    content passed to <code>render()</code> and new content
+                    content passed to <methodname>render()</methodname> and new content
                     generated by the decorator, or between items rendered by the
                     decorator (e.g. FormElements uses the separator between each
                     item rendered). In the case that a decorator replaces the
@@ -79,24 +79,24 @@
 
         <itemizedlist>
             <listitem><para>
-                    <code>setOption($key, $value)</code>: set a single option.
+                    <methodname>setOption($key, $value)</methodname>: set a single option.
             </para></listitem>
 
             <listitem><para>
-                    <code>getOption($key)</code>: retrieve a single option
+                    <methodname>getOption($key)</methodname>: retrieve a single option
                     value.
             </para></listitem>
 
             <listitem><para>
-                    <code>getOptions()</code>: retrieve all options.
+                    <methodname>getOptions()</methodname>: retrieve all options.
             </para></listitem>
 
             <listitem><para>
-                    <code>removeOption($key)</code>: remove a single option.
+                    <methodname>removeOption($key)</methodname>: remove a single option.
             </para></listitem>
 
             <listitem><para>
-                    <code>clearOptions()</code>: remove all options.
+                    <methodname>clearOptions()</methodname>: remove all options.
             </para></listitem>
         </itemizedlist>
 
@@ -105,13 +105,13 @@
             <classname>Zend_Form</classname> class types: <classname>Zend_Form</classname>,
             <classname>Zend_Form_Element</classname>, <classname>Zend_Form_DisplayGroup</classname>,
             and all classes deriving from them. The method
-            <code>setElement()</code> allows you to set the object the
-            decorator is currently working with, and <code>getElement()</code>
+            <methodname>setElement()</methodname> allows you to set the object the
+            decorator is currently working with, and <methodname>getElement()</methodname>
             is used to retrieve it.
         </para>
 
         <para>
-            Each decorator's <code>render()</code> method accepts a string,
+            Each decorator's <methodname>render()</methodname> method accepts a string,
             <code>$content</code>. When the first decorator is called, this
             string is typically empty, while on subsequent calls it will be
             populated. Based on the type of decorator and the options passed in,
@@ -165,7 +165,7 @@ interface Zend_Form_Decorator_Interface
         <para>
             To make this simpler, you can simply extend
             <classname>Zend_Form_Decorator_Abstract</classname>, which implements all methods
-            except <code>render()</code>.
+            except <methodname>render()</methodname>.
         </para>
 
         <para>

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

@@ -67,7 +67,7 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>setPluginLoader($loader, $type)</code>:
+                <methodname>setPluginLoader($loader, $type)</methodname>:
                 <code>$loader</code> is the plugin loader object itself, while
                 <code>$type</code> is one of the types specified above. This
                 sets the plugin loader for the given type to the newly
@@ -75,12 +75,12 @@
             </para></listitem>
 
             <listitem><para>
-                <code>getPluginLoader($type)</code>: retrieves the plugin
+                <methodname>getPluginLoader($type)</methodname>: retrieves the plugin
                 loader associated with <code>$type</code>.
             </para></listitem>
 
             <listitem><para>
-                <code>addPrefixPath($prefix, $path, $type = null)</code>: adds
+                <methodname>addPrefixPath($prefix, $path, $type = null)</methodname>: adds
                 a prefix/path association to the loader specified by
                 <code>$type</code>. If <code>$type</code> is null, it will
                 attempt to add the path to all loaders, by appending the prefix
@@ -92,7 +92,7 @@
             </para></listitem>
 
             <listitem><para>
-                <code>addPrefixPaths(array $spec)</code>: allows you to add
+                <methodname>addPrefixPaths(array $spec)</methodname>: allows you to add
                 many paths at once to one or more plugin loaders. It expects
                 each array item to be an array with the keys 'path', 'prefix',
                 and 'type'.
@@ -202,7 +202,7 @@ $form->addElementPrefixPath('My_Decorator', 'My/Decorator/', 'decorator');
             <classname>Zend_Filter</classname>. <classname>Zend_Form_Element</classname> has support
             for filter chains, allowing you to specify multiple, sequential filters. Filtering
             happens both during validation and when you retrieve the element value via
-            <code>getValue()</code>:
+            <methodname>getValue()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -252,7 +252,7 @@ $element->addFilter('alnum');
             <para>
                 If you have your own set of filter classes, you can tell
                 <classname>Zend_Form_Element</classname> about these using
-                <code>addPrefixPath()</code>. For instance, if you have
+                <methodname>addPrefixPath()</methodname>. For instance, if you have
                 filters under the 'My_Filter' prefix, you can tell
                 <classname>Zend_Form_Element</classname> about this as follows:
             </para>
@@ -269,7 +269,7 @@ $element->addPrefixPath('My_Filter', 'My/Filter/', 'filter');
 
         <para>
             If at any time you need the unfiltered value, use the
-            <code>getUnfilteredValue()</code> method:
+            <methodname>getUnfilteredValue()</methodname> method:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -288,31 +288,31 @@ $unfiltered = $element->getUnfilteredValue();
 
         <itemizedlist>
             <listitem><para>
-                <code>addFilter($nameOfFilter, array $options = null)</code>
+                <methodname>addFilter($nameOfFilter, array $options = null)</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>addFilters(array $filters)</code>
+                <methodname>addFilters(array $filters)</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>setFilters(array $filters)</code> (overwrites all filters)
+                <methodname>setFilters(array $filters)</methodname> (overwrites all filters)
             </para></listitem>
 
             <listitem><para>
-                <code>getFilter($name)</code> (retrieve a filter object by name)
+                <methodname>getFilter($name)</methodname> (retrieve a filter object by name)
             </para></listitem>
 
             <listitem><para>
-                <code>getFilters()</code> (retrieve all filters)
+                <methodname>getFilters()</methodname> (retrieve all filters)
             </para></listitem>
 
             <listitem><para>
-                <code>removeFilter($name)</code> (remove filter by name)
+                <methodname>removeFilter($name)</methodname> (remove filter by name)
             </para></listitem>
 
             <listitem><para>
-                <code>clearFilters()</code> (remove all filters)
+                <methodname>clearFilters()</methodname> (remove all filters)
             </para></listitem>
         </itemizedlist>
     </sect2>
@@ -370,7 +370,7 @@ $element->addValidator('alnum');
             <para>
                 If you have your own set of validator classes, you can tell
                 <classname>Zend_Form_Element</classname> about these using
-                <code>addPrefixPath()</code>. For instance, if you have
+                <methodname>addPrefixPath()</methodname>. For instance, if you have
                 validators under the 'My_Validator' prefix, you can tell
                 <classname>Zend_Form_Element</classname> about this as follows:
             </para>
@@ -397,7 +397,7 @@ $element->addValidator('alnum', true);
         <para>
             If you are using a string name to add a validator, and the
             validator class accepts arguments to the constructor, you may pass
-            these to the third parameter of <code>addValidator()</code> as an
+            these to the third parameter of <methodname>addValidator()</methodname> as an
             array:
         </para>
 
@@ -440,9 +440,9 @@ $validator = new Zend_Validate_StringLength(6, 20);
 
         <para>
             You can also set many validators at once, using
-            <code>addValidators()</code>. The basic usage is to pass an array
+            <methodname>addValidators()</methodname>. The basic usage is to pass an array
             of arrays, with each array containing 1 to 3 values, matching the
-            constructor of <code>addValidator()</code>:
+            constructor of <methodname>addValidator()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -493,7 +493,7 @@ element.validators.strlen.options.max = 20
 
         <para>
             To validate an element, pass the value to
-            <code>isValid()</code>:
+            <methodname>isValid()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -587,9 +587,9 @@ $messages = $element->getMessages();
 
         <para>
             In addition to validators, you can specify that an element is
-            required, using <code>setRequired(true)</code>. By default, this
+            required, using <methodname>setRequired(true)</methodname>. By default, this
             flag is false, meaning that your validator chain will be skipped if
-            no value is passed to <code>isValid()</code>. You can modify this
+            no value is passed to <methodname>isValid()</methodname>. You can modify this
             behavior in a number of ways:
         </para>
 
@@ -598,9 +598,9 @@ $messages = $element->getMessages();
                 <para>
                     By default, when an element is required, a flag,
                     'allowEmpty', is also true. This means that if a value
-                    evaluating to empty is passed to <code>isValid()</code>, the
+                    evaluating to empty is passed to <methodname>isValid()</methodname>, the
                     validators will be skipped. You can toggle this flag using
-                    the accessor <code>setAllowEmpty($flag)</code>; when the
+                    the accessor <methodname>setAllowEmpty($flag)</methodname>; when the
                     flag is false and a value is passed, the validators
                     will still run.
                 </para>
@@ -609,7 +609,7 @@ $messages = $element->getMessages();
             <listitem>
                 <para>
                     By default, if an element is required but does not contain
-                    a 'NotEmpty' validator, <code>isValid()</code> will add one
+                    a 'NotEmpty' validator, <methodname>isValid()</methodname> will add one
                     to the top of the stack, with the
                     <code>breakChainOnFailure</code> flag set. This behavior lends
                     required flag semantic meaning: if no value is passed,
@@ -621,8 +621,8 @@ $messages = $element->getMessages();
                 <para>
                     If you do not want this behavior, you can turn it off by
                     passing a false value to
-                    <code>setAutoInsertNotEmptyValidator($flag)</code>; this
-                    will prevent <code>isValid()</code> from placing the
+                    <methodname>setAutoInsertNotEmptyValidator($flag)</methodname>; this
+                    will prevent <methodname>isValid()</methodname> from placing the
                     'NotEmpty' validator in the validator chain.
                 </para>
             </listitem>
@@ -651,16 +651,16 @@ $messages = $element->getMessages();
 
         <itemizedlist>
             <listitem><para>
-                    <code>setRequired($flag)</code> and
-                    <code>isRequired()</code> allow you to set and retrieve the
+                    <methodname>setRequired($flag)</methodname> and
+                    <methodname>isRequired()</methodname> allow you to set and retrieve the
                     status of the 'required' flag. When set to boolean <constant>TRUE</constant>,
                     this flag requires that the element be in the data processed by
                     <classname>Zend_Form</classname>.
             </para></listitem>
 
             <listitem><para>
-                    <code>setAllowEmpty($flag)</code> and
-                    <code>getAllowEmpty()</code> allow you to modify the
+                    <methodname>setAllowEmpty($flag)</methodname> and
+                    <methodname>getAllowEmpty()</methodname> allow you to modify the
                     behaviour of optional elements (i.e., elements where the
                     required flag is false). When the 'allow empty' flag is
                     true, empty values will not be passed to the validator
@@ -668,7 +668,7 @@ $messages = $element->getMessages();
             </para></listitem>
 
             <listitem><para>
-                    <code>setAutoInsertNotEmptyValidator($flag)</code> allows
+                    <methodname>setAutoInsertNotEmptyValidator($flag)</methodname> allows
                     you to specify whether or not a 'NotEmpty' validator will be
                     prepended to the validator chain when the element is
                     required. By default, this flag is true.
@@ -680,27 +680,27 @@ $messages = $element->getMessages();
             </para></listitem>
 
             <listitem><para>
-                <code>addValidators(array $validators)</code>
+                <methodname>addValidators(array $validators)</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>setValidators(array $validators)</code> (overwrites all validators)
+                <methodname>setValidators(array $validators)</methodname> (overwrites all validators)
             </para></listitem>
 
             <listitem><para>
-                <code>getValidator($name)</code> (retrieve a validator object by name)
+                <methodname>getValidator($name)</methodname> (retrieve a validator object by name)
             </para></listitem>
 
             <listitem><para>
-                <code>getValidators()</code> (retrieve all validators)
+                <methodname>getValidators()</methodname> (retrieve all validators)
             </para></listitem>
 
             <listitem><para>
-                <code>removeValidator($name)</code> (remove validator by name)
+                <methodname>removeValidator($name)</methodname> (remove validator by name)
             </para></listitem>
 
             <listitem><para>
-                <code>clearValidators()</code> (remove all validators)
+                <methodname>clearValidators()</methodname> (remove all validators)
             </para></listitem>
         </itemizedlist>
 
@@ -717,55 +717,55 @@ $messages = $element->getMessages();
 
             <itemizedlist>
                 <listitem><para>
-                    <code>addErrorMessage($message)</code>: add an error message
+                    <methodname>addErrorMessage($message)</methodname>: add an error message
                     to display on form validation errors. You may call this more
                     than once, and new messages are appended to the stack.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>addErrorMessages(array $messages)</code>: add multiple
+                    <methodname>addErrorMessages(array $messages)</methodname>: add multiple
                     error messages to display on form validation errors.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setErrorMessages(array $messages)</code>: add multiple
+                    <methodname>setErrorMessages(array $messages)</methodname>: add multiple
                     error messages to display on form validation errors,
                     overwriting all previously set error messages.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>getErrorMessages()</code>: retrieve the list of
+                    <methodname>getErrorMessages()</methodname>: retrieve the list of
                     custom error messages that have been defined.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>clearErrorMessages()</code>: remove all custom error
+                    <methodname>clearErrorMessages()</methodname>: remove all custom error
                     messages that have been defined.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>markAsError()</code>: mark the element as having
+                    <methodname>markAsError()</methodname>: mark the element as having
                     failed validation.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>hasErrors()</code>: determine whether the element has
+                    <methodname>hasErrors()</methodname>: determine whether the element has
                     either failed validation or been marked as invalid.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>addError($message)</code>: add a message to the custom
+                    <methodname>addError($message)</methodname>: add a message to the custom
                     error messages stack and flag the element as invalid.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>addErrors(array $messages)</code>: add several
+                    <methodname>addErrors(array $messages)</methodname>: add several
                     messages to the custom error messages stack and flag the
                     element as invalid.
                 </para></listitem>
 
                 <listitem><para>
-                    <code>setErrors(array $messages)</code>: overwrite the
+                    <methodname>setErrors(array $messages)</methodname>: overwrite the
                     custom error messages stack with the provided messages and
                     flag the element as invalid.
                 </para></listitem>
@@ -928,7 +928,7 @@ $this->addDecorators(array(
             <para>
                 To get around this, you can use <emphasis>aliases</emphasis>.
                 Instead of passing a decorator or decorator name as the first
-                argument to <code>addDecorator()</code>, pass an array with a
+                argument to <methodname>addDecorator()</methodname>, pass an array with a
                 single element, with the alias pointing to the decorator object
                 or name:
             </para>
@@ -943,8 +943,8 @@ $decorator = $element->getDecorator('FooBar');
 ]]></programlisting>
 
             <para>
-                In the <code>addDecorators()</code> and
-                <code>setDecorators()</code> methods, you will need to pass
+                In the <methodname>addDecorators()</methodname> and
+                <methodname>setDecorators()</methodname> methods, you will need to pass
                 the 'decorator' option in the array representing the decorator:
             </para>
 
@@ -970,42 +970,42 @@ $fooBar  = $element->getDecorator('FooBar');
 
         <itemizedlist>
             <listitem><para>
-                <code>addDecorator($nameOrDecorator, array $options = null)</code>
+                <methodname>addDecorator($nameOrDecorator, array $options = null)</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>addDecorators(array $decorators)</code>
+                <methodname>addDecorators(array $decorators)</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>setDecorators(array $decorators)</code> (overwrites all decorators)
+                <methodname>setDecorators(array $decorators)</methodname> (overwrites all decorators)
             </para></listitem>
 
             <listitem><para>
-                <code>getDecorator($name)</code> (retrieve a decorator object by name)
+                <methodname>getDecorator($name)</methodname> (retrieve a decorator object by name)
             </para></listitem>
 
             <listitem><para>
-                <code>getDecorators()</code> (retrieve all decorators)
+                <methodname>getDecorators()</methodname> (retrieve all decorators)
             </para></listitem>
 
             <listitem><para>
-                <code>removeDecorator($name)</code> (remove decorator by name)
+                <methodname>removeDecorator($name)</methodname> (remove decorator by name)
             </para></listitem>
 
             <listitem><para>
-                <code>clearDecorators()</code> (remove all decorators)
+                <methodname>clearDecorators()</methodname> (remove all decorators)
             </para></listitem>
         </itemizedlist>
 
         <para>
             <classname>Zend_Form_Element</classname> also uses overloading to allow rendering
-            specific decorators. <code>__call()</code> will intercept methods
+            specific decorators. <methodname>__call()</methodname> will intercept methods
             that lead with the text 'render' and use the remainder of the method
             name to lookup a decorator; if found, it will then render that
             <emphasis>single</emphasis> decorator. Any arguments passed to the
             method call will be used as content to pass to the decorator's
-            <code>render()</code> method. As an example:
+            <methodname>render()</methodname> method. As an example:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -1032,37 +1032,37 @@ echo $element->renderHtmlTag("This is the html tag content");
         <itemizedlist>
             <listitem><para>
                 <emphasis>name</emphasis>: the element name. Uses the
-                <code>setName()</code> and <code>getName()</code> accessors.
+                <methodname>setName()</methodname> and <methodname>getName()</methodname> accessors.
             </para></listitem>
 
             <listitem><para>
                 <emphasis>label</emphasis>: the element label. Uses the
-                <code>setLabel()</code> and <code>getLabel()</code> accessors.
+                <methodname>setLabel()</methodname> and <methodname>getLabel()</methodname> accessors.
             </para></listitem>
 
             <listitem><para>
                 <emphasis>order</emphasis>: the index at which an element
-                should appear in the form. Uses the <code>setOrder()</code> and
-                <code>getOrder()</code> accessors.
+                should appear in the form. Uses the <methodname>setOrder()</methodname> and
+                <methodname>getOrder()</methodname> accessors.
             </para></listitem>
 
             <listitem><para>
                 <emphasis>value</emphasis>: the current element value. Uses the
-                <code>setValue()</code> and <code>getValue()</code> accessors.
+                <methodname>setValue()</methodname> and <methodname>getValue()</methodname> accessors.
             </para></listitem>
 
             <listitem><para>
                 <emphasis>description</emphasis>: a description of the element;
                 often used to provide tooltip or javascript contextual hinting
                 describing the purpose of the element. Uses the
-                <code>setDescription()</code> and <code>getDescription()</code>
+                <methodname>setDescription()</methodname> and <methodname>getDescription()</methodname>
                 accessors.
             </para></listitem>
 
             <listitem><para>
                 <emphasis>required</emphasis>: flag indicating whether or not
                 the element is required when performing form validation. Uses
-                the <code>setRequired()</code> and <code>getRequired()</code>
+                the <methodname>setRequired()</methodname> and <methodname>getRequired()</methodname>
                 accessors. This flag is false by default.
             </para></listitem>
 
@@ -1071,7 +1071,7 @@ echo $element->renderHtmlTag("This is the html tag content");
                 a non-required (optional) element should attempt to validate
                 empty values. If it is set to true and the required flag is false, empty
                 values are not passed to the validator chain and are presumed true.
-                Uses the <code>setAllowEmpty()</code> and <code>getAllowEmpty()</code>
+                Uses the <methodname>setAllowEmpty()</methodname> and <methodname>getAllowEmpty()</methodname>
                 accessors. This flag is true by default.
             </para></listitem>
 
@@ -1079,9 +1079,9 @@ echo $element->renderHtmlTag("This is the html tag content");
                 <emphasis>autoInsertNotEmptyValidator</emphasis>: flag
                 indicating whether or not to insert a 'NotEmpty' validator when
                 the element is required. By default, this flag is true. Set the
-                flag with <code>setAutoInsertNotEmptyValidator($flag)</code> and
+                flag with <methodname>setAutoInsertNotEmptyValidator($flag)</methodname> and
                 determine the value with
-                <code>autoInsertNotEmptyValidator()</code>.
+                <methodname>autoInsertNotEmptyValidator()</methodname>.
             </para></listitem>
         </itemizedlist>
 
@@ -1151,8 +1151,8 @@ $element->class = 'text;
         <itemizedlist>
             <listitem><para>Configuration:</para>
                 <itemizedlist>
-                    <listitem><para><code>setOptions(array $options)</code></para></listitem>
-                    <listitem><para><code>setConfig(Zend_Config $config)</code></para></listitem>
+                    <listitem><para><methodname>setOptions(array $options)</methodname></para></listitem>
+                    <listitem><para><methodname>setConfig(Zend_Config $config)</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
@@ -1160,43 +1160,43 @@ $element->class = 'text;
                 <itemizedlist>
                     <listitem>
                         <para>
-                            <code>setTranslator(Zend_Translate_Adapter $translator = null)</code>
+                            <methodname>setTranslator(Zend_Translate_Adapter $translator = null)</methodname>
                         </para>
                     </listitem>
-                    <listitem><para><code>getTranslator()</code></para></listitem>
-                    <listitem><para><code>setDisableTranslator($flag)</code></para></listitem>
-                    <listitem><para><code>translatorIsDisabled()</code></para></listitem>
+                    <listitem><para><methodname>getTranslator()</methodname></para></listitem>
+                    <listitem><para><methodname>setDisableTranslator($flag)</methodname></para></listitem>
+                    <listitem><para><methodname>translatorIsDisabled()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
             <listitem><para>Properties:</para>
                 <itemizedlist>
-                    <listitem><para><code>setName($name)</code></para></listitem>
-                    <listitem><para><code>getName()</code></para></listitem>
-                    <listitem><para><code>setValue($value)</code></para></listitem>
-                    <listitem><para><code>getValue()</code></para></listitem>
-                    <listitem><para><code>getUnfilteredValue()</code></para></listitem>
-                    <listitem><para><code>setLabel($label)</code></para></listitem>
-                    <listitem><para><code>getLabel()</code></para></listitem>
-                    <listitem><para><code>setDescription($description)</code></para></listitem>
-                    <listitem><para><code>getDescription()</code></para></listitem>
-                    <listitem><para><code>setOrder($order)</code></para></listitem>
-                    <listitem><para><code>getOrder()</code></para></listitem>
-                    <listitem><para><code>setRequired($flag)</code></para></listitem>
-                    <listitem><para><code>getRequired()</code></para></listitem>
-                    <listitem><para><code>setAllowEmpty($flag)</code></para></listitem>
-                    <listitem><para><code>getAllowEmpty()</code></para></listitem>
+                    <listitem><para><methodname>setName($name)</methodname></para></listitem>
+                    <listitem><para><methodname>getName()</methodname></para></listitem>
+                    <listitem><para><methodname>setValue($value)</methodname></para></listitem>
+                    <listitem><para><methodname>getValue()</methodname></para></listitem>
+                    <listitem><para><methodname>getUnfilteredValue()</methodname></para></listitem>
+                    <listitem><para><methodname>setLabel($label)</methodname></para></listitem>
+                    <listitem><para><methodname>getLabel()</methodname></para></listitem>
+                    <listitem><para><methodname>setDescription($description)</methodname></para></listitem>
+                    <listitem><para><methodname>getDescription()</methodname></para></listitem>
+                    <listitem><para><methodname>setOrder($order)</methodname></para></listitem>
+                    <listitem><para><methodname>getOrder()</methodname></para></listitem>
+                    <listitem><para><methodname>setRequired($flag)</methodname></para></listitem>
+                    <listitem><para><methodname>getRequired()</methodname></para></listitem>
+                    <listitem><para><methodname>setAllowEmpty($flag)</methodname></para></listitem>
+                    <listitem><para><methodname>getAllowEmpty()</methodname></para></listitem>
                     <listitem>
-                        <para><code>setAutoInsertNotEmptyValidator($flag)</code></para>
+                        <para><methodname>setAutoInsertNotEmptyValidator($flag)</methodname></para>
                     </listitem>
-                    <listitem><para><code>autoInsertNotEmptyValidator()</code></para></listitem>
-                    <listitem><para><code>setIgnore($flag)</code></para></listitem>
-                    <listitem><para><code>getIgnore()</code></para></listitem>
-                    <listitem><para><code>getType()</code></para></listitem>
-                    <listitem><para><code>setAttrib($name, $value)</code></para></listitem>
-                    <listitem><para><code>setAttribs(array $attribs)</code></para></listitem>
-                    <listitem><para><code>getAttrib($name)</code></para></listitem>
-                    <listitem><para><code>getAttribs()</code></para></listitem>
+                    <listitem><para><methodname>autoInsertNotEmptyValidator()</methodname></para></listitem>
+                    <listitem><para><methodname>setIgnore($flag)</methodname></para></listitem>
+                    <listitem><para><methodname>getIgnore()</methodname></para></listitem>
+                    <listitem><para><methodname>getType()</methodname></para></listitem>
+                    <listitem><para><methodname>setAttrib($name, $value)</methodname></para></listitem>
+                    <listitem><para><methodname>setAttribs(array $attribs)</methodname></para></listitem>
+                    <listitem><para><methodname>getAttrib($name)</methodname></para></listitem>
+                    <listitem><para><methodname>getAttribs()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
@@ -1208,11 +1208,11 @@ $element->class = 'text;
                                 $type)</code>
                         </para>
                     </listitem>
-                    <listitem><para><code>getPluginLoader($type)</code></para></listitem>
+                    <listitem><para><methodname>getPluginLoader($type)</methodname></para></listitem>
                     <listitem>
-                        <para><code>addPrefixPath($prefix, $path, $type = null)</code></para>
+                        <para><methodname>addPrefixPath($prefix, $path, $type = null)</methodname></para>
                     </listitem>
-                    <listitem><para><code>addPrefixPaths(array $spec)</code></para></listitem>
+                    <listitem><para><methodname>addPrefixPaths(array $spec)</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
@@ -1224,49 +1224,49 @@ $element->class = 'text;
                                 array())</code>
                         </para>
                     </listitem>
-                    <listitem><para><code>addValidators(array $validators)</code></para></listitem>
-                    <listitem><para><code>setValidators(array $validators)</code></para></listitem>
-                    <listitem><para><code>getValidator($name)</code></para></listitem>
-                    <listitem><para><code>getValidators()</code></para></listitem>
-                    <listitem><para><code>removeValidator($name)</code></para></listitem>
-                    <listitem><para><code>clearValidators()</code></para></listitem>
-                    <listitem><para><code>isValid($value, $context = null)</code></para></listitem>
-                    <listitem><para><code>getErrors()</code></para></listitem>
-                    <listitem><para><code>getMessages()</code></para></listitem>
+                    <listitem><para><methodname>addValidators(array $validators)</methodname></para></listitem>
+                    <listitem><para><methodname>setValidators(array $validators)</methodname></para></listitem>
+                    <listitem><para><methodname>getValidator($name)</methodname></para></listitem>
+                    <listitem><para><methodname>getValidators()</methodname></para></listitem>
+                    <listitem><para><methodname>removeValidator($name)</methodname></para></listitem>
+                    <listitem><para><methodname>clearValidators()</methodname></para></listitem>
+                    <listitem><para><methodname>isValid($value, $context = null)</methodname></para></listitem>
+                    <listitem><para><methodname>getErrors()</methodname></para></listitem>
+                    <listitem><para><methodname>getMessages()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
             <listitem><para>Filters:</para>
                 <itemizedlist>
                     <listitem>
-                        <para><code>addFilter($filter, $options = array())</code></para>
+                        <para><methodname>addFilter($filter, $options = array())</methodname></para>
                     </listitem>
-                    <listitem><para><code>addFilters(array $filters)</code></para></listitem>
-                    <listitem><para><code>setFilters(array $filters)</code></para></listitem>
-                    <listitem><para><code>getFilter($name)</code></para></listitem>
-                    <listitem><para><code>getFilters()</code></para></listitem>
-                    <listitem><para><code>removeFilter($name)</code></para></listitem>
-                    <listitem><para><code>clearFilters()</code></para></listitem>
+                    <listitem><para><methodname>addFilters(array $filters)</methodname></para></listitem>
+                    <listitem><para><methodname>setFilters(array $filters)</methodname></para></listitem>
+                    <listitem><para><methodname>getFilter($name)</methodname></para></listitem>
+                    <listitem><para><methodname>getFilters()</methodname></para></listitem>
+                    <listitem><para><methodname>removeFilter($name)</methodname></para></listitem>
+                    <listitem><para><methodname>clearFilters()</methodname></para></listitem>
                 </itemizedlist>
             </listitem>
 
             <listitem><para>Rendering:</para>
                 <itemizedlist>
                     <listitem>
-                        <para><code>setView(Zend_View_Interface $view = null)</code></para>
+                        <para><methodname>setView(Zend_View_Interface $view = null)</methodname></para>
                     </listitem>
-                    <listitem><para><code>getView()</code></para></listitem>
+                    <listitem><para><methodname>getView()</methodname></para></listitem>
                     <listitem>
-                        <para><code>addDecorator($decorator, $options = null)</code></para>
+                        <para><methodname>addDecorator($decorator, $options = null)</methodname></para>
                     </listitem>
-                    <listitem><para><code>addDecorators(array $decorators)</code></para></listitem>
-                    <listitem><para><code>setDecorators(array $decorators)</code></para></listitem>
-                    <listitem><para><code>getDecorator($name)</code></para></listitem>
-                    <listitem><para><code>getDecorators()</code></para></listitem>
-                    <listitem><para><code>removeDecorator($name)</code></para></listitem>
-                    <listitem><para><code>clearDecorators()</code></para></listitem>
+                    <listitem><para><methodname>addDecorators(array $decorators)</methodname></para></listitem>
+                    <listitem><para><methodname>setDecorators(array $decorators)</methodname></para></listitem>
+                    <listitem><para><methodname>getDecorator($name)</methodname></para></listitem>
+                    <listitem><para><methodname>getDecorators()</methodname></para></listitem>
+                    <listitem><para><methodname>removeDecorator($name)</methodname></para></listitem>
+                    <listitem><para><methodname>clearDecorators()</methodname></para></listitem>
                     <listitem>
-                        <para><code>render(Zend_View_Interface $view = null)</code></para>
+                        <para><methodname>render(Zend_View_Interface $view = null)</methodname></para>
                     </listitem>
                 </itemizedlist>
             </listitem>
@@ -1280,7 +1280,7 @@ $element->class = 'text;
             <classname>Zend_Form_Element</classname>'s constructor accepts either an
             array of options or a <classname>Zend_Config</classname> object containing
             options, and it can also be configured using either
-            <code>setOptions()</code> or <code>setConfig()</code>. Generally
+            <methodname>setOptions()</methodname> or <methodname>setConfig()</methodname>. Generally
             speaking, keys are named as follows:
         </para>
 
@@ -1302,7 +1302,7 @@ $element->class = 'text;
         <itemizedlist>
             <listitem><para>
                 <code>prefixPath</code> will be passed to
-                <code>addPrefixPaths()</code>
+                <methodname>addPrefixPaths()</methodname>
             </para></listitem>
 
             <listitem>
@@ -1386,8 +1386,8 @@ decorators.label.decorator = "Label"
 
         <para>
             There are two methods typically used to extend an element:
-            <code>init()</code>, which can be used to add custom initialization
-            logic to your element, and <code>loadDefaultDecorators()</code>,
+            <methodname>init()</methodname>, which can be used to add custom initialization
+            logic to your element, and <methodname>loadDefaultDecorators()</methodname>,
             which can be used to set a list of default decorators used by your
             element.
         </para>
@@ -1436,7 +1436,7 @@ $form->addPrefixPath('My_Element', 'My/Element/', 'element')
         <para>
             Another method you may want to override when extending
             <classname>Zend_Form_Element</classname> is the
-            <code>loadDefaultDecorators()</code> method. This method
+            <methodname>loadDefaultDecorators()</methodname> method. This method
             conditionally loads a set of default decorators for your element;
             you may wish to substitute your own decorators in your extending
             class:

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

@@ -26,7 +26,7 @@
 
         <para>
             You can disable translation for any form, element, display group, or
-            sub form by calling its <code>setDisableTranslator($flag)</code>
+            sub form by calling its <methodname>setDisableTranslator($flag)</methodname>
             method or passing a <code>disableTranslator</code> option to the
             object. This can be useful when you want to selectively disable
             translation for individual elements or sets of elements.
@@ -95,7 +95,7 @@ Zend_Form::setDefaultTranslator($translate);
             <listitem>
                 <para>
                     Finally, you can attach a translator to a specific form instance
-                    or to specific elements using their <code>setTranslator()</code>
+                    or to specific elements using their <methodname>setTranslator()</methodname>
                     methods:
                 </para>
 

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

@@ -29,8 +29,8 @@ $form = new Zend_Form;
 
         <para>
             If you wish to specify the form action and method (always good
-            ideas), you can do so with the <code>setAction()</code> and
-            <code>setMethod()</code> accessors:
+            ideas), you can do so with the <methodname>setAction()</methodname> and
+            <methodname>setMethod()</methodname> accessors:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -329,7 +329,7 @@ $element->addDecorators(array(
             in an HTML <code>&lt;form&gt;</code>. The action and method you
             provided when setting up the form are provided to the
             <code>&lt;form&gt;</code> tag, as are any attributes you set via
-            <code>setAttribs()</code> and family.
+            <methodname>setAttribs()</methodname> and family.
         </para>
 
         <para>
@@ -379,8 +379,8 @@ if ($form->isValid($_POST)) {
         <para>
             With AJAX requests, you can sometimes get away with validating
             a single element, or groups of elements.
-            <code>isValidPartial()</code> will validate a partial form. Unlike
-            <code>isValid()</code>, however, if a particular key is not
+            <methodname>isValidPartial()</methodname> will validate a partial form. Unlike
+            <methodname>isValid()</methodname>, however, if a particular key is not
             present, it will not run validations for that particular element:
         </para>
 
@@ -393,8 +393,8 @@ if ($form->isValidPartial($_POST)) {
 ]]></programlisting>
 
         <para>
-            An additional method, <code>processAjax()</code>, can be used
-            for validating partial forms. Unlike <code>isValidPartial()</code>,
+            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
             failure.
         </para>
@@ -438,9 +438,9 @@ if (!$form->isValid($_POST)) {
 
         <para>
             If you want to inspect the errors, you have two methods.
-            <code>getErrors()</code> returns an associative array of element
+            <methodname>getErrors()</methodname> returns an associative array of element
             names / codes (where codes is an array of error codes).
-            <code>getMessages()</code> returns an associative array of element
+            <methodname>getMessages()</methodname> returns an associative array of element
             names / messages (where messages is an associative array of error
             code / error message pairs). If a given element does not have any
             errors, it will not be included in the array.
@@ -561,7 +561,7 @@ class UserController extends Zend_Controller_Action
             All <classname>Zend_Form</classname> classes are configurable using
             <classname>Zend_Config</classname>; you can either pass a
             <classname>Zend_Config</classname> object to the constructor or pass it in
-            with <code>setConfig()</code>. Let's look at how we might create the
+            with <methodname>setConfig()</methodname>. Let's look at how we might create the
             above form using an INI file. First, let's follow the
             recommendations, and place our configurations into sections
             reflecting the release location, and focus on the 'development'

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

@@ -56,7 +56,7 @@ class Util
             The Captcha decorator is for use with the <link
                 linkend="zend.form.standardElements.captcha">CAPTCHA form
                 element</link>. It utilizes the CAPTCHA adapter's
-            <code>render()</code> method to generate the output.
+            <methodname>render()</methodname> method to generate the output.
         </para>
 
         <para>
@@ -75,7 +75,7 @@ class Util
             The Description decorator can be used to display a description set
             on a <classname>Zend_Form</classname>, <classname>Zend_Form_Element</classname>, or
             <classname>Zend_Form_DisplayGroup</classname> item; it pulls the description
-            using the object's <code>getDescription()</code> method. Common use
+            using the object's <methodname>getDescription()</methodname> method. Common use
             cases are for providing UI hints for your elements.
         </para>
 
@@ -84,16 +84,16 @@ class Util
             the description is present, then it is wrapped in an HTML
             <code>p</code> tag by default, though you may specify a tag by
             passing a <code>tag</code> option when creating the decorator, or
-            calling <code>setTag()</code>. You may additionally specify a class
+            calling <methodname>setTag()</methodname>. You may additionally specify a class
             for the tag using the <code>class</code> option or by calling
-            <code>setClass()</code>; by default, the class 'hint' is used.
+            <methodname>setClass()</methodname>; by default, the class 'hint' is used.
         </para>
 
         <para>
             The description is escaped using the view object's escaping
             mechanisms by default. You can disable this by passing a
             <constant>FALSE</constant> value to the decorator's 'escape' option or
-            <code>setEscape()</code> method.
+            <methodname>setEscape()</methodname> method.
         </para>
     </sect2>
 
@@ -148,7 +148,7 @@ class Util
         <para>
             Display groups and sub forms render their content within
             fieldsets by default. The Fieldset decorator checks for either a
-            'legend' option or a <code>getLegend()</code> method in the
+            'legend' option or a <methodname>getLegend()</methodname> method in the
             registered element, and uses that as a legend if non-empty. Any
             content passed in is wrapped in the HTML fieldset, replacing the
             original content. Any attributes set in the decorated item are
@@ -187,7 +187,7 @@ class Util
             Forms, display groups, and sub forms are collections of
             elements. In order to render these elements, they utilize the
             FormElements decorator, which iterates through all items,
-            calling <code>render()</code> on each and joining them with the
+            calling <methodname>render()</methodname> on each and joining them with the
             registered separator. It can either append or prepend content
             passed to it.
         </para>
@@ -294,17 +294,17 @@ class Util
 
         <para>
             By default, the decorator uses the element's src property, which can
-            be set with the <code>setImage()</code> method, as the image
+            be set with the <methodname>setImage()</methodname> method, as the image
             source. Additionally, the element's label will be used as the alt
             tag, and the <code>imageValue</code> (manipulated with the Image
-            element's <code>setImageValue()</code> and
-            <code>getImageValue()</code> accessors) will be used for the value.
+            element's <methodname>setImageValue()</methodname> and
+            <methodname>getImageValue()</methodname> accessors) will be used for the value.
         </para>
 
         <para>
             To specify an HTML tag with which to wrap the element, either pass a
             'tag' option to the decorator, or explicitly call
-            <code>setTag()</code>.
+            <methodname>setTag()</methodname>.
         </para>
     </sect2>
 
@@ -315,7 +315,7 @@ class Util
             Form elements typically have labels, and the Label decorator is
             used to render these labels. It proxies to the FormLabel view
             helper, and pulls the element label using the
-            <code>getLabel()</code> method of the element. If no label is
+            <methodname>getLabel()</methodname> method of the element. If no label is
             present, none is rendered. By default, labels are translated when a
             translation adapter exists and a translation for the label exists.
         </para>
@@ -325,7 +325,7 @@ class Util
             the label in that block-level tag. If the 'tag' option is
             present, and no label present, the tag is rendered with no
             content. You can specify the class to use with the tag with the
-            'class' option or by calling <code>setClass()</code>.
+            'class' option or by calling <methodname>setClass()</methodname>.
         </para>
 
         <para>
@@ -340,29 +340,29 @@ class Util
             <listitem><para>
                     <code>optionalPrefix</code>: set the text to prefix the
                     label with when the element is optional. Use the
-                    <code>setOptionalPrefix()</code> and
-                    <code>getOptionalPrefix()</code> accessors to manipulate it.
+                    <methodname>setOptionalPrefix()</methodname> and
+                    <methodname>getOptionalPrefix()</methodname> accessors to manipulate it.
             </para></listitem>
 
             <listitem><para>
                     <code>optionalSuffix</code>: set the text to append the
                     label with when the element is optional. Use the
-                    <code>setOptionalSuffix()</code> and
-                    <code>getOptionalSuffix()</code> accessors to manipulate it.
+                    <methodname>setOptionalSuffix()</methodname> and
+                    <methodname>getOptionalSuffix()</methodname> accessors to manipulate it.
             </para></listitem>
 
             <listitem><para>
                     <code>requiredPrefix</code>: set the text to prefix the
                     label with when the element is required. Use the
-                    <code>setRequiredPrefix()</code> and
-                    <code>getRequiredPrefix()</code> accessors to manipulate it.
+                    <methodname>setRequiredPrefix()</methodname> and
+                    <methodname>getRequiredPrefix()</methodname> accessors to manipulate it.
             </para></listitem>
 
             <listitem><para>
                     <code>requiredSuffix</code>: set the text to append the
                     label with when the element is required. Use the
-                    <code>setRequiredSuffix()</code> and
-                    <code>getRequiredSuffix()</code> accessors to manipulate it.
+                    <methodname>setRequiredSuffix()</methodname> and
+                    <methodname>getRequiredSuffix()</methodname> accessors to manipulate it.
             </para></listitem>
         </itemizedlist>
 
@@ -455,7 +455,7 @@ $form->setDecorators(array(
 
             <listitem><para>
                     Additionally, all options passed to the decorator via
-                    <code>setOptions()</code> that are not used internally (such
+                    <methodname>setOptions()</methodname> that are not used internally (such
                     as placement, separator, etc.) are passed to the view script
                     as view variables.
             </para></listitem>

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

@@ -40,7 +40,7 @@
 
         <para>
             After populating or validating a form, you can check if the given
-            button was clicked using the <code>isChecked()</code> method.
+            button was clicked using the <methodname>isChecked()</methodname> method.
         </para>
     </sect2>
 
@@ -72,7 +72,7 @@ $element->addPrefixPath('My_Captcha', 'My/Captcha/', 'captcha');
 ]]></programlisting>
 
         <para>
-            Captcha's may then be registered using the <code>setCaptcha()</code>
+            Captcha's may then be registered using the <methodname>setCaptcha()</methodname>
             method, which can take either a concrete CAPTCHA instance, or the
             short name of a CAPTCHA adapter:
         </para>
@@ -119,7 +119,7 @@ $element = new Zend_Form_Element_Captcha('foo', array(
             default, the <link
                 linkend="zend.form.standardDecorators.captcha">Captcha
                 decorator</link> is used, but an adapter may specify a different
-            one via its <code>getDecorator()</code> method.
+            one via its <methodname>getDecorator()</methodname> method.
         </para>
 
         <para>
@@ -143,7 +143,7 @@ $element = new Zend_Form_Element_Captcha('foo', array(
         <para>
             By default, the checked value is '1', and the unchecked value '0'.
             You can specify the values to use using the
-            <code>setCheckedValue()</code> and <code>setUncheckedValue()</code>
+            <methodname>setCheckedValue()</methodname> and <methodname>setUncheckedValue()</methodname>
             accessors, respectively. Internally, any time you set the value, if
             the provided value matches the checked value, then it is set, but
             any other value causes the unchecked value to be set.
@@ -152,8 +152,8 @@ $element = new Zend_Form_Element_Captcha('foo', array(
         <para>
             Additionally, setting the value sets the <code>checked</code>
             property of the checkbox. You can query this using
-            <code>isChecked()</code> or simply accessing the property. Using the
-            <code>setChecked($flag)</code> method will both set the state of the
+            <methodname>isChecked()</methodname> or simply accessing the property. Using the
+            <methodname>setChecked($flag)</methodname> method will both set the state of the
             flag as well as set the appropriate checked or unchecked value in the
             element. Please use this method when setting the checked state of a
             checkbox element to ensure the value is set properly.
@@ -217,8 +217,8 @@ $form->setAttrib('enctype', 'multipart/form-data');
 
             <para>
                 After the form is validated successfully, you must receive the file
-                to store it in the final destination using <code>receive()</code>. Additionally you
-                can determinate the final location using <code>getFileName()</code>:
+                to store it in the final destination using <methodname>receive()</methodname>. Additionally you
+                can determinate the final location using <methodname>getFileName()</methodname>:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -248,15 +248,15 @@ $location = $form->foo->getFileName();
 
             <para>
                 Within HTTP a file element has no value. For this reason and because of
-                security concerns <code>getValue()</code> returns only the uploaded filename
+                security concerns <methodname>getValue()</methodname> returns only the uploaded filename
                 and not the complete path. If you need the file path, call
-                <code>getFileName()</code>, which returns both the path and the name of the file.
+                <methodname>getFileName()</methodname>, which returns both the path and the name of the file.
             </para>
         </note>
 
         <para>
             Per default the file will automatically be received when you call
-            <code>getValues()</code> on the form. The reason behind this behaviour is, that the
+            <methodname>getValues()</methodname> on the form. The reason behind this behaviour is, that the
             file itself is the value of the file element.
         </para>
 
@@ -266,24 +266,24 @@ $form->getValues();
 
         <note>
             <para>
-                Therefor another call of <code>receive()</code> after calling
-                <code>getValues()</code> will not have an effect. Also creating a instance of
+                Therefor another call of <methodname>receive()</methodname> after calling
+                <methodname>getValues()</methodname> will not have an effect. Also creating a instance of
                 <classname>Zend_File_Transfer</classname> will not have an effect as there no file
                 anymore to receive.
             </para>
         </note>
 
         <para>
-            Still, sometimes you may want to call <code>getValues()</code> without receiving the
-            file. You can archive this by calling <code>setValueDisabled(true)</code>. To get the
-            actual value of this flag you can call <code>isValueDisabled()</code>.
+            Still, sometimes you may want to call <methodname>getValues()</methodname> without receiving the
+            file. You can archive this by calling <methodname>setValueDisabled(true)</methodname>. To get the
+            actual value of this flag you can call <methodname>isValueDisabled()</methodname>.
         </para>
 
         <example id="zend.form.standardElements.file.retrievement">
             <title>Explicit file retrievement</title>
 
             <para>
-                First call <code>setValueDisabled(true)</code>.
+                First call <methodname>setValueDisabled(true)</methodname>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -294,8 +294,8 @@ $element->setLabel('Upload an image:')
 ]]></programlisting>
 
             <para>
-                Now the file will not be received when you call <code>getValues()</code>.
-                So you must call <code>receive()</code> on the file element, or an instance of
+                Now the file will not be received when you call <methodname>getValues()</methodname>.
+                So you must call <methodname>receive()</methodname> on the file element, or an instance of
                 <classname>Zend_File_Transfer</classname> yourself.
             </para>
 
@@ -318,21 +318,21 @@ if ($form->isValid($form->getPost())) {
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>isUploaded()</code>: Checks if the file element has
+                    <methodname>isUploaded()</methodname>: Checks if the file element has
                     been uploaded or not.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>isReceived()</code>: Checks if the file element has
+                    <methodname>isReceived()</methodname>: Checks if the file element has
                     already been received.
                 </para>
             </listitem>
 
             <listitem>
                 <para>
-                    <code>isFiltered()</code>: Checks if the filters have already
+                    <methodname>isFiltered()</methodname>: Checks if the filters have already
                     been applied to the file element or not.
                 </para>
             </listitem>
@@ -358,7 +358,7 @@ if ($form->foo->isUploaded()) {
 
         <para>
             <classname>Zend_Form_Element_File</classname> also supports multiple files.
-            By calling the <code>setMultiFile($count)</code> method you can set
+            By calling the <methodname>setMultiFile($count)</methodname> method you can set
             the number of file elements you want to create. This keeps you
             from setting the same settings multiple times.
         </para>
@@ -368,7 +368,7 @@ if ($form->foo->isUploaded()) {
 
             <para>
                 Creating a multifile element is the same as setting a single
-                element. Just call <code>setMultiFile()</code> after the element is created:
+                element. Just call <methodname>setMultiFile()</methodname> after the element is created:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -389,7 +389,7 @@ $form->addElement($element, 'foo');
             <para>
                 You now have 3 identical file upload elements
                 with the same settings. To get the set multifile number simply call
-                <code>getMultiFile()</code>.
+                <methodname>getMultiFile()</methodname>.
             </para>
 
         </example>
@@ -419,7 +419,7 @@ $form->addElement($element, 'foo');
             To limit the size of the file uploaded, you can
             specify the maximum file size by setting the <code>MAX_FILE_SIZE</code>
             option on the form. When you set this value by using the
-            <code>setMaxFileSize($size)</code> method, it will be rendered with the
+            <methodname>setMaxFileSize($size)</methodname> method, it will be rendered with the
             file element.
         </para>
 
@@ -479,7 +479,7 @@ $form->addElement('hash', 'no_csrf_foo', array('salt' => 'unique'));
 ]]></programlisting>
 
         <para>
-            You can set the salt later using the <code>setSalt($salt)</code>
+            You can set the salt later using the <methodname>setSalt($salt)</methodname>
             method.
         </para>
 
@@ -507,12 +507,12 @@ $form->addElement('hash', 'no_csrf_foo', array('salt' => 'unique'));
 
         <para>
             Images need an image source. <classname>Zend_Form_Element_Image</classname>
-            allows you to specify this by using the <code>setImage()</code>
+            allows you to specify this by using the <methodname>setImage()</methodname>
             accessor (or 'image' configuration key). You can also optionally specify a value to use
-            when submitting the image using the <code>setImageValue()</code> accessor
+            when submitting the image using the <methodname>setImageValue()</methodname> accessor
             (or 'imageValue' configuration key). When the value set for the
             element matches the <code>imageValue</code>, then the accessor
-            <code>isChecked()</code> will return true.
+            <methodname>isChecked()</methodname> will return true.
         </para>
 
         <para>
@@ -548,7 +548,7 @@ $form->addElement('hash', 'no_csrf_foo', array('salt' => 'unique'));
             By default, this element registers an <code>InArray</code> validator
             which validates against the array keys of registered options. You
             can disable this behavior by either calling
-            <code>setRegisterInArrayValidator(false)</code>, or by passing a
+            <methodname>setRegisterInArrayValidator(false)</methodname>, or by passing a
             false value to the <code>registerInArrayValidator</code>
             configuration key.
         </para>
@@ -559,25 +559,25 @@ $form->addElement('hash', 'no_csrf_foo', array('salt' => 'unique'));
         </para>
 
         <itemizedlist>
-            <listitem><para><code>addMultiOption($option, $value)</code></para></listitem>
+            <listitem><para><methodname>addMultiOption($option, $value)</methodname></para></listitem>
 
-            <listitem><para><code>addMultiOptions(array $options)</code></para></listitem>
+            <listitem><para><methodname>addMultiOptions(array $options)</methodname></para></listitem>
 
-            <listitem><para><code>setMultiOptions(array $options)</code>
+            <listitem><para><methodname>setMultiOptions(array $options)</methodname>
                     (overwrites existing options)</para></listitem>
 
-            <listitem><para><code>getMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>getMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>getMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>getMultiOptions()</methodname></para></listitem>
 
-            <listitem><para><code>removeMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>removeMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>clearMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>clearMultiOptions()</methodname></para></listitem>
         </itemizedlist>
 
         <para>
             To mark checked items, you need to pass an array of values to
-            <code>setValue()</code>. The following will check the values "bar"
+            <methodname>setValue()</methodname>. The following will check the values "bar"
             and "bat":
         </para>
 
@@ -615,20 +615,20 @@ $element->setValue(array('bar', 'bat'));
         </para>
 
         <itemizedlist>
-            <listitem><para><code>addMultiOption($option, $value)</code></para></listitem>
+            <listitem><para><methodname>addMultiOption($option, $value)</methodname></para></listitem>
 
-            <listitem><para><code>addMultiOptions(array $options)</code></para></listitem>
+            <listitem><para><methodname>addMultiOptions(array $options)</methodname></para></listitem>
 
-            <listitem><para><code>setMultiOptions(array $options)</code>
+            <listitem><para><methodname>setMultiOptions(array $options)</methodname>
                     (overwrites existing options)</para></listitem>
 
-            <listitem><para><code>getMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>getMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>getMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>getMultiOptions()</methodname></para></listitem>
 
-            <listitem><para><code>removeMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>removeMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>clearMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>clearMultiOptions()</methodname></para></listitem>
         </itemizedlist>
 
         <para>
@@ -640,7 +640,7 @@ $element->setValue(array('bar', 'bat'));
             By default, this element registers an <code>InArray</code> validator
             which validates against the array keys of registered options. You
             can disable this behavior by either calling
-            <code>setRegisterInArrayValidator(false)</code>, or by passing a
+            <methodname>setRegisterInArrayValidator(false)</methodname>, or by passing a
             false value to the <code>registerInArrayValidator</code>
             configuration key.
         </para>
@@ -657,7 +657,7 @@ $element->setValue(array('bar', 'bat'));
 
         <para>
             <classname>Zend_Form_Element_Password</classname> achieves this by calling
-            <code>setObscureValue(true)</code> on each validator (ensuring that
+            <methodname>setObscureValue(true)</methodname> on each validator (ensuring that
             the password is obscured in validation error messages), and using
             the 'formPassword' view helper (which does not display the value
             passed to it).
@@ -679,7 +679,7 @@ $element->setValue(array('bar', 'bat'));
             By default, this element registers an <code>InArray</code> validator
             which validates against the array keys of registered options. You
             can disable this behavior by either calling
-            <code>setRegisterInArrayValidator(false)</code>, or by passing a
+            <methodname>setRegisterInArrayValidator(false)</methodname>, or by passing a
             false value to the <code>registerInArrayValidator</code>
             configuration key.
         </para>
@@ -691,20 +691,20 @@ $element->setValue(array('bar', 'bat'));
         </para>
 
         <itemizedlist>
-            <listitem><para><code>addMultiOption($option, $value)</code></para></listitem>
+            <listitem><para><methodname>addMultiOption($option, $value)</methodname></para></listitem>
 
-            <listitem><para><code>addMultiOptions(array $options)</code></para></listitem>
+            <listitem><para><methodname>addMultiOptions(array $options)</methodname></para></listitem>
 
-            <listitem><para><code>setMultiOptions(array $options)</code>
+            <listitem><para><methodname>setMultiOptions(array $options)</methodname>
                     (overwrites existing options)</para></listitem>
 
-            <listitem><para><code>getMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>getMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>getMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>getMultiOptions()</methodname></para></listitem>
 
-            <listitem><para><code>removeMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>removeMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>clearMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>clearMultiOptions()</methodname></para></listitem>
         </itemizedlist>
     </sect2>
 
@@ -740,7 +740,7 @@ $element->setValue(array('bar', 'bat'));
             By default, this element registers an <code>InArray</code> validator
             which validates against the array keys of registered options. You
             can disable this behavior by either calling
-            <code>setRegisterInArrayValidator(false)</code>, or by passing a
+            <methodname>setRegisterInArrayValidator(false)</methodname>, or by passing a
             false value to the <code>registerInArrayValidator</code>
             configuration key.
         </para>
@@ -751,20 +751,20 @@ $element->setValue(array('bar', 'bat'));
         </para>
 
         <itemizedlist>
-            <listitem><para><code>addMultiOption($option, $value)</code></para></listitem>
+            <listitem><para><methodname>addMultiOption($option, $value)</methodname></para></listitem>
 
-            <listitem><para><code>addMultiOptions(array $options)</code></para></listitem>
+            <listitem><para><methodname>addMultiOptions(array $options)</methodname></para></listitem>
 
-            <listitem><para><code>setMultiOptions(array $options)</code>
+            <listitem><para><methodname>setMultiOptions(array $options)</methodname>
                     (overwrites existing options)</para></listitem>
 
-            <listitem><para><code>getMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>getMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>getMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>getMultiOptions()</methodname></para></listitem>
 
-            <listitem><para><code>removeMultiOption($option)</code></para></listitem>
+            <listitem><para><methodname>removeMultiOption($option)</methodname></para></listitem>
 
-            <listitem><para><code>clearMultiOptions()</code></para></listitem>
+            <listitem><para><methodname>clearMultiOptions()</methodname></para></listitem>
         </itemizedlist>
 
         <para>
@@ -781,7 +781,7 @@ $element->setValue(array('bar', 'bat'));
             submit buttons; you can use the button used to submit the form to
             decide what action to take with the data submitted.
             <classname>Zend_Form_Element_Submit</classname> makes this decisioning easy,
-            by adding a <code>isChecked()</code> method; as only one button
+            by adding a <methodname>isChecked()</methodname> method; as only one button
             element will be submitted by the form, after populating or
             validating the form, you can call this method on each submit button
             to determine which one was used.
@@ -790,7 +790,7 @@ $element->setValue(array('bar', 'bat'));
         <para>
             <classname>Zend_Form_Element_Submit</classname> uses the label as the "value"
             of the submit button, translating it if a translation adapter is
-            present. <code>isChecked()</code> checks the submitted value against
+            present. <methodname>isChecked()</methodname> checks the submitted value against
             the label in order to determine if the button was used.
         </para>
 

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

@@ -129,13 +129,13 @@
                         <classname>Zend_Gdata_Spreadsheets_CellQuery</classname>. Query classes
                         provide methods used to construct a query for data
                         to be retrieved from GData services. Methods include
-                        getters and setters like <code>setUpdatedMin()</code>,
-                        <code>setStartIndex()</code>, and
-                        <code>getPublishedMin()</code>. The query classes also
+                        getters and setters like <methodname>setUpdatedMin()</methodname>,
+                        <methodname>setStartIndex()</methodname>, and
+                        <methodname>getPublishedMin()</methodname>. The query classes also
                         have a method to generate a URL representing the
                         constructed query -- <code>getQueryUrl</code>.
                         Alternatively, the query string component of the URL
-                        can be retrieved used the <code>getQueryString()</code>
+                        can be retrieved used the <methodname>getQueryString()</methodname>
                         method.
                     </para>
                 </listitem>
@@ -182,15 +182,15 @@
                         back from services and for constructing data to be
                         sent to services. These include getters and setters
                         such as
-                        <code>setText()</code> to set the child text
-                        node of an element, <code>getText()</code> to retrieve
-                        the text node of an element, <code>getStartTime()</code>
+                        <methodname>setText()</methodname> to set the child text
+                        node of an element, <methodname>getText()</methodname> to retrieve
+                        the text node of an element, <methodname>getStartTime()</methodname>
                         to retrieve the start time attribute of a When element,
                         and other similiar methods.
                         The data model classes also include methods such as
-                        <code>getDOM()</code> to retrieve a DOM representation
+                        <methodname>getDOM()</methodname> to retrieve a DOM representation
                         of the element and all children and
-                        <code>transferFromDOM()</code> to construct a data
+                        <methodname>transferFromDOM()</methodname> to construct a data
                         model representation of a DOM tree.
                     </para>
                 </listitem>
@@ -378,7 +378,7 @@ $gdata->setMinorProtocolVersion(null);
                     query. The value of the parameter is a string.
                 </para>
                 <para>
-                    Set this parameter with the <code>setQuery()</code>
+                    Set this parameter with the <methodname>setQuery()</methodname>
                     function.
                 </para>
             </listitem>
@@ -400,7 +400,7 @@ $gdata->setMinorProtocolVersion(null);
                     <classname>Zend_Gdata_Query</classname> class and its subclasses.
                 </para>
                 <para>
-                    Set this parameter with the <code>setAlt()</code>
+                    Set this parameter with the <methodname>setAlt()</methodname>
                     function.
                 </para>
             </listitem>
@@ -413,7 +413,7 @@ $gdata->setMinorProtocolVersion(null);
                     will not exceed this value.
                 </para>
                 <para>
-                    Set this parameter with the <code>setMaxResults()</code>
+                    Set this parameter with the <methodname>setMaxResults()</methodname>
                     function.
                 </para>
             </listitem>
@@ -425,7 +425,7 @@ $gdata->setMinorProtocolVersion(null);
                     Entries before this number are skipped.
                 </para>
                 <para>
-                    Set this parameter with the <code>setStartIndex()</code>
+                    Set this parameter with the <methodname>setStartIndex()</methodname>
                     function.
                 </para>
             </listitem>
@@ -446,8 +446,8 @@ $gdata->setMinorProtocolVersion(null);
                     these parameters.
                 </para>
                 <para>
-                    Set this parameter with the <code>setUpdatedMin()</code>
-                    and <code>setUpdatedMax()</code> functions.
+                    Set this parameter with the <methodname>setUpdatedMin()</methodname>
+                    and <methodname>setUpdatedMax()</methodname> functions.
                 </para>
             </listitem>
 
@@ -477,7 +477,7 @@ echo $query->maxResults;        // returns 10
 ]]></programlisting>
 
         <para>
-            You can clear all parameters with the <code>resetParameters()</code>
+            You can clear all parameters with the <methodname>resetParameters()</methodname>
             function. This is useful to do if you reuse a <classname>Zend_Gdata</classname>
             object for multiple queries.
         </para>
@@ -497,7 +497,7 @@ $query->resetParameters();      // clears all parameters
         <title>Fetching a Feed</title>
 
         <para>
-            Use the <code>getFeed()</code> function to retrieve
+            Use the <methodname>getFeed()</methodname> function to retrieve
             a feed from a specified URI.
             This function returns an instance of class specified
             as the second argument to getFeed, which defaults to
@@ -529,7 +529,7 @@ $feed = $gdata->getFeed($query);
             the feed may be broken up into many smaller "pages" of feeds. When
             this occurs, each page will contain a link to the next page in the
             series. This link can be accessed by calling
-            <code>getLink('next')</code>. The following example shows how to
+            <methodname>getLink('next')</methodname>. The following example shows how to
             retrieve the next page of a feed:
         </para>
 
@@ -562,7 +562,7 @@ $feed = $gdata->retrieveAllEntriesForFeed($gdata->getFeed($query));
         <para>
             Keep in mind when calling this function that it may take a long
             time to complete on large feeds. You may need to increase PHP's
-            execution time limit by calling <code>set_time_limit()</code>.
+            execution time limit by calling <methodname>set_time_limit()</methodname>.
         </para>
 
     </sect2>
@@ -625,14 +625,14 @@ foreach ($feed as $entry) {
 
         <para>
             The <classname>Zend_Gdata</classname> object has a function
-            <code>insertEntry()</code> with which you can upload data to save
+            <methodname>insertEntry()</methodname> with which you can upload data to save
             new entries to Google Data services.
         </para>
 
         <para>
             You can use the data model classes for each service to construct
             the appropriate entry to post to Google's services. The
-            <code>insertEntry()</code> function will accept a child of
+            <methodname>insertEntry()</methodname> function will accept a child of
             <classname>Zend_Gdata_App_Entry</classname> as data to post to the service.
             The method returns a child of <classname>Zend_Gdata_App_Entry</classname>
             which represents the state of the entry as it was returned from
@@ -641,7 +641,7 @@ foreach ($feed as $entry) {
 
         <para>
             Alternatively, you could construct the XML structure for an entry
-            as a string and pass the string to the <code>insertEntry()</code>
+            as a string and pass the string to the <methodname>insertEntry()</methodname>
             function.
         </para>
 
@@ -673,10 +673,10 @@ echo 'The <id> of the resulting entry is: ' . $entryResult->id->text;
         <title>Deleting Entries on Google Servers</title>
 
         <para>
-            Option 1: The <classname>Zend_Gdata</classname> object has a function <code>delete()</code>
+            Option 1: The <classname>Zend_Gdata</classname> object has a function <methodname>delete()</methodname>
             with which you can delete entries from Google Data
             services. Pass the edit URL value from
-            a feed entry to the <code>delete()</code> method.
+            a feed entry to the <methodname>delete()</methodname> method.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Gdata_Calendar.xml

@@ -249,7 +249,7 @@ try {
 }
 ]]></programlisting>
         <para>
-            Calling <code>getCalendarListFeed()</code> creates a new instance of
+            Calling <methodname>getCalendarListFeed()</methodname> creates a new instance of
             <classname>Zend_Gdata_Calendar_ListFeed</classname> containing each available calendar as an
             instance of <classname>Zend_Gdata_Calendar_ListEntry</classname>. After retrieving the feed, you
             can use the iterator and accessors contained within the feed to inspect the enclosed
@@ -389,7 +389,7 @@ $query->setStartMax('2006-12-16');
             <title>Retrieving Events By Fulltext Query</title>
             <para>
                 To print out all events which contain a specific word, for example "dogfood", use
-                the <code>setQuery()</code> method when creating the query.
+                the <methodname>setQuery()</methodname> method when creating the query.
             </para>
             <programlisting language="php"><![CDATA[
 $query->setQuery("dogfood");
@@ -399,8 +399,8 @@ $query->setQuery("dogfood");
             <title>Retrieving Individual Events</title>
             <para>
                 Individual events can be retrieved by specifying their event ID as part of the
-                query. Instead of calling <code>getCalendarEventFeed()</code>,
-                <code>getCalendarEventEntry()</code> should be called instead.
+                query. Instead of calling <methodname>getCalendarEventFeed()</methodname>,
+                <methodname>getCalendarEventEntry()</methodname> should be called instead.
             </para>
             <programlisting language="php"><![CDATA[
 $query = $service->newEventQuery();
@@ -417,7 +417,7 @@ try {
 ]]></programlisting>
             <para>
                 In a similar fashion, if the event URL is known, it can be passed directly into
-                <code>getCalendarEntry()</code> to retrieve a specific event. In this case, no
+                <methodname>getCalendarEntry()</methodname> to retrieve a specific event. In this case, no
                 query object is required since the event URL contains all the necessary information
                 to retrieve the event.
             </para>
@@ -533,7 +533,7 @@ try {
             </para>
             <para>
                 Once the event has been populated, it can be uploaded to the calendar server by
-                passing it as an argument to the calendar service's <code>insertEvent()</code>
+                passing it as an argument to the calendar service's <methodname>insertEvent()</methodname>
                 function.
             </para>
             <programlisting language="php"><![CDATA[
@@ -693,12 +693,12 @@ $newEvent = $service->insertEvent($event);
         <para>
             Once an instance of an event has been obtained, the event's attributes can be locally
             modified in the same way as when creating an event. Once all modifications are
-            complete, calling the event's <code>save()</code> method will upload the changes to the
+            complete, calling the event's <methodname>save()</methodname> method will upload the changes to the
             calendar server and return a copy of the event as it was created on the server.
         </para>
         <para>
             In the event another user has modified the event since the local copy was retrieved,
-            <code>save()</code> will fail and the server will return a 409 (Conflict) status code.
+            <methodname>save()</methodname> will fail and the server will return a 409 (Conflict) status code.
             To resolve this a fresh copy of the event must be retrieved from the server before
             attempting to resubmit any modifications.
         </para>
@@ -721,8 +721,8 @@ try {
         <title>Deleting Events</title>
         <para>
             Calendar events can be deleted either by calling the calendar service's
-            <code>delete()</code> method and providing the edit URL of an event or by calling an
-            existing event's own <code>delete()</code> method.
+            <methodname>delete()</methodname> method and providing the edit URL of an event or by calling an
+            existing event's own <methodname>delete()</methodname> method.
         </para>
         <para>
             In either case, the deleted event will still show up on a user's private event feed if

documentation/manual/en/module_specs/Zend_Gdata_Exception.xml

@@ -34,7 +34,7 @@ try {
                     <classname>Zend_Gdata_App_BadMethodCallException</classname>
                     indicates that a method was called for a service
                     that does not support the method. For example,
-                    the CodeSearch service does not support <code>post()</code>.
+                    the CodeSearch service does not support <methodname>post()</methodname>.
                 </para>
             </listitem>
             <listitem>

documentation/manual/en/module_specs/Zend_Gdata_Gapps.xml

@@ -51,7 +51,7 @@
 
             <para>
                 To set the domain for requests made by the service class,
-                either call <code>setDomain()</code> or specify the domain
+                either call <methodname>setDomain()</methodname> or specify the domain
                 when instantiating the service class. For example:
             </para>
 
@@ -68,7 +68,7 @@ $gdata = new Zend_Gdata_Gapps($client, $domain);
             <para>
                 Setting the domain for requests made by query classes is
                 similar to setting it for the service class-either call
-                <code>setDomain()</code> or specify the domain when creating
+                <methodname>setDomain()</methodname> or specify the domain when creating
                 the query. For example:
             </para>
 
@@ -109,7 +109,7 @@ $query = $gdata->newUserQuery($arg);
 
             <para>
                 User accounts can be created by calling the
-                <code>createUser()</code> convenience method:
+                <methodname>createUser()</methodname> convenience method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -119,7 +119,7 @@ $gdata->createUser('foo', 'Random', 'User', '••••••••');
             <para>
                 Users can also be created by instantiating UserEntry,
                 providing a username, given name, family name, and password,
-                then calling <code>insertUser()</code> on a service object to
+                then calling <methodname>insertUser()</methodname> on a service object to
                 upload the entry to the server.
             </para>
 
@@ -147,7 +147,7 @@ $user = $gdata->insertUser($user);
 
             <para>
                 Individual user accounts can be retrieved by calling the
-                <code>retrieveUser()</code> convenience method. If the user is
+                <methodname>retrieveUser()</methodname> convenience method. If the user is
                 not found, <constant>NULL</constant> will be returned.
             </para>
 
@@ -169,7 +169,7 @@ echo 'Has Agreed To Terms: ' .
                 Users can also be retrieved by creating an
                 instance of <classname>Zend_Gdata_Gapps_UserQuery</classname>, setting its username
                 property to equal the username of the user that is to be
-                retrieved, and calling <code>getUserEntry()</code> on a
+                retrieved, and calling <methodname>getUserEntry()</methodname> on a
                 service object with that query.
             </para>
 
@@ -203,7 +203,7 @@ echo 'Has Agreed To Terms: ' .
 
             <para>
                 To retrieve all users in a domain, call the
-                <code>retrieveAllUsers()</code> convenience method.
+                <methodname>retrieveAllUsers()</methodname> convenience method.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -221,7 +221,7 @@ foreach ($feed as $user) {
             </para>
 
             <para>
-                Alternatively, call <code>getUserFeed()</code> with no
+                Alternatively, call <methodname>getUserFeed()</methodname> with no
                 options. Keep in mind that on larger
                 domains this feed may be paged by the server. For more
                 information on paging, see <xref
@@ -245,7 +245,7 @@ foreach ($feed as $user) {
             <para>
                 The easiest way to update a user account is to retrieve the
                 user as described in the previous sections, make any desired
-                changes, then call <code>save()</code> on that user. Any
+                changes, then call <methodname>save()</methodname> on that user. Any
                 changes made will be propagated to the server.
             </para>
 
@@ -310,7 +310,7 @@ $user = $user->save();
                     their user account by instead
                     <emphasis>suspending</emphasis> their user account.
                     Accounts can be suspended or restored by using the
-                    <code>suspendUser()</code> and <code>restoreUser()</code>
+                    <methodname>suspendUser()</methodname> and <methodname>restoreUser()</methodname>
                     convenience methods:
                 </para>
 
@@ -369,7 +369,7 @@ $user = $user->save();
 
             <para>
                 Deleting a user account to which you already hold a UserEntry
-                is a simple as calling <code>delete()</code> on that
+                is a simple as calling <methodname>delete()</methodname> on that
                 entry.
             </para>
 
@@ -380,7 +380,7 @@ $user->delete();
 
             <para>
                 If you do not have access to a UserEntry object for an
-                account, use the <code>deleteUser()</code> convenience method.
+                account, use the <methodname>deleteUser()</methodname> convenience method.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -411,7 +411,7 @@ $gdata->deleteUser('foo');
 
             <para>
                 Nicknames can be created by calling the
-                <code>createNickname()</code> convenience method:
+                <methodname>createNickname()</methodname> convenience method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -421,7 +421,7 @@ $gdata->createNickname('foo', 'bar');
             <para>
                 Nicknames can also be created by instantiating NicknameEntry,
                 providing the nickname with a name and an owner, then calling
-                <code>insertNickname()</code> on a service object to upload
+                <methodname>insertNickname()</methodname> on a service object to upload
                 the entry to the server.
             </para>
 
@@ -439,7 +439,7 @@ $nickname = $gdata->insertNickname($nickname);
 
             <para>
                 Nicknames can be retrieved by calling the
-                <code>retrieveNickname()</code> convenience method. This will
+                <methodname>retrieveNickname()</methodname> convenience method. This will
                 return <constant>NULL</constant> if a user is not found.
             </para>
 
@@ -454,7 +454,7 @@ echo 'Owner: ' . $nickname->login->username . "\n";
                 Individual nicknames can also be retrieved by creating an
                 instance of <classname>Zend_Gdata_Gapps_NicknameQuery</classname>, setting its
                 nickname property to equal the nickname that is to be
-                retrieved, and calling <code>getNicknameEntry()</code> on a
+                retrieved, and calling <methodname>getNicknameEntry()</methodname> on a
                 service object with that query.
             </para>
 
@@ -481,7 +481,7 @@ echo 'Owner: ' . $nickname->login->username . "\n";
 
             <para>
                 To retrieve all nicknames associated with a given user, call
-                the convenience method <code>retrieveNicknames()</code>.
+                the convenience method <methodname>retrieveNicknames()</methodname>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -500,7 +500,7 @@ foreach ($feed as $nickname) {
             <para>
                 Alternatively, create a new <classname>Zend_Gdata_Gapps_NicknameQuery</classname>,
                 set its username property to the desired user, and submit the
-                query by calling <code>getNicknameFeed()</code> on a service
+                query by calling <methodname>getNicknameFeed()</methodname> on a service
                 object.
             </para>
 
@@ -520,7 +520,7 @@ foreach ($feed as $nickname) {
             <title>Retrieving all nicknames in a domain</title>
             <para>
                 To retrieve all nicknames in a feed, simply call the
-                convenience method <code>retrieveAllNicknames()</code>
+                convenience method <methodname>retrieveAllNicknames()</methodname>
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -538,7 +538,7 @@ foreach ($feed as $nickname) {
             </para>
 
             <para>
-                Alternatively, call <code>getNicknameFeed()</code> on a
+                Alternatively, call <methodname>getNicknameFeed()</methodname> on a
                 service object with no arguments.
             </para>
 
@@ -558,7 +558,7 @@ foreach ($feed as $nickname) {
 
             <para>
                 Deleting a nickname to which you already hold a NicknameEntry
-                for is a simple as calling <code>delete()</code> on that
+                for is a simple as calling <methodname>delete()</methodname> on that
                 entry.
             </para>
 
@@ -569,7 +569,7 @@ $nickname->delete();
 
             <para>
                 For nicknames which you do not hold a NicknameEntry for, use
-                the <code>deleteNickname()</code> convenience method.
+                the <methodname>deleteNickname()</methodname> convenience method.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -600,7 +600,7 @@ $gdata->deleteNickname('bar');
 
             <para>
                 Email lists can be created by calling the
-                <code>createEmailList()</code> convenience method:
+                <methodname>createEmailList()</methodname> convenience method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -610,7 +610,7 @@ $gdata->createEmailList('friends');
             <para>
                 Email lists can also be created by instantiating
                 EmailListEntry, providing a name for the list, then calling
-                <code>insertEmailList()</code> on a service object to upload
+                <methodname>insertEmailList()</methodname> on a service object to upload
                 the entry to the server.
             </para>
 
@@ -628,7 +628,7 @@ $list = $gdata->insertEmailList($list);
 
             <para>
                 To retrieve all email lists to which a particular recipient is
-                subscribed, call the <code>retrieveEmailLists()</code>
+                subscribed, call the <methodname>retrieveEmailLists()</methodname>
                 convenience method:
             </para>
 
@@ -648,7 +648,7 @@ foreach ($feed as $list) {
             <para>
                 Alternatively, create a new <classname>Zend_Gdata_Gapps_EmailListQuery</classname>,
                 set its recipient property to the desired email address, and
-                submit the query by calling <code>getEmailListFeed()</code> on
+                submit the query by calling <methodname>getEmailListFeed()</methodname> on
                 a service object.
             </para>
 
@@ -669,7 +669,7 @@ foreach ($feed as $list) {
 
             <para>
                 To retrieve all email lists in a domain, call the convenience
-                method <code>retrieveAllEmailLists()</code>.
+                method <methodname>retrieveAllEmailLists()</methodname>.
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -686,7 +686,7 @@ foreach ($feed as $list) {
             </para>
 
             <para>
-                Alternatively, call <code>getEmailListFeed()</code> on a
+                Alternatively, call <methodname>getEmailListFeed()</methodname> on a
                 service object with no arguments.
             </para>
 
@@ -731,7 +731,7 @@ $gdata->deleteEmailList('friends');
 
             <para>
                 To add a recipient to an email list, simply call the
-                <code>addRecipientToEmailList()</code> convenience method:
+                <methodname>addRecipientToEmailList()</methodname> convenience method:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -744,7 +744,7 @@ $gdata->addRecipientToEmailList('bar@somewhere.com', 'friends');
             <title>Retrieving the list of subscribers to an email list</title>
 
             <para>
-                The convenience method <code>retrieveAllRecipients()</code>
+                The convenience method <methodname>retrieveAllRecipients()</methodname>
                 can be used to retrieve the list of subscribers to an email list:
             </para>
 
@@ -759,7 +759,7 @@ foreach ($feed as $recipient) {
             <para>
                 Alternatively, construct a new EmailListRecipientQuery, set
                 its emailListName property to match the desired email list,
-                and call <code>getEmailListRecipientFeed()</code> on a service
+                and call <methodname>getEmailListRecipientFeed()</methodname> on a service
                 object.
             </para>
 
@@ -785,7 +785,7 @@ foreach ($feed as $recipient) {
 
             <para>
                 To remove a recipient from an email list, call the
-                <code>removeRecipientFromEmailList()</code> convenience
+                <methodname>removeRecipientFromEmailList()</methodname> convenience
                 method:
             </para>
 
@@ -821,10 +821,10 @@ $gdata->removeRecipientFromEmailList('baz@somewhere.com', 'friends');
 
         <para>
             While the complete list of errors received is available within
-            ServiceException as an array by calling <code>getErrors()</code>,
+            ServiceException as an array by calling <methodname>getErrors()</methodname>,
             often it is convenient to know if one specific error occurred. For
             these cases the presence of an error can be determined by calling
-            <code>hasError()</code>.
+            <methodname>hasError()</methodname>.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Gdata_Gbase.xml

@@ -206,7 +206,7 @@ $service = new Zend_Gdata_Gbase();
             <sect4 id="zend.gdata.gbase.retrieve.query.customeritems">
                 <title>Query Customer Items Feed</title>
                 <para>
-                    To execute a query against the customer items feed, invoke <code>newItemQuery()</code> and <code>getGbaseItemFeed()</code> methods:
+                    To execute a query against the customer items feed, invoke <methodname>newItemQuery()</methodname> and <methodname>getGbaseItemFeed()</methodname> methods:
                 </para>
                 <programlisting language="php"><![CDATA[
 $service = new Zend_Gdata_Gbase($client);
@@ -224,7 +224,7 @@ $feed = $service->getGbaseItemFeed($query);
             <sect4 id="zend.gdata.gbase.retrieve.query.snippets">
                 <title>Query Snippets Feed</title>
                 <para>
-                    To execute a query against the public snippets feed, invoke <code>newSnippetQuery()</code> and <code>getGbaseSnippetFeed()</code> methods:
+                    To execute a query against the public snippets feed, invoke <methodname>newSnippetQuery()</methodname> and <methodname>getGbaseSnippetFeed()</methodname> methods:
                 </para>
                 <programlisting language="php"><![CDATA[
 $service = new Zend_Gdata_Gbase();
@@ -246,7 +246,7 @@ $feed = $service->getGbaseSnippetFeed($query);
                 Google Base items can contain item-specific attributes such as <code>&lt;g:main_ingredient&gt;</code> and <code>&lt;g:weight&gt;</code>.
             </para>
             <para>
-                To iterate through all attributes of a given item, invoke <code>getGbaseAttributes()</code> and iterate through the results:
+                To iterate through all attributes of a given item, invoke <methodname>getGbaseAttributes()</methodname> and iterate through the results:
             </para>
             <programlisting language="php"><![CDATA[
 foreach ($feed->entries as $entry) {
@@ -283,7 +283,7 @@ foreach ($feed->entries as $entry) {
         <sect3 id="zend.gdata.gbase.crud.insert">
             <title>Insert an Item</title>
             <para>
-                Items can be added by using the <code>insertGbaseItem()</code> method for the Base service:
+                Items can be added by using the <methodname>insertGbaseItem()</methodname> method for the Base service:
             </para>
             <programlisting language="php"><![CDATA[
 $service = new Zend_Gdata_Gbase($client);
@@ -368,20 +368,20 @@ $entry->save($dryRun);
 // $service->updateGbaseItem($entry, $dryRun);
 ]]></programlisting>
             <para>
-                After making the changes, either invoke <code>save($dryRun)</code> method on the <classname>Zend_Gdata_Gbase_ItemEntry</classname> object or call <code>updateGbaseItem($entry, $dryRun)</code> method on the <classname>Zend_Gdata_Gbase</classname> object to save the changes.
+                After making the changes, either invoke <methodname>save($dryRun)</methodname> method on the <classname>Zend_Gdata_Gbase_ItemEntry</classname> object or call <methodname>updateGbaseItem($entry, $dryRun)</methodname> method on the <classname>Zend_Gdata_Gbase</classname> object to save the changes.
             </para>
         </sect3>
         <sect3 id="zend.gdata.gbase.crud.delete">
             <title>Delete an Item</title>
             <para>
-                You can remove an item by calling <code>deleteGbaseItem()</code> method:
+                You can remove an item by calling <methodname>deleteGbaseItem()</methodname> method:
             </para>
             <programlisting language="php"><![CDATA[
 $dryRun = false;
 $service->deleteGbaseItem($entry, $dryRun);
 ]]></programlisting>
             <para>
-                Alternatively, you can invoke <code>delete()</code> on the <classname>Zend_Gdata_Gbase_ItemEntry</classname> object:
+                Alternatively, you can invoke <methodname>delete()</methodname> on the <classname>Zend_Gdata_Gbase_ItemEntry</classname> object:
             </para>
             <programlisting language="php"><![CDATA[
 $dryRun = false;

documentation/manual/en/module_specs/Zend_Gdata_Health.xml

@@ -244,7 +244,7 @@ $healthService = new Zend_Gdata_Health($client,
                 <title>Query The Feed</title>
                 <para>
                     To execute a query against the profile feed, invoke a new instance of an <classname>Zend_Gdata_Health_Query</classname> and
-                    call the service's <code>getHealthProfileFeed()</code> method:
+                    call the service's <methodname>getHealthProfileFeed()</methodname> method:
                 </para>
                 <programlisting language="php"><![CDATA[
 $healthService = new Zend_Gdata_Health($client);
@@ -259,9 +259,9 @@ $query->setCategory("medication");
 
 $profileFeed = $healthService->getHealthProfileFeed($query);
 ]]></programlisting>
-                <para>Using <code>setDigest("true")</code> returns all of user's CCR data in a single Atom <code>&lt;entry&gt;</code>.</para>
-                <para>The <code>setCategory()</code> helper can be passed an additional parameter to return more specific CCR
-                information. For example, to return just the medication Lipitor, use <code>setCategory("medication", "Lipitor")</code>. The same
+                <para>Using <methodname>setDigest("true")</methodname> returns all of user's CCR data in a single Atom <code>&lt;entry&gt;</code>.</para>
+                <para>The <methodname>setCategory()</methodname> helper can be passed an additional parameter to return more specific CCR
+                information. For example, to return just the medication Lipitor, use <methodname>setCategory("medication", "Lipitor")</methodname>. The same
                 methodology can be applied to other categories such as conditions, allergies, lab results, etc.</para>
                 <para>
                     A full list of supported query parameters is available in the <ulink url="http://code.google.com/apis/health/reference.html#Parameters">query parameters section</ulink>
@@ -276,7 +276,7 @@ $profileFeed = $healthService->getHealthProfileFeed($query);
                 consolidate all of the CCR elements (that match your query) into a single Atom <code>&lt;entry&gt;</code>.
             </para>
             <para>
-                To retrieve the full CCR information from an entry, make a call to the <classname>Zend_Gdata_Health_ProfileEntry</classname> class's <code>getCcr()</code> method.
+                To retrieve the full CCR information from an entry, make a call to the <classname>Zend_Gdata_Health_ProfileEntry</classname> class's <methodname>getCcr()</methodname> method.
                 That returns a <classname>Zend_Gdata_Health_Extension_CCR</classname>:
             </para>
             <programlisting language="php"><![CDATA[
@@ -294,8 +294,8 @@ foreach ($entries as $entry) {
 }
 ]]></programlisting>
             <para>
-              Here, the <code>getCcr()</code> method is used in conjunction with a magic helper to drill down and extract just the
-              medication data from the entry's CCR. The formentioned magic helper takes the form <code>getCATEGORYNAME()</code>, where
+              Here, the <methodname>getCcr()</methodname> method is used in conjunction with a magic helper to drill down and extract just the
+              medication data from the entry's CCR. The formentioned magic helper takes the form <methodname>getCATEGORYNAME()</methodname>, where
               <code>CATEGORYNAME</code> is a supported Google Health category. See the
               <ulink url="http://code.google.com/apis/health/reference.html#CatQueries">Google Health reference Guide</ulink> for the possible categories.
             </para>
@@ -332,7 +332,7 @@ foreach ($conditions as $cond) {
         <sect3 id="zend.gdata.health.profilelist.query">
             <title>Query The Feed</title>
             <para>
-                To execute a query against the profile list feed, call the service's <code>getHealthProfileListFeed()</code> method:
+                To execute a query against the profile list feed, call the service's <methodname>getHealthProfileListFeed()</methodname> method:
             </para>
             <programlisting language="php"><![CDATA[
 $client = Zend_Gdata_ClientLogin::getHttpClient('user@gmail.com',
@@ -349,7 +349,7 @@ foreach ($entries as $entry) {
 }
 ]]></programlisting>
             <para>
-              Once you've determined which profile to use, call <code>setProfileID()</code> with the profileID as an argument.
+              Once you've determined which profile to use, call <methodname>setProfileID()</methodname> with the profileID as an argument.
               This will restrict subsequent API requests to be against that particular profile:
             </para>
             <programlisting language="php"><![CDATA[
@@ -375,7 +375,7 @@ echo '<p><b>Queried profileID</b>: ' . $profileID . '</p>';
             <sect3 id="zend.gdata.health.notice.send">
                 <title>Sending a notice</title>
           <para>
-              Notices can be sent by using the <code>sendHealthNotice()</code> method for the Health service:
+              Notices can be sent by using the <methodname>sendHealthNotice()</methodname> method for the Health service:
           </para>
           <programlisting language="php"><![CDATA[
 $healthService = new Zend_Gdata_Health($client);

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

@@ -166,7 +166,7 @@ $response = $client->request();
             connection using the following PHP command:
         </para>
         <para>
-            <code>fsockopen('tls://www.example.com', 443)</code>
+            <methodname>fsockopen('tls://www.example.com', 443)</methodname>
         </para>
 
         <sect3 id="zend.http.client.adapters.socket.streamcontext">
@@ -398,7 +398,7 @@ $client = new Zend_Http_Client($uri, $config);
             the Socket Adapter and it also accepts the same configuration parameters
             as the Socket and Proxy adapters. You can also change the cURL options by either specifying
             the 'curloptions' key in the constructor of the adapter or by calling
-            <code>setCurlOption($name, $value)</code>. The <code>$name</code> key
+            <methodname>setCurlOption($name, $value)</methodname>. The <code>$name</code> key
             corresponds to the CURL_* constants of the cURL extension. You can
             get access to the Curl handle by calling <code>$adapter->getHandle();</code>
         </para>

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

@@ -374,8 +374,8 @@ $cookie->match('http://www.example.com/', true, time() + (3 * 3600));
             fetch cookies from a CookieJar object. Your Zend_Http_Client 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: <code>getCookie()</code>,
-            <code>getAllCookies()</code>, and <code>getMatchingCookies()</code>.
+            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.
         </para>

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

@@ -153,7 +153,7 @@ if (isset($_POST['xmlToken'])) {
             Once the adapter has been configured, you can then use the standard
             <classname>Zend_Auth</classname> facilities to validate the provided
             information card token and authenticate the user by examining the
-            identity provided by the <code>getIdentity()</code> method.
+            identity provided by the <methodname>getIdentity()</methodname> method.
         </para>
     </sect2>
 
@@ -211,7 +211,7 @@ if (isset($_POST['xmlToken'])) {
             case with the <classname>Zend_Auth_Adapter_InfoCard</classname>, we create an
             instance of <classname>Zend_InfoCard</classname> and then set one or more SSL
             certificate public/private key pairs used by the web server. Once
-            configured, we can use the <code>process()</code> method to process
+            configured, we can use the <methodname>process()</methodname> method to process
             the information card and return the results.
         </para>
     </sect2>
@@ -232,11 +232,11 @@ if (isset($_POST['xmlToken'])) {
             <classname>Zend_InfoCard_Claims::isValid()</classname> method. Claims
             themselves can either be retrieved by simply accessing the
             identifier desired (i.e. <code>givenname</code>) as a property of
-            the object or through the <code>getClaim()</code> method.
+            the object or through the <methodname>getClaim()</methodname> method.
         </para>
 
         <para>
-            In most cases you will never need to use the <code>getClaim()</code>
+            In most cases you will never need to use the <methodname>getClaim()</methodname>
             method. However, if your <code>requiredClaims</code> mandate that
             you request claims from multiple different sources/namespaces then
             you will need to extract them explicitly using this method (simply
@@ -251,7 +251,7 @@ if (isset($_POST['xmlToken'])) {
             As part of the validation process, it is the developer's responsibility to
             examine the issuing source of the claims contained within the
             information card and to decide if that source is a trusted source of
-            information. To do so, the <code>getIssuer()</code> method is
+            information. To do so, the <methodname>getIssuer()</methodname> method is
             provided within the <classname>Zend_InfoCard_Claims</classname> object which
             returns the URI of the issuer of the information card claims.
         </para>
@@ -269,7 +269,7 @@ if (isset($_POST['xmlToken'])) {
             claim as part of the <code>requiredClaims</code> of the request. If
             this claim is requested then the <classname>Zend_InfoCard_Claims</classname>
             object will provide a unique identifier for the specific card that
-            was submitted by calling the <code>getCardID()</code> method.
+            was submitted by calling the <methodname>getCardID()</methodname> method.
         </para>
 
         <para>
@@ -350,9 +350,9 @@ public function submitinfocardAction()
             To prevent this, one must implement the
             <classname>Zend_InfoCard_Adapter_Interface</classname> and set an
             instance of this interface prior to calling either the
-            <code>process()</code> (standalone) or <code>authenticate()</code>
+            <methodname>process()</methodname> (standalone) or <methodname>authenticate()</methodname>
             method as a <classname>Zend_Auth</classname> adapter. To set this interface,
-            the <code>setAdapter()</code> method should be used. In the example below,
+            the <methodname>setAdapter()</methodname> method should be used. In the example below,
             we set a <classname>Zend_InfoCard</classname> adapter and use it in our
             application:
         </para>

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

@@ -53,7 +53,7 @@ $phpNative = Zend_Json::decode($encodedValue, Zend_Json::TYPE_OBJECT);
         <para>
             If you are encoding PHP objects by default the encoding mechanism
             can only access public properties of these objects. When a method
-            <code>toJson()</code> is implemented on an object to encode, <classname>Zend_Json</classname>
+            <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
             of its internal state.
         </para>
@@ -65,7 +65,7 @@ $phpNative = Zend_Json::decode($encodedValue, Zend_Json::TYPE_OBJECT);
         <para>
             Zend_Json has two different modes depending if ext/json is enabled in
             your PHP installation or not. If ext/json is installed by default
-            <code>json_encode()</code> and <code>json_decode()</code> functions
+            <methodname>json_encode()</methodname> and <methodname>json_decode()</methodname> functions
             are used for encoding and decoding JSON. If ext/json is not installed
             a Zend Framework implementation in PHP code is used for en-/decoding.
             This is considerably slower than using the php extension, but behaves
@@ -90,7 +90,7 @@ Zend_Json::$useBuiltinEncoderDecoder = true:
             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
-            objects with valid javascript callbacks. This works for both <code>json_encode()</code>
+            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

@@ -213,37 +213,37 @@ $server->handle();
             </para>
 
             <itemizedlist>
-                <listitem><para><code>addFunction($function)</code>: Specify a
+                <listitem><para><methodname>addFunction($function)</methodname>: Specify a
                         userland function to attach to the server.</para></listitem>
-                <listitem><para><code>setClass($class)</code>: Specify a class
+                <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>
                 <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><code>handle($request = false)</code>: Handle a
+                <listitem><para><methodname>handle($request = false)</methodname>: Handle a
                         JSON-RPC request; optionally, pass a
                         <classname>Zend_Json_Server_Request</classname> object to utilize
                         (creates one by default).</para></listitem>
-                <listitem><para><code>getFunctions()</code>: Return a list of
+                <listitem><para><methodname>getFunctions()</methodname>: Return a list of
                         all attached methods.</para></listitem>
                 <listitem><para><code>setRequest(Zend_Json_Server_Request
                         $request)</code>: Specify a request object for the
                         server to utilize.</para></listitem>
-                <listitem><para><code>getRequest()</code>: Retrieve the request
+                <listitem><para><methodname>getRequest()</methodname>: Retrieve the request
                         object used by the server.</para></listitem>
                 <listitem><para><code>setResponse(Zend_Json_Server_Response
                         $response)</code>: Set the response object for the
                         server to utilize.</para></listitem>
-                <listitem><para><code>getResponse()</code>: Retrieve the
+                <listitem><para><methodname>getResponse()</methodname>: Retrieve the
                         response object used by the server.</para></listitem>
-                <listitem><para><code>setAutoEmitResponse($flag)</code>:
+                <listitem><para><methodname>setAutoEmitResponse($flag)</methodname>:
                         Indicate whether the server should automatically emit
                         the response and all headers; by default, this is
                         true.</para></listitem>
-                <listitem><para><code>autoEmitResponse()</code>: Determine if
+                <listitem><para><methodname>autoEmitResponse()</methodname>: Determine if
                         auto-emission of the response is enabled.</para></listitem>
-                <listitem><para><code>getServiceMap()</code>: Retrieve the
+                <listitem><para><methodname>getServiceMap()</methodname>: Retrieve the
                         service map description in the form of a
                         <classname>Zend_Json_Server_Smd</classname> object</para></listitem>
             </itemizedlist>
@@ -258,7 +258,7 @@ $server->handle();
                 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 <code>toJson()</code>
+                and can render itself as JSON via the <methodname>toJson()</methodname>
                 method.
             </para>
 
@@ -267,47 +267,47 @@ $server->handle();
             </para>
 
             <itemizedlist>
-                <listitem><para><code>setOptions(array $options)</code>: Specify
+                <listitem><para><methodname>setOptions(array $options)</methodname>: Specify
                         object configuration. <code>$options</code> may contain
                         keys matching any 'set' method:
-                        <code>setParams()</code>, <code>setMethod()</code>,
-                        <code>setId()</code>, and
-                        <code>setVersion()</code>.</para></listitem>
-                <listitem><para><code>addParam($value, $key = null)</code>: Add
+                        <methodname>setParams()</methodname>, <methodname>setMethod()</methodname>,
+                        <methodname>setId()</methodname>, and
+                        <methodname>setVersion()</methodname>.</para></listitem>
+                <listitem><para><methodname>addParam($value, $key = null)</methodname>: Add
                         a parameter to use with the method call. Parameters can be
                         just the values, or can optionally include the parameter
                         name.</para></listitem>
-                <listitem><para><code>addParams(array $params)</code>: Add
+                <listitem><para><methodname>addParams(array $params)</methodname>: Add
                         multiple parameters at once; proxies to
-                        <code>addParam()</code></para></listitem>
-                <listitem><para><code>setParams(array $params)</code>: Set all
+                        <methodname>addParam()</methodname></para></listitem>
+                <listitem><para><methodname>setParams(array $params)</methodname>: Set all
                         parameters at once; overwrites any existing
                         parameters.</para></listitem>
-                <listitem><para><code>getParam($index)</code>: Retrieve a
+                <listitem><para><methodname>getParam($index)</methodname>: Retrieve a
                         parameter by position or name.</para></listitem>
-                <listitem><para><code>getParams()</code>: Retrieve all
+                <listitem><para><methodname>getParams()</methodname>: Retrieve all
                         parameters at once.</para></listitem>
-                <listitem><para><code>setMethod($name)</code>: Set the method to
+                <listitem><para><methodname>setMethod($name)</methodname>: Set the method to
                         call.</para></listitem>
-                <listitem><para><code>getMethod()</code>: Retrieve the method
+                <listitem><para><methodname>getMethod()</methodname>: Retrieve the method
                         that will be called.</para></listitem>
-                <listitem><para><code>isMethodError()</code>: Determine whether
+                <listitem><para><methodname>isMethodError()</methodname>: Determine whether
                         or not the request is malformed and would result in an
                         error.</para></listitem>
-                <listitem><para><code>setId($name)</code>: Set the request
+                <listitem><para><methodname>setId($name)</methodname>: Set the request
                         identifier (used by the client to match requests to
                         responses).</para></listitem>
-                <listitem><para><code>getId()</code>: Retrieve the request
+                <listitem><para><methodname>getId()</methodname>: Retrieve the request
                         identifier.</para></listitem>
-                <listitem><para><code>setVersion($version)</code>: Set the
+                <listitem><para><methodname>setVersion($version)</methodname>: Set the
                         JSON-RPC specification version the request conforms to.
                         May be either '1.0' or '2.0'.</para></listitem>
-                <listitem><para><code>getVersion()</code>: Retrieve the JSON-RPC
+                <listitem><para><methodname>getVersion()</methodname>: Retrieve the JSON-RPC
                         specification version used by the
                         request.</para></listitem>
-                <listitem><para><code>loadJson($json)</code>: Load the request
+                <listitem><para><methodname>loadJson($json)</methodname>: Load the request
                         object from a JSON string.</para></listitem>
-                <listitem><para><code>toJson()</code>: Render the request as
+                <listitem><para><methodname>toJson()</methodname>: Render the request as
                         a JSON string.</para></listitem>
             </itemizedlist>
 
@@ -315,7 +315,7 @@ $server->handle();
                 An HTTP 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 <code>getRawJson()</code> method.
+                access to the raw JSON via the <methodname>getRawJson()</methodname> method.
             </para>
         </sect3>
 
@@ -336,32 +336,32 @@ $server->handle();
             </para>
 
             <itemizedlist>
-                <listitem><para><code>setResult($value)</code>: Set the response
+                <listitem><para><methodname>setResult($value)</methodname>: Set the response
                     result.</para></listitem>
-                <listitem><para><code>getResult()</code>: Retrieve the response
+                <listitem><para><methodname>getResult()</methodname>: Retrieve the response
                     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>
-                <listitem><para><code>getError()</code>: Retrieve the error
+                <listitem><para><methodname>getError()</methodname>: Retrieve the error
                     object, if any.</para></listitem>
-                <listitem><para><code>isError()</code>: Whether or not the
+                <listitem><para><methodname>isError()</methodname>: Whether or not the
                     response is an error response.</para></listitem>
-                <listitem><para><code>setId($name)</code>: Set the request
+                <listitem><para><methodname>setId($name)</methodname>: Set the request
                     identifier (so the client may match the response with
                     the original request).</para></listitem>
-                <listitem><para><code>getId()</code>: Retrieve the request
+                <listitem><para><methodname>getId()</methodname>: Retrieve the request
                     identifier.</para></listitem>
-                <listitem><para><code>setVersion($version)</code>: Set the
+                <listitem><para><methodname>setVersion($version)</methodname>: Set the
                     JSON-RPC version the response conforms to.</para></listitem>
-                <listitem><para><code>getVersion()</code>: Retrieve the JSON-RPC
+                <listitem><para><methodname>getVersion()</methodname>: Retrieve the JSON-RPC
                     version the response conforms to.</para></listitem>
-                <listitem><para><code>toJson()</code>: Serialize the response to
+                <listitem><para><methodname>toJson()</methodname>: Serialize the response to
                     JSON. If the response is an error response, serializes the
                     error object.</para></listitem>
-                <listitem><para><code>setServiceMap($serviceMap)</code>: Set the
+                <listitem><para><methodname>setServiceMap($serviceMap)</methodname>: Set the
                     service map object for the response.</para></listitem>
-                <listitem><para><code>getServiceMap()</code>: Retrieve the
+                <listitem><para><methodname>getServiceMap()</methodname>: Retrieve the
                     service map object, if any.</para></listitem>
             </itemizedlist>
 
@@ -397,24 +397,24 @@ $server->handle();
             </para>
 
             <itemizedlist>
-                <listitem><para><code>setCode($code)</code>: Set the error code;
+                <listitem><para><methodname>setCode($code)</methodname>: Set the error code;
                     if the code is not in the accepted XML-RPC error code range,
                     -32000 will be assigned.</para></listitem>
-                <listitem><para><code>getCode()</code>: Retrieve the current
+                <listitem><para><methodname>getCode()</methodname>: Retrieve the current
                     error code.</para></listitem>
-                <listitem><para><code>setMessage($message)</code>: Set the error
+                <listitem><para><methodname>setMessage($message)</methodname>: Set the error
                     message.</para></listitem>
-                <listitem><para><code>getMessage()</code>: Retrieve the current
+                <listitem><para><methodname>getMessage()</methodname>: Retrieve the current
                     error message.</para></listitem>
-                <listitem><para><code>setData($data)</code>: Set auxiliary data
+                <listitem><para><methodname>setData($data)</methodname>: Set auxiliary data
                     further qualifying the error, such as a
                     backtrace.</para></listitem>
-                <listitem><para><code>getData()</code>: Retrieve any current
+                <listitem><para><methodname>getData()</methodname>: Retrieve any current
                     auxiliary error data.</para></listitem>
-                <listitem><para><code>toArray()</code>: Cast the error to an
+                <listitem><para><methodname>toArray()</methodname>: Cast the error to an
                     array. The array will contain the keys 'code', 'message',
                     and 'data'.</para></listitem>
-                <listitem><para><code>toJson()</code>: Cast the error to a
+                <listitem><para><methodname>toJson()</methodname>: Cast the error to a
                     JSON-RPC error representation.</para></listitem>
             </itemizedlist>
         </sect3>
@@ -474,71 +474,71 @@ $server->handle();
             </para>
 
             <itemizedlist>
-                <listitem><para><code>setOptions(array $options)</code>: Setup
+                <listitem><para><methodname>setOptions(array $options)</methodname>: Setup
                         an SMD object from an array of options. All mutators
                         (methods beginning with 'set') can be used as
                         keys.</para></listitem>
-                <listitem><para><code>setTransport($transport)</code>: Set the
+                <listitem><para><methodname>setTransport($transport)</methodname>: Set the
                         transport used to access the service; only POST is
                         currently supported.</para></listitem>
-                <listitem><para><code>getTransport()</code>: Get the current
+                <listitem><para><methodname>getTransport()</methodname>: Get the current
                         service transport.</para></listitem>
-                <listitem><para><code>setEnvelope($envelopeType)</code>: Set the
+                <listitem><para><methodname>setEnvelope($envelopeType)</methodname>: Set the
                         request envelope that should be used to access the
                         service. Currently, supports the constants
                         <classname>Zend_Json_Server_Smd::ENV_JSONRPC_1</classname> and
                         <classname>Zend_Json_Server_Smd::ENV_JSONRPC_2</classname>.</para></listitem>
-                <listitem><para><code>getEnvelope()</code>: Get the current
+                <listitem><para><methodname>getEnvelope()</methodname>: Get the current
                         request envelope.</para></listitem>
-                <listitem><para><code>setContentType($type)</code>: Set the
+                <listitem><para><methodname>setContentType($type)</methodname>: Set the
                         content type requests should use (by default, this is
                         'application/json').</para></listitem>
-                <listitem><para><code>getContentType()</code>: Get the current
+                <listitem><para><methodname>getContentType()</methodname>: Get the current
                         content type for requests to the service.</para></listitem>
-                <listitem><para><code>setTarget($target)</code>: Set the URL
+                <listitem><para><methodname>setTarget($target)</methodname>: Set the URL
                         endpoint for the service.</para></listitem>
-                <listitem><para><code>getTarget()</code>: Get the URL endpoint
+                <listitem><para><methodname>getTarget()</methodname>: Get the URL endpoint
                         for the service.</para></listitem>
-                <listitem><para><code>setId($id)</code>: Typically, this is the
+                <listitem><para><methodname>setId($id)</methodname>: Typically, this is the
                         URL endpoint of the service (same as the
                         target).</para></listitem>
-                <listitem><para><code>getId()</code>: Retrieve the service ID
+                <listitem><para><methodname>getId()</methodname>: Retrieve the service ID
                         (typically the URL endpoint of the
                         service).</para></listitem>
-                <listitem><para><code>setDescription($description)</code>: Set a
+                <listitem><para><methodname>setDescription($description)</methodname>: Set a
                         service description (typically narrative information
                         describing the purpose of the service).</para></listitem>
-                <listitem><para><code>getDescription()</code>: Get the service
+                <listitem><para><methodname>getDescription()</methodname>: Get the service
                         description.</para></listitem>
-                <listitem><para><code>setDojoCompatible($flag)</code>: Set a
+                <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
                         will be formatted to comply with the format that Dojo's
                         JSON-RPC client expects.</para></listitem>
-                <listitem><para><code>isDojoCompatible()</code>: Returns the
+                <listitem><para><methodname>isDojoCompatible()</methodname>: Returns the
                         value of the Dojo compatibility flag (false, by
                         default).</para></listitem>
-                <listitem><para><code>addService($service)</code>: Add a service
+                <listitem><para><methodname>addService($service)</methodname>: Add a service
                         to the map. May be an array of information to pass to
                         the constructor of
                         <classname>Zend_Json_Server_Smd_Service</classname>, or an
                         instance of that class.</para></listitem>
-                <listitem><para><code>addServices(array $services)</code>: Add
+                <listitem><para><methodname>addServices(array $services)</methodname>: Add
                         multiple services at once.</para></listitem>
-                <listitem><para><code>setServices(array $services)</code>: Add
+                <listitem><para><methodname>setServices(array $services)</methodname>: Add
                         multiple services at once, overwriting any previously
                         set services.</para></listitem>
-                <listitem><para><code>getService($name)</code>: Get a service by
+                <listitem><para><methodname>getService($name)</methodname>: Get a service by
                         its name.</para></listitem>
-                <listitem><para><code>getServices()</code>: Get all attached
+                <listitem><para><methodname>getServices()</methodname>: Get all attached
                         services.</para></listitem>
-                <listitem><para><code>removeService($name)</code>: Remove a
+                <listitem><para><methodname>removeService($name)</methodname>: Remove a
                         service from the map.</para></listitem>
-                <listitem><para><code>toArray()</code>: Cast the service map to
+                <listitem><para><methodname>toArray()</methodname>: Cast the service map to
                         an array.</para></listitem>
-                <listitem><para><code>toDojoArray()</code>: Cast the service map
+                <listitem><para><methodname>toDojoArray()</methodname>: Cast the service map
                         to an array compatible with Dojo Toolkit.</para></listitem>
-                <listitem><para><code>toJson()</code>: Cast the service map to a
+                <listitem><para><methodname>toJson()</methodname>: Cast the service map to a
                         JSON representation.</para></listitem>
             </itemizedlist>
 
@@ -548,29 +548,29 @@ $server->handle();
             </para>
 
             <itemizedlist>
-                <listitem><para><code>setOptions(array $options)</code>: Set
+                <listitem><para><methodname>setOptions(array $options)</methodname>: Set
                         object state from an array. Any mutator (methods
                         beginning with 'set') may be used as a key and set via
                         this method.</para></listitem>
-                <listitem><para><code>setName($name)</code>: Set the service
+                <listitem><para><methodname>setName($name)</methodname>: Set the service
                         name (typically, the function or method name).</para></listitem>
-                <listitem><para><code>getName()</code>: Retrieve the service
+                <listitem><para><methodname>getName()</methodname>: Retrieve the service
                         name.</para></listitem>
-                <listitem><para><code>setTransport($transport)</code>: Set the
+                <listitem><para><methodname>setTransport($transport)</methodname>: Set the
                         service transport (currently, only transports supported
                         by <classname>Zend_Json_Server_Smd</classname> are allowed).</para></listitem>
-                <listitem><para><code>getTransport()</code>: Retrieve the
+                <listitem><para><methodname>getTransport()</methodname>: Retrieve the
                         current transport.</para></listitem>
-                <listitem><para><code>setTarget($target)</code>: Set the URL
+                <listitem><para><methodname>setTarget($target)</methodname>: Set the URL
                         endpoint of the service (typically, this will be the
                         same as the overall SMD to which the service is
                         attached).</para></listitem>
-                <listitem><para><code>getTarget()</code>: Get the URL endpoint
+                <listitem><para><methodname>getTarget()</methodname>: Get the URL endpoint
                         of the service.</para></listitem>
-                <listitem><para><code>setEnvelope($envelopeType)</code>: Set the
+                <listitem><para><methodname>setEnvelope($envelopeType)</methodname>: Set the
                         service envelope (currently, only envelopes supported
                         by <classname>Zend_Json_Server_Smd</classname> are allowed).</para></listitem>
-                <listitem><para><code>getEnvelope()</code>: Retrieve the service
+                <listitem><para><methodname>getEnvelope()</methodname>: Retrieve the service
                         envelope type.</para></listitem>
                 <listitem><para><code>addParam($type, array $options = array(),
                             $order = null)</code>: Add a parameter to the
@@ -588,24 +588,24 @@ $server->handle();
                             describing the parameter</para></listitem>
                     </itemizedlist>
                 </listitem>
-                <listitem><para><code>addParams(array $params)</code>: Add
+                <listitem><para><methodname>addParams(array $params)</methodname>: Add
                     several parameters at once; each param should be an assoc
                     array containing minimally the key 'type' describing the
                     parameter type, and optionally the key 'order'; any other
                     keys will be passed as <code>$options</code> to
-                    <code>addOption()</code>.</para></listitem>
-                <listitem><para><code>setParams(array $params)</code>: Set many
+                    <methodname>addOption()</methodname>.</para></listitem>
+                <listitem><para><methodname>setParams(array $params)</methodname>: Set many
                     parameters at once, overwriting any existing
                     parameters.</para></listitem>
-                <listitem><para><code>getParams()</code>: Retrieve all currently
+                <listitem><para><methodname>getParams()</methodname>: Retrieve all currently
                     set parameters.</para></listitem>
-                <listitem><para><code>setReturn($type)</code>: Set the return
+                <listitem><para><methodname>setReturn($type)</methodname>: Set the return
                     value type of the service.</para></listitem>
-                <listitem><para><code>getReturn()</code>: Get the return value
+                <listitem><para><methodname>getReturn()</methodname>: Get the return value
                     type of the service.</para></listitem>
-                <listitem><para><code>toArray()</code>: Cast the service to an
+                <listitem><para><methodname>toArray()</methodname>: Cast the service to an
                     array.</para></listitem>
-                <listitem><para><code>toJson()</code>: Cast the service to a
+                <listitem><para><methodname>toJson()</methodname>: Cast the service to a
                     JSON representation.</para></listitem>
             </itemizedlist>
         </sect3>

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

@@ -51,8 +51,8 @@
             <classname>Zend_View_Interface</classname> or extending
             <classname>Zend_View_Abstract</classname> for rendering your layout script.
             Simply pass in your custom view object as a parameter to the
-            constructor/<code>startMvc()</code>, or set it using the
-            <code>setView()</code> accessor:
+            constructor/<methodname>startMvc()</methodname>, or set it using the
+            <methodname>setView()</methodname> accessor:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -79,7 +79,7 @@ $layout->setView($view);
                 implementation that does not support these helpers, you will
                 need to find a way to get the layout variables to the view. This
                 can be done by either extending the <classname>Zend_Layout</classname>
-                object and altering the <code>render()</code> method to pass
+                object and altering the <methodname>render()</methodname> method to pass
                 variables to the view, or creating your own plugin class that
                 passes them prior to rendering the layout.
             </para>
@@ -108,7 +108,7 @@ $layoutVars   = $placeholders->placeholder('Zend_Layout')->getArrayCopy();
             default plugin will be suitable, but should you desire to write
             your own, you can specify the name of the plugin class to load by
             passing the <code>pluginClass</code> option to the
-            <code>startMvc()</code> method.
+            <methodname>startMvc()</methodname> method.
         </para>
 
         <para>
@@ -141,7 +141,7 @@ $layoutVars   = $placeholders->placeholder('Zend_Layout')->getArrayCopy();
             an action helper class extending
             <classname>Zend_Controller_Action_Helper_Abstract</classname> and pass the
             class name as the <code>helperClass</code> option to the
-            <code>startMvc()</code> method. Details of the implementation are
+            <methodname>startMvc()</methodname> method. Details of the implementation are
             up to you.
         </para>
     </sect2>
@@ -248,8 +248,8 @@ $layout->setInflector($inflector);
                 to specify an absolute path for a layout view script, or know
                 that the mechanism you will be using for specifying the layout
                 script does not need inflection. Simply use the
-                <code>enableInflection()</code> and
-                <code>disableInflection()</code> methods.
+                <methodname>enableInflection()</methodname> and
+                <methodname>disableInflection()</methodname> methods.
             </para>
         </note>
     </sect2>

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

@@ -7,9 +7,9 @@
         <classname>Zend_Layout</classname> has a variety of configuration options. These
         may be set by calling the appropriate accessors, passing an array or
         <classname>Zend_Config</classname> object to the constructor or
-        <code>startMvc()</code>, passing an array of options to
-        <code>setOptions()</code>, or passing a <classname>Zend_Config</classname> object
-        to <code>setConfig()</code>.
+        <methodname>startMvc()</methodname>, passing an array of options to
+        <methodname>setOptions()</methodname>, or passing a <classname>Zend_Config</classname> object
+        to <methodname>setConfig()</methodname>.
     </para>
 
     <itemizedlist>
@@ -18,20 +18,20 @@
                 current inflector to resolve the name provided to the
                 appropriate layout view script. By default, this value is
                 'layout' and resolves to 'layout.phtml'. Accessors
-                are <code>setLayout()</code> and <code>getLayout()</code>.
+                are <methodname>setLayout()</methodname> and <methodname>getLayout()</methodname>.
         </para></listitem>
 
         <listitem><para>
                 <emphasis>layoutPath</emphasis>: the base path to layout view
-                scripts. Accessors are <code>setLayoutPath()</code> and
-                <code>getLayoutPath()</code>.
+                scripts. Accessors are <methodname>setLayoutPath()</methodname> and
+                <methodname>getLayoutPath()</methodname>.
         </para></listitem>
 
         <listitem><para>
                 <emphasis>contentKey</emphasis>: the layout variable used for
                 default content (when used with the MVC). Default value is
-                'content'. Accessors are <code>setContentKey()</code> and
-                <code>getContentKey()</code>.
+                'content'. Accessors are <methodname>setContentKey()</methodname> and
+                <methodname>getContentKey()</methodname>.
         </para></listitem>
 
         <listitem><para>
@@ -40,8 +40,8 @@
                 layout will not be rendered (this is to prevent double-rendering
                 of the layout when the <link linkend="zend.controller.plugins.standard.errorhandler">ErrorHandler
                 plugin</link> is in use). By default, the flat is true.
-                Accessors are <code>setMvcSuccessfulActionOnly()</code> and
-                <code>getMvcSuccessfulActionOnly()</code>.
+                Accessors are <methodname>setMvcSuccessfulActionOnly()</methodname> and
+                <methodname>getMvcSuccessfulActionOnly()</methodname>.
         </para></listitem>
 
         <listitem><para>
@@ -50,8 +50,8 @@
                 attempt to use the view object registered with <link
                     linkend="zend.controller.actionhelpers.viewrenderer">the
                     ViewRenderer</link> if no view object has been passed to it
-                explicitly. Accessors are <code>setView()</code> and
-                <code>getView()</code>.
+                explicitly. Accessors are <methodname>setView()</methodname> and
+                <methodname>getView()</methodname>.
         </para></listitem>
 
         <listitem><para>
@@ -59,8 +59,8 @@
                 when using <classname>Zend_Layout</classname> with the MVC components. By
                 default, this is
                 <classname>Zend_Layout_Controller_Action_Helper_Layout</classname>.
-                Accessors are <code>setHelperClass()</code> and
-                <code>getHelperClass()</code>.
+                Accessors are <methodname>setHelperClass()</methodname> and
+                <methodname>getHelperClass()</methodname>.
         </para></listitem>
 
         <listitem><para>
@@ -68,8 +68,8 @@
                 class to use when using <classname>Zend_Layout</classname> with the MVC
                 components. By default, this is
                 <classname>Zend_Layout_Controller_Plugin_Layout</classname>. Accessors
-                are <code>setPluginClass()</code> and
-                <code>getPluginClass()</code>.
+                are <methodname>setPluginClass()</methodname> and
+                <methodname>getPluginClass()</methodname>.
         </para></listitem>
 
         <listitem><para>
@@ -77,8 +77,8 @@
                 resolving layout names to layout view script paths; see <link
                     linkend="zend.layout.advanced.inflector">the
                     <classname>Zend_Layout</classname> inflector documentation for more
-                    details</link>. Accessors are <code>setInflector()</code>
-                and <code>getInflector()</code>.
+                    details</link>. Accessors are <methodname>setInflector()</methodname>
+                and <methodname>getInflector()</methodname>.
         </para></listitem>
     </itemizedlist>
 
@@ -88,7 +88,7 @@
         <para>
             In order for the <code>helperClass</code> and
             <code>pluginClass</code> settings to have effect, they must be
-            passed in as options to <code>startMvc()</code>; if set later, they
+            passed in as options to <methodname>startMvc()</methodname>; if set later, they
             have no affect.
         </para>
     </note>
@@ -123,7 +123,7 @@ $config = new Zend_Config_Ini('/path/to/layout.ini', 'layout');
             <title>Passing options to the constructor or startMvc()</title>
 
             <para>
-                Both the constructor and the <code>startMvc()</code> static
+                Both the constructor and the <methodname>startMvc()</methodname> static
                 method can accept either an array of options or a
                 <classname>Zend_Config</classname> object with options in order to
                 configure the <classname>Zend_Layout</classname> instance.
@@ -167,7 +167,7 @@ $layout = Zend_Layout::startMvc($config);
             <para>
                 Sometimes you need to configure the <classname>Zend_Layout</classname>
                 object after it has already been instantiated;
-                <code>setOptions()</code> and <code>setConfig()</code> give you
+                <methodname>setOptions()</methodname> and <methodname>setConfig()</methodname> give you
                 a quick and easy way to do so:
             </para>
 
@@ -183,7 +183,7 @@ $layout->setConfig($options);
                 Note, however, that certain options, such as
                 <code>pluginClass</code> and <code>helperClass</code>, will have
                 no affect when passed using this method; they need to be passed
-                to the constructor or <code>startMvc()</code> method.
+                to the constructor or <methodname>startMvc()</methodname> method.
             </para>
         </example>
 

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

@@ -121,7 +121,7 @@ Zend_Layout::startMvc();
 ]]></programlisting>
 
         <para>
-            <code>startMvc()</code> can take an optional array of options or
+            <methodname>startMvc()</methodname> can take an optional array of options or
             <classname>Zend_Config</classname> object to customize the instance; these
             options are detailed in <xref linkend="zend.layout.options" />.
         </para>
@@ -162,7 +162,7 @@ class FooController extends Zend_Controller_Action
 
         <para>
             At any time, you can fetch the <classname>Zend_Layout</classname> instance
-            registered with the MVC via the <code>getMvcInstance()</code> static
+            registered with the MVC via the <methodname>getMvcInstance()</methodname> static
             method:
         </para>
 
@@ -182,11 +182,11 @@ $layout = Zend_Layout::getMvcInstance();
 
         <para>
             As an example, let's say your code first hits
-            <code>FooController::indexAction()</code>, which renders some
+            <methodname>FooController::indexAction()</methodname>, which renders some
             content to the default response segment, and then forwards to
-            <code>NavController::menuAction()</code>, which renders content to
+            <methodname>NavController::menuAction()</methodname>, which renders content to
             the 'nav' response segment. Finally, you forward to
-            <code>CommentController::fetchAction()</code> and fetch some
+            <methodname>CommentController::fetchAction()</methodname> and fetch some
             comments, but render those to the default response segment as well
             (which appends content to that segment). Your view script could then
             render each separately:

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Attribute.xml

@@ -30,13 +30,13 @@
         <varlistentry>
             <term><code>object</code> and <code>array</code></term>
             <listitem><para>The value will be converted to a string by using
-            <code>serialize()</code>.</para></listitem>
+            <methodname>serialize()</methodname>.</para></listitem>
         </varlistentry>
 
         <varlistentry>
             <term><code>resource</code></term>
             <listitem><para>If a <code>stream</code> resource is given, the data will be
-            fetched by calling <code>stream_get_contents()</code>.</para></listitem>
+            fetched by calling <methodname>stream_get_contents()</methodname>.</para></listitem>
         </varlistentry>
 
         <varlistentry>
@@ -232,7 +232,7 @@
                         default) <code>$value</code> will be appended to the attribute.
                         <code>$value</code> can be an integer value or an array of
                         integers. Date-time-conversion according to
-                        <code>Zend_Ldap_Attribute::convertToLdapDateTimeValue()</code> will
+                        <methodname>Zend_Ldap_Attribute::convertToLdapDateTimeValue()</methodname> will
                         take place.
                     </entry>
                 </row>
@@ -252,7 +252,7 @@
                         value at the given index will be returned. If the index is out of
                         bounds, <code>null</code> will be returned. Date-time-conversion
                         according to
-                        <code>Zend_Ldap_Attribute::convertFromLdapDateTimeValue()</code>
+                        <methodname>Zend_Ldap_Attribute::convertFromLdapDateTimeValue()</methodname>
                         will take place.
                     </entry>
                 </row>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Dn.xml

@@ -29,7 +29,7 @@
 
     <para>
         The default case-folding is <code>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</code> and
-        can be set with <code>Zend_Ldap_Dn::setDefaultCaseFold()</code>. Each instance of
+        can be set with <methodname>Zend_Ldap_Dn::setDefaultCaseFold()</methodname>. Each instance of
         <classname>Zend_Ldap_Dn</classname> can have its own case-folding-setting. If the
         <code>$caseFold</code> parameter is ommitted in method-calls it defaults to the
         instance's case-folding setting.
@@ -38,10 +38,10 @@
     <para>
         The class implements <code>ArrayAccess</code> to allow indexer-access to the
         different parts of the DN. The <code>ArrayAccess</code>-methods proxy to
-        <code>Zend_Ldap_Dn::get($offset, 1, null)</code> for <code>offsetGet(integer
-        $offset)</code>, to <code>Zend_Ldap_Dn::set($offset, $value)</code> for
-        <code>offsetSet()</code> and to <code>Zend_Ldap_Dn::remove($offset, 1)</code> for
-        <code>offsetUnset()</code>. <code>offsetExists()</code> simply checks if the index
+        <methodname>Zend_Ldap_Dn::get($offset, 1, null)</methodname> for <code>offsetGet(integer
+        $offset)</code>, to <methodname>Zend_Ldap_Dn::set($offset, $value)</methodname> for
+        <methodname>offsetSet()</methodname> and to <methodname>Zend_Ldap_Dn::remove($offset, 1)</methodname> for
+        <methodname>offsetUnset()</methodname>. <methodname>offsetExists()</methodname> simply checks if the index
         is within the bounds.
     </para>
 
@@ -64,7 +64,7 @@
                     <entry>
                         Creates a <classname>Zend_Ldap_Dn</classname> instance from an array
                         or a string. The array must conform to the array structure detailed
-                        under <code>Zend_Ldap_Dn::implodeDn()</code>.
+                        under <methodname>Zend_Ldap_Dn::implodeDn()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -85,7 +85,7 @@
                     <entry>
                         Creates a <classname>Zend_Ldap_Dn</classname> instance from an array.
                         The array must conform to the array structure detailed under
-                        <code>Zend_Ldap_Dn::implodeDn()</code>.
+                        <methodname>Zend_Ldap_Dn::implodeDn()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -180,7 +180,7 @@
                         Sets the case-folding option to the current DN instance. If
                         <code>$caseFold</code> is null the default case-folding setting
                         (<code>Zend_Ldap_Dn::ATTR_CASEFOLD_NONE</code> by default or set
-                        via <code>Zend_Ldap_Dn::setDefaultCaseFold()</code> will be set for
+                        via <methodname>Zend_Ldap_Dn::setDefaultCaseFold()</methodname> will be set for
                         the current instance.
                     </entry>
                 </row>
@@ -196,7 +196,7 @@
                     <entry><code>string __toString()</code></entry>
                     <entry>
                         Returns DN as a string - proxies to
-                        <code>Zend_Ldap_Dn::toString(null)</code>.
+                        <methodname>Zend_Ldap_Dn::toString(null)</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -224,7 +224,7 @@
                     </entry>
                     <entry>
                         Undoes the conversion done by
-                        <code>Zend_Ldap_Dn::escapeValue()</code>.
+                        <methodname>Zend_Ldap_Dn::escapeValue()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -279,7 +279,7 @@ array("dc" => "org")
                     </entry>
                     <entry>
                         Implodes an array in the form delivered by
-                        <code>Zend_Ldap_Dn::explodeDn()</code> to a DN string.
+                        <methodname>Zend_Ldap_Dn::explodeDn()</methodname> to a DN string.
                         <code>$separator</code> defaults to <code>','</code> but some LDAP
                         servers also understand <code>';'</code>. <code>$dnArray</code>
                         must of type

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Filter.xml

@@ -132,7 +132,7 @@
                         parameters will be escaped and substituted into <code>$mask</code>
                         by using
                         <ulink url="http://php.net/sprintf">
-                        <code>sprintf()</code></ulink>
+                        <methodname>sprintf()</methodname></ulink>
                     </entry>
                 </row>
                 <row>
@@ -173,7 +173,7 @@
                     <entry><code>string __toString()</code></entry>
                     <entry>
                         Returns a string representation of the filter. Proxies to
-                        <code>Zend_Ldap_Filter::toString()</code>.
+                        <methodname>Zend_Ldap_Filter::toString()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -223,7 +223,7 @@
                     </entry>
                     <entry>
                         Undoes the conversion done by
-                        <code>Zend_Ldap_Filter::escapeValue()</code>. Converts any
+                        <methodname>Zend_Ldap_Filter::escapeValue()</methodname>. Converts any
                         sequences of a backslash followed by two hex digits into the
                         corresponding character.
                     </entry>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-RootDse.xml

@@ -7,14 +7,14 @@
 
     <para>
         <classname>Zend_Ldap_Node_RootDse</classname> includes the magic propery accessors
-        <code>__get()</code> and <code>__isset()</code> to access the attributes by their
-        name. They proxy to <code>Zend_Ldap_Node_RootDse::getAttribute()</code> and
-        <code>Zend_Ldap_Node_RootDse::existsAttribute()</code> respectively.
-        <code>__set()</code> and <code>__unset()</code> are also implemented but they throw
+        <methodname>__get()</methodname> and <methodname>__isset()</methodname> to access the attributes by their
+        name. They proxy to <methodname>Zend_Ldap_Node_RootDse::getAttribute()</methodname> and
+        <methodname>Zend_Ldap_Node_RootDse::existsAttribute()</methodname> respectively.
+        <methodname>__set()</methodname> and <methodname>__unset()</methodname> are also implemented but they throw
         a <code>BadMethodCallException</code> as modifications are not allowed on RootDSE
         nodes. Furthermore the class implements <code>ArrayAccess</code> for
-        array-style-access to the attributes. <code>offsetSet()</code> and
-        <code>offsetUnset()</code> also throw a <code>BadMethodCallException</code> due ro
+        array-style-access to the attributes. <methodname>offsetSet()</methodname> and
+        <methodname>offsetUnset()</methodname> also throw a <code>BadMethodCallException</code> due ro
         obvious reasons.
     </para>
 
@@ -57,14 +57,14 @@
                     <entry><code>string toString()</code></entry>
                     <entry>
                         Returns the DN of the current node - proxies to
-                        <code>Zend_Ldap_Dn::getDnString()</code>.
+                        <methodname>Zend_Ldap_Dn::getDnString()</methodname>.
                     </entry>
                 </row>
                 <row>
                     <entry><code>string __toString()</code></entry>
                     <entry>
                         Casts to string representation - proxies to
-                        <code>Zend_Ldap_Dn::toString()</code>.
+                        <methodname>Zend_Ldap_Dn::toString()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -77,7 +77,7 @@
                         <code>$includeSystemAttributes</code> is <code>false</code>
                         (defaults to <code>true</code>) the system specific attributes are
                         stripped from the array. Unlike
-                        <code>Zend_Ldap_Node_RootDse::getAttributes()</code> the resulting
+                        <methodname>Zend_Ldap_Node_RootDse::getAttributes()</methodname> the resulting
                         array contains the DN with key <code>'dn'</code>.
                     </entry>
                 </row>
@@ -88,7 +88,7 @@
                     </entry>
                     <entry>
                         Returns a <acronym>JSON</acronym> representation of the current node using
-                        <code>Zend_Ldap_Node_RootDse::toArray()</code>.
+                        <methodname>Zend_Ldap_Node_RootDse::toArray()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -142,7 +142,7 @@
                     </entry>
                     <entry>
                         Gets a <acronym>LDAP</acronym> attribute. Data conversion is applied using
-                        <code>Zend_Ldap_Attribute::getAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::getAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -165,7 +165,7 @@
                     <entry>
                         Gets a <acronym>LDAP</acronym> date/time attribute. Data conversion is applied
                         using
-                        <code>Zend_Ldap_Attribute::getDateTimeAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::getDateTimeAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node.xml

@@ -5,12 +5,12 @@
 
     <para>
         <classname>Zend_Ldap_Node</classname> includes the magic propery accessors
-        <code>__set()</code>, <code>__get()</code>, <code>__unset()</code> and
-        <code>__isset()</code> to access the attributes by their name. They proxy to
-        <code>Zend_Ldap_Node::setAttribute()</code>,
-        <code>Zend_Ldap_Node::getAttribute()</code>,
-        <code>Zend_Ldap_Node::deleteAttribute()</code> and
-        <code>Zend_Ldap_Node::existsAttribute()</code> respectively. Furthermore the class
+        <methodname>__set()</methodname>, <methodname>__get()</methodname>, <methodname>__unset()</methodname> and
+        <methodname>__isset()</methodname> to access the attributes by their name. They proxy to
+        <methodname>Zend_Ldap_Node::setAttribute()</methodname>,
+        <methodname>Zend_Ldap_Node::getAttribute()</methodname>,
+        <methodname>Zend_Ldap_Node::deleteAttribute()</methodname> and
+        <methodname>Zend_Ldap_Node::existsAttribute()</methodname> respectively. Furthermore the class
         implements <code>ArrayAccess</code> for array-style-access to the attributes.
         <classname>Zend_Ldap_Node</classname> also implements <code>Iterator</code> and
         <code>RecursiveIterato</code> to allow for recursive tree-traversal.
@@ -103,7 +103,7 @@
                     <entry>
                         Tells if the node is consiedered as new (not present on the
                         server). Please note, that this doesn't tell if the node is really
-                        present on the server. Use <code>Zend_Ldap_Node::exists()</code> to
+                        present on the server. Use <methodname>Zend_Ldap_Node::exists()</methodname> to
                         see if a node is already there.
                     </entry>
                 </row>
@@ -111,22 +111,22 @@
                     <entry><code>boolean willBeDeleted()</code></entry>
                     <entry>
                         Tells if this node is going to be deleted once
-                        <code>Zend_Ldap_Node::update()</code> is called.
+                        <methodname>Zend_Ldap_Node::update()</methodname> is called.
                     </entry>
                 </row>
                 <row>
                     <entry><code>Zend_Ldap_Node delete()</code></entry>
                     <entry>
                         Marks this node as to be deleted. Node will be deleted on
-                        calling <code>Zend_Ldap_Node::update()</code> if
-                        <code>Zend_Ldap_Node::willBeDeleted()</code> is true.
+                        calling <methodname>Zend_Ldap_Node::update()</methodname> if
+                        <methodname>Zend_Ldap_Node::willBeDeleted()</methodname> is true.
                     </entry>
                 </row>
                 <row>
                     <entry><code>boolean willBeMoved()</code></entry>
                     <entry>
                         Tells if this node is going to be moved once
-                        <code>Zend_Ldap_Node::update()</code> is called.
+                        <methodname>Zend_Ldap_Node::update()</methodname> is called.
                     </entry>
                 </row>
                 <row>
@@ -189,7 +189,7 @@
                     </entry>
                     <entry>
                         Sets the new DN for this node effectively moving the node
-                        once <code>Zend_Ldap_Node::update()</code> is called.
+                        once <methodname>Zend_Ldap_Node::update()</methodname> is called.
                     </entry>
                 </row>
                 <row>
@@ -199,7 +199,7 @@
                     </entry>
                     <entry>
                         This is an alias for
-                        <code>Zend_Ldap_Node::setDn()</code>.
+                        <methodname>Zend_Ldap_Node::setDn()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -209,7 +209,7 @@
                     </entry>
                     <entry>
                         This is an alias for
-                        <code>Zend_Ldap_Node::setDn()</code>.
+                        <methodname>Zend_Ldap_Node::setDn()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -243,8 +243,8 @@
                     <entry>
                         Gets changed node data. The array contains all changed
                         attributes. This format can be used in
-                        <code>Zend_Ldap::add()</code> and
-                        <code>Zend_Ldap::update()</code>.
+                        <methodname>Zend_Ldap::add()</methodname> and
+                        <methodname>Zend_Ldap::update()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -255,14 +255,14 @@
                     <entry><code>string toString()</code></entry>
                     <entry>
                         Returns the DN of the current node - proxies to
-                        <code>Zend_Ldap_Dn::getDnString()</code>.
+                        <methodname>Zend_Ldap_Dn::getDnString()</methodname>.
                     </entry>
                 </row>
                 <row>
                     <entry><code>string __toString()</code></entry>
                     <entry>
                         Casts to string representation - proxies to
-                        <code>Zend_Ldap_Dn::toString()</code>.
+                        <methodname>Zend_Ldap_Dn::toString()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -275,7 +275,7 @@
                         <code>$includeSystemAttributes</code> is <code>false</code>
                         (defaults to <code>true</code>) the system specific attributes are
                         stripped from the array. Unlike
-                        <code>Zend_Ldap_Node::getAttributes()</code> the resulting array
+                        <methodname>Zend_Ldap_Node::getAttributes()</methodname> the resulting array
                         contains the DN with key <code>'dn'</code>.
                     </entry>
                 </row>
@@ -286,7 +286,7 @@
                     </entry>
                     <entry>
                         Returns a <acronym>JSON</acronym> representation of the current node using
-                        <code>Zend_Ldap_Node::toArray()</code>.
+                        <methodname>Zend_Ldap_Node::toArray()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -340,7 +340,7 @@
                     </entry>
                     <entry>
                         Gets a <acronym>LDAP</acronym> attribute. Data conversion is applied using
-                        <code>Zend_Ldap_Attribute::getAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::getAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -362,7 +362,7 @@
                     </entry>
                     <entry>
                         Sets a <acronym>LDAP</acronym> attribute. Data conversion is applied using
-                        <code>Zend_Ldap_Attribute::setAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::setAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -372,7 +372,7 @@
                     </entry>
                     <entry>
                         Appends to a <acronym>LDAP</acronym> attribute. Data conversion is applied
-                        using <code>Zend_Ldap_Attribute::setAttribute()</code>.
+                        using <methodname>Zend_Ldap_Attribute::setAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -383,7 +383,7 @@
                     <entry>
                         Gets a <acronym>LDAP</acronym> date/time attribute. Data conversion is applied
                         using
-                        <code>Zend_Ldap_Attribute::getDateTimeAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::getDateTimeAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -394,7 +394,7 @@
                     <entry>
                         Sets a <acronym>LDAP</acronym> date/time attribute. Data conversion is applied
                         using
-                        <code>Zend_Ldap_Attribute::setDateTimeAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::setDateTimeAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -405,7 +405,7 @@
                     <entry>
                         Appends to a <acronym>LDAP</acronym> date/time attribute. Data conversion is
                         applied using
-                        <code>Zend_Ldap_Attribute::setDateTimeAttribute()</code>.
+                        <methodname>Zend_Ldap_Attribute::setDateTimeAttribute()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -465,7 +465,7 @@
                     <entry>
                         Searches the nodes's subtree with the given
                         <code>$filter</code> and the given search parameters. See
-                        <code>Zend_Ldap::search()</code> for details on the parameters
+                        <methodname>Zend_Ldap::search()</methodname> for details on the parameters
                         <code>$scope</code> and <code>$sort</code>.
                     </entry>
                 </row>
@@ -477,7 +477,7 @@
                     <entry>
                         Count the nodes's subtree items matching the given
                         <code>$filter</code> and the given search scope. See
-                        <code>Zend_Ldap::search()</code> for details on the
+                        <methodname>Zend_Ldap::search()</methodname> for details on the
                         <code>$scope</code> parameter.
                     </entry>
                 </row>
@@ -493,7 +493,7 @@
                     </entry>
                     <entry>
                         Searches the nodes's children matching the given
-                        <code>$filter</code>. See <code>Zend_Ldap::search()</code> for
+                        <code>$filter</code>. See <methodname>Zend_Ldap::search()</methodname> for
                         details on the <code>$sort</code> parameter.
                     </entry>
                 </row>

documentation/manual/en/module_specs/Zend_Ldap-API-Ldap.xml

@@ -27,7 +27,7 @@
                     <entry>
                         Escapes a value to be used in a <acronym>LDAP</acronym> filter according to RFC
                         2254. This method is <emphasis>deprecated</emphasis>, please use
-                        <code>Zend_Ldap_Filter_Abstract::escapeValue()</code>
+                        <methodname>Zend_Ldap_Filter_Abstract::escapeValue()</methodname>
                         instead.
                     </entry>
                 </row>
@@ -40,17 +40,17 @@
                         <code>$keys</code> or <code>$keys</code> and <code>$vals</code> are
                         given, these arrays will be filled with the appropriate DN keys and
                         values. This method is <emphasis>deprecated</emphasis>, please use
-                        <code>Zend_Ldap_Dn::checkDn()</code> instead.
+                        <methodname>Zend_Ldap_Dn::checkDn()</methodname> instead.
                     </entry>
                 </row>
                 <row>
-                    <entry><code>__construct($options)</code></entry>
+                    <entry><methodname>__construct($options)</methodname></entry>
                     <entry>
                         Constructor. The <code>$options</code> parameter is optional
                         and can be set to an array or a <classname>Zend_Config</classname> instance.
                         If no options are provided at instantiation, the connection
                         parameters must be passed to the instance using
-                        <code>Zend_Ldap::setOptions()</code>. The allowed options are
+                        <methodname>Zend_Ldap::setOptions()</methodname>. The allowed options are
                         specified in <link
                             linkend="zend.ldap.api.configuration.table">Zend_Ldap
                             Options</link>
@@ -132,7 +132,7 @@
                         Connects the Zend_Ldap instance to the given <acronym>LDAP</acronym> server.
                         All parameters are optional and will be taken from the LDAP
                         connection and binding parameters passed to the instance via the
-                        construtor or via <code>Zend_Ldap::setOptions()</code> when set to
+                        construtor or via <methodname>Zend_Ldap::setOptions()</methodname> when set to
                         <code>null</code>.
                     </entry>
                 </row>
@@ -213,9 +213,9 @@
                                         returned entries. To include all possible attributes (ACL
                                         restrictions can disallow certain attribute to be retrieved
                                         by a given user) pass either an empty array
-                                        <code>array()</code> or <code>array('*')</code> to the
+                                        <methodname>array()</methodname> or <methodname>array('*')</methodname> to the
                                         method. On some <acronym>LDAP</acronym> servers you can retrieve special
-                                        internal attributes by passing <code>array('*', '+')</code>
+                                        internal attributes by passing <methodname>array('*', '+')</methodname>
                                         to the method.
                                     </para>
                                 </listitem>
@@ -229,7 +229,7 @@
                                         If given the result collection will be sorted
                                         after the attribute <code>$sort</code>. Results can only be
                                         sorted after one single attribute as this parameter uses
-                                        the ext/ldap function <code>ldap_sort()</code>.
+                                        the ext/ldap function <methodname>ldap_sort()</methodname>.
                                     </para>
                                 </listitem>
                             </varlistentry>
@@ -260,7 +260,7 @@
                     </entry>
                     <entry>
                         Counts the elements returned by the given search parameters.
-                        See <code>Zend_Ldap::search()</code> for a detailed description of
+                        See <methodname>Zend_Ldap::search()</methodname> for a detailed description of
                         the method parameters.
                     </entry>
                 </row>
@@ -290,8 +290,8 @@
                     <entry>
                         Performs a search operation and returns the result as an PHP
                         array. This is essentially the same method as
-                        <code>Zend_Ldap::search()</code> except for the return type. See
-                        <code>Zend_Ldap::search()</code> for a detailed description of the
+                        <methodname>Zend_Ldap::search()</methodname> except for the return type. See
+                        <methodname>Zend_Ldap::search()</methodname> for a detailed description of the
                         method parameters.
                     </entry>
                 </row>
@@ -304,7 +304,7 @@
                         Retrieves the <acronym>LDAP</acronym> entry identified by <code>$dn</code> with
                         the attributes specified in <code>$attributes</code>. If
                         <code>$attributes</code> is ommitted, all attributes
-                        (<code>array()</code>) are included in the result.
+                        (<methodname>array()</methodname>) are included in the result.
                         <code>$throwOnNotFound</code> is <code>false</code> by default, so
                         the method will return <code>null</code> if the specified entry
                         cannot be found. If set to <code>true</code>, a
@@ -391,7 +391,7 @@
                         Moving will fail if <code>$recursively</code> is <code>false</code>
                         and the entry <code>$from</code> is not a leaf entry.
                         <code>$alwaysEmulate</code> controls whether the ext/ldap function
-                        <code>ldap_rename()</code> should be used if available. This can
+                        <methodname>ldap_rename()</methodname> should be used if available. This can
                         only work for leaf entries and for servers and for ext/ldap
                         supporting this function. Set to <code>true</code> to always use an
                         emulated rename operation.
@@ -414,7 +414,7 @@
                     </entry>
                     <entry>
                         This is an alias for
-                        <code>Zend_Ldap::rename()</code>.
+                        <methodname>Zend_Ldap::rename()</methodname>.
                     </entry>
                 </row>
                 <row>
@@ -431,7 +431,7 @@
                         descendants will be moved. Moving will fail if
                         <code>$recursively</code> is <code>false</code> and the entry
                         <code>$from</code> is not a leaf entry. <code>$alwaysEmulate</code>
-                        controls whether the ext/ldap function <code>ldap_rename()</code>
+                        controls whether the ext/ldap function <methodname>ldap_rename()</methodname>
                         should be used if available. This can only work for leaf entries
                         and for servers and for ext/ldap supporting this function. Set to
                         <code>true</code> to always use an emulated rename
@@ -503,9 +503,9 @@
 
         <para>
             <classname>Zend_Ldap_Collection</classname> implements <code>Iterator</code> to
-            allow for item traversal using <code>foreach()</code> and
-            <code>Countable</code> to be able to respond to <code>count()</code>. With its
-            protected <code>_createEntry()</code> method it provides a simple extension
+            allow for item traversal using <methodname>foreach()</methodname> and
+            <code>Countable</code> to be able to respond to <methodname>count()</methodname>. With its
+            protected <methodname>_createEntry()</methodname> method it provides a simple extension
             point for developers needing custom result objects.
         </para>
 

documentation/manual/en/module_specs/Zend_Ldap-API.xml

@@ -127,7 +127,7 @@
                         <entry>
                             The <acronym>LDAP</acronym> search filter used to search for accounts.
                             This string is a <ulink
-                                url="http://php.net/sprintf"><code>sprintf()</code></ulink>
+                                url="http://php.net/sprintf"><methodname>sprintf()</methodname></ulink>
                             style expression that must contain one '<emphasis>%s</emphasis>' to
                             accommodate the username. The default value is
                             '<emphasis>(&amp;(objectClass=user)(sAMAccountName=%s))</emphasis>'

documentation/manual/en/module_specs/Zend_Loader-Autoloader-Resource.xml

@@ -76,7 +76,7 @@ $resourceLoader = new Zend_Loader_Autoloader_Resource(array(
         <para>
             Now that we have setup the base resource autoloader, we can add some
             components to it to autoload. This is done using the
-            <code>addResourceType()</code> method, which accepts three
+            <methodname>addResourceType()</methodname> method, which accepts three
             arguments: a resource "type", used internally as a reference name;
             the subdirectory path underneath the base path in which these
             resources live; and the component namespace to append to the base
@@ -91,7 +91,7 @@ $resourceLoader->addResourceType('acl', 'acls/', 'Acl')
 
         <para>
             Alternately, you could pass these as an array to
-            <code>addResourceTypes()</code>; the following is equivalent to the
+            <methodname>addResourceTypes()</methodname>; the following is equivalent to the
             above:
         </para>
 

documentation/manual/en/module_specs/Zend_Loader-Autoloader.xml

@@ -40,7 +40,7 @@
         <para>
             The first time an instance of the autoloader is retrieved, it
             registers itself with <code>spl_autoload</code>. You retrieve an
-            instance using the <code>getInstance()</code> method:
+            instance using the <methodname>getInstance()</methodname> method:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -51,7 +51,7 @@ $autoloader = Zend_Loader_Autoloader::getInstance();
             By default, the autoloader is configured to match the "Zend_" and
             "ZendX_" namespaces. If you have your own library code that uses
             your own namespace, you may register it with the autoloader using
-            the <code>registerNamespace()</code> method. For instance, if your
+            the <methodname>registerNamespace()</methodname> method. For instance, if your
             library code is prefixed with "My_", you could do so as follows:
         </para>
 
@@ -84,7 +84,7 @@ $autoloader->registerNamespace('My_');
             As an example, you may want to utilize one or more eZcomponents
             components with your Zend Framework application. To use its
             autoloading capabilities, push it onto the autoloader stack using
-            <code>pushAutoloader()</code>:
+            <methodname>pushAutoloader()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -97,7 +97,7 @@ $autoloader->pushAutoloader(array('ezcBase', 'autoload'), 'ezc');
         </para>
 
         <para>
-            You can use the <code>unshiftAutoloader()</code> method to add the
+            You can use the <methodname>unshiftAutoloader()</methodname> method to add the
             autoloader to the beginning of the autoloader chain.
         </para>
 
@@ -107,7 +107,7 @@ $autoloader->pushAutoloader(array('ezcBase', 'autoload'), 'ezc');
             <classname>Zend_Loader::loadClass()</classname>. Most of the time, this is
             exactly what you want. However, there may be cases where you want to
             suppress them. You can do this using
-            <code>suppressNotFoundWarnings()</code>:
+            <methodname>suppressNotFoundWarnings()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -119,7 +119,7 @@ $autoloader->suppressNotFoundWarnings(true);
             namespace. For instance, PEAR libraries do not share a common
             namespace, making specifying individual namespaces difficult when
             many PEAR components are in use. You can use the
-            <code>setFallbackAutoloader()</code> method to have the autoloader
+            <methodname>setFallbackAutoloader()</methodname> method to have the autoloader
             act as a catch-all:
         </para>
 
@@ -146,8 +146,8 @@ interface Zend_Loader_Autoloader_Interface
 
         <para>
             When using this interface, you can simply pass a class instance to
-            <classname>Zend_Loader_Autoloader</classname>'s <code>pushAutoloader()</code>
-            and <code>unshiftAutoloader()</code> methods:
+            <classname>Zend_Loader_Autoloader</classname>'s <methodname>pushAutoloader()</methodname>
+            and <methodname>unshiftAutoloader()</methodname> methods:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -179,7 +179,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                 </thead>
                 <tbody>
                     <row>
-                        <entry><code>getInstance()</code></entry>
+                        <entry><methodname>getInstance()</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry>N/A</entry>
                         <entry><para>
@@ -191,7 +191,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>resetInstance()</code></entry>
+                        <entry><methodname>resetInstance()</methodname></entry>
                         <entry><code>void</code></entry>
                         <entry>N/A</entry>
                         <entry><para>
@@ -203,7 +203,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>autoload($class)</code></entry>
+                        <entry><methodname>autoload($class)</methodname></entry>
                         <entry><code>string|false</code></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -218,7 +218,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>setDefaultAutoloader($callback)</code></entry>
+                        <entry><methodname>setDefaultAutoloader($callback)</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -232,7 +232,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>getDefaultAutoloader()</code></entry>
+                        <entry><methodname>getDefaultAutoloader()</methodname></entry>
                         <entry><code>callback</code></entry>
                         <entry>N/A</entry>
                         <entry><para>
@@ -243,7 +243,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>setAutoloaders(array $autoloaders)</code></entry>
+                        <entry><methodname>setAutoloaders(array $autoloaders)</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -258,7 +258,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>getAutoloaders()</code></entry>
+                        <entry><methodname>getAutoloaders()</methodname></entry>
                         <entry><type>Array</type></entry>
                         <entry>N/A</entry>
                         <entry><para>
@@ -267,7 +267,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>getNamespaceAutoloaders($namespace)</code></entry>
+                        <entry><methodname>getNamespaceAutoloaders($namespace)</methodname></entry>
                         <entry><type>Array</type></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -281,7 +281,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>registerNamespace($namespace)</code></entry>
+                        <entry><methodname>registerNamespace($namespace)</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -297,7 +297,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>unregisterNamespace($namespace)</code></entry>
+                        <entry><methodname>unregisterNamespace($namespace)</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -313,7 +313,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>getRegisteredNamespace()</code></entry>
+                        <entry><methodname>getRegisteredNamespace()</methodname></entry>
                         <entry><type>Array</type></entry>
                         <entry>N/A</entry>
                         <entry><para>
@@ -323,7 +323,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>suppressNotFoundWarnings($flag = null)</code></entry>
+                        <entry><methodname>suppressNotFoundWarnings($flag = null)</methodname></entry>
                         <entry><code>boolean|Zend_Loader_Autoloader</code></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -343,7 +343,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>setFallbackAutoloader($flag)</code></entry>
+                        <entry><methodname>setFallbackAutoloader($flag)</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -358,7 +358,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>isFallbackAutoloader()</code></entry>
+                        <entry><methodname>isFallbackAutoloader()</methodname></entry>
                         <entry><type>Boolean</type></entry>
                         <entry>N/A</entry>
                         <entry><para>
@@ -370,7 +370,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>getClassAutoloaders($class)</code></entry>
+                        <entry><methodname>getClassAutoloaders($class)</methodname></entry>
                         <entry><type>Array</type></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -386,7 +386,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>unshiftAutoloader($callback, $namespace = '')</code></entry>
+                        <entry><methodname>unshiftAutoloader($callback, $namespace = '')</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -409,7 +409,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>pushAutoloader($callback, $namespace = '')</code></entry>
+                        <entry><methodname>pushAutoloader($callback, $namespace = '')</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>
@@ -432,7 +432,7 @@ $autoloader->pushAutoloader($foo, 'Foo_');
                     </row>
 
                     <row>
-                        <entry><code>removeAutoloader($callback, $namespace = '')</code></entry>
+                        <entry><methodname>removeAutoloader($callback, $namespace = '')</methodname></entry>
                         <entry><classname>Zend_Loader_Autoloader</classname></entry>
                         <entry><itemizedlist>
                             <listitem><para>

documentation/manual/en/module_specs/Zend_Loader-PluginLoader.xml

@@ -145,21 +145,21 @@ $loader = new Zend_Loader_PluginLoader(array(), 'foobar');
 
         <itemizedlist>
             <listitem><para>
-                    <code>getPaths($prefix = null)</code> returns all paths as
+                    <methodname>getPaths($prefix = null)</methodname> returns all paths as
                     prefix / path pairs if no <code>$prefix</code> is provided,
                     or just the paths registered for a given prefix if a
                     <code>$prefix</code> is present.
             </para></listitem>
 
             <listitem><para>
-                    <code>clearPaths($prefix = null)</code> will clear all
+                    <methodname>clearPaths($prefix = null)</methodname> will clear all
                     registered paths by default, or only those associated with a
                     given prefix, if the <code>$prefix</code> is provided and
                     present in the stack.
             </para></listitem>
 
             <listitem><para>
-                    <code>removePrefixPath($prefix, $path = null)</code> allows
+                    <methodname>removePrefixPath($prefix, $path = null)</methodname> allows
                     you to selectively remove a specific path associated with a
                     given prefix. If no <code>$path</code> is provided, all
                     paths for that prefix are removed. If a <code>$path</code>
@@ -174,15 +174,15 @@ $loader = new Zend_Loader_PluginLoader(array(), 'foobar');
 
         <para>
             Sometimes you simply want to determine if a plugin class has been
-            loaded before you perform an action. <code>isLoaded()</code> takes a
+            loaded before you perform an action. <methodname>isLoaded()</methodname> takes a
             plugin name, and returns the status.
         </para>
 
         <para>
             Another common use case for the <code>PluginLoader</code> is to
             determine fully qualified plugin class names of loaded classes;
-            <code>getClassName()</code> provides this functionality. Typically,
-            this would be used in conjunction with <code>isLoaded()</code>:
+            <methodname>getClassName()</methodname> provides this functionality. Typically,
+            this would be used in conjunction with <methodname>isLoaded()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Loader.xml

@@ -16,7 +16,7 @@
             user input or method argument. If you are loading a file or a
             class whose name is constant, there is no benefit to using
             <classname>Zend_Loader</classname> over using traditional PHP functions such as
-            <ulink url="http://php.net/require_once"><code>require_once()</code></ulink>.
+            <ulink url="http://php.net/require_once"><methodname>require_once()</methodname></ulink>.
         </para>
     </tip>
 
@@ -28,7 +28,7 @@
             The static method <classname>Zend_Loader::loadFile()</classname> loads a PHP
             file. The file loaded may contain any PHP code.
             The method is a wrapper for the PHP function
-            <ulink url="http://php.net/include"><code>include()</code></ulink>.
+            <ulink url="http://php.net/include"><methodname>include()</methodname></ulink>.
             This method returns boolean false on failure, for example
             if the specified file does not exist.
         </para>
@@ -59,9 +59,9 @@ Zend_Loader::loadFile($filename, $dirs=null, $once=false);
         <para>
             The <code>$once</code> argument is a boolean. If <constant>TRUE</constant>,
             <classname>Zend_Loader::loadFile()</classname> uses the PHP function
-            <ulink url="http://php.net/include"><code>include_once()</code></ulink>
+            <ulink url="http://php.net/include"><methodname>include_once()</methodname></ulink>
             for loading the file, otherwise the PHP function
-            <ulink url="http://php.net/include_once"><code>include()</code></ulink>
+            <ulink url="http://php.net/include_once"><methodname>include()</methodname></ulink>
             is used.
         </para>
 
@@ -138,7 +138,7 @@ if (Zend_Loader::isReadable($filename)) {
             The <code>$filename</code> argument specifies the filename to
             check. This may contain path information.
             This method is a wrapper for the PHP function
-            <ulink url="http://php.net/is_readable"><code>is_readable()</code></ulink>.
+            <ulink url="http://php.net/is_readable"><methodname>is_readable()</methodname></ulink>.
             The PHP function does not search the <code>include_path</code>,
             while <classname>Zend_Loader::isReadable()</classname> does.
         </para>
@@ -153,10 +153,10 @@ if (Zend_Loader::isReadable($filename)) {
             The <classname>Zend_Loader</classname> class contains a method you can register with the
             PHP SPL autoloader. <classname>Zend_Loader::autoload()</classname> is the
             callback method. As a convenience, <classname>Zend_Loader</classname> provides the
-            <code>registerAutoload()</code> function to register its
-            <code>autoload()</code> method. If the <code>spl_autoload</code>
+            <methodname>registerAutoload()</methodname> function to register its
+            <methodname>autoload()</methodname> method. If the <code>spl_autoload</code>
             extension is not present in your PHP environment, then the
-            <code>registerAutoload()</code> method throws a <classname>Zend_Exception</classname>.
+            <methodname>registerAutoload()</methodname> method throws a <classname>Zend_Exception</classname>.
         </para>
 
         <example id="zend.loader.load.autoload.example">
@@ -169,15 +169,15 @@ Zend_Loader::registerAutoload();
         <para>
             After registering the Zend Framework autoload callback, you can
             reference classes from Zend Framework without having to load
-            them explicitly. The <code>autoload()</code> method uses
+            them explicitly. The <methodname>autoload()</methodname> method uses
             <classname>Zend_Loader::loadClass()</classname> automatically when you
             reference a class.
         </para>
 
         <para>
             If you have extended the <classname>Zend_Loader</classname> class, you can give an
-            optional argument to <code>registerAutoload()</code>, to specify
-            the class from which to register an <code>autoload()</code> method.
+            optional argument to <methodname>registerAutoload()</methodname>, to specify
+            the class from which to register an <methodname>autoload()</methodname> method.
         </para>
 
         <example id="zend.loader.load.autoload.example-extended">
@@ -185,11 +185,11 @@ Zend_Loader::registerAutoload();
                 extended class</title>
             <para>
                 Because of the semantics of static function references in PHP,
-                you must implement code for both <code>loadClass()</code>
-                and <code>autoload()</code>, and the <code>autoload()</code>
-                must call <code>self::loadClass()</code>. If your
-                <code>autoload()</code> method delegates to its parent to
-                call <code>self::loadClass()</code>, then it calls the
+                you must implement code for both <methodname>loadClass()</methodname>
+                and <methodname>autoload()</methodname>, and the <methodname>autoload()</methodname>
+                must call <methodname>self::loadClass()</methodname>. If your
+                <methodname>autoload()</methodname> method delegates to its parent to
+                call <methodname>self::loadClass()</methodname>, then it calls the
                 method of that name in the parent class, not the subclass.
             </para>
             <programlisting language="php"><![CDATA[
@@ -217,7 +217,7 @@ Zend_Loader::registerAutoload('My_Loader');
 
         <para>
             You can remove an autoload callback. The
-            <code>registerAutoload()</code> has an optional second argument,
+            <methodname>registerAutoload()</methodname> has an optional second argument,
             which is <constant>TRUE</constant> by default. If this argument is
             <constant>FALSE</constant>, the autoload callback is unregistered from the
             SPL autoload stack.

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

@@ -21,7 +21,7 @@
         <title>Normalizing Dates and Times</title>
 
         <para>
-            The <code>getDate()</code> method parses strings containing dates in localized formats. The results are
+            The <methodname>getDate()</methodname> method parses strings containing dates in localized formats. The results are
             returned in a structured array, with well-defined keys for each part of the date. In addition, the array
             will contain a key 'date_format' showing the format string used to parse the input date string. Since a
             localized date string may not contain all parts of a date/time, the key-value pairs are optional. For
@@ -31,7 +31,7 @@
         </para>
 
         <para>
-            If <code>setOption(array('fix_date' => true))</code> is set the <code>getDate()</code> method adds a key 'fixed'
+            If <methodname>setOption(array('fix_date' => true))</methodname> is set the <methodname>getDate()</methodname> method adds a key 'fixed'
             with a whole number value indicating if the input date string required "fixing" by rearranging the day,
             month, or year in the input to fit the format used.
         </para>
@@ -78,9 +78,9 @@
 
         <para>
             These specifiers (below) are a small subset of the full "ISO" set supported by <classname>Zend_Date</classname>'s
-            <code>toString()</code>. If you need to use PHP <code>date()</code> compatible format specifiers, then first
-            call <code>setOptions(array('format_type' => 'php'))</code>. And if you want to convert only one special format
-            string from PHP <code>date()</code> compatible format to "ISO" format use <code>convertPhpToIsoFormat()</code>.
+            <methodname>toString()</methodname>. If you need to use PHP <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 PHP <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,
             and 'i' using the PHP date format).
         </para>
@@ -187,12 +187,12 @@ Array
         </example>
 
         <para>
-            Since <code>getDate()</code> is "locale-aware", specifying the <code>$locale</code> is sufficient for date
+            Since <methodname>getDate()</methodname> is "locale-aware", specifying the <code>$locale</code> is sufficient for date
             strings adhering to that locale's format. The option '<code>fix_date</code>' uses simple tests to
             determine if the day or month is not valid, and then applies heuristics to try and correct any detected
             problems. Note the use of '<classname>Zend_Locale_Format::STANDARD</classname>' as the value for
             '<code>date_format</code>' to prevent the use of a class-wide default date format set using
-            <code>setOptions()</code>. This forces getDate to use the default date format for <code>$locale</code>.
+            <methodname>setOptions()</methodname>. This forces getDate to use the default date format for <code>$locale</code>.
         </para>
 
         <example id="zend.locale.date.normalize.example-2">
@@ -337,7 +337,7 @@ print_r ($date);
 
         <para>
             The option '<code>fix_date</code>' uses simple tests to determine if the day or month is not
-            valid, and then applies heuristics to try and correct any detected problems. <code>getDate()</code>
+            valid, and then applies heuristics to try and correct any detected problems. <methodname>getDate()</methodname>
             automatically detects and corrects some kinds of problems with input, such as misplacing the year:
         </para>
 
@@ -361,8 +361,8 @@ print_r ($date);
         <title>Testing Dates</title>
 
         <para>
-            Use <code>checkDateFormat($inputString, array('date_format' => $format, $locale))</code> to check if a given string
-            contains all expected date parts. The <code>checkDateFormat()</code> method uses <code>getDate()</code>, but without
+            Use <methodname>checkDateFormat($inputString, array('date_format' => $format, $locale))</methodname> to check if a given string
+            contains all expected date parts. The <methodname>checkDateFormat()</methodname> method uses <methodname>getDate()</methodname>, but without
             the option <code>'fixdate'</code> to avoid returning true when the input fails to conform to the date
             format. If errors are detected in the input, such as swapped values for months and days, the
             option <code>'fixdate'</code> method will apply heuristics to "correct" dates before determining their
@@ -394,7 +394,7 @@ if (Zend_Locale_Format::checkDateFormat('13.Apr.2006',
 
         <para>
             Normally, a time will be returned with a date, if the input contains both. If the proper format is not
-            known, but the locale relevant to the user input is known, then <code>getTime()</code> should be used,
+            known, but the locale relevant to the user input is known, then <methodname>getTime()</methodname> should be used,
             because it uses the default time format for the selected locale.
         </para>
 
@@ -420,7 +420,7 @@ if (Zend_Locale_Format::getTime('13:44:42',
         <title>Testing Times</title>
 
         <para>
-            Use <code>checkDateFormat()</code> to check if a given string contains a proper time.
+            Use <methodname>checkDateFormat()</methodname> to check if a given string contains a proper time.
             The usage is exact the same as with checking Dates, only <code>date_format</code>
             should contain the parts which you expect to have.
         </para>

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

@@ -74,7 +74,7 @@ if ($locale->equals($mylocale)) {
         <title>Default locales</title>
 
         <para>
-            The method <code>getDefault()</code> returns an array of relevant locales using
+            The method <methodname>getDefault()</methodname> returns an array of relevant locales using
             information from the user's web browser (if available), information from the
             environment of the host server, and Zend Framework settings. As with the constructor
             for <classname>Zend_Locale</classname>, the first parameter selects a preference of
@@ -108,17 +108,17 @@ print_r($found2);
             <itemizedlist>
                 <listitem>
                     <para>
-                        <code>getEnvironment()</code>
+                        <methodname>getEnvironment()</methodname>
                     </para>
                 </listitem>
                 <listitem>
                     <para>
-                        <code>getBrowser()</code>
+                        <methodname>getBrowser()</methodname>
                     </para>
                 </listitem>
                 <listitem>
                     <para>
-                        <code>getLocale()</code>
+                        <methodname>getLocale()</methodname>
                     </para>
                 </listitem>
             </itemizedlist>
@@ -131,7 +131,7 @@ print_r($found2);
         <title>Set a new locale</title>
 
         <para>
-            A new locale can be set with the function <code>setLocale()</code>. This function takes a locale string as
+            A new locale can be set with the function <methodname>setLocale()</methodname>. This function takes a locale string as
             parameter. If no locale is given, a locale is
             <link linkend="zend.locale.selection">automatically selected</link>.
             Since <classname>Zend_Locale</classname> objects are "light", this method exists primarily to cause side-effects for code that
@@ -159,8 +159,8 @@ print $locale->toString();
         <title>Getting the language and region</title>
 
         <para>
-            Use <code>getLanguage()</code> to obtain a string containing the two character language code from the string
-            locale identifier. Use <code>getRegion()</code> to obtain a string containing the two character region code
+            Use <methodname>getLanguage()</methodname> to obtain a string containing the two character language code from the string
+            locale identifier. Use <methodname>getRegion()</methodname> to obtain a string containing the two character region code
             from the string locale identifier.
         </para>
 
@@ -184,7 +184,7 @@ print $locale->getRegion();
         <title>Obtaining localized strings</title>
 
         <para>
-            <code>getTranslationList()</code> gives you access to localized informations of several types. These
+            <methodname>getTranslationList()</methodname> gives you access to localized informations of several types. These
             information are useful if you want to display localized data to a customer without the need
             of translating it. They are already available for your usage.
         </para>
@@ -623,16 +623,16 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
         </table>
 
         <para>
-            If you are in need of a single translated value, you can use the <code>getTranslation()</code>
+            If you are in need of a single translated value, you can use the <methodname>getTranslation()</methodname>
             method. It returns always a string but it accepts some different types than the
-            <code>getTranslationList()</code> method. Also value is the same as before with one difference.
+            <methodname>getTranslationList()</methodname> method. Also value is the same as before with one difference.
             You have to give the detail you want to get returned as additional value.
         </para>
 
         <note>
             <para>
                 Because you have almost always give a value as detail this parameter has to be given
-                as first parameter. This differs from the <code>getTranslationList()</code> method.
+                as first parameter. This differs from the <methodname>getTranslationList()</methodname> method.
             </para>
         </note>
 
@@ -725,7 +725,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             of the day as string value ('sun', 'mon', etc.). If you want to receive data
                             for other calendars, contexts or format, then you must give an array instead of
                             an integer with the expected values. The array has to look like this:
-                            <code>array('calendar', 'context', 'format', 'day abbreviation')</code>. If you
+                            <methodname>array('calendar', 'context', 'format', 'day abbreviation')</methodname>. If you
                             give only an string then the default values are the 'gregorian' calendar,
                             the context 'format' and the format 'wide'. Use
                             <link linkend="zend.date.introduction">Zend_Date</link> for simplicity</entry>
@@ -736,7 +736,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             quarter as integer and it has to be between 1 and 4. If you want to receive
                             data for other calendars, contexts or formats, then you must give an array
                             instead of an integer with the expected values. The array has to look like this:
-                            <code>array('calendar', 'context', 'format', 'quarter number')</code>. If you
+                            <methodname>array('calendar', 'context', 'format', 'quarter number')</methodname>. If you
                             give only an string then the default values are the 'gregorian' calendar,
                             the context 'format' and the format 'wide'</entry>
                     </row>
@@ -760,7 +760,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             number as string or integer. If you want to receive data for other calendars or
                             formats, then you must give an array instead of the era number with the expected
                             values. The array has to look like this:
-                            <code>array('calendar', 'format', 'era number')</code>. If you give only an
+                            <methodname>array('calendar', 'format', 'era number')</methodname>. If you give only an
                             string then the default values are the 'gregorian' calendar and the 'abbr'
                             format</entry>
                     </row>
@@ -776,7 +776,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             If you omit the value then the 'gregorian' calendar will be used with the
                             'medium' format. If you give a string then the 'gregorian' calendar will be
                             used with the given format. Or you can also give an array which will have to
-                            look like this: <code>array('calendar', 'format')</code>. Use
+                            look like this: <methodname>array('calendar', 'format')</methodname>. Use
                             <link linkend="zend.date.introduction">Zend_Date</link> for simplicity</entry>
                     </row>
                     <row>
@@ -791,7 +791,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             If you omit the value then the 'gregorian' calendar will be used with the
                             'medium' format. If you give a string then the 'gregorian' calendar will be
                             used with the given format. Or you can also give an array which will have to
-                            look like this: <code>array('calendar', 'format')</code>. Use
+                            look like this: <methodname>array('calendar', 'format')</methodname>. Use
                             <link linkend="zend.date.introduction">Zend_Date</link> for simplicity</entry>
                     </row>
                     <row>
@@ -823,7 +823,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             field which has to be returned as string. In this case the 'gregorian'
                             calendar will be used. You can get the field for other calendar formats if you
                             give an array which has to look like this:
-                            <code>array('calendar', 'date field')</code></entry>
+                            <methodname>array('calendar', 'date field')</methodname></entry>
                     </row>
                     <row>
                         <entry><emphasis>Relative</emphasis></entry>
@@ -832,7 +832,7 @@ print Zend_Locale::getTranslation('de', 'language', 'zh');
                             the number of days relative to tomorrow to receive the expected string. Yesterday
                             would be '-1', tomorrow '1' and so on. This will use the 'gregorian' calendar. If
                             you want to get relative dates for other calendars you will have to give an array
-                            which has to look like this: <code>array('calendar', 'relative days')</code>. Use
+                            which has to look like this: <methodname>array('calendar', 'relative days')</methodname>. Use
                             <link linkend="zend.date.introduction">Zend_Date</link> for simplicity</entry>
                     </row>
                     <row>
@@ -1161,8 +1161,8 @@ echo Zend_Locale::getLanguageTranslation($frenchCode, 'de_AT');
 
         <para>
             To generate a list of all languages known by <classname>Zend_Locale</classname>, with each language name shown in its own language,
-            try the example below in a web page. Similarly, <code>getCountryTranslationList()</code> and
-            <code>getCountryTranslation()</code> could be used to create a table mapping your native language names for
+            try the example below in a web page. Similarly, <methodname>getCountryTranslationList()</methodname> and
+            <methodname>getCountryTranslation()</methodname> could be used to create a table mapping your native language names for
             regions to the names of the regions shown in another language. Use a
             <code>try .. catch</code> block to handle exceptions that occur when using a locale that does not exist. Not
             all languages are also locales. In the example, below exceptions are ignored to prevent early termination.
@@ -1193,7 +1193,7 @@ foreach($list as $language => $content) {
         <title>Obtaining translations for "yes" and "no"</title>
 
         <para>
-            Frequently, programs need to solicit a "yes" or "no" response from the user. Use <code>getQuestion()</code>
+            Frequently, programs need to solicit a "yes" or "no" response from the user. Use <methodname>getQuestion()</methodname>
             to obtain an array containing the correct word(s) or regex strings to use for prompting the user in a
             particular $locale (defaults to the current object's locale). The returned array will contain the
             following informations :
@@ -1272,7 +1272,7 @@ Array
         <para>
             Sometimes you will want to get a list of all known locales. This can be used for several tasks
             like the creation of a selectbox. For this purpose you can use the static
-            <code>getLocaleList()</code> method which will return a list of all known locales.
+            <methodname>getLocaleList()</methodname> method which will return a list of all known locales.
         </para>
 
         <example id="zend.locale.getlocalelist.example-1">
@@ -1296,7 +1296,7 @@ $localelist = Zend_Locale::getLocaleList();
 
         <para>
             When you want to detect if a given input, regardless of its source, is a locale you should use
-            the static <code>isLocale()</code> method. The first parameter of this method is the string which
+            the static <methodname>isLocale()</methodname> method. The first parameter of this method is the string which
             you want to check.
         </para>
 
@@ -1316,7 +1316,7 @@ if (Zend_Locale::isLocale($input)) {
             As you can see, the output of this method is always a boolean. There is only one reason you could
             get an exception when calling this method. When your system does not provide any locale and
             Zend Framework is not able to detect it automatically. Normally this shows that there is a problem
-            with your OS in combination with PHP's <code>setlocale()</code>.
+            with your OS in combination with PHP's <methodname>setlocale()</methodname>.
         </para>
 
         <para>
@@ -1328,7 +1328,7 @@ if (Zend_Locale::isLocale($input)) {
 
         <para>
             Still it's sometimes usefull to prevent this automatic degrading, and this is where the second
-            parameter of <code>isLocale()</code> comes in place. The <code>strict</code> parameter defaults to
+            parameter of <methodname>isLocale()</methodname> comes in place. The <code>strict</code> parameter defaults to
             <constant>FALSE</constant> and can be used to prevent degrading when set to <constant>TRUE</constant>.
         </para>
 
@@ -1373,7 +1373,7 @@ if ($locale instanceof Zend_Locale) {
         </example>
 
         <para>
-            With Zend Framework 1.8 we added a static <code>findLocale()</code> method which returns you a locale
+            With Zend Framework 1.8 we added a static <methodname>findLocale()</methodname> method which returns you a locale
             string which you can work with. It processes the following tasks:
         </para>
 

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

@@ -30,15 +30,15 @@
     <tip>
         <title>Zend_Locale and setLocale()</title>
         <para>
-            <ulink url="http://php.net/setlocale">PHP's documentation</ulink> states that <code>setlocale()</code>
+            <ulink url="http://php.net/setlocale">PHP's documentation</ulink> states that <methodname>setlocale()</methodname>
             is not threadsave because it is maintained per process and not per thread. This means that, in
             multithreaded environments, you can have the problem that the locale changes while the script
             never has changed the locale itself. This can lead to unexpected behaviour when you use
-            <code>setlocale()</code> in your scripts.
+            <methodname>setlocale()</methodname> in your scripts.
         </para>
         <para>
             When you are using <classname>Zend_Locale</classname> you will not have this limitations, because
-            <classname>Zend_Locale</classname> is not related to or coupled with PHP's <code>setlocale()</code>.
+            <classname>Zend_Locale</classname> is not related to or coupled with PHP's <methodname>setlocale()</methodname>.
         </para>
     </tip>
 
@@ -224,7 +224,7 @@ $locale3 = new Zend_Locale(Zend_Locale::FRAMEWORK);
                 <listitem>
                     <para>
                         const <classname>Zend_Locale::ENVIRONMENT</classname> - PHP publishes the host server's locale via the PHP
-                        internal function <code>setlocale()</code>. If no matching locale can be found, then preference
+                        internal function <methodname>setlocale()</methodname>. If no matching locale can be found, then preference
                         is given to <code>FRAMEWORK</code> and lastly <code>BROWSER</code>.
                     </para>
                 </listitem>
@@ -249,7 +249,7 @@ $locale3 = new Zend_Locale(Zend_Locale::FRAMEWORK);
         <para>
             <classname>Zend_Locale</classname> provides three additionally locales. These locales do not belong to
             any language or region. They are "automatic" locales which means that they have the same effect
-            as the method <code>getDefault()</code> but without the negative effects like creating an instance.
+            as the method <methodname>getDefault()</methodname> but without the negative effects like creating an instance.
             These "automatic" locales can be used anywhere, where also a standard locale and also the
             definition of a locale, its string representation, can be used. This offers simplicity for
             situations like working with locales which are provided by a browser.
@@ -276,7 +276,7 @@ $locale3 = new Zend_Locale(Zend_Locale::FRAMEWORK);
                     <para>
                         <code>'environment'</code> - <classname>Zend_Locale</classname> should work with the information
                         which is provided by the host server. It is published by PHP via the internal function
-                        <code>setlocale()</code>.
+                        <methodname>setlocale()</methodname>.
                     </para>
                     <para>
                         If a environment provides more than one locale, <classname>Zend_Locale</classname> will use the
@@ -351,8 +351,8 @@ $date = new Zend_Date($locale);
 
         <para>
             Since Zend Framework Release 1.5 there is a much better way to handle this. You can set a
-            default locale which the static <code>setDefault()</code> method. Of course, every unknown
-            or not full qualified locale will also throw an exception. <code>setDefault()</code> should
+            default locale which the static <methodname>setDefault()</methodname> method. Of course, every unknown
+            or not full qualified locale will also throw an exception. <methodname>setDefault()</methodname> should
             be the first call before you initiate any class using <classname>Zend_Locale</classname>. See the
             following example for details:
         </para>
@@ -467,7 +467,7 @@ echo $date->getDate();
             parsing numbers and dates using separators and month names. The date format 'format_type' option selects between
             CLDR/ISO date format specifier tokens and PHP'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 <code>toNumber()</code> (see
+            format for use with <methodname>toNumber()</methodname> (see
             <xref
                 linkend= "zend.locale.number.localize"/>
             ).

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

@@ -35,7 +35,7 @@
             <ulink url="http://en.wikipedia.org/wiki/Numeral">number systems</ulink>
             different from the common
             <ulink url="http://en.wikipedia.org/wiki/Decimal">decimal system</ulink>
-            (e.g. "3.14"). Numbers can be normalized with the <code>getNumber()</code> function to obtain the standard
+            (e.g. "3.14"). Numbers can be normalized with the <methodname>getNumber()</methodname> function to obtain the standard
             decimal representation. for all number-related discussions in this manual,
             <ulink url="http://en.wikipedia.org/wiki/Arabic_numerals">Arabic/European numerals (0,1,2,3,4,5,6,7,8,9)</ulink>
             are implied, unless explicitly stated otherwise. The options array may contain a 'locale' to define grouping
@@ -60,7 +60,7 @@ print $number; // will return 13524.678
             <title>Precision and Calculations</title>
 
             <para>
-                Since <code>getNumber($value, array $options = array())</code> can normalize extremely large numbers,
+                Since <methodname>getNumber($value, array $options = array())</methodname> can normalize extremely large numbers,
                 check the result carefully before using finite precision calculations, such as ordinary PHP math
                 operations. For example, <code>if ((string)int_val($number) != $number) { use
                 <ulink url="http://www.php.net/bc">BCMath</ulink>
@@ -71,7 +71,7 @@ print $number; // will return 13524.678
 
             <para>
                 Also, the precision of the resulting decimal representation can be rounded to a desired length with
-                <code>getNumber()</code> with the option <code>'precision'</code>. If no precision is given,
+                <methodname>getNumber()</methodname> with the option <code>'precision'</code>. If no precision is given,
                 no rounding occurs. Use only PHP integers to specify the precision.
             </para>
 
@@ -110,11 +110,11 @@ print $number; // will return 13524.67
         <title>Number localization</title>
 
         <para>
-            <code>toNumber($value, array $options = array())</code> can localize numbers to the following
+            <methodname>toNumber($value, array $options = array())</methodname> can localize numbers to the following
             <link linkend="zend.locale.appendix">supported locales</link>
             . This function will return a localized string of the given number in a conventional format for a specific
             locale. The 'number_format' option explicitly specifies a non-default number format for use with
-            <code>toNumber()</code>.
+            <methodname>toNumber()</methodname>.
         </para>
 
         <example id="zend.locale.number.localize.example-1">
@@ -133,14 +133,14 @@ print $number;
             <note>
                 <title>Unlimited length</title>
                 <para>
-                    <code>toNumber()</code> can localize numbers with unlimited length. It is not related to integer or
+                    <methodname>toNumber()</methodname> can localize numbers with unlimited length. It is not related to integer or
                     float limitations.
                 </para>
             </note>
         </para>
 
         <para>
-            The same way as within <code>getNumber()</code>, <code>toNumber()</code> handles precision. If no precision
+            The same way as within <methodname>getNumber()</methodname>, <methodname>toNumber()</methodname> handles precision. If no precision
             is given, the complete localized number will be returned.
         </para>
 
@@ -240,7 +240,7 @@ print $number;
         <title>Number testing</title>
 
         <para>
-            <code>isNumber($value, array $options = array())</code> checks if a given string is a number and returns
+            <methodname>isNumber($value, array $options = array())</methodname> checks if a given string is a number and returns
             true or false.
         </para>
 
@@ -263,7 +263,7 @@ if (Zend_Locale_Format::isNumber('13.445,36', array('locale' => 'de_AT')) {
         <title>Float value normalization</title>
 
         <para>
-            Floating point values can be parsed with the <code>getFloat($value, array $options = array())</code>
+            Floating point values can be parsed with the <methodname>getFloat($value, array $options = array())</methodname>
             function. A floating point value will be returned.
         </para>
 
@@ -288,7 +288,7 @@ print $number;
         <title>Floating point value localization</title>
 
         <para>
-            <code>toFloat()</code> can localize floating point values. This function will return a localized string of
+            <methodname>toFloat()</methodname> can localize floating point values. This function will return a localized string of
             the given number.
         </para>
 
@@ -313,7 +313,7 @@ print $number;
         <title>Floating point value testing</title>
 
         <para>
-            <code>isFloat($value, array $options = array())</code> checks if a given string is a floating point value
+            <methodname>isFloat($value, array $options = array())</methodname> checks if a given string is a floating point value
             and returns true or false.
         </para>
 
@@ -336,7 +336,7 @@ if (Zend_Locale_Format::isFloat('13.445,36', array('locale' => $locale)) {
         <title>Integer value normalization</title>
 
         <para>
-            Integer values can be parsed with the <code>getInteger()</code> function. A integer value will be returned.
+            Integer values can be parsed with the <methodname>getInteger()</methodname> function. A integer value will be returned.
         </para>
 
         <example id="zend.locale.integer.normalize.example-1">
@@ -358,7 +358,7 @@ print $number;
         <title>Integer point value localization</title>
 
         <para>
-            <code>toInteger($value, array $options = array())</code> can localize integer values. This function will
+            <methodname>toInteger($value, array $options = array())</methodname> can localize integer values. This function will
             return a localized string of the given number.
         </para>
 
@@ -381,7 +381,7 @@ print $number;
         <title>Integer value testing</title>
 
         <para>
-            <code>isInteger($value, array $options = array())</code> checks if a given string is a integer value and
+            <methodname>isInteger($value, array $options = array())</methodname> checks if a given string is a integer value and
             returns true or false.
         </para>
 
@@ -427,7 +427,7 @@ if (Zend_Locale_Format::isInteger('13.445', array('locale' => $locale)) {
             Suppose a web form collected a numeric input expressed using Eastern Arabic digits "١‎٠٠".
             Most software and PHP functions expect input using Arabic numerals. Fortunately, converting this input
             to its equivalent Latin numerals "100" requires little effort using
-            <code>convertNumerals($inputNumeralString, $sourceNumeralSystem, $destNumeralSystem)</code>
+            <methodname>convertNumerals($inputNumeralString, $sourceNumeralSystem, $destNumeralSystem)</methodname>
             , which returns the <code>$input</code> with numerals in the script <code>$sourceNumeralSystem</code>
             converted to the script <code>$destNumeralSystem</code>.
         </para>

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

@@ -12,7 +12,7 @@
 
       <para>
         To filter before all writers, you can add any number of Filters to a
-        Log object using the <code>addFilter()</code> method:
+        Log object using the <methodname>addFilter()</methodname> method:
 
         <programlisting language="php"><![CDATA[
 $logger = new Zend_Log();

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

@@ -29,7 +29,7 @@ $formatter = new Zend_Log_Formatter_Simple($format);
 
     <para>
       A formatter is set on an individual Writer object using the Writer's
-      <code>setFormatter()</code> method:
+      <methodname>setFormatter()</methodname> method:
 
       <programlisting language="php"><![CDATA[
 $writer = new Zend_Log_Writer_Stream('php://output');

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

@@ -54,7 +54,7 @@ $logger->addWriter($writer);
 
         It is important to note that the Log must
         have at least one Writer. You can add any number of Writers using the
-        Log's <code>addWriter()</code> method.
+        Log's <methodname>addWriter()</methodname> method.
       </para>
 
       <para>
@@ -74,20 +74,20 @@ $logger = new Zend_Log($writer);
       <title>Logging Messages</title>
 
       <para>
-        To log a message, call the <code>log()</code> method of a Log instance
+        To log a message, call the <methodname>log()</methodname> method of a Log instance
         and pass it the message with a corresponding priority:
 
       <programlisting language="php"><![CDATA[
 $logger->log('Informational message', Zend_Log::INFO);
 ]]></programlisting>
 
-      The first parameter of the <code>log()</code> method is a string <code>message</code> and the second
+      The first parameter of the <methodname>log()</methodname> method is a string <code>message</code> and the second
       parameter is an integer <code>priority</code>. The priority must be one of the priorities recognized
       by the Log instance. This is explained in the next section.
     </para>
 
     <para>
-      A shortcut is also available. Instead of calling the <code>log()</code> method, you can
+      A shortcut is also available. Instead of calling the <methodname>log()</methodname> method, you can
       call a method by the same name as the priority:
 
       <programlisting language="php"><![CDATA[
@@ -105,7 +105,7 @@ $logger->emerg('Emergency message');
     <para>
       If the Log object is no longer needed, set the variable containing it to
       <constant>NULL</constant> to destroy it. This will automatically call the
-      <code>shutdown()</code> instance method of each attached Writer before
+      <methodname>shutdown()</methodname> instance method of each attached Writer before
       the Log object is destroyed:
 
       <programlisting language="php"><![CDATA[
@@ -161,7 +161,7 @@ DEBUG   = 7;  // Debug: debug messages
 
     <para>
       User-defined priorities can be added at runtime using the Log's
-      <code>addPriority()</code> method:
+      <methodname>addPriority()</methodname> method:
 
       <programlisting language="php"><![CDATA[
 $logger->addPriority('FOO', 8);
@@ -183,7 +183,7 @@ $logger->foo('Foo Message');
     <title>Understanding Log Events</title>
 
     <para>
-      When you call the <code>log()</code> method or one of its shortcuts, a
+      When you call the <methodname>log()</methodname> method or one of its shortcuts, a
       log event is created. This is simply an associative array with data
       describing the event that is passed to the writers. The following keys
       are always created in this array: <code>timestamp</code>,
@@ -198,7 +198,7 @@ $logger->foo('Foo Message');
     </para>
 
     <para>
-      To add a new item to every future event, call the <code>setEventItem()</code>
+      To add a new item to every future event, call the <methodname>setEventItem()</methodname>
       method giving a key and a value:
 
       <programlisting language="php"><![CDATA[
@@ -209,11 +209,11 @@ $logger->setEventItem('pid', getmypid());
       it with the PID of the current process. Once a new item has been
       set, it is available automatically to all writers along with all of the
       other data event data during logging. An item can be overwritten at any
-      time by calling the <code>setEventItem()</code> method again.
+      time by calling the <methodname>setEventItem()</methodname> method again.
     </para>
 
     <para>
-      Setting a new event item with <code>setEventItem()</code> causes the
+      Setting a new event item with <methodname>setEventItem()</methodname> causes the
       new item to be sent to all writers of the logger. However, this does
       not guarantee that the writers actually record the item. This is
       because the writers won't know what to do with it unless a formatter

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

@@ -82,7 +82,7 @@ $response->sendHeaders();
       <title>Setting Styles for Priorities</title>
 
       <para>
-        Built-in and user-defined priorities can be styled with the <code>setPriorityStyle()</code> method.
+        Built-in and user-defined priorities can be styled with the <methodname>setPriorityStyle()</methodname> method.
       </para>
       <programlisting language="php"><![CDATA[
 $logger->addPriority('FOO', 8);
@@ -90,7 +90,7 @@ $writer->setPriorityStyle(8, 'TRACE');
 $logger->foo('Foo Message');
 ]]></programlisting>
       <para>
-        The default style for user-defined priorities can be set with the <code>setDefaultPriorityStyle()</code> method.
+        The default style for user-defined priorities can be set with the <methodname>setDefaultPriorityStyle()</methodname> method.
       </para>
       <programlisting language="php"><![CDATA[
 $writer->setDefaultPriorityStyle('TRACE');

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

@@ -73,7 +73,7 @@ $log->error('unable to connect to database');
         <para>
             When using <classname>Zend_Log_Writer_Mail</classname> with a
             <classname>Zend_Layout</classname> instance, you have the option to set a
-            custom formatter by using the <code>setLayoutFormatter()</code>
+            custom formatter by using the <methodname>setLayoutFormatter()</methodname>
             method. If no <classname>Zend_Layout</classname>-specific entry formatter was
             specified, the formatter currently in use will be used. Full usage
             of <classname>Zend_Layout</classname> with a custom formatter is outlined
@@ -117,7 +117,7 @@ $log->error('unable to connect to database');
         <title>Subject Line Error Level Summary</title>
 
         <para>
-            The <code>setSubjectPrependText()</code> method may be used in place
+            The <methodname>setSubjectPrependText()</methodname> method may be used in place
             of <classname>Zend_Mail::setSubject()</classname> to have the email subject
             line dynamically written before the email is sent. For example, if
             the subject prepend text reads "Errors from script", the subject of

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

@@ -149,7 +149,7 @@ var_dump($mock->events[0]);
 
     <para>
       There is no composite Writer object. However, a Log instance can write
-      to any number of Writers. To do this, use the <code>addWriter()</code>
+      to any number of Writers. To do this, use the <methodname>addWriter()</methodname>
       method:
 
       <programlisting language="php"><![CDATA[

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

@@ -6,24 +6,24 @@
         Recipients can be added in three ways:
         <itemizedlist>
         <listitem>
-        <para><code>addTo()</code>: Adds a recipient to the mail with a "To" header</para>
+        <para><methodname>addTo()</methodname>: Adds a recipient to the mail with a "To" header</para>
         </listitem>
         <listitem>
-        <para><code>addCc()</code>: Adds a recipient to the mail with a "Cc" header</para>
+        <para><methodname>addCc()</methodname>: Adds a recipient to the mail with a "Cc" header</para>
         </listitem>
         <listitem>
-        <para><code>addBcc()</code>: Adds a recipient to the mail not visible in the header.</para>
+        <para><methodname>addBcc()</methodname>: Adds a recipient to the mail not visible in the header.</para>
         </listitem>
         </itemizedlist>
     </para>
     <para>
-        <code>getRecipients()</code> serves list of the recipients. <code>clearRecipients()</code>
+        <methodname>getRecipients()</methodname> serves list of the recipients. <methodname>clearRecipients()</methodname>
         clears the list.
     </para>
     <note>
         <title>Additional parameter</title>
         <para>
-            <code>addTo()</code> and <code>addCc()</code> accept a second optional parameter that is used as a
+            <methodname>addTo()</methodname> and <methodname>addCc()</methodname> accept a second optional parameter that is used as a
             human-readable name of the recipient for the header. Double quotation is changed to
             single quotation and angle brackets to square brackets in the parameter.
         </para>

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

@@ -3,7 +3,7 @@
 <sect1 id="zend.mail.additional-headers">
     <title>Additional Headers</title>
     <para>
-        Arbitrary mail headers can be set by using the <code>addHeader()</code> method. It requires two
+        Arbitrary mail headers can be set by using the <methodname>addHeader()</methodname> method. It requires two
         parameters containing the name and the value of the header field. A third optional parameter determines
         if the header should have only one or multiple values:
     </para>
@@ -17,7 +17,7 @@ $mail->addHeader('X-greetingsTo', 'Dad', true);
 ]]></programlisting>
     </example>
 
-    <para>To set the Reply-To: header there exists the function <code>setReplyTo($email, $name=null)</code>,
+    <para>To set the Reply-To: header there exists the function <methodname>setReplyTo($email, $name=null)</methodname>,
         because it requires additional special escaping of the different parts (email and name).</para>
 
 </sect1>

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

@@ -3,10 +3,10 @@
 <sect1 id="zend.mail.attachments">
     <title>Attachments</title>
     <para>
-        Files can be attached to an e-mail using the <code>createAttachment()</code> method. The default behavior
+        Files can be attached to an e-mail using the <methodname>createAttachment()</methodname> method. The default behavior
         of <classname>Zend_Mail</classname> is to assume the attachment is a binary object (application/octet-stream),
         that it should be transferred with base64 encoding, and that it is handled as an attachment. These assumptions can be
-        overridden by passing more parameters to <code>createAttachment()</code>:
+        overridden by passing more parameters to <methodname>createAttachment()</methodname>:
     </para>
     <example id="zend.mail.attachments.example-1">
         <title>E-Mail Messages with Attachments</title>
@@ -22,7 +22,7 @@ $mail->createAttachment($myImage,
     </example>
     <para>
         If you want more control over the MIME part generated for this attachment you can use the return value
-        of <code>createAttachment()</code> to modify its attributes. The <code>createAttachment()</code> method
+        of <methodname>createAttachment()</methodname> to modify its attributes. The <methodname>createAttachment()</methodname> method
         returns a <classname>Zend_Mime_Part</classname> object:
     </para>
     <programlisting language="php"><![CDATA[
@@ -37,7 +37,7 @@ $at->filename    = 'test.gif';
 $mail->send();
 ]]></programlisting>
     <para>
-        An alternative is to create an instance of <classname>Zend_Mime_Part</classname> and add it with <code>addAttachment()</code>:
+        An alternative is to create an instance of <classname>Zend_Mime_Part</classname> and add it with <methodname>addAttachment()</methodname>:
     </para>
     <programlisting language="php"><![CDATA[
 $mail = new Zend_Mail();

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

@@ -5,7 +5,7 @@
     <para>
         In a multipart message, a MIME boundary for separating the different parts of the message is normally
         generated at random. In some cases, however, you might want to specify the MIME boundary that is used.
-        This can be done using the <code>setMimeBoundary()</code> method, as in the following example:
+        This can be done using the <methodname>setMimeBoundary()</methodname> method, as in the following example:
     </para>
     <example id="zend.mail.boundary.example-1">
         <title>Changing the MIME Boundary</title>

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

@@ -4,9 +4,9 @@
     <title>Using Different Transports</title>
     <para>
         In case you want to send different e-mails through different connections, you can also pass the
-        transport object directly to <code>send()</code> without a prior call to
-        <code>setDefaultTransport()</code>. The passed object will override the default transport for the
-        actual <code>send()</code> request.
+        transport object directly to <methodname>send()</methodname> without a prior call to
+        <methodname>setDefaultTransport()</methodname>. The passed object will override the default transport for the
+        actual <methodname>send()</methodname> request.
     </para>
     <example id="zend.mail.different-transports.example-1">
         <title>Using Different Transports</title>

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

@@ -4,8 +4,8 @@
     <title>Encoding</title>
     <para>
         Text and HTML message bodies are encoded with the quotedprintable mechanism by default. Message headers
-        are also encoded with the quotedprintable mechanism if you do not specify base64 in <code>setHeaderEncoding()</code>.
-        All other attachments are encoded via base64 if no other encoding is given in the <code>addAttachment()</code>
+        are also encoded with the quotedprintable mechanism if you do not specify base64 in <methodname>setHeaderEncoding()</methodname>.
+        All other attachments are encoded via base64 if no other encoding is given in the <methodname>addAttachment()</methodname>
         call or assigned to the MIME part object later. 7Bit and 8Bit encoding currently only pass on the
         binary content data.
     </para>

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

@@ -3,8 +3,8 @@
 <sect1 id="zend.mail.html-mails">
     <title>HTML E-Mail</title>
     <para>
-        To send an e-mail in HTML format, set the body using the method <code>setBodyHTML()</code> instead of
-        <code>setBodyText()</code>. The MIME content type will automatically be set to <code>text/html</code>
+        To send an e-mail in HTML format, set the body using the method <methodname>setBodyHTML()</methodname> instead of
+        <methodname>setBodyText()</methodname>. The MIME content type will automatically be set to <code>text/html</code>
         then. If you use both HTML and Text bodies, a multipart/alternative MIME message will automatically be
         generated:
     </para>

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

@@ -38,13 +38,13 @@ $mail->send();
             <title>Minimum definitions</title>
             <para>
                 In order to send an e-mail with <classname>Zend_Mail</classname> you have to specify at least one recipient, a
-                sender (e.g., with <code>setFrom()</code>), and a message body (text and/or HTML).
+                sender (e.g., with <methodname>setFrom()</methodname>), and a message body (text and/or HTML).
             </para>
         </note>
 
         <para>
             For most mail attributes there are "get" methods to read the information stored in the mail object. For
-            further details, please refer to the API documentation. A special one is <code>getRecipients()</code>.
+            further details, please refer to the API documentation. A special one is <methodname>getRecipients()</methodname>.
             It returns an array with all recipient e-mail addresses that were added prior to the method call.
         </para>
 
@@ -76,10 +76,10 @@ $mail->setBodyText('This is the text of the mail.')
 
         <para>
             The default transport for a <classname>Zend_Mail</classname> instance is <classname>Zend_Mail_Transport_Sendmail</classname>.
-            It is essentially a wrapper to the PHP <ulink url="http://php.net/mail"><code>mail()</code></ulink> function.
-            If you wish to pass additional parameters to the <ulink url="http://php.net/mail"><code>mail()</code></ulink> function,
+            It is essentially a wrapper to the PHP <ulink url="http://php.net/mail"><methodname>mail()</methodname></ulink> function.
+            If you wish to pass additional parameters to the <ulink url="http://php.net/mail"><methodname>mail()</methodname></ulink> function,
             simply create a new transport instance and pass your parameters to the constructor. The new transport instance
-            can then act as the default <classname>Zend_Mail</classname> transport, or it can be passed to the <code>send()</code>
+            can then act as the default <classname>Zend_Mail</classname> transport, or it can be passed to the <methodname>send()</methodname>
             method of <classname>Zend_Mail</classname>.
         </para>
 
@@ -88,7 +88,7 @@ $mail->setBodyText('This is the text of the mail.')
             <title>Passing additional parameters to the Zend_Mail_Transport_Sendmail transport</title>
 
             <para>
-                This example shows how to change the Return-Path of the <ulink url="http://php.net/mail"><code>mail()</code></ulink>
+                This example shows how to change the Return-Path of the <ulink url="http://php.net/mail"><methodname>mail()</methodname></ulink>
                 function.
             </para>
 
@@ -109,7 +109,7 @@ $mail->send();
         <note>
             <title>Safe mode restrictions</title>
             <para>
-                The optional additional parameters will be cause the <ulink url="http://php.net/mail"><code>mail()</code></ulink> function to fail
+                The optional additional parameters will be cause the <ulink url="http://php.net/mail"><methodname>mail()</methodname></ulink> function to fail
                 if PHP is running in safe mode.
             </para>
         </note>

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

@@ -4,7 +4,7 @@
     <title>Sending via SMTP</title>
     <para>
         To send mail via SMTP, <classname>Zend_Mail_Transport_Smtp</classname> needs to be created and registered with
-        <classname>Zend_Mail</classname> before the <code>send()</code> method is called. For all remaining
+        <classname>Zend_Mail</classname> before the <methodname>send()</methodname> method is called. For all remaining
         <classname>Zend_Mail::send()</classname> calls in the current script, the SMTP transport will then be used:
     </para>
     <example id="zend.mail.sending.example-1">
@@ -15,11 +15,11 @@ Zend_Mail::setDefaultTransport($tr);
 ]]></programlisting>
     </example>
     <para>
-        The <code>setDefaultTransport()</code> method and the constructor of
+        The <methodname>setDefaultTransport()</methodname> method and the constructor of
         <classname>Zend_Mail_Transport_Smtp</classname> are not expensive. These two lines can be processed at script
         setup time (e.g., config.inc or similar) to configure the behavior of the <classname>Zend_Mail</classname> class
         for the rest of the script. This keeps configuration information out of the application logic - whether
-        mail is sent via SMTP or <ulink url="http://php.net/mail"><code>mail()</code></ulink>, what mail server
+        mail is sent via SMTP or <ulink url="http://php.net/mail"><methodname>mail()</methodname></ulink>, what mail server
         is used, etc.
     </para>
 </sect1>

documentation/manual/en/module_specs/Zend_Mail_Read.xml

@@ -174,7 +174,7 @@ $mail = new Zend_Mail_Storage_Pop3(array('host'     => 'example.com',
 
         <para>
             Messages can be fetched after you've opened the storage . You need the message number, which is a counter
-            starting with 1 for the first message. To fetch the message, you use the method <code>getMessage()</code>:
+            starting with 1 for the first message. To fetch the message, you use the method <methodname>getMessage()</methodname>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -183,7 +183,7 @@ $message = $mail->getMessage($messageNum);
 
         <para>
             Array access is also supported, but this access method won't supported any additional parameters that could be added to
-            <code>getMessage()</code>. As long as you don't mind, and can live with the default values, you may use:
+            <methodname>getMessage()</methodname>. As long as you don't mind, and can live with the default values, you may use:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -199,7 +199,7 @@ foreach ($mail as $messageNum => $message) {
 ]]></programlisting>
 
         <para>
-            To count the messages in the storage, you can either use the method <code>countMessages()</code> or use array
+            To count the messages in the storage, you can either use the method <methodname>countMessages()</methodname> or use array
             access:
         </para>
 
@@ -211,7 +211,7 @@ $maxMessage = $mail->countMessages();
 $maxMessage = count($mail);
 ]]></programlisting>
 
-        <para>To remove a mail, you use the method <code>removeMessage()</code> or again array access:</para>
+        <para>To remove a mail, you use the method <methodname>removeMessage()</methodname> or again array access:</para>
 
         <programlisting language="php"><![CDATA[
 // method
@@ -225,12 +225,12 @@ unset($mail[$messageNum]);
     <sect2 id="zend.mail.read-message">
         <title>Working with messages</title>
 
-        <para>After you fetch the messages with <code>getMessage()</code> you want to fetch headers, the content
+        <para>After you fetch the messages with <methodname>getMessage()</methodname> you want to fetch headers, the content
         or single parts of a multipart message. All headers can be accessed via properties or the method
-        <code>getHeader()</code> if you want more control or have unusual header names. The header names are
+        <methodname>getHeader()</methodname> if you want more control or have unusual header names. The header names are
         lower-cased internally, thus the case of the header name in the mail message doesn't matter. Also headers
         with a dash can be written in camel-case. If no header is found for both notations an exception is thrown.
-        To encounter this the method <code>headerExists()</code> can be used to check the existance of a header.</para>
+        To encounter this the method <methodname>headerExists()</methodname> can be used to check the existance of a header.</para>
 
         <programlisting language="php"><![CDATA[
 // get the message object
@@ -249,7 +249,7 @@ if( isset($message->cc) ) { // or $message->headerExists('cc');
 ]]></programlisting>
 
         <para>If you have multiple headers with the same name- i.e. the Received headers- you might want an array
-        instead of a string. In this case, use the <code>getHeader()</code> method.</para>
+        instead of a string. In this case, use the <methodname>getHeader()</methodname> method.</para>
 
         <programlisting language="php"><![CDATA[
 // get header as property - the result is always a string,
@@ -273,7 +273,7 @@ if (is_string($received)) {
 }
 ]]></programlisting>
 
-        <para>The method <code>getHeaders()</code> returns all headers as array with the lower-cased name as
+        <para>The method <methodname>getHeaders()</methodname> returns all headers as array with the lower-cased name as
         key and the value as and array for multiple headers or as string for single headers.</para>
 
         <programlisting language="php"><![CDATA[
@@ -290,7 +290,7 @@ foreach ($message->getHeaders() as $name => $value) {
 ]]></programlisting>
 
         <para>If you don't have a multipart message, fetching the content is easily done via
-        <code>getContent()</code>. Unlike the headers, the content is only fetched when needed (aka late-fetch).</para>
+        <methodname>getContent()</methodname>. Unlike the headers, the content is only fetched when needed (aka late-fetch).</para>
 
         <programlisting language="php"><![CDATA[
 // output message content for HTML
@@ -299,11 +299,11 @@ echo $message->getContent();
 echo '</pre>';
 ]]></programlisting>
 
-        <para>Checking for multipart messages is done with the method <code>isMultipart()</code>. If you have
+        <para>Checking for multipart messages is done with the method <methodname>isMultipart()</methodname>. If you have
         multipart message you can get an instance of <classname>Zend_Mail_Part</classname> with the method
-        <code>getPart()</code>. <classname>Zend_Mail_Part</classname> is the base class of <classname>Zend_Mail_Message</classname>,
-        so you have the same methods: <code>getHeader()</code>, <code>getHeaders()</code>, <code>getContent()</code>,
-        <code>getPart()</code>, <code>isMultipart</code> and the properties for headers.</para>
+        <methodname>getPart()</methodname>. <classname>Zend_Mail_Part</classname> is the base class of <classname>Zend_Mail_Message</classname>,
+        so you have the same methods: <methodname>getHeader()</methodname>, <methodname>getHeaders()</methodname>, <methodname>getContent()</methodname>,
+        <methodname>getPart()</methodname>, <code>isMultipart</code> and the properties for headers.</para>
 
         <programlisting language="php"><![CDATA[
 // get the first none multipart part
@@ -317,7 +317,7 @@ echo $part->getContent();
 ]]></programlisting>
 
         <para><classname>Zend_Mail_Part</classname> also implements <code>RecursiveIterator</code>, which makes it easy to scan through all parts. And
-        for easy output, it also implements the magic method <code>__toString()</code>, which returns the content.</para>
+        for easy output, it also implements the magic method <methodname>__toString()</methodname>, which returns the content.</para>
 
         <programlisting language="php"><![CDATA[
 // output first text/plain part
@@ -345,8 +345,8 @@ if (!$foundPart) {
 
         <para>Maildir and IMAP support storing flags. The class <classname>Zend_Mail_Storage</classname> has constants for all known
         maildir and IMAP system flags, named <classname>Zend_Mail_Storage::FLAG_&lt;flagname&gt;</classname>. To check
-        for flags <classname>Zend_Mail_Message</classname> has a method called <code>hasFlag()</code>. With
-        <code>getFlags()</code> you'll get all set flags.</para>
+        for flags <classname>Zend_Mail_Message</classname> has a method called <methodname>hasFlag()</methodname>. With
+        <methodname>getFlags()</methodname> you'll get all set flags.</para>
 
         <programlisting language="php"><![CDATA[
 // find unread messages
@@ -388,7 +388,7 @@ foreach ($flags as $flag) {
 
         <para>As IMAP allows user or client defined flags, you could get flags that don't have a constant in
         <classname>Zend_Mail_Storage</classname>. Instead, they are returned as strings and can be checked the same way with
-        <code>hasFlag()</code>.</para>
+        <methodname>hasFlag()</methodname>.</para>
 
         <programlisting language="php"><![CDATA[
 // check message for client defined flags $IsSpam, $SpamTested
@@ -452,8 +452,8 @@ $mail = new Zend_Mail_Storage_Imap(array('host'     => 'example.com',
             With the method getFolders($root = null) you can get the folder hierarchy starting with the root folder or
             the given folder. It's returned as an instance of <classname>Zend_Mail_Storage_Folder</classname>, which implements
             <code>RecursiveIterator</code> and all children are also instances of <classname>Zend_Mail_Storage_Folder</classname>. Each of
-            these instances has a local and a global name returned by the methods <code>getLocalName()</code> and
-            <code>getGlobalName()</code>. The global name is the absolute name from the root folder (including
+            these instances has a local and a global name returned by the methods <methodname>getLocalName()</methodname> and
+            <methodname>getGlobalName()</methodname>. The global name is the absolute name from the root folder (including
             delimiters), the local name is the name in the parent folder.
         </para>
 
@@ -485,9 +485,9 @@ $mail = new Zend_Mail_Storage_Imap(array('host'     => 'example.com',
 
         <para>
             If you use the iterator, the key of the current element is the local name. The global name is also returned
-            by the magic method <code>__toString()</code>. Some folders may not be selectable, which means they can't
+            by the magic method <methodname>__toString()</methodname>. Some folders may not be selectable, which means they can't
             store messages and selecting them results in an error. This can be checked with the method
-            <code>isSelectable()</code>. So it's very easy to output the whole tree in a view:
+            <methodname>isSelectable()</methodname>. So it's very easy to output the whole tree in a view:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -508,8 +508,8 @@ echo '</select>';
 ]]></programlisting>
 
         <para>
-            The current selected folder is returned by the method <code>getSelectedFolder()</code>. Changing the folder
-            is done with the method <code>selectFolder()</code>, which needs the global name as parameter. If you want
+            The current selected folder is returned by the method <methodname>getSelectedFolder()</methodname>. Changing the folder
+            is done with the method <methodname>selectFolder()</methodname>, which needs the global name as parameter. If you want
             to avoid to write delimiters you can also use the properties of a <classname>Zend_Mail_Storage_Folder</classname> instance:
         </para>
 
@@ -558,8 +558,8 @@ foreach ($mail as $message) {
 
             <para>
             <classname>Zend_Mail_Storage_Mbox</classname>, <classname>Zend_Mail_Storage_Folder_Mbox</classname>, <classname>Zend_Mail_Storage_Maildir</classname> and
-            <classname>Zend_Mail_Storage_Folder_Maildir</classname> implement the magic methods <code>__sleep()</code> and
-            <code>__wakeup()</code>, which means they are serializable. This avoids parsing the files or directory tree
+            <classname>Zend_Mail_Storage_Folder_Maildir</classname> implement the magic methods <methodname>__sleep()</methodname> and
+            <methodname>__wakeup()</methodname>, which means they are serializable. This avoids parsing the files or directory tree
             more than once. The disadvantage is that your Mbox or Maildir storage should not change. Some easy checks
             may be done, like reparsing the current Mbox file if the modification time changes, or reparsing the folder
             structure if a folder has vanished (which still results in an error, but you can search for another folder
@@ -686,14 +686,14 @@ $mail = new Example_Mail_Pop3_Knock(array('host'        => 'localhost',
             <para>
             <classname>Zend_Mail_Storage_Writable_Maildir</classname> has support for Maildir++ quotas. It's disabled by default,
             but it's possible to use it manually, if the automatic checks are not desired (this means
-            <code>appendMessage()</code>, <code>removeMessage()</code> and <code>copyMessage()</code> do no checks
+            <methodname>appendMessage()</methodname>, <methodname>removeMessage()</methodname> and <methodname>copyMessage()</methodname> do no checks
             and do not add entries to the maildirsize file). If enabled, an exception is thrown if you try to write
             to the maildir and it's already over quota.
             </para>
 
             <para>
-            There are three methods used for quotas: <code>getQuota()</code>, <code>setQuota()</code> and
-            <code>checkQuota()</code>:
+            There are three methods used for quotas: <methodname>getQuota()</methodname>, <methodname>setQuota()</methodname> and
+            <methodname>checkQuota()</methodname>:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -706,7 +706,7 @@ echo 'You are ', $mail->checkQuota() ? 'over quota' : 'not over quota', "\n";
 ]]></programlisting>
 
             <para>
-            <code>checkQuota()</code> can also return a more detailed response:
+            <methodname>checkQuota()</methodname> can also return a more detailed response:
             </para>
 
             <programlisting language="php"><![CDATA[
@@ -722,7 +722,7 @@ echo $quota['size'], ' of ', $quota['quota']['size'], ' octets';
 
             <para>
             If you want to specify your own quota instead of using the one specified in the maildirsize file you
-            can do with <code>setQuota()</code>:
+            can do with <methodname>setQuota()</methodname>:
             </para>
 
             <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Measure-Creation.xml

@@ -60,7 +60,7 @@ echo $unit;
             strings instead. <classname>Zend_Measure_Number</classname> uses the BCMath extension
             to support arbitrary precision, as shown in the example below, to avoid limitations in
             many PHP functions, such as
-            <ulink url="http://php.net/bin2dec"><code>bin2dec()</code></ulink>.
+            <ulink url="http://php.net/bin2dec"><methodname>bin2dec()</methodname></ulink>.
         </para>
 
         <example id="zend.measure.creation.string.example-1">

documentation/manual/en/module_specs/Zend_Measure-Edit.xml

@@ -55,7 +55,7 @@
 
         <para>
             Probably the most important feature is the conversion into different units of measurement. The conversion of
-            a unit can be done any number of times using the method <code>convertTo()</code>. Units of measurement can
+            a unit can be done any number of times using the method <methodname>convertTo()</methodname>. Units of measurement can
             only be converted to other units of the same type (class). Therefore, it is not possible to convert (e.g.) a
             length into a weight, which would might encourage poor programming practices and allow errors to propagate
             without exceptions.
@@ -90,7 +90,7 @@ print "Ton:".$unit->convertTo(Zend_Measure_Weight::TON, 3);
         <title>Add and subtract</title>
 
         <para>
-            Measurements can be added together using <code>add()</code> and subtracted using <code>sub()</code>. Each
+            Measurements can be added together using <methodname>add()</methodname> and subtracted using <methodname>sub()</methodname>. Each
             addition will create a new object for the result. The actual object will never be changed by the class. The
             new object will be of the same type as the originating object. Dynamic objects support a fluid style of
             programming, where complex sequences of operations can be nested without risk of side-effects altering the
@@ -118,7 +118,7 @@ echo $sum; // outputs "300 cm"
             <para>
                 Adding one object to another will automatically convert it to the correct unit. It is not necessary to
                 call
-                <link linkend="zend.measure.edit.convert"><code>convertTo()</code>
+                <link linkend="zend.measure.edit.convert"><methodname>convertTo()</methodname>
                 </link>
                 before adding different units.
             </para>
@@ -150,7 +150,7 @@ echo $sum;
         <title>Compare</title>
 
         <para>
-            Measurements can also be compared, but without automatic unit conversion. Thus, <code>equals()</code>
+            Measurements can also be compared, but without automatic unit conversion. Thus, <methodname>equals()</methodname>
             returns <constant>TRUE</constant>, only if both the value and the unit of measure are identical.
         </para>
 
@@ -194,7 +194,7 @@ if ($unit->equals($unit2)) {
         <title>Compare</title>
 
         <para>
-            To determine if a measurement is less than or greater than another, use <code>compare()</code>, which
+            To determine if a measurement is less than or greater than another, use <methodname>compare()</methodname>, which
             returns 0, -1 or 1 depending on the difference between the two objects. Identical measurements will return
             0. Lesser ones will return a negative, greater ones a positive value.
         </para>
@@ -221,7 +221,7 @@ print "Greater:".$unit3->compare($unit2);
         <title>Manually change values</title>
 
         <para>
-            To change the value of a measurement explicitly, use <code>setValue()</code>. to overwrite the current
+            To change the value of a measurement explicitly, use <methodname>setValue()</methodname>. to overwrite the current
             value. The parameters are the same as the constructor.
         </para>
 
@@ -251,7 +251,7 @@ echo $unit;
         <title>Manually change types</title>
 
         <para>
-            To change the type of a measurement without altering its value use <code>setType()</code>.
+            To change the type of a measurement without altering its value use <methodname>setType()</methodname>.
         </para>
 
         <example id="zend.measure.edit.changetype.example-1">

documentation/manual/en/module_specs/Zend_Measure-Output.xml

@@ -68,7 +68,7 @@ echo $unit;
         <title>Outputting values</title>
 
         <para>
-            The value of a measurement can be output using <code>getValue()</code>.
+            The value of a measurement can be output using <methodname>getValue()</methodname>.
             <example id="zend.measure.output.value.example-1">
                 <title>Output a value</title>
                 <programlisting language="php"><![CDATA[
@@ -84,7 +84,7 @@ echo $unit->getValue();
         </para>
 
         <para>
-            The <code>getValue()</code> method accepts an optional parameter '<code>round</code>' which allows to
+            The <methodname>getValue()</methodname> method accepts an optional parameter '<code>round</code>' which allows to
             define a precision for the generated output. The standard precision is '<code>2</code>'.
         </para>
     </sect2>
@@ -94,7 +94,7 @@ echo $unit->getValue();
         <title>Output with unit of measurement</title>
 
         <para>
-            The function <code>getType()</code> returns the current unit of measurement.
+            The function <methodname>getType()</methodname> returns the current unit of measurement.
             <example id="zend.measure.output.unit.example-1">
                 <title>Outputting units</title>
                 <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Memory-MemoryManager.xml

@@ -173,7 +173,7 @@ function foo()
 
             <para>
                 You can retrieve or set the memory limit setting using the
-                <code>getMemoryLimit()</code> and <code>setMemoryLimit($newLimit)</code>
+                <methodname>getMemoryLimit()</methodname> and <methodname>setMemoryLimit($newLimit)</methodname>
                 methods:
                 <programlisting language="php"><![CDATA[
 $oldLimit = $memoryManager->getMemoryLimit();  // Get memory limit in bytes
@@ -206,7 +206,7 @@ $memoryManager->setMemoryLimit($newLimit);     // Set memory limit in bytes
 
             <para>
                 You can retrieve or set the minimum size using the
-                <code>getMinSize()</code> and <code>setMinSize($newSize)</code>
+                <methodname>getMinSize()</methodname> and <methodname>setMinSize($newSize)</methodname>
                 methods:
                 <programlisting language="php"><![CDATA[
 $oldMinSize = $memoryManager->getMinSize();  // Get MinSize in bytes

documentation/manual/en/module_specs/Zend_Memory-MemoryObjects.xml

@@ -9,7 +9,7 @@
         <title>Movable</title>
 
         <para>
-            Create movable memory objects using the <code>create([$data])</code>
+            Create movable memory objects using the <methodname>create([$data])</methodname>
             method of the memory manager:
             <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->create($data);
@@ -28,7 +28,7 @@ $memObject = $memoryManager->create($data);
         <title>Locked</title>
 
         <para>
-            Create locked memory objects using the <code>createLocked([$data])</code>
+            Create locked memory objects using the <methodname>createLocked([$data])</methodname>
             method of the memory manager:
             <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->createLocked($data);
@@ -88,7 +88,7 @@ $memObject->value = substr($memObject->value, $start, $length);
 
         <para>
             An alternative way to access memory object data is to use the
-            <link linkend="zend.memory.memory-objects.api.getRef"><code>getRef()</code></link>
+            <link linkend="zend.memory.memory-objects.api.getRef"><methodname>getRef()</methodname></link>
             method. This method <emphasis>must</emphasis> be used for PHP
             versions before 5.2. It also may have to be used in some other
             cases for performance reasons.
@@ -112,7 +112,7 @@ public function &getRef();
 ]]></programlisting>
 
             <para>
-                The <code>getRef()</code> method returns reference to the object value.
+                The <methodname>getRef()</methodname> method returns reference to the object value.
             </para>
 
             <para>
@@ -124,15 +124,15 @@ public function &getRef();
             </para>
 
             <para>
-                The <code>getRef()</code> method <emphasis>must</emphasis> be
+                The <methodname>getRef()</methodname> method <emphasis>must</emphasis> be
                 used to access memory object data for PHP versions before 5.2.
             </para>
 
             <para>
                 Tracking changes to data needs additional resources.
-                The <code>getRef()</code> method returns reference to string,
+                The <methodname>getRef()</methodname> method returns reference to string,
                 which is changed directly by user application.
-                So, it's a good idea to use the <code>getRef()</code> method
+                So, it's a good idea to use the <methodname>getRef()</methodname> method
                 for value data processing:
                 <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->create($data);
@@ -156,8 +156,8 @@ for ($count = 0; $count < strlen($value); $count++) {
 public function touch();
 ]]></programlisting>
             <para>
-                The <code>touch()</code> method should be used in common with
-                <code>getRef()</code>. It signals that object value has been changed:
+                The <methodname>touch()</methodname> method should be used in common with
+                <methodname>getRef()</methodname>. It signals that object value has been changed:
                 <programlisting language="php"><![CDATA[
 $memObject = $memoryManager->create($data);
 ...
@@ -188,7 +188,7 @@ public function lock();
 ]]></programlisting>
 
             <para>
-                The <code>lock()</code> methods locks object in memory.
+                The <methodname>lock()</methodname> methods locks object in memory.
                 It should be used to prevent swapping of some objects you choose.
                 Normally, this is not necessary, because the memory manager uses
                 an intelligent algorithm to choose candidates for swapping.
@@ -198,7 +198,7 @@ public function lock();
 
             <para>
                 Locking objects in memory also guarantees that reference
-                returned by the <code>getRef()</code> method is valid until you
+                returned by the <methodname>getRef()</methodname> method is valid until you
                 unlock the object:
                 <programlisting language="php"><![CDATA[
 $memObject1 = $memoryManager->create($data1);
@@ -232,7 +232,7 @@ public function unlock();
 ]]></programlisting>
 
             <para>
-                <code>unlock()</code> method unlocks object when it's no longer
+                <methodname>unlock()</methodname> method unlocks object when it's no longer
                 necessary to be locked. See the example above.
             </para>
 
@@ -247,7 +247,7 @@ public function isLocked();
 ]]></programlisting>
 
             <para>
-                The <code>isLocked()</code> method can be used to check if
+                The <methodname>isLocked()</methodname> method can be used to check if
                 object is locked. It returns <constant>TRUE</constant> if the object
                 is locked, or <constant>FALSE</constant> if it is not locked.
                 This is always <constant>TRUE</constant> for "locked" objects,

documentation/manual/en/module_specs/Zend_Mime.xml

@@ -102,17 +102,17 @@
         <itemizedlist>
             <listitem>
                 <para>
-                    <code>boundary()</code>: Returns the MIME boundary string.
+                    <methodname>boundary()</methodname>: Returns the MIME boundary string.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <code>boundaryLine()</code>: Returns the complete MIME boundary line.
+                    <methodname>boundaryLine()</methodname>: Returns the complete MIME boundary line.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <code>mimeEnd()</code>: Returns the complete MIME end boundary line.
+                    <methodname>mimeEnd()</methodname>: Returns the complete MIME end boundary line.
                 </para>
             </listitem>
         </itemizedlist>

documentation/manual/en/module_specs/Zend_Mime_Message.xml

@@ -58,7 +58,7 @@
 
         <para><code>-&gt;getMime()</code> returns the instance of
         <classname>Zend_Mime</classname> that will be used to render the message when
-        <code>generateMessage()</code> is called.</para>
+        <methodname>generateMessage()</methodname> is called.</para>
 
         <para><code>-&gt;generateMessage()</code> renders the <classname>Zend_Mime_Message</classname>
         content to a string.</para>

documentation/manual/en/module_specs/Zend_Mime_Part.xml

@@ -41,13 +41,13 @@ public $language;
   <sect2 id="zend.mime.part.methods">
     <title>Methods for rendering the message part to a string</title>
 
-    <para><code>getContent()</code> returns the encoded content of the
+    <para><methodname>getContent()</methodname> returns the encoded content of the
     MimePart as a string using the encoding specified in the attribute
     $encoding. Valid values are Zend_Mime::ENCODING_* Characterset conversions are
     not performed.</para>
 
     <para>
-        <code>getHeaders()</code> returns the Mime-Headers for the
+        <methodname>getHeaders()</methodname> returns the Mime-Headers for the
         MimePart as generated from the information in the publicly accessible
         attributes. The attributes of the object need to be set correctly before
         this method is called.

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

@@ -28,7 +28,7 @@
             entirely empty, or take an array or a
             <classname>Zend_Config</classname> object with pages to put in the
             container. Each page in the given array/config will eventually be
-            passed to the <code>addPage()</code> method of the container class,
+            passed to the <methodname>addPage()</methodname> method of the container class,
             which means that each element in the array/config can be an array or
             a config object, or a <classname>Zend_Navigation_Page</classname>
             instance.
@@ -405,8 +405,8 @@ $container = new Zend_Navigation($config);
 
         <para>
             Adding pages to a container can be done with the methods
-            <code>addPage()</code>, <code>addPages()</code>, or
-            <code>setPages()</code>. See examples below for explanation.
+            <methodname>addPage()</methodname>, <methodname>addPages()</methodname>, or
+            <methodname>setPages()</methodname>. See examples below for explanation.
         </para>
 
         <example id="zend.navigation.containers.adding.example">
@@ -455,8 +455,8 @@ $container->setPages($pages);
         <title>Removing pages</title>
 
         <para>
-            Removing pages can be done with <code>removePage()</code> or
-            <code>removePages()</code>. The first method accepts a an instance
+            Removing pages can be done with <methodname>removePage()</methodname> or
+            <methodname>removePages()</methodname>. The first method accepts a an instance
             of a page, or an integer. The integer corresponds to the
             <code>order</code> a page has. The latter method will remove all
             pages in the container.
@@ -503,12 +503,12 @@ $container->removePages();      // removes all pages
 
         <para>
             Containers have finder methods for retrieving pages.
-            They are <code>findOneBy($property, $value)</code>,
-            <code>findAllBy($property, $value)</code>, and
-            <code>findBy($property, $value, $all = false)</code>.
+            They are <methodname>findOneBy($property, $value)</methodname>,
+            <methodname>findAllBy($property, $value)</methodname>, and
+            <methodname>findBy($property, $value, $all = false)</methodname>.
             Those methods will recursively search the container for
             pages matching the given <code>$page->$property == $value</code>.
-            The first method, <code>findOneBy()</code>, will return a
+            The first method, <methodname>findOneBy()</methodname>, will return a
             single page matching the property with the given value, or
             null if it cannot be found. The second method will return
             all pages with a property matching the given value. The third
@@ -519,13 +519,13 @@ $container->removePages();      // removes all pages
         <para>
             The finder methods can also be used magically by appending the
             property name to <code>findBy</code>, <code>findOneBy</code>, or
-            <code>findAllBy</code>, e.g. <code>findOneByLabel('Home')</code> to
+            <code>findAllBy</code>, e.g. <methodname>findOneByLabel('Home')</methodname> to
             return the first matching page with label <code>Home</code>.
-            Other combinations are <code>findByLabel(...)</code>,
-            <code>findOnyByTitle(...)</code>,
-            <code>findAllByController(...)</code>, etc. Finder
+            Other combinations are <methodname>findByLabel(...)</methodname>,
+            <methodname>findOnyByTitle(...)</methodname>,
+            <methodname>findAllByController(...)</methodname>, etc. Finder
             methods also work on custom properties, such as
-            <code>findByFoo('bar')</code>.
+            <methodname>findByFoo('bar')</methodname>.
         </para>
 
         <example id="zend.navigation.containers.finding.example">
@@ -679,14 +679,14 @@ foreach ($it as $page) {
         <title>Other operations</title>
 
         <para>
-            The method <code>hasPage(Zend_Navigation_Page $page)</code> checks
-            if the container has the given page. The method <code>hasPages()</code>
+            The method <methodname>hasPage(Zend_Navigation_Page $page)</methodname> checks
+            if the container has the given page. The method <methodname>hasPages()</methodname>
             checks if there are any pages in the container, and is equivalent
             to <code>count($container) > 1</code>.
         </para>
 
         <para>
-            The <code>toArray()</code> method converts the container and the
+            The <methodname>toArray()</methodname> method converts the container and the
             pages in it to an array. This can be useful for serializing and
             debugging.
         </para>

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

@@ -77,7 +77,7 @@ $container = new Zend_Navigation(array(
         </para>
 
         <para>
-            Since release 1.9, the <code>_renderDeepestMenu()</code> method in
+            Since release 1.9, the <methodname>_renderDeepestMenu()</methodname> method in
             <classname>Zend_View_Helper_Navigation_Menu</classname> will accept
             active pages at one level below <code>minDepth</code>, as long as
             the page has children.

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

@@ -12,9 +12,9 @@
 
     <para>
         Option keys are mapped to <code>set</code> methods. This means that
-        the option <code>order</code> maps to the method <code>setOrder()</code>,
+        the option <code>order</code> maps to the method <methodname>setOrder()</methodname>,
         and <code>reset_params</code> maps to the method
-        <code>setResetParams()</code>. If there is no setter method for
+        <methodname>setResetParams()</methodname>. If there is no setter method for
         the option, it will be set as a custom property of the page.
     </para>
 
@@ -82,7 +82,7 @@
                 <row>
                     <entry><code>rel</code></entry>
                     <entry><type>Array</type></entry>
-                    <entry><code>array()</code></entry>
+                    <entry><methodname>array()</methodname></entry>
                     <entry>
                         Specifies forward relations for the page.
                         Each element in the array is a key-value pair, where the
@@ -99,7 +99,7 @@
                 <row>
                     <entry><code>rev</code></entry>
                     <entry><type>Array</type></entry>
-                    <entry><code>array()</code></entry>
+                    <entry><methodname>array()</methodname></entry>
                     <entry>
                         Specifies reverse relations for the page. Works exactly
                         like <code>rel</code>.
@@ -170,7 +170,7 @@
                     <entry>
                         Child pages of the page. This could be an <type>Array</type>
                         or <classname>Zend_Config</classname> object containing either page
-                        options that can be passed to the <code>factory()</code>
+                        options that can be passed to the <methodname>factory()</methodname>
                         method, or actual <classname>Zend_Navigation_Page</classname>
                         instances, or a mixture of both.
                     </entry>
@@ -183,9 +183,9 @@
         <title>Custom properties</title>
         <para>
             All pages support setting and getting of custom properties by
-            use of the magic methods <code>__set($name, $value)</code>,
-            <code>__get($name)</code>, <code>__isset($name)</code> and
-            <code>__unset($name)</code>. Custom properties may have any value,
+            use of the magic methods <methodname>__set($name, $value)</methodname>,
+            <methodname>__get($name)</methodname>, <methodname>__isset($name)</methodname> and
+            <methodname>__unset($name)</methodname>. Custom properties may have any value,
             and will be included in the array that is returned from
             <code>$page->toArray()</code>, which means that pages
             can be serialized/deserialized successfully even if the pages

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

@@ -6,14 +6,14 @@
     <para>
         When extending <classname>Zend_Navigation_Page</classname>, there is
         usually no need to override the constructor or the methods
-        <code>setOptions()</code> or <code>setConfig()</code>. The page
+        <methodname>setOptions()</methodname> or <methodname>setConfig()</methodname>. The page
         constructor takes a single parameter, an <type>Array</type> or a
         <classname>Zend_Config</classname> object, which is passed to
-        <code>setOptions()</code> or <code>setConfig()</code> respectively.
-        Those methods will in turn call <code>set()</code> method, which
+        <methodname>setOptions()</methodname> or <methodname>setConfig()</methodname> respectively.
+        Those methods will in turn call <methodname>set()</methodname> method, which
         will map options to native or custom properties. If the option
         <code>internal_id</code> is given, the method will first look for a
-        method named <code>setInternalId()</code>, and pass the option to this
+        method named <methodname>setInternalId()</methodname>, and pass the option to this
         method if it exists. If the method does not exist, the option will be
         set as a custom property of the page, and be accessible via
         <code>$internalId = $page->internal_id;</code> or
@@ -25,7 +25,7 @@
 
         <para>
             The only thing a custom page class needs to implement is the
-            <code>getHref()</code> method.
+            <methodname>getHref()</methodname> method.
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -44,8 +44,8 @@ class My_Simple_Page extends Zend_Navigation_Page
 
         <para>
             When adding properties to an extended page, there is no need
-            to override/modify <code>setOptions()</code> or
-            <code>setConfig()</code>.
+            to override/modify <methodname>setOptions()</methodname> or
+            <methodname>setConfig()</methodname>.
         </para>
 
         <programlisting language="php"><![CDATA[

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

@@ -7,8 +7,8 @@
         MVC pages are defined using MVC parameters known from the
         <classname>Zend_Controller</classname> component. An MVC page will use
         <classname>Zend_Controller_Action_Helper_Url</classname> internally
-        in the <code>getHref()</code> method to generate hrefs, and
-        the <code>isActive()</code> method will intersect the
+        in the <methodname>getHref()</methodname> method to generate hrefs, and
+        the <methodname>isActive()</methodname> method will intersect the
         <classname>Zend_Controller_Request_Abstract</classname> params
         with the page's params to determine if the page is active.
     </para>
@@ -55,7 +55,7 @@
                 <row>
                     <entry><code>params</code></entry>
                     <entry><type>Array</type></entry>
-                    <entry><code>array()</code></entry>
+                    <entry><methodname>array()</methodname></entry>
                     <entry>
                         User params to use when generating href to the page.
                     </entry>
@@ -195,7 +195,7 @@ $page->isActive(); // returns false
 
         <para>
             Routes can be used with MVC pages. If a page has a route, this
-            route will be used in <code>getHref()</code> to generate the URL
+            route will be used in <methodname>getHref()</methodname> to generate the URL
             for the page.
         </para>
 
@@ -205,7 +205,7 @@ $page->isActive(); // returns false
                     Note that when using the <code>route</code> property in a
                     page, you should also specify the default params that the
                     route defines (module, controller, action, etc.), otherwise
-                    the <code>isActive()</code> method will not be able to
+                    the <methodname>isActive()</methodname> method will not be able to
                     determine if the page is active. The reason for this is that
                     there is currently no way to get the default params from a
                     <classname>Zend_Controller_Router_Route_Interface</classname> object,

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

@@ -289,7 +289,7 @@ if ($_SERVER['REQUEST_METHOD'] == 'GET' &&
         <para>
             If you compare this example with previous examples split in to
             separate pages, you will see only the one
-            difference besides the dispatch code: <code>unset($_GET['openid_action'])</code>. This
+            difference besides the dispatch code: <methodname>unset($_GET['openid_action'])</methodname>. This
             call to <code>unset</code> is necessary to route the next request to main
             handler.
         </para>

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

@@ -37,16 +37,16 @@
         <para>
             If you've ever used the SPL interface
             <ulink url="http://www.php.net/~helly/php/ext/spl/interfaceCountable.html"><code>Countable</code></ulink>,
-            you're familiar with <code>count()</code>. As used with
+            you're familiar with <methodname>count()</methodname>. As used with
             <classname>Zend_Paginator</classname>, this is the total number of items
             in the data collection.
             Additionally, the <classname>Zend_Paginator</classname> instance provides a method
-            <code>countAllItems()</code> that proxies to the adapter
-            <code>count()</code> method.
+            <methodname>countAllItems()</methodname> that proxies to the adapter
+            <methodname>count()</methodname> method.
         </para>
 
         <para>
-            The <code>getItems()</code> method is only slightly more
+            The <methodname>getItems()</methodname> method is only slightly more
             complicated. For this, your adapter is supplied with an offset and
             the number of items to display per page. You must return the
             appropriate slice of data. For an array, that would be:
@@ -71,7 +71,7 @@ return array_slice($this->_array, $offset, $itemCountPerPage);
         <para>
             Creating your own scrolling style requires that you implement
             <classname>Zend_Paginator_ScrollingStyle_Interface</classname>, which defines
-            a single method, <code>getPages()</code>. Specifically,
+            a single method, <methodname>getPages()</methodname>. Specifically,
         </para>
 
         <para>
@@ -127,7 +127,7 @@ Zend_Paginator::addScrollingStylePrefixPath($prefix, $path);
             <classname>Zend_Paginator</classname> can be told to cache the data it has already
             passed on, preventing the adapter from fetching them each time they are used.
             To tell paginator to automatically cache the adapter's data, just pass to
-            its <code>setCache()</code> method a <classname>Zend_Cache_Core</classname> instance.
+            its <methodname>setCache()</methodname> method a <classname>Zend_Cache_Core</classname> instance.
         </para>
 
         <para>
@@ -143,7 +143,7 @@ Zend_Paginator::setCache($cache);
         <para>
             As far as <classname>Zend_Paginator</classname> has got a <classname>Zend_Cache_Core</classname> instance, data will
             be cached. Sometimes you would like not to cache data even if you already passed
-            a cache instance. You should then use <code>setCacheEnable()</code> for that.
+            a cache instance. You should then use <methodname>setCacheEnable()</methodname> for that.
         </para>
 
         <para>
@@ -160,7 +160,7 @@ $paginator->setCacheEnable(false);
         <para>
             When a cache is set, data are automatically stored in it and pulled out from
             it. It then can be useful to empty the cache manually. You can get this done by
-            calling <code>clearPageItemCache($pageNumber)</code>.
+            calling <methodname>clearPageItemCache($pageNumber)</methodname>.
             If you don't pass any parameter, the whole cache will be empty. You can optionally
             pass a parameter representing the page number to empty in the cache:
         </para>
@@ -201,7 +201,7 @@ $paginator->setItemCountPerPage(2);
 
         <para>
             It is also possible to see the data in cache and ask for them directly.
-            <code>getPageItemCache()</code> can be used for that:
+            <methodname>getPageItemCache()</methodname> can be used for that:
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_ProgressBar.xml

@@ -44,7 +44,7 @@ $progressBar->finish();
             of the loop, the progressbar status is set to finished.
         </para>
         <para>
-            You can also call the <code>update()</code> method of
+            You can also call the <methodname>update()</methodname> method of
             <classname>Zend_ProgressBar</classname> without arguments, which just
             recalculates ETA and notifies the adapter. This is useful when there
             is no data update but you want the progressbar to be updated.
@@ -58,7 +58,7 @@ $progressBar->finish();
             you can give the name of a session namespace as fourth argument
             to the constructor. In that case, the progressbar will not notify
             the adapter within the constructor, but only when you call
-            <code>update()</code> or <code>finish()</code>. Also the current
+            <methodname>update()</methodname> or <methodname>finish()</methodname>. Also the current
             value, the status text and the start time for ETA calculation will
             be fetched in the next request run again.
         </para>

documentation/manual/en/module_specs/Zend_ProgressBar_Adapter_JsPull.xml

@@ -11,8 +11,8 @@
         like the JSON 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
-        <code>update()</code> is called or <constant>TRUE</constant>, when
-        <code>finish()</code> is called.
+        <methodname>update()</methodname> is called or <constant>TRUE</constant>, when
+        <methodname>finish()</methodname> is called.
     </para>
     <para>
         You can set the adapter options either via the <code>set*</code> methods

documentation/manual/en/module_specs/Zend_Reflection-Reference.xml

@@ -21,7 +21,7 @@
 
     <para>
         Each reflection object in <classname>Zend_Reflection</classname> overrides the
-        <code>getDocblock()</code> method to return an instance of
+        <methodname>getDocblock()</methodname> method to return an instance of
         <classname>Zend_Reflection_Docblock</classname>. This class provides introspection
         into the docblocks and annotation tags.
     </para>
@@ -49,43 +49,43 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>getContents()</code>: returns the full contents of the
+                <methodname>getContents()</methodname>: returns the full contents of the
                 docblock.
             </para></listitem>
 
             <listitem><para>
-                <code>getStartLine()</code>: returns the starting position of
+                <methodname>getStartLine()</methodname>: returns the starting position of
                 the docblock within the defining file.
             </para></listitem>
 
             <listitem><para>
-                <code>getEndLine()</code>: get last line of docblock within the
+                <methodname>getEndLine()</methodname>: get last line of docblock within the
                 defining file.
             </para></listitem>
 
             <listitem><para>
-                <code>getShortDescription()</code>: get the short, one-line
+                <methodname>getShortDescription()</methodname>: get the short, one-line
                 description (usually the first line of the docblock).
             </para></listitem>
 
             <listitem><para>
-                <code>getLongDescription()</code>: get the long description from
+                <methodname>getLongDescription()</methodname>: get the long description from
                 the docblock.
             </para></listitem>
 
             <listitem><para>
-                <code>hasTag($name)</code>: determine if the docblock has the
+                <methodname>hasTag($name)</methodname>: determine if the docblock has the
                 given annotation tag.
             </para></listitem>
 
             <listitem><para>
-                <code>getTag($name)</code>: Retrieve the given annotation tag
+                <methodname>getTag($name)</methodname>: Retrieve the given annotation tag
                 reflection object, or a boolean <constant>FALSE</constant> if it's not
                 present.
             </para></listitem>
 
             <listitem><para>
-                <code>getTags($filter)</code>: Retrieve all tags, or all tags
+                <methodname>getTags($filter)</methodname>: Retrieve all tags, or all tags
                 matching the given <code>$filter</code> string. The tags
                 returned will be an array of
                 <classname>Zend_Reflection_Docblock_Tag</classname> objects.
@@ -110,16 +110,16 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>factory($tagDocblockLine)</code>: instantiate the
+                <methodname>factory($tagDocblockLine)</methodname>: instantiate the
                 appropriate tag reflection class and return it.
             </para></listitem>
 
             <listitem><para>
-                <code>getName()</code>: return the annotation tag name.
+                <methodname>getName()</methodname>: return the annotation tag name.
             </para></listitem>
 
             <listitem><para>
-                <code>getDescription()</code>: return the annotation
+                <methodname>getDescription()</methodname>: return the annotation
                 description.
             </para></listitem>
         </itemizedlist>
@@ -138,11 +138,11 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>getType()</code>: return the parameter variable type.
+                <methodname>getType()</methodname>: return the parameter variable type.
             </para></listitem>
 
             <listitem><para>
-                <code>getVariableName()</code>: return the parameter variable
+                <methodname>getVariableName()</methodname>: return the parameter variable
                 name.
             </para></listitem>
         </itemizedlist>
@@ -162,7 +162,7 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>getType()</code>: return the return type.
+                <methodname>getType()</methodname>: return the return type.
             </para></listitem>
         </itemizedlist>
     </sect2>
@@ -178,17 +178,17 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>getFileName()</code>: retrieve the filename of the file
+                <methodname>getFileName()</methodname>: retrieve the filename of the file
                 being reflected.
             </para></listitem>
 
             <listitem><para>
-                <code>getStartLine()</code>: retrieve the starting line of the
+                <methodname>getStartLine()</methodname>: retrieve the starting line of the
                 file (always "1").
             </para></listitem>
 
             <listitem><para>
-                <code>getEndLine()</code> retrieve the last line / number of
+                <methodname>getEndLine()</methodname> retrieve the last line / number of
                 lines in the file.
             </para></listitem>
 
@@ -217,7 +217,7 @@
             </para></listitem>
 
             <listitem><para>
-                <code>getContents()</code>: retrieve the full contents of the
+                <methodname>getContents()</methodname>: retrieve the full contents of the
                 file.
             </para></listitem>
         </itemizedlist>
@@ -229,7 +229,7 @@
         <para>
             <classname>Zend_Reflection_Class</classname> extends
             <code>ReflectionClass</code>, and follows its API. It adds one
-            additional method, <code>getDeclaringFile()</code>, which may be
+            additional method, <methodname>getDeclaringFile()</methodname>, which may be
             used to retrieve the <classname>Zend_Reflection_File</classname> reflection
             object for the defining file.
         </para>
@@ -242,27 +242,27 @@
 
         <itemizedlist>
             <listitem><para>
-                <code>getDeclaringFile($reflectionClass = 'Zend_Reflection_File')</code>
+                <methodname>getDeclaringFile($reflectionClass = 'Zend_Reflection_File')</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>getDocblock($reflectionClass = 'Zend_Reflection_Docblock')</code>
+                <methodname>getDocblock($reflectionClass = 'Zend_Reflection_Docblock')</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>getInterfaces($reflectionClass = 'Zend_Reflection_Class')</code>
+                <methodname>getInterfaces($reflectionClass = 'Zend_Reflection_Class')</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>getMethod($reflectionClass = 'Zend_Reflection_Method')</code>
+                <methodname>getMethod($reflectionClass = 'Zend_Reflection_Method')</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>getMethods($filter = -1, $reflectionClass = 'Zend_Reflection_Method')</code>
+                <methodname>getMethods($filter = -1, $reflectionClass = 'Zend_Reflection_Method')</methodname>
             </para></listitem>
 
             <listitem><para>
-                <code>getParentClass($reflectionClass = 'Zend_Reflection_Class')</code>
+                <methodname>getParentClass($reflectionClass = 'Zend_Reflection_Class')</methodname>
             </para></listitem>
 
             <listitem><para>
@@ -329,7 +329,7 @@
             </para></listitem>
 
             <listitem><para>
-                <code>getReturn()</code>: retrieve the return type reflection
+                <methodname>getReturn()</methodname>: retrieve the return type reflection
                 object.
             </para></listitem>
         </itemizedlist>
@@ -382,7 +382,7 @@
             </para></listitem>
 
             <listitem><para>
-                <code>getType()</code>: get the parameter type.
+                <methodname>getType()</methodname>: get the parameter type.
             </para></listitem>
         </itemizedlist>
     </sect2>

documentation/manual/en/module_specs/Zend_Registry.xml

@@ -22,7 +22,7 @@
         <title>Setting Values in the Registry</title>
 
         <para>
-            Use the static method <code>set()</code> to store an entry in the registry, .
+            Use the static method <methodname>set()</methodname> to store an entry in the registry, .
         </para>
 
         <example id="zend.registry.using.storing.example">
@@ -35,7 +35,7 @@ Zend_Registry::set('index', $value);
         <para>
             The value returned can be an object, an array, or a scalar.
             You can change the value stored in a specific entry of
-            the registry by calling the <code>set()</code> method to set the entry
+            the registry by calling the <methodname>set()</methodname> method to set the entry
             to a new value.
         </para>
 
@@ -51,7 +51,7 @@ Zend_Registry::set('index', $value);
 
         <para>
             To retrieve an entry from the registry, use the static
-            <code>get()</code> method.
+            <methodname>get()</methodname> method.
         </para>
 
         <example id="zend.registry.using.retrieving.example">
@@ -62,7 +62,7 @@ $value = Zend_Registry::get('index');
         </example>
 
         <para>
-            The <code>getInstance()</code> method returns the singleton registry object.
+            The <methodname>getInstance()</methodname> method returns the singleton registry object.
             This registry object is iterable, making all values stored in the registry easily accessible.
         </para>
 
@@ -115,7 +115,7 @@ $registry = new Zend_Registry(array('index' => $value));
             Once such a <classname>Zend_Registry</classname> object is instantiated,
             you can use it by calling any array object method or by setting it
             as the singleton instance for <classname>Zend_Registry</classname> with the static method
-            <code>setInstance()</code>.
+            <methodname>setInstance()</methodname>.
         </para>
 
         <example id="zend.registry.using.constructing.example-setinstance">
@@ -128,7 +128,7 @@ Zend_Registry::setInstance($registry);
         </example>
 
         <para>
-            The <code>setInstance()</code> method throws a <classname>Zend_Exception</classname>
+            The <methodname>setInstance()</methodname> method throws a <classname>Zend_Exception</classname>
             if the static registry has already been initialized.
         </para>
 
@@ -212,7 +212,7 @@ var_dump($registry->index);
 
         <para>
             To find out if a particular index in the registry
-            has been set, use the static method <code>isRegistered()</code>.
+            has been set, use the static method <methodname>isRegistered()</methodname>.
         </para>
 
         <example id="zend.registry.using.isset.example-isregistered">
@@ -226,7 +226,7 @@ if (Zend_Registry::isRegistered($index)) {
 
         <para>
             To find out if a particular index in a registry
-            array or object has a value, use the <code>isset()</code> function
+            array or object has a value, use the <methodname>isset()</methodname> function
             as you would with an ordinary array.
         </para>
 
@@ -258,7 +258,7 @@ if (isset($registry->index)) {
             If you want to add functionality to the registry, you should
             create a class that extends <classname>Zend_Registry</classname> and
             specify this class to instantiate for the singleton in the static registry.
-            Use the static method <code>setClassName()</code> to specify
+            Use the static method <methodname>setClassName()</methodname> to specify
             the class.
             <note>
                 <para>The class must be a subclass of <classname>Zend_Registry</classname>.</para>
@@ -290,13 +290,13 @@ Zend_Registry::set('index', $value);
         <para>
             Although it is not normally necessary, you can
             unset the singleton instance of the registry, if desired.
-            Use the static method <code>_unsetInstance()</code> to do so.
+            Use the static method <methodname>_unsetInstance()</methodname> to do so.
         </para>
 
         <warning>
             <title>Data Loss Risk</title>
             <para>
-                When you use <code>_unsetInstance()</code>,
+                When you use <methodname>_unsetInstance()</methodname>,
                 all data in the static registry are
                 discarded and cannot be recovered.
             </para>
@@ -304,7 +304,7 @@ Zend_Registry::set('index', $value);
 
         <para>
             You might use this method, for example, if you want to
-            use <code>setInstance()</code> or <code>setClassName()</code>
+            use <methodname>setInstance()</methodname> or <methodname>setClassName()</methodname>
             after the singleton registry object has been initialized.
             Unsetting the singleton instance allows you to use these methods
             even after the singleton registry object has been set. Using

documentation/manual/en/module_specs/Zend_Rest_Client.xml

@@ -32,8 +32,8 @@ echo $client->sayHello('Davey', 'Day')->get(); // "Hello Davey, Good Day"
                 <classname>Zend_Rest_Client</classname> attempts to make remote methods
                 look as much like native methods as possible, the only
                 difference being that you must follow the method call with one
-                of either <code>get()</code>, <code>post()</code>,
-                <code>put()</code> or <code>delete()</code>. This call may be
+                of either <methodname>get()</methodname>, <methodname>post()</methodname>,
+                <methodname>put()</methodname> or <methodname>delete()</methodname>. This call may be
                 made via method chaining or in separate method calls:
             </para>
 
@@ -73,8 +73,8 @@ if ($result->isSuccess()) {
 
         <para>
             In the example above, you can see that we use the request result as
-            an object, to call <code>isSuccess()</code>, and then because of
-            <code>__toString()</code>, we can simply <code>echo</code> the
+            an object, to call <methodname>isSuccess()</methodname>, and then because of
+            <methodname>__toString()</methodname>, we can simply <code>echo</code> the
             object to get the result. <classname>Zend_Rest_Client_Response</classname>
             will allow you to echo any scalar value. For complex types, you can
             use either array or object notation.