[svnbook commit] r2247 - trunk/src/it/book

Miky noreply at red-bean.com
Thu Jun 22 12:33:38 CDT 2006


Author: Miky
Date: Thu Jun 22 12:33:38 2006
New Revision: 2247

Modified:
   trunk/src/it/book/ch03.xml

Log:
new contribution from Miky

Modified: trunk/src/it/book/ch03.xml
==============================================================================
--- trunk/src/it/book/ch03.xml	(original)
+++ trunk/src/it/book/ch03.xml	Thu Jun 22 12:33:38 2006
@@ -1,24 +1,47 @@
-<chapter id="svn.tour">
+<chapter id="svn.tour">
   <title>Guided Tour</title>
+  <title>Gita guidata</title>
 
   <simplesect>
 
-    <para>Now we will go into the details of using Subversion.  By the
+    <para lang="en">
+      Now we will go into the details of using Subversion.  By the
       time you reach the end of this chapter, you will be able to
       perform almost all the tasks you need to use Subversion in a
       normal day's work.  You'll start with an initial checkout of
       your code, and walk through making changes and examining those
       changes.  You'll also see how to bring changes made by others
       into your working copy, examine them, and work through any
-      conflicts that might arise.</para>
+      conflicts that might arise.
+    </para>
+
+    <para>
+      Entriamo nei dettagli dell'utilizzo di Subversion.Alla fine
+      di questo capitolo,si sarà  in grado di utilizzare al meglio tutti
+      i task di cui si ha bisogno per utilizzare Subversion in un normale
+      lavoro quotidiano.La prima cosa da fare è il checkout del proprio
+      codice,poi procedere effettuando modifiche ed esaminando tali cambiamenti.
+      Si imparerà  anche a importare cambiamenti fatti da altri nella propria cartella di lavoro,
+      ad esaminarli e a risolvere qualsiasi tipo di conflitto  possa nascere.
+    </para>
 
-    <para>Note that this chapter is not meant to be an exhaustive list
+    <para lang="en">
+      Note that this chapter is not meant to be an exhaustive list
       of all Subversion's commands—rather, it's a conversational
       introduction to the most common Subversion tasks you'll
       encounter.  This chapter assumes that you've read and understood
       <xref linkend="svn.basic"/> and are familiar with the general
       model of Subversion.  For a complete reference of all commands,
-      see <xref linkend="svn.ref"/>.</para>
+      see <xref linkend="svn.ref"/>.
+    </para>
+
+    <para>
+      Questo capitolo non vuole essere un elenco esaustivo di tutti
+      i comandi di Subversion,quanto piuttosto un'introduzione ai più comuni tasks
+      di Subversion che si possono incontrare.Si assume che si sia letto e compreso
+      <xref linkend="svn.basic"/> e che si abbia familiarità  con i modelli di Subversion.
+      Per un riferimento completo a tutti i comandi si rimanda a <xref linkend="svn.ref"/>.
+    </para>
 
   </simplesect>
 
@@ -27,15 +50,31 @@
   <!-- ================================================================= -->
   <sect1 id="svn.tour.help">
     <title>Help!</title>
+  
 
 
-    <para>Before reading on, here is the most important command you'll
+    <para lang="en">
+      Before reading on, here is the most important command you'll
       ever need when using Subversion: <command>svn help</command>.
       The Subversion command-line client is
-      self-documenting—at any time, a quick <command>svn help
-      <subcommand></command> will describe the syntax, switches,
-      and behavior of the <command>subcommand</command>.</para>
+      self-documenting—at any time, a quick <command>
+        svn help
+        <subcommand>
+      </command> will describe the syntax,switches,
+      and behavior of the <command>subcommand</command>.
+    </para>
+
 
+    <para>
+      Prima di andare oltre,qui c'è il comando principale di cui si ha bisogno
+      quando si usa Subversion: <command>svn help</command>.
+      Il client a riga di comando di Subversion è autoesplicativo;
+      ad ogni modo,un veloce comando svn help ,<command>
+        svn help
+        <subcommand>
+      </command>,descriverà la sintassi,
+      gli switches e il comportamento del comando <command>subcommand</command>
+    </para>
   </sect1>
 
   <!-- ================================================================= -->
@@ -44,12 +83,24 @@
   <sect1 id="svn.tour.import">
     <title>Import</title>
 
