[DOCUMENTATION] English:

- fixed tags, no translational changes

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

documentation/manual/en/ref/installation.xml

@@ -11,17 +11,17 @@
 
     <para>
         Installing Zend Framework is extremely simple. Once you have downloaded and extracted the
-        framework, you should add the /library folder in the distribution to the beginning of your
-        include path. You may also want to move the library folder
+        framework, you should add the <filename>/library</filename> folder in the distribution to
+        the beginning of your include path. You may also want to move the library folder
         to another- possibly shared- location on your file system.
 
         <itemizedlist>
             <listitem>
                 <para>
                     <ulink url="http://framework.zend.com/download/latest">Download the latest
-                    stable release.</ulink> This version, available in both <code>.zip</code> and
-                    <code>.tar.gz</code> formats, is a good choice for those who are new to Zend
-                    Framework.
+                    stable release.</ulink> This version, available in both
+                    <filename>.zip</filename> and <filename>.tar.gz</filename> formats, is a
+                    good choice for those who are new to Zend Framework.
                 </para>
             </listitem>
             <listitem>
@@ -46,17 +46,17 @@
                 <para>
                     <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.export.html">
                     Exporting</ulink> is useful if you want to get a particular framework revision
-                    without the <code>.svn</code> directories as created in a working copy.
+                    without the <filename>.svn</filename> directories as created in a working copy.
                 </para>
                 <para>
                     <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.checkout.html">
                     Check out a working copy</ulink> if you want contribute to Zend Framework, a
                     working copy can be updated any time with
                     <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.update.html">
-                    <code>svn update</code></ulink> and changes can be commited to our SVN
+                    svn update</ulink> and changes can be commited to our SVN
                     repository with the
                     <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.commit.html">
-                    <code>svn commit</code></ulink> command.
+                    svn commit</ulink> command.
                 </para>
                 <para>
                     An
@@ -78,8 +78,8 @@
         access the framework classes. Though there are
         <ulink url="http://www.php.net/manual/en/configuration.changes.php">
         several ways to achieve this</ulink>, your PHP
-        <ulink url="http://www.php.net/manual/en/ini.core.php#ini.include-path">
-        <code>include_path</code></ulink> needs to contain the path to the Zend Framework library.
+        <ulink url="http://www.php.net/manual/en/ini.core.php#ini.include-path">include_path</ulink>
+        needs to contain the path to the Zend Framework library.
     </para>
 
     <para>

documentation/manual/en/ref/overview.xml

@@ -17,26 +17,26 @@
         robust, high performance MVC implementation, a database abstraction that is simple to
         use, and a forms component that implements HTML form rendering, validation, and filtering
         so that developers can consolidate all of these operations using one easy-to-use, object
-        oriented interface. Other components, such as Zend_Auth and Zend_Acl, provide user
-        authentication and authorization against all common credential stores. Still others
-        implement client libraries to simply access to the most popular web services available.
-        Whatever your application needs are, you're likely to find a Zend Framework component
-        that can be used to dramatically reduce development time with a thoroughly tested
-        foundation.
+        oriented interface. Other components, such as <classname>Zend_Auth</classname> and
+        <classname>Zend_Acl</classname>, provide user authentication and authorization against
+        all common credential stores. Still others implement client libraries to simply access
+        to the most popular web services available. Whatever your application needs are, you're
+        likely to find a Zend Framework component that can be used to dramatically reduce
+        development time with a thoroughly tested foundation.
     </para>
     <para>
         The principal sponsor of the Zend Framework project is <ulink url="http://www.zend.com">
-        Zend Technologies</ulink>, but many companies have contributed components or significant features
-        to the framework. Companies such as Google, Microsoft, and StrikeIron have partnered
-        with Zend to provide interfaces to web services and other technologies that they wish to make
-        available to Zend Framework developers.
+        Zend Technologies</ulink>, but many companies have contributed components or significant
+        features to the framework. Companies such as Google, Microsoft, and StrikeIron have
+        partnered with Zend to provide interfaces to web services and other technologies that they
+        wish to make available to Zend Framework developers.
     </para>
     <para>
-        Zend Framework could not deliver and support all of these features without the help of the vibrant
-        ZF community. Community members, including contributors, make themselves available
-        on <ulink url="http://framework.zend.com/archives">mailing lists</ulink>, <ulink url="http://www.zftalk.com">
-        IRC channels</ulink>, and other forums. Whatever question you have about ZF, the community
-        is always available to address it.
+        Zend Framework could not deliver and support all of these features without the help of the
+        vibrant ZF community. Community members, including contributors, make themselves available
+        on <ulink url="http://framework.zend.com/archives">mailing lists</ulink>,
+        <ulink url="http://www.zftalk.com">IRC channels</ulink>, and other forums. Whatever
+        question you have about ZF, the community is always available to address it.
     </para>
 </sect1>
 <!--

