[svnbook-pt-br commit] r33 - trunk/book

codesite-noreply at google.com codesite-noreply at google.com
Sat Mar 15 13:57:47 CDT 2008


Author: herrera.leandro
Date: Fri Mar 14 14:02:07 2008
New Revision: 33

Modified:
   trunk/book/foreword.xml

Log:
Tradução parcial da seção foreword.

Modified: trunk/book/foreword.xml
==============================================================================
--- trunk/book/foreword.xml	(original)
+++ trunk/book/foreword.xml	Fri Mar 14 14:02:07 2008
@@ -3,6 +3,16 @@
 the best solution for now, even though there's also a real preface in
 ch00.xml. -->
 
+<!--
+There is a difference between the words foreword and preface. 
+A foreword is an introductory statement written by someone other
+than the book's author.
+A preface is an introductory statement written by the book's author.
+So I think that "Apresenta��o" it would be a nice translation from Foreword.
+
+Herrera
+-->
+
 <preface id="svn.foreword">
 
   <prefaceinfo>
@@ -10,118 +20,125 @@
       <firstname>Karl</firstname>
       <surname>Fogel</surname>
     </author>
-    <pubdate>Chicago, March 14, 2004</pubdate>
+    <pubdate>Chicago, 14 de Mar�o de 2004</pubdate>
   </prefaceinfo>
 
-  <title>Foreword</title>
+  <title>Apresenta��o</title>
 
-  <para>A bad Frequently Asked Questions (FAQ) sheet is one that is
-    composed not of the questions people actually asked, but of the
-    questions the FAQ's author <emphasis>wished</emphasis> people
-    had asked.  Perhaps you've seen the type before:</para>
+  <para>Uma base ruim de Perguntas Freq�entes (FAQ), � aquela que �
+    composta n�o de perguntas que as pessoas realmente fizeram, mas
+    de perguntas que o autor da FAQ <emphasis>desejou</emphasis> que
+    as pessoas tivessem feito. Talvez voc� j� tenha visto isto antes:</para>
 
   <blockquote>
-    <para>Q: How can I use Glorbosoft XYZ to maximize team
-      productivity?</para>
+    <para>P: De que forma posso utilizar o Glorbosoft XYZ para
+      maximizar a produtividade da equipe?</para>
   </blockquote>
 
   <blockquote>
-    <para>A: Many of our customers want to know how they can
-      maximize productivity through our patented office groupware
-      innovations.  The answer is simple: first, click on the
-      <quote><literal>File</literal></quote> menu, scroll down to
-      <quote><literal>Increase Productivity</literal></quote>,
-      then…</para>
+    <para>R: Muitos dos nossos clientes desejam saber como podem
+      maximizar a produtividade atrav�s de nossas inova��es
+      patenteadas de groupware para escrit�rios.  A resposta �
+      simples: primeiro, clique no menu 
+      <quote><literal>Arquivo</literal></quote>. Des�a at� a op��o
+      <quote><literal>Aumentar Produtividade</literal></quote>,
+      ent�o…</para>
   </blockquote>
 
