[svnbook] r6043 committed - branches/1.8/fr

chris-nanteuil at users.sourceforge.net chris-nanteuil at users.sourceforge.net
Sat Sep 4 16:19:44 UTC 2021


Revision: 6043
          http://sourceforge.net/p/svnbook/source/6043
Author:   chris-nanteuil
Date:     2021-09-04 16:19:44 +0000 (Sat, 04 Sep 2021)
Log Message:
-----------
[fr] Keeping in sync with English version.
  The names of the hooks remain inside <literal> tags as they are not
  directly understandable in French.

Modified Paths:
--------------
    branches/1.8/fr/Makefile
    branches/1.8/fr/README
    branches/1.8/fr/book/appa-quickstart.xml
    branches/1.8/fr/book/appb-svn-for-cvs-users.xml
    branches/1.8/fr/book/appc-webdav.xml
    branches/1.8/fr/book/appd-berkeley-db.xml
    branches/1.8/fr/book/ch04-branching-and-merging.xml
    branches/1.8/fr/book/ch05-repository-admin.xml
    branches/1.8/fr/book/ch06-server-configuration.xml
    branches/1.8/fr/book/ref-reposhooks.xml

Property Changed:
----------------
    branches/1.8/fr/
    branches/1.8/fr/Makefile
    branches/1.8/fr/book/
    branches/1.8/fr/book/ch04-branching-and-merging.xml
    branches/1.8/fr/book/ch05-repository-admin.xml
    branches/1.8/fr/book/ch06-server-configuration.xml

Index: branches/1.8/fr
===================================================================
--- branches/1.8/fr	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr	2021-09-04 16:19:44 UTC (rev 6043)

Property changes on: branches/1.8/fr
___________________________________________________________________
Modified: svn:mergeinfo
## -1 +1 ##
-/trunk/en:5065-5922
\ No newline at end of property
+/trunk/en:5065-6042
\ No newline at end of property
Modified: branches/1.8/fr/Makefile
===================================================================
--- branches/1.8/fr/Makefile	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/Makefile	2021-09-04 16:19:44 UTC (rev 6043)
@@ -1,5 +1,14 @@
 include ../tools/Makefile.base
+
 # Customization hooks for xsltproc options
+
+# Customization for the html target
 HTML_XSLTPROC_OPTS = --stringparam l10n.gentext.language fr
+
+# Customization for the pdf target
+# Examples
+# Custom page size: --stringparam page.height 9in --stringparam page.width 6.4in
+# Paper type A4: --stringparam paper.type A4
 FO_XSLTPROC_OPTS = --param fop1.extensions 1 --stringparam paper.type A4 --stringparam l10n.gentext.language fr
+
 L10N_REVISION = r


Property changes on: branches/1.8/fr/Makefile
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
 /branches/1.5/fr/Makefile:3977
-/trunk/en/Makefile:5065-5129
+/trunk/en/Makefile:5065-6042
 /trunk/src/fr/Makefile:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/README
===================================================================
--- branches/1.8/fr/README	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/README	2021-09-04 16:19:44 UTC (rev 6043)
@@ -132,6 +132,9 @@
 
      Poof!  You now have PNG support.
 
+   * If you want to customize the output, for example change the paper
+     type, check the FO_XSLTPROC_OPTS variable in en/Makefile.
+     
    * From this directory (en, or another language directory), do 
 
         $ make all-pdf

Index: branches/1.8/fr/book
===================================================================
--- branches/1.8/fr/book	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book	2021-09-04 16:19:44 UTC (rev 6043)

Property changes on: branches/1.8/fr/book
___________________________________________________________________
Deleted: svn:mergeinfo
## -1 +0,0 ##
-/trunk/en/book:5065-5965
\ No newline at end of property
Modified: branches/1.8/fr/book/appa-quickstart.xml
===================================================================
--- branches/1.8/fr/book/appa-quickstart.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/appa-quickstart.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -290,7 +290,7 @@
       <xref linkend="svn.reposadmin"/>.</para>
 
 <!--
-    <para>Subversion has no concept of a <quote>project.</quote> The
+    <para>Subversion has no concept of a <quote>project</quote>. The
       repository is just a virtual versioned filesystem, a large tree
       that can hold anything you wish.  Some administrators prefer to
       store only one project in a repository, and others prefer to