-    <para>You use <command>svn import</command> to import a new
+    <para lang="en">
+      You use <command>svn import</command> to import a new
       project into a Subversion repository.  While this is most likely
       the very first thing you will do when you set up your Subversion
       server, it's not something that happens very often.  For a
       detailed description of import, see <xref
-      linkend="svn.tour.other.import"/> later in this chapter.</para>
+      linkend="svn.tour.other.import"/> later in this chapter.
+    </para>
+
+
+
+    <para>
+      Per importare un nuovo progetto nel repository di Subversion, si usa il comando
+      <command>svn import</command>.Sebbene questa sia la prima cosa da fare quando
+      si fa il set up di Subversion server,non è una cosa che si debba fare frequentemente.
+      Per una descrizione dettagliata dell'import si rimanda a  <xref
+      linkend="svn.tour.other.import"/> nel seguito di questo capitolo
+    </para>
 
   </sect1>
 
@@ -58,58 +109,102 @@
   <!-- ================================================================= -->
   <sect1 id="svn.tour.revs">
     <title>Revisions: Numbers, Keywords, and Dates, Oh My!</title>
+    <title>Revisioni:Numeri,Chiavi e Date</title>
 
-    <para>Before we go on, you should know a bit about how to identify
+    <para lang="en">
+      Before we go on, you should know a bit about how to identify
       a particular revision in your repository.  As you learned in
       <xref linkend="svn.basic.in-action.revs"/>, a revision is a
       <quote>snapshot</quote> of the repository at a particular moment
       in time.  As you continue to commit and grow your repository,
-      you need a mechanism for identifying these snapshots.</para>
+      you need a mechanism for identifying these snapshots.
+    </para>
 
-    <para>You specify these revisions by using the
+
+    <para>
+      Prima di andare avanti, bisogna sapere qualcosa su come identificare
+      una particolare revisione nel proprio repository.  Come si è visto in
+      <xref linkend="svn.basic.in-action.revs"/>, una revisione è <quote>un'istantanea </quote>
+      del repository fatta in  un particolare istante di tempo.  Man mano che
+      si continua a fare commit  aumentano le dimensioni del repository,
+      perciò bisogna avere un metodo per identificare queste istantanee..
+    </para>
+
+    <para lang="en">
+      You specify these revisions by using the
       <option>--revision</option> (<option>-r</option>) switch plus
       the revision you want (<command>svn --revision REV</command>) or
       you can specify a range by separating two revisions with a colon
       (<command>svn --revision REV1:REV2</command>).  And Subversion
       lets you refer to these revisions by number, keyword, or
-      date.</para>
-    
+      date.
+    </para>
+    <para>
+      Per specificare le revisioni si usa l'opzione <option>--revision</option>
+      (<option>-r</option>) specificando la revisione desiderata (<command>svn --revision REV</command>)
+      oppure si può specificare un intervallo separando due revisioni con i due punti ":"
+      (<command>svn --revision REV1:REV2</command>).Subversion permette di referenziare
+      queste revisioni attraverso numeri,chiavi oppure data.
+    </para>
     <!-- =============================================================== -->
     <sect2 id="svn.tour.revs.numbers">
       <title>Revision Numbers</title>
-      
-      <para>When you create a new Subversion repository, it begins its
+
+      <para lang="en">
+        When you create a new Subversion repository, it begins its
         life at revision zero and each successive commit increases the
         revision number by one.  After your commit completes, the
         Subversion client informs you of the new revision
-        number:</para>
-      
+        number:
+      </para>
+      <para>
+        Quando si crea un nuovo repository Subversion,esso comincia la sua vita dalla revisione zero
+        e ogni successivo commit incrementa il numero di revisione di uno.
+        Quando si completa il commit ,il client Subversion comunica il nuovo numero della revisione.
+      </para>
       <screen>
-$ svn commit --message "Corrected number of cheese slices."
-Sending        sandwich.txt
-Transmitting file data .
-Committed revision 3.
-</screen>
+        $ svn commit --message "Corrected number of cheese slices."
+        Sending        sandwich.txt
+        Transmitting file data .
+        Committed revision 3.
+      </screen>
 
-      <para>If at any point in the future you want to refer to that
+      <para lang="en">
+        If at any point in the future you want to refer to that
         revision (we'll see how and why we might want to do that later
         in this chapter), you can refer to it as
