Browse Source

[DOCUMENTATION] French: sync manual

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@22200 44c647ce-9c0f-0410-b52a-842ac1e357ba
mikaelkael 15 years ago
parent
commit
b0d3ea9aca

+ 9 - 1
documentation/manual/fr/module_specs/Zend_Validate-Sitemap.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- EN-Revision: 20794 -->
+<!-- EN-Revision: 21263 -->
 <!-- Reviewed: no -->
 <sect2 id="zend.validate.sitemap">
     <title>Validateurs de Sitemap</title>
@@ -93,4 +93,12 @@ $validator->isValid('foo'); // false
 ]]></programlisting>
         </example>
     </sect3>
+
+    <sect3 id="zend.validate.set.sitemap.options">
+        <title>Options supportées par Zend_Validate_Sitemap_*</title>
+
+        <para>
+            Il n'y a pas d'options supportées par ce validateur.
+        </para>
+    </sect3>
 </sect2>

+ 11 - 3
documentation/manual/fr/module_specs/Zend_View-Helpers-HeadTitle.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 21825 -->
+<!-- EN-Revision: 22090 -->
 <!-- Reviewed: no -->
 <sect3 id="zend.view.helpers.initial.headtitle">
     <title>L'aide de vue HeadTitle</title>
@@ -16,12 +16,20 @@
         méthode <methodname>toString()</methodname> pour forcer la génération d'un élément
         <code>&lt;title&gt;</code>, et ajoute une méthode <methodname>headTitle()</methodname> pour des réglages
         faciles et rapides et pour l'aggrégation des éléments du titre. La signature de la méthode
-        est <methodname>headTitle($title, $setType = 'APPEND')</methodname> ; par défaut, la valeur est ajoutée
-        en fin de pile (pour aggréger les segments du titre), mais vous pouvez aussi spécifier
+        est <methodname>headTitle($title, $setType = null)</methodname> ; par défaut, la valeur est ajoutée
+        en fin de pile (pour aggréger les segments du titre) si laissé à null, mais vous pouvez aussi spécifier
         "<constant>PREPEND</constant>" (pour l'ajouter en début de pile) ou "<constant>SET</constant>" (pour
         remplacer la pile existante).
     </para>
 
+    <para>
+        Since setting the aggregating (attach) order on each call to <methodname>
+        headTitle</methodname> can be cumbersome, you can set a default attach order
+        by calling <methodname>setDefaultAttachOrder()</methodname> which is applied
+        to all <methodname>headTitle()</methodname> calls unless you explicitly
+        pass a different attach order as the second parameter.
+    </para>
+
     <example id="zend.view.helpers.initial.headtitle.basicusage">
         <title>Utilisation basique de l'aide HeadTitle</title>
 

+ 47 - 2
documentation/manual/fr/ref/coding_standard.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 20876 -->
+<!-- EN-Revision: 21740 -->
 <!-- Reviewed: no -->
 <appendix id="coding-standard">
     <title>Convention de codage PHP de Zend Framework</title>
@@ -179,6 +179,49 @@
                     that pre-date that version may not follow this rule, but will be renamed in
                     the future in order to comply.
                 </para>
+
+                <para>
+                    The rationale for the change is due to namespace usage. As we look towards Zend
+                    Framework 2.0 and usage of <acronym>PHP</acronym> 5.3, we will be using
+                    namespaces. The easiest way to automate conversion to namespaces is to simply
+                    convert underscores to the namespace separator -- but under the old naming
+                    conventions, this leaves the classname as simply "Abstract" or "Interface" --
+                    both of which are reserved keywords in <acronym>PHP</acronym>. If we prepend the
+                    (sub)component name to the classname, we can avoid these issues.
+                </para>
+
+                <para>
+                    To illustrate the situation, consider converting the class
+                    <classname>Zend_Controller_Request_Abstract</classname> to use namespaces:
+                </para>
+
+                <programlisting language="php"><![CDATA[
+namespace Zend\Controller\Request;
+
+abstract class Abstract
+{
+    // ...
+}
+]]></programlisting>
+
+                <para>
+                    Clearly, this will not work. Under the new naming conventions, however, this
+                    would become:
+                </para>
+
+                <programlisting language="php"><![CDATA[
+namespace Zend\Controller\Request;
+
+abstract class RequestAbstract
+{
+    // ...
+}
+]]></programlisting>
+
+                <para>
+                    We still retain the semantics and namespace separation, while omitting the
+                    keyword issues; simultaneously, it better describes the abstract class.
+                </para>
             </note>
         </sect2>
 
