# HG changeset patch
# User Javier Rojas <jerojasro@devnull.li>
# Date 1225764032 18000
# Node ID 2c2c86824c61661dbdfe7c7475f76ce3b6fde9a9
# Parent  4fa646914ff8cc356338db5c120a4f7b281c9b59
began translation of the "behind the scenes" chapter

diff -r 4fa646914ff8 -r 2c2c86824c61 es/Leame.1st
--- a/es/Leame.1st	Mon Nov 03 15:11:36 2008 -0500
+++ b/es/Leame.1st	Mon Nov 03 21:00:32 2008 -0500
@@ -101,6 +101,7 @@
 || tour-basic.tex  || Javier Rojas  ||    100%    || 19/10/2008 ||  27/10/2008 ||
 || undo.tex        || Igor Támara   ||     15%    || 26/10/2008 ||             ||
 || tour-merge.tex  || Javier Rojas  ||    100%    || 28/10/2008 ||  03/11/2008 ||
+|| concepts.tex    || Javier Rojas  ||      4%    || 03/11/2008 ||             ||
 
 == Archivos en proceso de revisión ==
 ||'''archivo''' || '''revisor''' ||'''Estado'''||'''Inicio'''||  '''Fin'''  ||
diff -r 4fa646914ff8 -r 2c2c86824c61 es/concepts.tex
--- a/es/concepts.tex	Mon Nov 03 15:11:36 2008 -0500
+++ b/es/concepts.tex	Mon Nov 03 21:00:32 2008 -0500
@@ -1,26 +1,29 @@
-\chapter{Behind the scenes}
+\chapter{Tras bambalinas}
 \label{chap:concepts}
 
-Unlike many revision control systems, the concepts upon which
-Mercurial is built are simple enough that it's easy to understand how
-the software really works.  Knowing this certainly isn't necessary,
-but I find it useful to have a ``mental model'' of what's going on.
+A diferencia de varios sistemas de control de revisiones, los
+conceptos en los que se fundamenta Mercurial son lo suficientemente
+simples como para entender fácilmente cómo funciona el software. 
+Saber esto no es necesario, pero considero útil tener un ``modelo
+mental'' de qué es lo que sucede.
 
-This understanding gives me confidence that Mercurial has been
-carefully designed to be both \emph{safe} and \emph{efficient}.  And
-just as importantly, if it's easy for me to retain a good idea of what
-the software is doing when I perform a revision control task, I'm less
-likely to be surprised by its behaviour.
+Comprender esto me da la confianza de que Mercurial ha sido
+cuidadosamente diseñado para ser tanto \emph{seguro} como
+\emph{eficiente}.  Y tal vez con la misma importancia, si es fácil
+para mí hacerme a una idea adecuada de qué está haciendo el software
+cuando llevo a cabo una tarea relacionada con control de revisiones,
+es menos probable que me sosprenda su comportamiento.
 
-In this chapter, we'll initially cover the core concepts behind
-Mercurial's design, then continue to discuss some of the interesting
-details of its implementation.
+En este capítulo, cubriremos inicialmente los conceptos centrales
+del diseño de Mercurial, y luego discutiremos algunos detalles
+interesantes de su implementación.
 
-\section{Mercurial's historical record}
+\section{Registro del historial de Mercurial}
 
-\subsection{Tracking the history of a single file}
+\subsection{Seguir el historial de un único fichero}
 
-When Mercurial tracks modifications to a file, it stores the history
+Cuando Mercurial sigue las modificaciones a un fichero, guarda el
+historial de dicho fichero en un objeto de metadatos llamado
 of that file in a metadata object called a \emph{filelog}.  Each entry
 in the filelog contains enough information to reconstruct one revision
 of the file that is being tracked.  Filelogs are stored as files in