@@ -299,7 +299,7 @@
       in <xref linkend="svn.reposadmin.projects.chooselayout"/>.
       Either way, the repository manages only files and directories,
       so it's up to humans to interpret particular directories as
-      <quote>projects.</quote>  So while you might see references to
+      <quote>projects</quote>.  So while you might see references to
       projects throughout this book, keep in mind that we're only ever
       talking about some directory (or collection of directories) in
       the repository.</para>

Modified: branches/1.8/fr/book/appb-svn-for-cvs-users.xml
===================================================================
--- branches/1.8/fr/book/appb-svn-for-cvs-users.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/appb-svn-for-cvs-users.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -101,15 +101,15 @@
     <para>Similarly, in CVS, a tag or branch is an annotation on the
       file or on the version information for that individual file,
       whereas in Subversion, a tag or branch is a copy of an entire
-      tree (by convention, into the <filename>/branches</filename>
-      or <filename>/tags</filename> directories that appear at the top
-      level of the repository, beside <filename>/trunk</filename>).  In
+      tree (by convention, into the <filename>branches/</filename>
+      or <filename>tags/</filename> directories that appear at the top
+      level of the repository, beside <filename>trunk/</filename>).  In
       the repository as a whole, many versions of each file may be
       visible: the latest version on each branch, every tagged
       version, and of course the latest version on the trunk
       itself.  So, to refine the terms even further, one would often
       say <quote><filename>foo.c</filename> as it appears in
-      <filename>/branches/REL1</filename> in revision
+      <filename>branches/REL1</filename> in revision
       5.</quote></para>
 -->
     <para>De la même manière, dans CVS, une étiquette et une branche
@@ -117,9 +117,9 @@
       version de ce fichier. En revanche, dans Subversion, une branche
       ou une étiquette sont des copies complètes d'une arborescence
       (situées respectivement par convention dans les répertoires
-      <filename>/branches</filename> et <filename>/tags</filename> qui
+      <filename>branches/</filename> et <filename>tags/</filename> qui
       se trouvent à la racine de l'arborescence du dépôt, à côté de
-      <filename>/trunk</filename>). Dans l'ensemble du dépôt, plusieurs
+      <filename>trunk/</filename>). Dans l'ensemble du dépôt, plusieurs
       versions de chaque fichier peuvent être visibles : la
       dernière version à l'intérieur de chaque branche, la version au
       sein de chaque étiquette et, bien sûr, la dernière version dans le
@@ -126,7 +126,7 @@
       tronc lui-même (sous <filename>/trunk</filename>). Ainsi, pour
       être vraiment précis, il convient de dire
       <quote><filename>machin.c</filename> tel qu'il était dans
-      <filename>/branches/IDEE1</filename> à la révision
+      <filename>branches/IDÉE1</filename> à la révision
       5</quote>.</para>
 
 <!--
@@ -713,7 +713,7 @@
       travail locale.</para>
 
 <!--
-    <para>To set or get a property name, use the <command>svn
+    <para>To set or get a property value, use the <command>svn
       propset</command> and <command>svn propget</command>
       subcommands.  To list all properties on an object, use
       <command>svn proplist</command>.</para>
@@ -1034,7 +1034,7 @@
 
 <!--
     <para>The most popular (and mature) conversion tool is
-      cvs2svn (<ulink url="http://cvs2svn.tigris.org/"/>), a Python
+      cvs2svn (<ulink url="https://github.com/mhagger/cvs2svn/"/>), a Python
       program originally created by members of Subversion's own
       development community.  This tool is meant to run exactly once:
       it scans your CVS repository multiple times and attempts to

Modified: branches/1.8/fr/book/appc-webdav.xml
===================================================================
--- branches/1.8/fr/book/appc-webdav.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/appc-webdav.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -90,7 +90,7 @@
       committee was left with the responsibility of writing RFC 3253 a
       few years later.  The new RFC adds versioning concepts to
       WebDAV, placing the <quote>V</quote> back in
-      <quote>DAV</quote>—hence the term <quote>DeltaV.</quote>
+      <quote>DAV</quote>—hence the term <quote>DeltaV</quote>.
       WebDAV/DeltaV clients and servers are often called just
       <quote>DeltaV</quote> programs, since DeltaV implies the
       existence of basic WebDAV.</para>
