hgbook
diff fr/ch00-preface.xml @ 965:1421a5493113
Sadly, translation on preface is to be start over as it content has been completly changed
author | Romain PELISSE <belaran@gmail.com> |
---|---|
date | Sun Aug 16 13:18:39 2009 +0200 (2009-08-16) |
parents | en/ch00-preface.xml@d5688822c51d |
children | 48b202b19e2b |
line diff
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 1.2 +++ b/fr/ch00-preface.xml Sun Aug 16 13:18:39 2009 +0200 1.3 @@ -0,0 +1,262 @@ 1.4 +<!-- vim: set filetype=docbkxml shiftwidth=2 autoindent expandtab tw=77 : --> 1.5 + 1.6 +<preface id="chap:preface"> 1.7 + <?dbhtml filename="preface.html"?> 1.8 + <title>Preface</title> 1.9 + 1.10 + <sect1> 1.11 + <title>Technical storytelling</title> 1.12 + 1.13 + <para id="x_72e">A few years ago, when I wanted to explain why I believed 1.14 + that distributed revision control is important, the field was 1.15 + then so new that there was almost no published literature to 1.16 + refer people to.</para> 1.17 + 1.18 + <para id="x_72f">Although at that time I spent some time working on the 1.19 + internals of Mercurial itself, I switched to writing this book 1.20 + because that seemed like the most effective way to help the 1.21 + software to reach a wide audience, along with the idea that 1.22 + revision control ought to be distributed in nature. I publish 1.23 + the book online under a liberal license for the same 1.24 + reason: to get the word out.</para> 1.25 + 1.26 + <para id="x_730">There's a familiar rhythm to a good software book that 1.27 + closely resembles telling a story: What is this thing? Why does 1.28 + it matter? How will it help me? How do I use it? In this 1.29 + book, I try to answer those questions for distributed revision 1.30 + control in general, and for Mercurial in particular.</para> 1.31 + </sect1> 1.32 + 1.33 + <sect1> 1.34 + <title>Thank you for supporting Mercurial</title> 1.35 + 1.36 + <para id="x_731">By purchasing a copy of this book, you are supporting the 1.37 + continued development and freedom of Mercurial in particular, 1.38 + and of open source and free software in general. O'Reilly Media 1.39 + and I are donating my royalties on the sales of this book to the 1.40 + Software Freedom Conservancy (<ulink 1.41 + url="http://www.softwarefreedom.org/">http://www.softwarefreedom.org/</ulink>) 1.42 + which provides clerical and legal support to Mercurial and a 1.43 + number of other prominent and worthy open source software 1.44 + projects.</para> 1.45 + </sect1> 1.46 + 1.47 + <sect1> 1.48 + <title>Acknowledgments</title> 1.49 + 1.50 + <para id="x_732">This book would not exist were it not for the efforts of 1.51 + Matt Mackall, the author and project lead of Mercurial. He is 1.52 + ably assisted by hundreds of volunteer contributors across the 1.53 + world.</para> 1.54 + 1.55 + <para id="x_733">My children, Cian and Ruairi, always stood ready to help me 1.56 + to unwind with wonderful, madcap little-boy games. I'd also 1.57 + like to thank my ex-wife, Shannon, for her support.</para> 1.58 + 1.59 + <para id="x_734">My colleagues and friends provided help and support in 1.60 + innumerable ways. This list of people is necessarily very 1.61 + incomplete: Stephen Hahn, Karyn Ritter, Bonnie Corwin, James 1.62 + Vasile, Matt Norwood, Eben Moglen, Bradley Kuhn, Robert Walsh, 1.63 + Jeremy Fitzhardinge, Rachel Chalmers.</para> 1.64 + 1.65 + <para id="x_735">I developed this book in the open, posting drafts of 1.66 + chapters to the book web site as I completed them. Readers then 1.67 + submitted feedback using a web application that I developed. By 1.68 + the time I finished writing the book, more than 100 people had 1.69 + submitted comments, an amazing number considering that the 1.70 + comment system was live for only about two months towards the 1.71 + end of the writing process.</para> 1.72 + 1.73 + <para id="x_736">I would particularly like to recognize the following people, 1.74 + who between them contributed over a third of the total number of 1.75 + comments. I would like to thank them for their care and effort 1.76 + in providing so much detailed feedback.</para> 1.77 + 1.78 + <para id="x_737">Martin Geisler, Damien Cassou, Alexey Bakhirkin, Till Plewe, 1.79 + Dan Himes, Paul Sargent, Gokberk Hamurcu, Matthijs van der 1.80 + Vleuten, Michael Chermside, John Mulligan, Jordi Fita, Jon 1.81 + Parise.</para> 1.82 + 1.83 + <para id="x_738">I also want to acknowledge the help of the many people who 1.84 + caught errors and provided helpful suggestions throughout the 1.85 + book.</para> 1.86 + 1.87 + <para id="x_739">Jeremy W. Sherman, Brian Mearns, Vincent Furia, Iwan 1.88 + Luijks, Billy Edwards, Andreas Sliwka, Paweł Sołyga, Eric 1.89 + Hanchrow, Steve Nicolai, Michał Masłowski, Kevin Fitch, Johan 1.90 + Holmberg, Hal Wine, Volker Simonis, Thomas P Jakobsen, Ted 1.91 + Stresen-Reuter, Stephen Rasku, Raphael Das Gupta, Ned 1.92 + Batchelder, Lou Keeble, Li Linxiao, Kao Cardoso Félix, Joseph 1.93 + Wecker, Jon Prescot, Jon Maken, John Yeary, Jason Harris, 1.94 + Geoffrey Zheng, Fredrik Jonson, Ed Davies, David Zumbrunnen, 1.95 + David Mercer, David Cabana, Ben Karel, Alan Franzoni, Yousry 1.96 + Abdallah, Whitney Young, Vinay Sajip, Tom Towle, Tim Ottinger, 1.97 + Thomas Schraitle, Tero Saarni, Ted Mielczarek, Svetoslav 1.98 + Agafonkin, Shaun Rowland, Rocco Rutte, Polo-Francois Poli, 1.99 + Philip Jenvey, Petr Tesałék, Peter R. Annema, Paul Bonser, 1.100 + Olivier Scherler, Olivier Fournier, Nick Parker, Nick Fabry, 1.101 + Nicholas Guarracino, Mike Driscoll, Mike Coleman, Mietek Bák, 1.102 + Michael Maloney, László Nagy, Kent Johnson, Julio Nobrega, Jord 1.103 + Fita, Jonathan March, Jonas Nockert, Jim Tittsler, Jeduan 1.104 + Cornejo Legorreta, Jan Larres, James Murphy, Henri Wiechers, 1.105 + Hagen Möbius, Gábor Farkas, Fabien Engels, Evert Rol, Evan 1.106 + Willms, Eduardo Felipe Castegnaro, Dennis Decker Jensen, Deniz 1.107 + Dogan, David Smith, Daed Lee, Christine Slotty, Charles Merriam, 1.108 + Guillaume Catto, Brian Dorsey, Bob Nystrom, Benoit Boissinot, 1.109 + Avi Rosenschein, Andrew Watts, Andrew Donkin, Alexey Rodriguez, 1.110 + Ahmed Chaudhary.</para> 1.111 + </sect1> 1.112 + 1.113 + <sect1> 1.114 + <title>Conventions Used in This Book</title> 1.115 + 1.116 + <para id="x_73a">The following typographical conventions are used in this 1.117 + book:</para> 1.118 + 1.119 + <variablelist> 1.120 + <varlistentry> 1.121 + <term>Italic</term> 1.122 + 1.123 + <listitem> 1.124 + <para id="x_73b">Indicates new terms, URLs, email addresses, filenames, 1.125 + and file extensions.</para> 1.126 + </listitem> 1.127 + </varlistentry> 1.128 + 1.129 + <varlistentry> 1.130 + <term><literal>Constant width</literal></term> 1.131 + 1.132 + <listitem> 1.133 + <para id="x_73c">Used for program listings, as well as within 1.134 + paragraphs to refer to program elements such as variable 1.135 + or function names, databases, data types, environment 1.136 + variables, statements, and keywords.</para> 1.137 + </listitem> 1.138 + </varlistentry> 1.139 + 1.140 + <varlistentry> 1.141 + <term><userinput>Constant width bold</userinput></term> 1.142 + 1.143 + <listitem> 1.144 + <para id="x_73d">Shows commands or other text that should be typed 1.145 + literally by the user.</para> 1.146 + </listitem> 1.147 + </varlistentry> 1.148 + 1.149 + <varlistentry> 1.150 + <term><replaceable>Constant width italic</replaceable></term> 1.151 + 1.152 + <listitem> 1.153 + <para id="x_73e">Shows text that should be replaced with user-supplied 1.154 + values or by values determined by context.</para> 1.155 + </listitem> 1.156 + </varlistentry> 1.157 + </variablelist> 1.158 + 1.159 + <tip> 1.160 + <para id="x_73f">This icon signifies a tip, suggestion, or general 1.161 + note.</para> 1.162 + </tip> 1.163 + 1.164 + <caution> 1.165 + <para id="x_740">This icon indicates a warning or caution.</para> 1.166 + </caution> 1.167 + </sect1> 1.168 + 1.169 + <sect1> 1.170 + <title>Using Code Examples</title> 1.171 + 1.172 + <para id="x_741">This book is here to help you get your job done. In general, 1.173 + you may use the code in this book in your programs and 1.174 + documentation. You do not need to contact us for permission 1.175 + unless you’re reproducing a significant portion of the code. For 1.176 + example, writing a program that uses several chunks of code from 1.177 + this book does not require permission. Selling or distributing a 1.178 + CD-ROM of examples from O’Reilly books does require permission. 1.179 + Answering a question by citing this book and quoting example 1.180 + code does not require permission. Incorporating a significant 1.181 + amount of example code from this book into your product’s 1.182 + documentation does require permission.</para> 1.183 + 1.184 + <para id="x_742">We appreciate, but do not require, attribution. An 1.185 + attribution usually includes the title, author, publisher, and 1.186 + ISBN. For example: “<emphasis>Book Title</emphasis> by Some 1.187 + Author. Copyright 2008 O’Reilly Media, Inc., 1.188 + 978-0-596-xxxx-x.”</para> 1.189 + 1.190 + <para id="x_743">If you feel your use of code examples falls outside fair use 1.191 + or the permission given above, feel free to contact us at 1.192 + <email>permissions@oreilly.com</email>.</para> 1.193 + </sect1> 1.194 + 1.195 + <sect1> 1.196 + <title>Safari® Books Online</title> 1.197 + 1.198 + <note role="safarienabled"> 1.199 + <para id="x_744">When you see a Safari® Books Online icon on the cover of 1.200 + your favorite technology book, that means the book is 1.201 + available online through the O’Reilly Network Safari 1.202 + Bookshelf.</para> 1.203 + </note> 1.204 + 1.205 + <para id="x_745">Safari offers a solution that’s better than e-books. It’s a 1.206 + virtual library that lets you easily search thousands of top 1.207 + tech books, cut and paste code samples, download chapters, and 1.208 + find quick answers when you need the most accurate, current 1.209 + information. Try it for free at <ulink role="orm:hideurl:ital" 1.210 + url="http://my.safaribooksonline.com/?portal=oreilly">http://my.safaribooksonline.com</ulink>.</para> 1.211 + </sect1> 1.212 + 1.213 + <sect1> 1.214 + <title>How to Contact Us</title> 1.215 + 1.216 + <para id="x_746">Please address comments and questions concerning this book 1.217 + to the publisher:</para> 1.218 + 1.219 + <simplelist type="vert"> 1.220 + <member>O’Reilly Media, Inc.</member> 1.221 + 1.222 + <member>1005 Gravenstein Highway North</member> 1.223 + 1.224 + <member>Sebastopol, CA 95472</member> 1.225 + 1.226 + <member>800-998-9938 (in the United States or Canada)</member> 1.227 + 1.228 + <member>707-829-0515 (international or local)</member> 1.229 + 1.230 + <member>707 829-0104 (fax)</member> 1.231 + </simplelist> 1.232 + 1.233 + <para id="x_747">We have a web page for this book, where we list errata, 1.234 + examples, and any additional information. You can access this 1.235 + page at:</para> 1.236 + 1.237 + <simplelist type="vert"> 1.238 + <member><ulink url="http://www.oreilly.com/catalog/<catalog 1.239 + page>"></ulink></member> 1.240 + </simplelist> 1.241 + 1.242 + <remark>Don’t forget to update the <url> attribute, 1.243 + too.</remark> 1.244 + 1.245 + <para id="x_748">To comment or ask technical questions about this book, send 1.246 + email to:</para> 1.247 + 1.248 + <simplelist type="vert"> 1.249 + <member><email>bookquestions@oreilly.com</email></member> 1.250 + </simplelist> 1.251 + 1.252 + <para id="x_749">For more information about our books, conferences, Resource 1.253 + Centers, and the O’Reilly Network, see our web site at:</para> 1.254 + 1.255 + <simplelist type="vert"> 1.256 + <member><ulink url="http://www.oreilly.com"></ulink></member> 1.257 + </simplelist> 1.258 + </sect1> 1.259 +</preface> 1.260 + 1.261 +<!-- 1.262 +local variables: 1.263 +sgml-parent-document: ("00book.xml" "book" "preface") 1.264 +end: 1.265 +-->