[DOCUMENTATION] French: sync manual

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

documentation/manual/fr/module_specs/Zend_Application-AvailableResources-CacheManager.xml

@@ -44,7 +44,7 @@ resources.cachemanager.database.frontendBackendAutoload = false
             Ensuite récupérer ce cache à partir du gestionnaire est aussi simple que d'accéder
             à une instance de gestionnaire (<classname>Zend_Cache_Manager</classname>) récupéré
             à partir de <classname>Zend_Application_Resource_Cachemanager</classname> et d'appeler
-            <methodname>$cacheManager->getCache('database');</methodname>. L'exemple ci-dessous
+            <methodname>$cacheManager->getCache('database')</methodname>. L'exemple ci-dessous
             est extrait d'un contrôleur dans lequel la classe de bootstrap est accessible via un
             paramètre du contrôleur frontal (qui est automatiquement assigné lors de l'amorçage).
             Comme vous pouvez le voir, la ressource de gestionnaire de cache implémente la méthode

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

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- EN-Revision: 21109 -->
+<!-- EN-Revision: 22140 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.cache.backends">
     <title>Les backends Zend_Cache</title>
@@ -527,6 +527,22 @@ $cache = Zend_Cache::factory('Core', 'Zend_Cache_Backend_ZendServer_Disk',
             involvement of <acronym>PHP</acronym> or Zend Framework at all.
         </para>
 
+        <note>
+            <para>
+                <classname>Zend_Cache_Frontend_Capture</classname> operates
+                by registering a callback function to be called
+                when the output buffering it uses is cleaned. In order for this to operate
+                correctly, it must be the final output buffer in the request. To guarantee
+                this, the output buffering used by the Dispatcher <emphasis>must</emphasis> be
+                disabled by calling <classname>Zend_Controller_Front</classname>'s
+                <methodname>setParam()</methodname> method, for example,
+                <command>$front->setParam('disableOutputBuffering', true);</command> or adding
+                "resources.frontcontroller.params.disableOutputBuffering = true"
+                to your bootstrap configuration file (assumed <acronym>INI</acronym>) if using
+                <classname>Zend_Application</classname>.
+            </para>
+        </note>
+
         <para>
             The benefits of this cache include a large throughput increase since
             all subsequent requests return the static file and don't need any

documentation/manual/fr/module_specs/Zend_Cache-Frontends.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- EN-Revision: 21130 -->
+<!-- EN-Revision: 22140 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.cache.frontends">
     <title>Les frontends Zend_Cache</title>
@@ -658,7 +658,7 @@ $res = $cache->foobar2('1', '2');
                     quand le buffer de sortie qu'il utilise est nettoyé. Dans le but de fonctionner
                     correctement, il doit être le buffer de sortie final de la requête. Pour
                     garantir ceci, le buffer de sortie utilisé par le distributeur (Dispatcher)
-                    nécessite d'être désactivé en appelant la méthode
+                    <emphasis>doit</emphasis> être désactivé en appelant la méthode
                     <methodname>setParam()</methodname> de
                     <classname>Zend_Controller_Front</classname>, par exemple
                     <command>$front->setParam('disableOutputBuffering', true);</command> ou en
@@ -965,4 +965,43 @@ if ($unTest) {
 ]]></programlisting>
         </sect3>
     </sect2>
+
+    <sect2 id="zend.cache.frontends.capture">
+        <title>Zend_Cache_Frontend_Capture</title>
+
+        <sect3 id="zend.cache.frontends.capture.introduction">
+            <title>Introduction</title>
+
+            <para>
+                <classname>Zend_Cache_Frontend_Capture</classname> is like
+                <classname>Zend_Cache_Frontend_Output</classname> but designed for a complete page.
+                It's impossible to use <classname>Zend_Cache_Frontend_Capture</classname> for
+                caching only a single block. This class is specifically designed to operate in
+                concert only with the <classname>Zend_Cache_Backend_Static</classname> backend to
+                assist in caching entire pages of <acronym>HTML</acronym> / <acronym>XML</acronym>
+                or other content to a physical static file on the local filesystem.
+            </para>
+
+            <para>
+                Please refer to the documentation on
+                <classname>Zend_Cache_Backend_Static</classname> for all use cases pertaining to
+                this class.
+            </para>
+
+            <note>
+                <para>
+                    This frontend operates by registering a callback function to be called
+                    when the output buffering it uses is cleaned. In order for this to operate
+                    correctly, it must be the final output buffer in the request. To guarantee
+                    this, the output buffering used by the Dispatcher <emphasis>must</emphasis> be
+                    disabled by calling <classname>Zend_Controller_Front</classname>'s
+                    <methodname>setParam()</methodname> method, for example,
+                    <command>$front->setParam('disableOutputBuffering', true);</command> or adding
+                    "resources.frontcontroller.params.disableOutputBuffering = true"
+                    to your bootstrap configuration file (assumed <acronym>INI</acronym>) if using
+                    <classname>Zend_Application</classname>.
+                </para>
+            </note>
+        </sect3>
+     </sect2>
 </sect1>

documentation/manual/fr/module_specs/Zend_Uri.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 20799 -->
+<!-- EN-Revision: 22081 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.uri.chapter">
     <title>Zend_Uri</title>
@@ -51,10 +51,10 @@ $uri = Zend_Uri::factory('http');
             <methodname>Zend_Uri::factory()</methodname> <footnote>
                 <para>
                     Actuellement, <classname>Zend_Uri</classname> ne supporte que les schémas
-                    <acronym>HTTP</acronym> et <acronym>HTTPS</acronym>
+                    intégrés <acronym>HTTP</acronym> et <acronym>HTTPS</acronym>
                 </para>
-            </footnote>. Si un schéma non supporté lui est passé, une
-            <classname>Zend_Uri_Exception</classname> sera levée.
+            </footnote>. Si un schéma non supporté lui est passé ou aucune classe n'est spécifié,
+            une <classname>Zend_Uri_Exception</classname> sera levée.
         </para>
 
         <para>
@@ -62,6 +62,40 @@ $uri = Zend_Uri::factory('http');
             <methodname>Zend_Uri::factory()</methodname> retournera une sous-classe d'elle-même
             spécialisée pour le schéma à créer.
         </para>
+
+        <sect3>
+            <title>Creating a New Custom-Class URI</title>
+
+            <para>
+                Starting from Zend Framework 1.10.5, you can specify a custom class to be
+                used when creating the Zend_Uri instance, as a second parameter to the
+                <methodname>Zend_Uri::factory()</methodname> method.
+                This enables you to subclass Zend_Uri and create your own custom URI classes,
+                and instantiate new URI objects based on your own custom classes.
+            </para>
+
+            <para>
+                The 2nd parameter passed to <methodname>Zend_Uri::factory()</methodname> must
+                be a string with the name of a class extending <classname>Zend_Uri</classname>.
+                The class must either be alredy-loaded, or loadable using <methodname>Zend_Loader::loadClass()</methodname> -
+                that is, it must follow the Zend Framework class and file naming conventions, and
+                must be in your include_path.
+            </para>
+
+            <example id="zend.uri.creation.custom.example-1">
+                <title>Creating a URI using a custom class</title>
+
+                <programlisting language="php"><![CDATA[
+// Create a new 'ftp' URI based on a custom class
+$ftpUri = Zend_Uri::factory(
+    'ftp://user@ftp.example.com/path/file',
+    'MyLibrary_Uri_Ftp'
+);
+
+// $ftpUri is an instance of MyLibrary_Uri_Ftp, which is a subclass of Zend_Uri
+]]></programlisting>
+            </example>
+        </sect3>
     </sect2>
 
     <sect2 id="zend.uri.manipulation">