[Python-checkins] CVS: distutils/doc/inst inst.tex,1.10,1.11

2000年4月19日 18:40:14 -0400 (EDT)

Update of /projects/cvsroot/distutils/doc/inst
In directory kaluha:/tmp/cvs-serv13250
Modified Files:
	inst.tex 
Log Message:
Changed '\tilde' and '\bslash' to the standard '\textasciitilde' and
'\textbackslash'.
Index: inst.tex
===================================================================
RCS file: /projects/cvsroot/distutils/doc/inst/inst.tex,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -r1.10 -r1.11
*** inst.tex	2000年04月19日 22:34:11	1.10
--- inst.tex	2000年04月19日 22:40:12	1.11
***************
*** 178,184 ****
 
 On Windows, you'd probably unpack the archive before opening the command
! prompt. If you downloaded the archive file to \file{C:\bslash{}Temp},
 then it probably unpacked (depending on your software) into
! \file{C:\bslash{}Temp\bslash{}foo-1.0}; from the command prompt window,
 you would then run
 \begin{verbatim}
--- 178,184 ----
 
 On Windows, you'd probably unpack the archive before opening the command
! prompt. If you downloaded the archive file to \file{C:\textbackslash{}Temp},
 then it probably unpacked (depending on your software) into
! \file{C:\textbackslash{}Temp\textbackslash{}foo-1.0}; from the command prompt window,
 you would then run
 \begin{verbatim}
***************
*** 279,283 ****
 \lineiv{Windows}
 {\filenq{\var{prefix}}}
! {\filenq{C:\bslash{}Python}}
 {(2)}
 \lineiv{Mac~OS (pure)}
--- 279,283 ----
 \lineiv{Windows}
 {\filenq{\var{prefix}}}
! {\filenq{C:\textbackslash{}Python}}
 {(2)}
 \lineiv{Mac~OS (pure)}
***************
*** 299,303 ****
 \filevar{exec-prefix} are \file{/usr/local}.
 \item[(2)] The default installation directory on Windows was
! \file{C:\bslash{}Program Files\bslash{}Python} under Python 1.6a1,
 1.5.2, and earlier.
 \end{description}
--- 299,303 ----
 \filevar{exec-prefix} are \file{/usr/local}.
 \item[(2)] The default installation directory on Windows was
! \file{C:\textbackslash{}Program Files\textbackslash{}Python} under Python 1.6a1,
 1.5.2, and earlier.
 \end{description}
***************
*** 392,396 ****
 \end{verbatim}
 where you can supply any directory you like for the \longprogramopt{home}
! option. Lazy typists can just type a tilde (\code{\tilde}); the
 \command{install} command will expand this to your home directory:
 \begin{verbatim}
--- 392,396 ----
 \end{verbatim}
 where you can supply any directory you like for the \longprogramopt{home}
! option. Lazy typists can just type a tilde (\code{\textasciitilde}); the
 \command{install} command will expand this to your home directory:
 \begin{verbatim}
***************
*** 488,492 ****
 python setup.py install --prefix="\Temp\Python"
 \end{verbatim}
! to install modules to the \file{\bslash{}Temp} directory on the current
 drive.
 
--- 488,492 ----
 python setup.py install --prefix="\Temp\Python"
 \end{verbatim}
! to install modules to the \file{\textbackslash{}Temp} directory on the current
 drive.
 
***************
*** 496,501 ****
 \installscheme{prefix}{}
 {prefix}{}
! {prefix}{\bslash{}Scripts}
! {prefix}{\bslash{}Data}
 
 
--- 496,501 ----
 \installscheme{prefix}{}
 {prefix}{}
! {prefix}{\textbackslash{}Scripts}
! {prefix}{\textbackslash{}Data}
 
 
***************
*** 547,551 ****
 For example, say you're installing a module distribution to your home
 directory under Unix---but you want scripts to go in
! \file{\tilde/scripts} rather than \file{\tilde/bin}. As you might
 expect, you can override this directory with the
 \longprogramopt{install-scripts} option; in this case, it makes most sense to
--- 547,551 ----
 For example, say you're installing a module distribution to your home
 directory under Unix---but you want scripts to go in
! \file{\textasciitilde/scripts} rather than \file{\textasciitilde/bin}. As you might
 expect, you can override this directory with the
 \longprogramopt{install-scripts} option; in this case, it makes most sense to