@@ -211,7 +211,7 @@
 
 <!--
     <para>A long-held debate in the Subversion developer community
-      about whether it was worthfile to remedy either of these
+      about whether it was worthwhile to remedy either of these
       situations eventually reached closure, with the Subversion
       developers officially deciding to abandon plans to fully support
       DeltaV.  As of Subversion 1.7, Subversion clients and servers
@@ -1150,7 +1150,7 @@
           system registry to turn off this behavior.  Just change the
           value of the <literal>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\BasicAuthLevel</literal>
           key from <userinput>1</userinput> to <userinput>2</userinput>.  A final warning:  be sure to set up the Web
-          Folder to point to the repository's root directory
+          Folders to point to the repository's root directory
           (<filename>/</filename>), rather than some subdirectory
           such as <filename>/trunk</filename>.  Vista Web Folders
           seems to work only against repository roots.</para>
@@ -1390,7 +1390,7 @@
 <!--
         <para>Linux davfs2 is a filesystem module for the Linux
           kernel, whose development is organized at
-          <ulink url="http://dav.sourceforge.net/"/>.  Once you
+	  <ulink url="http://savannah.nongnu.org/projects/davfs2"/>.  Once you
           install davfs2, you can mount a WebDAV network share using
           the usual Linux mount command:</para>
 -->

Modified: branches/1.8/fr/book/appd-berkeley-db.xml
===================================================================
--- branches/1.8/fr/book/appd-berkeley-db.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/appd-berkeley-db.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -836,13 +836,13 @@
       <para>For more information on the Berkeley DB tool chain,
         visit the documentation section of the Berkeley DB section
         of Oracle's web site, located at <ulink
-        url="http://www.oracle.com/technology/documentation/berkeley-db/db/"
+        url="https://docs.oracle.com/cd/E17275_01/html/api_reference/C/utilities.html"/>.
         />.</para>
 -->
       <para>Pour davantage d'informations sur la suite d'outils Berkeley DB,
         consultez la documentation en ligne sur le site Internet d'Oracle,
         dans la section Berkeley DB : <ulink
-        url="http://www.oracle.com/technology/documentation/berkeley-db/db/"
+        url="https://docs.oracle.com/cd/E17275_01/html/api_reference/C/utilities.html"/>.
         /> (ce site est en anglais).</para>
 
     </sect2>

Modified: branches/1.8/fr/book/ch04-branching-and-merging.xml
===================================================================
--- branches/1.8/fr/book/ch04-branching-and-merging.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/ch04-branching-and-merging.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -8017,10 +8017,6 @@
       <indexterm>
         <primary>branches</primary>
         <secondary>vendor branches</secondary>
-      </indexterm>
-      <indexterm>
-        <primary>branches</primary>
-        <secondary>vendor branches</secondary>
       </indexterm>As is especially the case when developing software, the data
       that you maintain under version control is often closely related
       to, or perhaps dependent upon, someone else's data.  Generally,


Property changes on: branches/1.8/fr/book/ch04-branching-and-merging.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,2 +1,2 ##
-/trunk/en/book/ch04-branching-and-merging.xml:5065-5576
+/trunk/en/book/ch04-branching-and-merging.xml:5065-6042
 /trunk/src/fr/book/ch04-branching-and-merging.xml:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/fr/book/ch05-repository-admin.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/ch05-repository-admin.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -1387,8 +1387,8 @@
 <!--
         <para>The syntax of the <filename>hooks-env</filename> file is
           pretty straightforward: each section name is the name of a
-          hook script (such as <literal>pre-commit</literal>
-          or <literal>post-revprop-change</literal>), and the
+          hook script (such as <literal>[pre-commit]</literal>
+          or <literal>[post-revprop-change]</literal>), and the
           configuration items inside that section are treated as
           mappings of environment variable names to desired values.
           Additionally, there is a
@@ -1403,8 +1403,8 @@
         <para>La syntaxe du fichier <filename>hooks-env</filename> est
           très simple : chaque nom de section correspond à la
           procédure automatique à laquelle la section s'applique (tels