-        <quote>3</quote>.</para>
-
+        <quote>3</quote>.
+      </para>
+      <para>
+        Se ad un certo punto,in seguito ci si vuole riferire a quella particolare revisione
+        (si vedrà come e perchè si dovrebbe volerlo nel seguito di questo capitolo),
+        ci si può riferire ad essa in questo modo : <quote>3</quote>.
+      </para>
     </sect2>
-    
+
     <!-- =============================================================== -->
     <sect2 id="svn.tour.revs.keywords">
       <title>Revision Keywords</title>
-      
-      <para>The Subversion client understands a number of
+
+
+      <para lang="en">
+        The Subversion client understands a number of
         <firstterm>revision keywords</firstterm>.  These keywords
         can be used instead of integer arguments to the
         <option>--revision</option> switch, and are resolved into
-        specific revision numbers by Subversion:</para>
-
+        specific revision numbers by Subversion:
+      </para>
+      <para>
+        Il client Subversion riconosce un numero di <firstterm>
+          chiavi per le revisioni
+        </firstterm>.
+        Queste chiavi possono essere usate al posto degli argomenti interi
+        per richiamare le <option>--revisioni</option> e vengono risolte
+        in specifici numeri di revisione da Subversion:
+      </para>
       <note>
-        <para>Each directory in your working copy contains an
+        <para lang="en">
+          Each directory in your working copy contains an
           administrative subdirectory called
           <filename>.svn</filename>.  For every file in a directory,
           Subversion keeps a copy of each file in the administrative
@@ -117,91 +212,155 @@
           end-of-line translation, no nothing) copy of the file as it
           existed in the last revision (called the <quote>BASE</quote>
           revision) that you updated it to in your working copy.  We
-          refer to this file as the <firstterm>pristine
-          copy</firstterm> or <firstterm>text-base</firstterm> version
+          refer to this file as the <firstterm>
+            pristine
+            copy
+          </firstterm> or <firstterm>text-base</firstterm> version
           of your file, and it's always an exact byte-for-byte copy of
-          the file as it exists in the repository.</para> 
-        </note>
-      
+          the file as it exists in the repository.
+        </para>
+        <para>
+          Ogni cartella della propria copia di lavoro contiene una sottocartella
+          di amministrazione chiamata <filename>.svn</filename>.
+          Per ogni file in una cartella,Subversion mantiene una copia nell'area di amministrazione.
+          Questa copia non è modificabile(non si possono espandere le chiavi,
+          non si può passare alla fine della riga,non si può fare niente)ed è la copia dell'ultima versione
+          del file (chiamata the <quote>BASE</quote> revisione)che si è aggiornata nella propria copia di lavoro.
+          Ci si riferirà a questo file come alla versione <firstterm>copia di ripristino</firstterm> oppure
+          <firstterm>testo-base</firstterm>,esso è sempre una copia esatta byte per byte del file che
+          si trova nel repository.
+        </para>
+      </note>
+
       <variablelist>
-        
+
         <varlistentry>
           <term>HEAD</term>
           <listitem>
-            <para>The latest (or <quote>youngest</quote>) revision in
-              the repository.</para>
+            <para lang="en">
+              The latest (or <quote>youngest</quote>) revision in
+              the repository.
+            </para>
+            <para>
+              L'ultima revisione (o <quote>la più recente</quote>)nel repository.
+            </para>
           </listitem>
         </varlistentry>
-        
+
         <varlistentry>
           <term>BASE</term>
           <listitem>
-            <para>The revision number of an item in a working copy.
-              If the item has been locally modified, the <quote>BASE
-              version</quote> refers to the way the item appears
-              without those local modifications.</para>
+            <para>
+              The revision number of an item in a working copy.
+              If the item has been locally modified, the <quote>
+                BASE
+                version
+              </quote> refers to the way the item appears
+              without those local modifications.
+            </para>
+            <para>
+              Il numero di revisione di un oggetto in una copia di lavoro.
+              Se l'oggetto è stato modificato in locale, la  <quote>
+                versione BASE
+              </quote> fa riferimento al modo in cui l'oggetto appare
+              senza le modifiche effettuate.
+            </para>
           </listitem>
         </varlistentry>
-        
+
         <varlistentry>
           <term>COMMITTED</term>
           <listitem>