-  <para>The problem with such FAQs is that they are not, in a
-    literal sense, FAQs at all.  No one ever called the tech support
-    line and asked, <quote>How can we maximize
-    productivity?</quote>.  Rather, people asked highly specific
-    questions, like, <quote>How can we change the calendaring system
-    to send reminders two days in advance instead of one?</quote>
-    and so on.  But it's a lot easier to make up imaginary
-    Frequently Asked Questions than it is to discover the real ones.
-    Compiling a true FAQ sheet requires a sustained, organized
-    effort: over the lifetime of the software, incoming questions
-    must be tracked, responses monitored, and all gathered into a
-    coherent, searchable whole that reflects the collective
-    experience of users in the wild.  It calls for the patient,
-    observant attitude of a field naturalist.  No grand
-    hypothesizing, no visionary pronouncements here—open eyes
-    and accurate note-taking are what's needed most.</para>
-
-  <para>What I love about this book is that it grew out of just such
-    a process, and shows it on every page.  It is the direct result
-    of the authors' encounters with users.  It began with Ben
-    Collins-Sussman's observation that people were asking the same
-    basic questions over and over on the Subversion mailing lists:
-    What are the standard workflows to use with Subversion?  Do
-    branches and tags work the same way as in other version control
-    systems?  How can I find out who made a particular change?</para>
-
-  <para>Frustrated at seeing the same questions day after day, Ben
-    worked intensely over a month in the summer of 2002 to write
-    <citetitle>The Subversion Handbook</citetitle>, a sixty page
-    manual that covered all the basics of using Subversion.  The
-    manual made no pretense of being complete, but it was
-    distributed with Subversion and got users over that initial hump
-    in the learning curve.  When O'Reilly and Associates decided to
-    publish a full-length Subversion book, the path of least
-    resistance was obvious: just expand the Subversion
-    handbook.</para>
-
-  <para>The three co-authors of the new book were thus presented
-    with an unusual opportunity.  Officially, their task was to
-    write a book top-down, starting from a table of contents and an
-    initial draft.  But they also had access to a steady
+<!-- Nesta se��o tinha um termo "Field Naturalist" que eh uma esp�cie de 
+     cientista bi�logo. Achei melhor ficar s� com o termo cientista.
+-->
+
+  <para>O problema com estas bases de FAQ � que eles n�o s�o,
+    propriamente ditas, FAQ.  Ningu�m nunca liga para o suporte
+    t�cnico e pergunta <quote>Como n�s podemos maximizar a
+    produtividade?</quote>.  Em vez disso, as pessoas fazem perguntas
+    muito mais espec�ficas, como: <quote>Como podemos alterar o
+    sistema de calend�rio para enviar lembretes dois dias antes ao
+    inv�s de um?</quote>, etc.  Mas � muito mais f�cil forjar
+    Perguntas Freq�entes imagin�rias do que descobrir as
+    verdadeiras.  Compilar uma verdadeira base de FAQ exige um
+    esfor�o cont�nuo e organizado: atrav�s do ciclo de vida do
+    software, as quest�es que chegam devem ser rastreadas, respostas
+    monitoradas, e tudo deve ser reunido em um todo coerente,
+    pesquis�vel que reflete a experi�ncia coletiva dos usu�rios
+    em seu mundo.  Isto requer a paci�ncia e a atitude observadora de
+    um cientista.  Nenhuma grande teoria ou pronunciamentos vision�rios
+    aqui—olhos abertos e anota��es precisas s�o o principal.</para>
+
+  <para>O que eu amo neste livro � que ele surgiu deste processo, e
+    isto � evidenciado em cada p�gina.  Ele � o resultado direto dos
+    encontros entre os autores e usu�rios.  Ele come�ou quando Ben
+    Collins-Sussman observou que as pessoas estavam fazendo as mesmas
+    perguntas b�sicas diversas vezes nas listas de discuss�o
+    do Subversion, como por exemplo: Quais s�o os
+    procedimentos-padr�o para se utilizar o Subversion?
+    Branches e tags funcionam do mesmo modo como em outros sistemas
+    de controle de vers�o?  Como eu posso saber quem realizou uma
+    altera��o em particular?</para>
+
+  <para>Frustrado em ver as mesmas quest�es dia ap�s dia, Ben
+    trabalhou intensamente durante um m�s no ver�o de 2002 para
+    escrever <citetitle>The Subversion Handbook</citetitle>, um
+    manual de sessenta p�ginas cobrindo todas as funcionalidades
+    b�sicas do Subversion.  O manual n�o tinha a pretens�o de ser
+    completo, mas ele foi distribu�do com o Subversion e auxiliou os
+    usu�rios a ultrapassarem as dificuldades iniciais na curva de
+    aprendizado.  Quando a O'Reilly and Associates decidiu publicar
+    um livro completo sobre o Subversion, o caminho menos cr�tico
+    estava �bvio: apenas estender o manual.</para>
+
+  <para>Para os tr�s co-autores do novo livro ent�o lhes foi dada uma
+    oportunidade �mpar.  Oficialmente, sua tarefa era escrever um
+    livro top-down, starting from a table of contents and an initial draft.  But they also had access to a steady
     stream—indeed, an uncontrollable geyser—of bottom-up
     source material.  Subversion was already in the hands of
     thousands of early adopters, and those users were giving tons of
     feedback, not only about Subversion, but about its existing
     documentation.</para>
 