-          que <literal>pre-commit</literal> ou
-          <literal>post-revprop-change</literal>) et les éléments à
+          que <literal>[pre-commit]</literal> ou
+          <literal>[post-revprop-change]</literal>) et les éléments à
           l'intérieur des sections sont les variables d'environnement
           dont on souhaite définir les valeurs. En plus, il existe une
           section générale <literal>[default]</literal>, qui permet


Property changes on: branches/1.8/fr/book/ch05-repository-admin.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
 /branches/1.5/fr/book/ch05-repository-admin.xml:3977-5144
-/trunk/en/book/ch05-repository-admin.xml:5065-5576
+/trunk/en/book/ch05-repository-admin.xml:5065-6042
 /trunk/src/fr/book/ch05-repository-admin.xml:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/book/ch06-server-configuration.xml
===================================================================
--- branches/1.8/fr/book/ch06-server-configuration.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/ch06-server-configuration.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -4082,7 +4082,7 @@
 
       <informalexample>
         <programlisting>
-LoadModule dav_svn_module     C:/Subversion/lib/mod_dav_svn.so
+LoadModule dav_svn_module     C:/Subversion/libexec/mod_dav_svn.so
 </programlisting>
       </informalexample>
 
@@ -7705,7 +7705,7 @@
             of the mechanisms that one might employ to accomplish this
             replication fall short in one way or
             another<footnote><para><ulink
-            url="http://subversion.tigris.org/issues/show_bug.cgi?id=3457"
+            url="https://subversion.apache.org/issue3457"
             /> tracks these problems.</para></footnote>.  Many teams
             don't use Subversion's locking features at all, so this
             may be a nonissue for you.  Sadly, for those teams which
@@ -7726,7 +7726,7 @@
             sont utilisés pour effectuer cette réplication sont
             confrontés à un problème à un moment ou à un autre<footnote>
 				<para><ulink
-            url="http://subversion.tigris.org/issues/show_bug.cgi?id=3457"
+            url="https://subversion.apache.org/issue3457"
             /> suit ces problèmes.</para>
 			</footnote>. De nombreuses équipes n'utilisent pas du tout
 			les fonctionnalités de verrouillage de Subversion, il s'agit


Property changes on: branches/1.8/fr/book/ch06-server-configuration.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
 /branches/1.5/fr/book/ch06-server-configuration.xml:3977-5196
-/trunk/en/book/ch06-server-configuration.xml:5065-5847
+/trunk/en/book/ch06-server-configuration.xml:5065-6042
 /trunk/src/fr/book/ch06-server-configuration.xml:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/book/ref-reposhooks.xml
