[Python-checkins] CVS: python/dist/src/Doc/doc doc.tex,1.31,1.32

[Fred L. Drake]

Update of /cvsroot/python/python/dist/src/Doc/doc
In directory slayer.i.sourceforge.net:/tmp/cvs-serv28601/doc

Modified Files:
	doc.tex 
Log Message:

Document directories are not always named with three characters any more;
reported by Detlef Lannert <lannert@uni-duesseldorf.de>.


Index: doc.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/doc/doc.tex,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -r1.31 -r1.32
*** doc.tex	2000/09/16 21:23:25	1.31
--- doc.tex	2000/09/21 05:26:43	1.32
***************
*** 22,26 ****
  \begin{abstract}
  \noindent
! The Python language documentation has a substantial body of
  documentation, much of it contributed by various authors.  The markup
  used for the Python documentation is based on \LaTeX{} and requires a
--- 22,26 ----
  \begin{abstract}
  \noindent
! The Python language has a substantial body of
  documentation, much of it contributed by various authors.  The markup
  used for the Python documentation is based on \LaTeX{} and requires a
***************
*** 94,99 ****
      \term{Document Sources}
  	The \LaTeX{} sources for each document are placed in a
! 	separate directory.  These directories are given short,
! 	three-character names:
  
  	\begin{tableii}{p{.75in}|p{3in}}{filenq}{Directory}{Document Title}
--- 94,99 ----
      \term{Document Sources}
  	The \LaTeX{} sources for each document are placed in a
! 	separate directory.  These directories are given short
! 	names which vaguely indicate the document in each:
  
  	\begin{tableii}{p{.75in}|p{3in}}{filenq}{Directory}{Document Title}
***************
*** 161,165 ****
  
    Perhaps the most important concept to keep in mind while marking up
!   Python documentation is the while \TeX{} is unstructured, \LaTeX{} was
    designed as a layer on top of \TeX{} which specifically supports 
    structured markup.  The Python-specific markup is intended to extend
--- 161,165 ----
  
    Perhaps the most important concept to keep in mind while marking up
!   Python documentation is that while \TeX{} is unstructured, \LaTeX{} was
    designed as a layer on top of \TeX{} which specifically supports 
    structured markup.  The Python-specific markup is intended to extend
***************
*** 220,224 ****
    document class was that it serve a similar role as the LDP's HOWTO
    series, but the applicability of the class turns out to be somewhat
!   more broad.  This class is used for ``how-to'' documents (this
    document is an example) and for shorter reference manuals for small,
    fairly cohesive module libraries.  Examples of the later use include
--- 220,224 ----
    document class was that it serve a similar role as the LDP's HOWTO
    series, but the applicability of the class turns out to be somewhat
!   broader.  This class is used for ``how-to'' documents (this
    document is an example) and for shorter reference manuals for small,
    fairly cohesive module libraries.  Examples of the later use include
***************
*** 299,303 ****
        should be specified as a \keyword{typedef} name, \code{struct
        \var{tag}}, or the name of a primitive type.  If it is a pointer
!       type, the trailing asterisk should not be preceeded by a space.
        \var{name} should be the name of the function (or function-like
        pre-processor macro), and \var{args} should give the types and
--- 299,303 ----
        should be specified as a \keyword{typedef} name, \code{struct
        \var{tag}}, or the name of a primitive type.  If it is a pointer
!       type, the trailing asterisk should not be preceded by a space.
        \var{name} should be the name of the function (or function-like
        pre-processor macro), and \var{args} should give the types and
***************
*** 320,324 ****
        \keyword{typedef} name, \code{struct \var{tag}}, or the name of
        a primitive type.  If variable has a pointer type, the trailing
!       asterisk should \emph{not} be preceeded by a space.
      \end{envdesc}
  
--- 320,324 ----
        \keyword{typedef} name, \code{struct \var{tag}}, or the name of
        a primitive type.  If variable has a pointer type, the trailing
!       asterisk should \emph{not} be preceded by a space.
      \end{envdesc}