diff ja/daily.tex @ 379:beab196f78da

- more hook.tex - more daily.tex

--- a/ja/daily.tex	Fri Jan 09 23:05:26 2009 +0900
+++ b/ja/daily.tex	Thu Jan 15 16:34:43 2009 +0900
@@ -54,58 +54,98 @@
 %\subsection{Explicit versus implicit file naming}
 \subsection{$BL@<(E*$J%U%!%$%kL?L>BP0EL[$N%U%!%$%kL?L>(B}
 
-A useful behaviour that Mercurial has is that if you pass the name of
-a directory to a command, every Mercurial command will treat this as
-``I want to operate on every file in this directory and its
-subdirectories''.
+%A useful behaviour that Mercurial has is that if you pass the name of
+%a directory to a command, every Mercurial command will treat this as
+%``I want to operate on every file in this directory and its
+%subdirectories''.
+%\interaction{daily.files.add-dir}
+%Notice in this example that Mercurial printed the names of the files
+%it added, whereas it didn't do so when we added the file named
+%\filename{a} in the earlier example.
+
+Mercurial$B$NA4$F$N%3%^%s%I$O!$0z?t$H$7$F%G%#%l%/%H%jL>$rEO$9$H!$%G%#%l%/%H(B
+$B%j$NFb$NA4$F$N%U%!%$%k$H%5%V%G%#%l%/%H%j$KBP$9$kA`:n$G$"$k$H2r<a$9$k$?$a(B
+$BJXMx$G$"$k!%(B
 \interaction{daily.files.add-dir}
-Notice in this example that Mercurial printed the names of the files
-it added, whereas it didn't do so when we added the file named
-\filename{a} in the earlier example.
+$B$3$NNc$G$O(BMercurial$B$ODI2C$7$?%U%!%$%kL>$rI=<($7$F$$$k$,!$A0$NNc$G(B
+\filename{a}$B$H$$$&L>A0$N%U%!%$%k$rDI2C$7$?:]$K$OI=<($7$F$$$J$+$C$?E@$KCm(B
+$B0U$5$l$?$$!%(B
 
-What's going on is that in the former case, we explicitly named the
-file to add on the command line, so the assumption that Mercurial
-makes in such cases is that you know what you were doing, and it
-doesn't print any output.
+%What's going on is that in the former case, we explicitly named the
+%file to add on the command line, so the assumption that Mercurial
+%makes in such cases is that you know what you were doing, and it
+%doesn't print any output.
+
+$BA0$NNc$G$O%3%^%s%I%i%$%s$G$I$N%U%!%$%k$rDI2C$9$k$N$+$rL@<(E*$K;XDj$7$?$?(B
+$B$a!$(BMercurial$B$O%f!<%6$,2?$r$7$h$&$H$7$F$$$k$N$+J,$+$C$F$$$k$H?dDj$7$F2?$b(B
+$BI=<($7$J$+$C$?!%(B
 
-However, when we \emph{imply} the names of files by giving the name of
-a directory, Mercurial takes the extra step of printing the name of
-each file that it does something with.  This makes it more clear what
-is happening, and reduces the likelihood of a silent and nasty
-surprise.  This behaviour is common to most Mercurial commands.
+%However, when we \emph{imply} the names of files by giving the name of
+%a directory, Mercurial takes the extra step of printing the name of
+%each file that it does something with.  This makes it more clear what
+%is happening, and reduces the likelihood of a silent and nasty
+%surprise.  This behaviour is common to most Mercurial commands.
+
+$B$7$+$7%G%#%l%/%H%jL>$rM?$($k$3$H$G%U%!%$%kL>$r0EL[E*$KM?$($?>l9g!"(B
+Mercurial$B$O4XO"$9$k%U%!%$%k$NL>A0$r(B1$B$D$:$DI=<($9$kDI2C$N%9%F%C%W$rF'$`!%(B
+$B$3$l$K$h$C$F2?$,5/$3$C$F$$$k$N$+M}2r$7$d$9$/$9$k$H6&$K!$D@L[N"$KLq2p$JLd(B
+$BBj$,5/$3$k2DG=@-$r8:$i$7$F$$$k!%$3$N5sF0$O(BMercurial$B$NBgH>$N%3%^%s%I$K6&(B
+$BDL$7$F$$$k!%(B
 
 %\subsection{Aside: Mercurial tracks files, not directories}
-\subsection{$B$3$\$lOC(B: Mercurial$B$O%G%#%l%/%H%j$G$O$J$/%U%!%$%k$rDI@W$9$k(B}
+\subsection{$BM>CL(B: Mercurial$B$O%G%#%l%/%H%j$G$O$J$/%U%!%$%k$rDI@W$9$k(B}
 
-Mercurial does not track directory information.  Instead, it tracks
-the path to a file.  Before creating a file, it first creates any
-missing directory components of the path.  After it deletes a file, it
-then deletes any empty directories that were in the deleted file's
-path.  This sounds like a trivial distinction, but it has one minor
-practical consequence: it is not possible to represent a completely
-empty directory in Mercurial.
+%Mercurial does not track directory information.  Instead, it tracks
+%the path to a file.  Before creating a file, it first creates any
+%missing directory components of the path.  After it deletes a file, it
+%then deletes any empty directories that were in the deleted file's
+%path.  This sounds like a trivial distinction, but it has one minor
+%practical consequence: it is not possible to represent a completely
+%empty directory in Mercurial.
+
+Mercurial$B$O%G%#%l%/%H%j>pJs$rDI@W$7$J$$!%$=$NBe$o$j!$%U%!%$%k$X$N%Q%9$rDI(B
+$B@W$7$F$$$k!%%U%!%$%k$r:n@.$9$k:]$K$O!$$^$:%Q%9$N%G%#%l%/%H%jItJ,$rJd40$9(B
+$B$k!%%U%!%$%k$r>C5n$7$?8e$O!$%U%!%$%k$N4^$^$l$F$$$?6u$N%G%#%l%/%H%j$rA4$F(B
+$B>C5n$9$k!%$3$l$OEvA3$N5sF0$N$h$&$K8+$($k$,!$<B:]>e$O>.$5$JLdBj$r0z$-5/$3(B
+$B$9!%$9$J$o$A!$(BMercurial$B$O40A4$K6u$N%G%#%l%/%H%j$rI=8=$9$k$3$H$,$G$-$J$$$N(B
+$B$G$"$k!%(B
 
-Empty directories are rarely useful, and there are unintrusive
-workarounds that you can use to achieve an appropriate effect.  The
-developers of Mercurial thus felt that the complexity that would be
-required to manage empty directories was not worth the limited benefit
-this feature would bring.
+%Empty directories are rarely useful, and there are unintrusive
+%workarounds that you can use to achieve an appropriate effect.  The
+%developers of Mercurial thus felt that the complexity that would be
+%required to manage empty directories was not worth the limited benefit
+%this feature would bring.
+
+$B6u$N%G%#%l%/%H%j$,M-MQ$G$"$k$3$H$OLGB?$K$J$$$,!$E,Ev$J%o!<%/%"%i%&%s%I$H(B
+$B$7$F!$%j%]%8%H%j$NF0$-$rK8$2$J$$J}K!$,B8:_$9$k!%(B
+Mercurial$B$N3+H/<T$?$A$O!$6u$N%G%#%l%/%H%j$rI=8=$9$k$?$a$K2C$o$kJ#;($5$O!$$=(B
+$B$N5!G=$K8+9g$o$J$$$H9M$($?!%(B
 
-If you need an empty directory in your repository, there are a few
-ways to achieve this. One is to create a directory, then \hgcmd{add} a
-``hidden'' file to that directory.  On Unix-like systems, any file
-name that begins with a period (``\texttt{.}'') is treated as hidden
-by most commands and GUI tools.  This approach is illustrated in
-figure~\ref{ex:daily:hidden}.
+%If you need an empty directory in your repository, there are a few
+%ways to achieve this. One is to create a directory, then \hgcmd{add} a
+%``hidden'' file to that directory.  On Unix-like systems, any file
+%name that begins with a period (``\texttt{.}'') is treated as hidden
+%by most commands and GUI tools.  This approach is illustrated in
+%figure~\ref{ex:daily:hidden}.
+
+$B%j%]%8%H%j$K6u$N%G%#%l%/%H%j$,I,MW$J>l9g!$$3$l$r<B8=$9$kJ}K!$,$$$/$D$+$"(B
+$B$k!%(B1$B$DL\$O!$$^$:%G%#%l%/%H%j$r:n@.$7!$1#$7%U%!%$%k$r$3$N%G%#%l%/%H%jFb$K(B
+\hgcmd{add}$B$9$k!%(BUnix$B7O%7%9%F%`$G$O!$%T%j%*%I(B(``\texttt{.}'')$B$G;O$^$k%U%!(B
+$B%$%k$OBgH>$N%3%^%s%I$H(BGUI$B%D!<%k$G1#$7%U%!%$%k$H$7$F<h$j07$o$l$k!%(B
+$B>\:Y$K$D$$$F$O?^(B~\ref{ex:daily:hidden}$B$r;2>H$5$l$?$$!%(B
 
 \begin{figure}[ht]
   \interaction{daily.files.hidden}
-  \caption{Simulating an empty directory using a hidden file}
+%  \caption{Simulating an empty directory using a hidden file}
+  \caption{$B1#$7%U%!%$%k$r;H$C$F6u$N%G%#%l%/%H%j$r%7%_%e%l!<%H$9$k(B}
   \label{ex:daily:hidden}
 \end{figure}
 
-Another way to tackle a need for an empty directory is to simply
-create one in your automated build scripts before they will need it.
+%Another way to tackle a need for an empty directory is to simply
+%create one in your automated build scripts before they will need it.
+
+$B6u$N%G%#%l%/%H%j$r07$&JL$NJ}K!$K$O!$<+F0%S%k%I%9%/%j%W%H$NCf$G!$I,MW$K$J$k(B
+$BA0$K:n@.$9$k$3$H$,$"$k!%(B
 
 %\section{How to stop tracking a file}
 \section{$B%U%!%$%kDI@W$NDd;_(B}