===================================================================
--- branches/1.8/fr/book/ref-reposhooks.xml	2021-09-01 11:59:32 UTC (rev 6042)
+++ branches/1.8/fr/book/ref-reposhooks.xml	2021-09-04 16:19:44 UTC (rev 6043)
@@ -292,7 +292,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>pre-commit</literal> hook is run just
+      <para>The pre-commit hook is run just
         before a commit transaction is promoted to a new revision.
         Typically, this hook is used to protect against commits that
         are disallowed due to content or location (e.g., your
@@ -311,7 +311,7 @@
         l'entrée du journal de propagation ne soit pas vide).</para>
 
 <!--
-      <para>If the <literal>pre-commit</literal> hook program
+      <para>If the pre-commit hook program
         returns a nonzero exit value, the commit is aborted, the
         commit transaction is removed, and anything printed to
         <filename>stderr</filename> is marshalled back to the client.</para>
@@ -430,7 +430,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>post-commit</literal> hook is run after the
+      <para>The post-commit hook is run after the
         transaction is committed and a new revision is created.  Most
         people use this hook to send out descriptive emails about
         the commit or to notify some other tool (such as an issue
@@ -447,7 +447,7 @@
         procédure automatique pour déclencher une sauvegarde.</para>
 
 <!--
-      <para>If the <literal>post-commit</literal> hook returns a
+      <para>If the post-commit hook returns a
         nonzero exit status, the commit <emphasis>will
         not</emphasis> be aborted since it has already
         completed.  However, anything that the hook printed
@@ -560,7 +560,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>pre-revprop-change</literal> hook is run
+      <para>The pre-revprop-change hook is run
         immediately prior to the modification of a revision property
         when performed outside the scope of a normal commit.  Unlike
         the other hooks, the default state of this one is to deny
@@ -579,7 +579,7 @@
         propriété de révision.</para>
 
 <!--
-      <para>If the <literal>pre-revprop-change</literal> hook doesn't
+      <para>If the pre-revprop-change hook doesn't
         exist, isn't executable, or returns a nonzero exit value, no
         change to the property will be made, and anything printed
         to <filename>stderr</filename> is marshalled back to the
@@ -717,13 +717,13 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>post-revprop-change</literal> hook is run
+      <para>The post-revprop-change hook is run
         immediately after the modification of a revision property
         when performed outside the scope of a normal commit.  As you can
         derive from the description of its counterpart, the
-        <literal>pre-revprop-change</literal> hook, this hook will
+        pre-revprop-change hook, this hook will
         not run at all unless
-        the <literal>pre-revprop-change</literal> hook is
+        the pre-revprop-change hook is
         implemented.  It is typically used to send email
         notification of the property change.</para>
 -->
@@ -741,7 +741,7 @@
         modifiée.</para>
 
 <!--
-      <para>If the <literal>post-revprop-change</literal> hook returns a
+      <para>If the post-revprop-change hook returns a
         nonzero exit status, the change <emphasis>will
         not</emphasis> be aborted since it has already
         completed.  However, anything that the hook printed
@@ -878,7 +878,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>pre-lock</literal> hook runs whenever
+      <para>The pre-lock hook runs whenever
         someone attempts to lock a path.  It can be used to prevent
         locks altogether or to create a more complex policy
         specifying exactly which users are allowed to lock
@@ -896,7 +896,7 @@
         verrou pré-existant.</para>
 
 <!--
-      <para>If the <literal>pre-lock</literal> hook program returns
+      <para>If the pre-lock hook program returns
         a nonzero exit value, the lock action is aborted and
         anything printed to <filename>stderr</filename> is
         marshalled back to the client.</para>
@@ -921,7 +921,7 @@
 
       <warning>
 <!--
-        <para>If the <literal>pre-lock</literal> script takes
+        <para>If the pre-lock script takes
           advantage of lock token dictation feature, the
           responsibility of generating a <emphasis>unique</emphasis>
           lock token falls to the script itself.  Failure to
@@ -1045,7 +1045,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>post-lock</literal> hook runs after one or
+      <para>The post-lock hook runs after one or
         more paths have been locked.  It is typically used to send
         email notification of the lock event.</para>
 -->
@@ -1055,7 +1055,7 @@
         notification signalant ce verrouillage.</para>
 
 <!--
-      <para>If the <literal>post-lock</literal> hook returns a
+      <para>If the post-lock hook returns a
         nonzero exit status, the lock <emphasis>will
         not</emphasis> be aborted since it has already
         completed.  However, anything that the hook printed
@@ -1170,7 +1170,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>pre-unlock</literal> hook runs whenever
+      <para>The pre-unlock hook runs whenever
         someone attempts to remove a lock on a file.  It can be used
         to create policies that specify which users are allowed to
         unlock particular paths.  It's particularly important for
@@ -1191,7 +1191,7 @@
         être implémenté par la procédure automatique.</para>
 
 <!--
-      <para>If the <literal>pre-unlock</literal> hook program
+      <para>If the pre-unlock hook program
         returns a nonzero exit value, the unlock action is aborted
         and anything printed to <filename>stderr</filename> is marshalled back to the
         client.</para>
@@ -1309,7 +1309,7 @@
       <title>Description</title>
 
 <!--
-      <para>The <literal>post-unlock</literal> hook runs after one
+      <para>The post-unlock hook runs after one
         or more paths have been unlocked.  It is typically used to
         send email notification of the unlock event.</para>
 -->
@@ -1319,7 +1319,7 @@
         e-mails de notification signalant ce déverrouillage.</para>
 
 <!--
-      <para>If the <literal>post-unlock</literal> hook returns a
+      <para>If the post-unlock hook returns a
         nonzero exit status, the unlock <emphasis>will
         not</emphasis> be aborted since it has already
         completed.  However, anything that the hook printed




More information about the svnbook-dev mailing list