-  <para>During the entire time they wrote this book, Ben, Mike, and
-    Brian haunted the Subversion mailing lists and chat rooms
-    incessantly, carefully noting the problems users were having in
-    real-life situations.  Monitoring such feedback was part of their
-    job descriptions at CollabNet anyway, and it gave them a huge
-    advantage when they set out to document Subversion.  The book
-    they produced is grounded firmly in the bedrock of experience,
-    not in the shifting sands of wishful thinking; it combines the
-    best aspects of user manual and FAQ sheet.  This duality might
-    not be noticeable on a first reading.  Taken in order, front to
-    back, the book is simply a straightforward description of a
-    piece of software.  There's the overview, the obligatory guided
-    tour, the chapter on administrative configuration, some advanced
-    topics, and of course a command reference and troubleshooting
-    guide.  Only when you come back to it later, seeking the
-    solution to some specific problem, does its authenticity shine
-    out: the telling details that can only result from encounters
+  <para>Durante todo o tempo em que eles escreveram o livro, Ben,
+    Mike, e Brian habitaram as listas de discuss�o e salas de
+    bate-papo do Subversion, registrando cuidadosamente os problemas
+    que os usu�rio estavam tendo em situa��es na vida-real.
+    Monitorar este feedback, fazia parte da descri��o de sua fun��o
+    na CollabNet, e isto lhes deu uma enorme vantagem quando
+    come�aram a documentar o Subversion.  O livro que eles produziram
+    � solidamente fundamentado na rocha da experi�ncia, n�o nas
+    areias mut�veis da ilus�o; ele combina os melhores aspectos de um
+    manual de usu�rio e uma base de FAQ.  Esta dualidade talvez n�o
+    seja percept�vel numa primeira leitura.  Lido na ordem, de frente
+    para tr�s, o livro � uma descri��o bem direta de uma pe�a de
+    software.  Existe a vis�o geral, o obrigat�rio tour, o cap�tulo
+    sobre configura��o administrativa, alguns t�picos avan�ados, e �
+    claro uma refer�ncia de comandos e um guia de resolu��o de
+    problemas.  Somente quando voc� o ler novamente mais tarde,
+    procurando a solu��o para um problema espec�fico, � que sua
+    autenticidade reluzir�: the telling details that can only result from encounters
     with the unexpected, the examples honed from genuine use cases,
     and most of all the sensitivity to the user's needs and the
     user's point of view.</para>
 
-  <para>Of course, no one can promise that this book will answer
-    every question you have about Subversion.  Sometimes, the
-    precision with which it anticipates your questions will seem
-    eerily telepathic; yet occasionally, you will stumble into a
-    hole in the community's knowledge, and come away empty-handed.
-    When this happens, the best thing you can do is email
-    <email>users at subversion.tigris.org</email> and present your
-    problem.  The authors are still there, still watching, and they
-    include not just the three listed on the cover, but many others
-    who contributed corrections and original material.  From the
-    community's point of view, solving your problem is merely a
-    pleasant side effect of a much larger project—namely,
+  <para>� claro, que ningu�m pode prometer que este livro responder�
+    todas as d�vidas que voc� tem sobre o Subversion.  Certas vezes,
+    a precis�o com que ele antecipa suas perguntas parecer�
+    assustadoramente telep�tica; ainda sim, ocasionalmente, voc� will stumble into a
+    hole no conhecimento da comunidade, e sair� de m�os-vazias.
+    Quando isto acontecer, a melhor coisa que voc� pode fazer �
+    enviar um email para <email>users at subversion.tigris.org</email> e
+    apresentar seu problema.  Os autores ainda est�o l�, continuam
+    observando, e n�o somente os tr�s listados na capa, mas muitos
+    outros que contribu�ram com corre��es e materiais originais.
+    Do ponto de vista da comunidade, resolver o seu problema �
+    meramente um agrad�vel efeito de um projeto muito maior—namely,
     slowly adjusting this book, and ultimately Subversion itself, to
     more closely match the way people actually use it.  They are
     eager to hear from you not merely because they can help you, but
-    because you can help them.  With Subversion as with all active
-    free software projects, <emphasis>you are not
-    alone</emphasis>.</para>
+    because you can help them.  Com o Subversion, assim como em todo
+    projeto ativo de software livre, <emphasis>voc� n�o est�
+    sozinho</emphasis>.</para>
 
-  <para>Let this book be your first companion.</para>
+  <para>Que este livro seja seu primeiro companheiro.</para>
 
 </preface>
 




More information about the svn-pt_br mailing list