documentation/manual/en/ref/performance-classloading.xml

@@ -9,8 +9,8 @@
         Framework. Between the sheer number of class files that need to be
         loaded for many components, to the use of plugins that do not have a 1:1
         relationship between their class name and the file system, the various
-        calls to <code>include_once</code> and <code>require_once</code> can be
-        problematic. This chapter intends to provide some concrete solutions to
+        calls to <methodname>include_once</methodname> and <methodname>require_once</methodname>
+        can be problematic. This chapter intends to provide some concrete solutions to
         these issues.
     </para>
 
@@ -40,7 +40,7 @@
             <para>
                 There are two easy ways to ensure this. First, you can hardcode
                 the paths in your php.ini, httpd.conf, or .htaccess. Second, you
-                can use PHP's <code>realpath()</code> function when setting your
+                can use PHP's <methodname>realpath()</methodname> function when setting your
                 include_path:
             </para>
 
@@ -68,7 +68,7 @@ set_include_path(implode(PATH_SEPARATOR, $paths);
 
             <para>
                 However, even so, it's typically a trivial task to simply pass
-                the path to <code>realpath()</code>.
+                the path to <methodname>realpath()</methodname>.
             </para>
         </sect3>
 
@@ -136,7 +136,7 @@ set_include_path(implode(PATH_SEPARATOR, $paths);
 
             <para>
                 First, we'll create a library directory in our project. Inside
-                that directory, we'll symlink our Zend Framework's library/Zend
+                that directory, we'll symlink our Zend Framework's <filename>library/Zend</filename>
                 directory, as well as the necessary directories from our PEAR
                 installation:
             </para>
@@ -156,14 +156,14 @@ library
 
             <para>
                 Next, we'll opt to create our include_path programmatically
-                within our public/index.php file. This allows us to move our
+                within our <filename>public/index.php</filename> file. This allows us to move our
                 code around on the file system, without needing to edit the
                 include_path every time.
             </para>
 
             <para>
                 We'll borrow ideas from each of the suggestions above: we'll use
-                absolute paths, as determined using <code>realpath()</code>;
+                absolute paths, as determined using <methodname>realpath()</methodname>;
                 we'll include the Zend Framework include path early; we've
                 already consolidated include_paths; and we'll put the current
                 directory as the last path. In fact, we're doing really well
@@ -230,7 +230,7 @@ set_include_path(implode(PATH_SEPARATOR, $paths));
                 process trivially, helping boost performance in your production
                 application. It should be noted, however, that if you use this
                 technique, you <emphasis>must</emphasis> utilize autoloading;
-                you can do that from your "public/index.php" file with the
+                you can do that from your "<filename>public/index.php</filename>" file with the
                 following code:
             </para>
 
@@ -284,7 +284,7 @@ Zend_Loader_Autoloader::getInstance();
 
             <listitem><para>
                 <classname>Zend_Filter_Inflector</classname>: filters (used by the
-                ViewRenderer action helper and Zend_Layout)
+                ViewRenderer action helper and <classname>Zend_Layout</classname>)
             </para></listitem>
 
             <listitem><para>

documentation/manual/en/ref/performance-database.xml

@@ -79,7 +79,7 @@
                 select statements is a perfectly legitimate approach,
             </para>
             <para>
-                Run <code>EXPLAIN</code> on your queries, and test a variety of
+                Run <constant>EXPLAIN</constant> on your queries, and test a variety of
                 approaches until you can reliably hit your indices in the most
                 performant way -- and then hardcode the SQL as a class property
                 or constant.
@@ -87,8 +87,8 @@
 
             <para>
                 If the SQL requires variable arguments, provide placeholders in
-                the SQL, and utilize a combination of <code>vsprintf</code> and
-                <code>array_walk</code> to inject the values into the SQL:
+                the SQL, and utilize a combination of <methodname>vsprintf()</methodname> and
+                <methodname>array_walk()</methodname> to inject the values into the SQL:
             </para>
 
             <programlisting role="php"><![CDATA[

documentation/manual/en/ref/performance-localization.xml

@@ -41,13 +41,13 @@
                 </para></listitem>
 
                 <listitem><para>
-                    <emphasis>CSV</emphasis>: uses <code>fgetcsv()</code> to
+                    <emphasis>CSV</emphasis>: uses <methodname>fgetcsv()</methodname> to
                     parse a CSV file and transform it into a native PHP format.
                 </para></listitem>
 
                 <listitem><para>
                     <emphasis>INI</emphasis>: uses
-                    <code>parse_ini_file()</code> to parse an INI file and
+                    <methodname>parse_ini_file()</methodname> to parse an INI file and
                     transform it into a native PHP format. This and the CSV
                     adapter are roughly equivalent performance-wise.
                 </para></listitem>