@@ -206,7 +249,9 @@
                 <para>
                     This naming convention is new with version 1.9.0 of Zend Framework. Classes
                     that pre-date that version may not follow this rule, but will be renamed in
-                    the future in order to comply.
+                    the future in order to comply. See <link
+                        linkend="coding-standard.naming-conventions.abstracts">the previous
+                        section</link> for more information on the rationale for this change.
                 </para>
             </note>
         </sect2>

+ 14 - 10
documentation/manual/fr/ref/migration-110.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 20876 -->
+<!-- EN-Revision: 21825 -->
 <!-- Reviewed: no -->
 <sect1 id="migration.110">
     <title>Zend Framework 1.10</title>
@@ -20,7 +20,7 @@
             in the router interface, throw an exception if no route matches. The error
             plugin will then catch that exception and forward to the error controller.
             You can then test for that specific error with the constant
-            <constant></constant>:
+            <constant>Zend_Controller_Plugin_ErrorHandler::EXCEPTION_NO_ROUTE</constant>:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -130,7 +130,7 @@ $authors = $feed->getAuthors()->getValues();
             </para>
 
             <para>
-                When you are in need of the original values you can eighter store them before
+                When you are in need of the original values you can either store them before
                 initiating <classname>Zend_File_Transfer</classname> or use the
                 <property>disableInfos</property> option at initiation. Note that this option is
                 useless when its given after initiation.
@@ -211,13 +211,15 @@ $authors = $feed->getAuthors()->getValues();
         <para>
             <classname>Zend_Filter_StripTags</classname> contains a flag,
             <varname>commentsAllowed</varname>, that, in previous versions, allowed you to
-            optionally whitelist HTML comments in HTML text filtered by the class. However, this
-            opens code enabling the flag to <acronym>XSS</acronym> attacks, particularly in Internet
-            Explorer (which allows specifying conditional functionality via HTML comments). Starting
+            optionally whitelist <acronym>HTML</acronym> comments in <acronym>HTML</acronym> text
+            filtered by the class. However, this opens code enabling the flag to
+            <acronym>XSS</acronym> attacks, particularly in Internet Explorer (which allows
+            specifying conditional functionality via <acronym>HTML</acronym> comments). Starting
             in version 1.9.7 (and backported to versions 1.8.5 and 1.7.9), the
-            <varname>commentsAllowed</varname> flag no longer has any meaning, and all HTML
-            comments, including those containing other HTML tags or nested commments, will be
-            stripped from the final output of the filter.
+            <varname>commentsAllowed</varname> flag no longer has any meaning, and all
+            <acronym>HTML</acronym> comments, including those containing other
+            <acronym>HTML</acronym> tags or nested commments, will be stripped from the final output
+            of the filter.
         </para>
     </sect2>
 
@@ -239,7 +241,9 @@ $authors = $feed->getAuthors()->getValues();
             </para>
 
             <programlisting language="php"><![CDATA[
-$trans = new Zend_Translate('xliff', '/path/to/source', $locale, array('useId' => false));
+$trans = new Zend_Translate(
+    'xliff', '/path/to/source', $locale, array('useId' => false)
+);
 ]]></programlisting>
         </sect3>
     </sect2>