-            <para>The most recent revision prior to, or equal to,
-              <literal>BASE</literal>, in which an item changed.</para>
+            <para lang ="en">
+              The most recent revision prior to, or equal to,
+              <literal>BASE</literal>, in which an item changed.
+            </para>
+            <para>
+              La revisione più recente "prima di" oppure "uguale a"
+              <literal>BASE</literal>,nella quale un oggetto è cambiato.
+            </para>
           </listitem>
         </varlistentry>
-        
+
         <varlistentry>
           <term>PREV</term>
           <listitem>
-            <para>The revision immediately <emphasis>before</emphasis>
+            <para lang="en">
+              The revision immediately <emphasis>before</emphasis>
               the last revision in which an item changed.
-              (Technically, <literal>COMMITTED</literal> - 1.)</para>
+              (Technically, <literal>COMMITTED</literal> - 1.)
+            </para>
+            <para>
+              La revisione immediatamente <emphasis>precedente</emphasis> rispetto
+              all'ultima revisione nella quale un oggetto è cambiato.
+              (Tecnicamente, <literal>COMMITTED</literal> - 1.)
+            </para>
           </listitem>
         </varlistentry>
-        
+
       </variablelist>
 
       <note>
-        <para><literal>PREV</literal>, <literal>BASE</literal>, and
+        <para lang ="en">
+          <literal>PREV</literal>, <literal>BASE</literal>, and
           <literal>COMMITTED</literal> can be used to refer to local
-          paths, but not to URLs.</para>
+          paths, but not to URLs.
+        </para>
+        <para>
+          <literal>PREV</literal>,<literal>BASE</literal>, and
+          <literal>COMMITTED</literal> possono essere usati per far riferimento a percorsi locali
+          ma non a URLs.
+
+        </para>
       </note>
-      
-      <para>Here are some examples of revision keywords in action.
-        Don't worry if the commands don't make sense yet; we'll be
-        explaining these commands as we go through the chapter:</para>
-      
-      <screen>
-$ svn diff --revision PREV:COMMITTED foo.c
-# shows the last change committed to foo.c
 
-$ svn log --revision HEAD
-# shows log message for the latest repository commit
+      <para lang="en">
+        Here are some examples of revision keywords in action.
+        Don't worry if the commands don't make sense yet; we'll be
+        explaining these commands as we go through the chapter:
+      </para>
+      <para>
+        Diamo alcuni esempi di chiavi di revisione in azione.
+        Non bisogna preoccuparsi se i comandi sembrano non aver senso;
+        saranno spiegati in seguito.
+      </para>
 
-$ svn diff --revision HEAD
-# compares your working file (with local changes) to the latest version
-# in the repository
+      <screen>
+        $ svn diff --revision PREV:COMMITTED foo.c
+        # shows the last change committed to foo.c
 
-$ svn diff --revision BASE:HEAD foo.c
-# compares your <quote>pristine</quote> foo.c (no local changes) with the 
-# latest version in the repository
+        $ svn log --revision HEAD
+        # shows log message for the latest repository commit
 
-$ svn log --revision BASE:HEAD
-# shows all commit logs since you last updated
+        $ svn diff --revision HEAD
+        # compares your working file (with local changes) to the latest version
+        # in the repository
+
+        $ svn diff --revision BASE:HEAD foo.c
+        # compares your <quote>pristine</quote> foo.c (no local changes) with the
+        # latest version in the repository
+
+        $ svn log --revision BASE:HEAD
+        # shows all commit logs since you last updated
+
+        $ svn update --revision PREV foo.c
+        # rewinds the last change on foo.c
+        # (foo.c's working revision is decreased)
+      </screen>
 
-$ svn update --revision PREV foo.c
-# rewinds the last change on foo.c
-# (foo.c's working revision is decreased)
-</screen>
-      
-      <para>These keywords allow you to perform many common (and
+      <para lang="en">
+        These keywords allow you to perform many common (and
         helpful) operations without having to look up specific
         revision numbers or remember the exact revision of your
-        working copy.</para>
-      
+        working copy.
+      </para>
+      <para>
+        Queste chiavi permettono di effettuare le più comuni
+        (e utili) operazioni senza bisogno di specificare i numeri di revisione
+        o di ricordare l'esatta revisione della propria copia di lavoro.
+      </para>
+
     </sect2>
-    
     <!-- =============================================================== -->
     <sect2 id="svn.tour.revs.dates">
       <title>Date di revisione</title>




More information about the svnbook-dev mailing list