[Python-checkins] CVS: python/dist/src/Doc/ref ref1.tex,1.13,1.14 ref2.tex,1.31,1.32 ref3.tex,1.76,1.77

Tue, 27 Nov 2001 23:26:17 -0800

Update of /cvsroot/python/python/dist/src/Doc/ref
In directory usw-pr-cvs1:/tmp/cvs-serv17014/ref

Modified Files:
	ref1.tex ref2.tex ref3.tex 
Log Message:
Clean up some markup cruft.  A number of the macros that take no
parameters (like \UNIX) are commonly entered using an empty group to
separate the markup from a following inter-word space; this is not
needed when the next character is punctuation, or the markup is the
last thing in the enclosing group.  These cases were marked
inconsistently; the empty group is now *only* used when needed.

Index: ref1.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ref/ref1.tex,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** ref1.tex	2001/06/23 05:27:20	1.13
--- ref1.tex	2001/11/28 07:26:15	1.14
***************
*** 76,80 ****
  to describe the notion of `control character' if needed.
  \index{lexical definitions}
! \index{ASCII@\ASCII{}}

  Even though the notation used is almost the same, there is a big
--- 76,80 ----
  to describe the notion of `control character' if needed.
  \index{lexical definitions}
! \index{ASCII@\ASCII}

  Even though the notation used is almost the same, there is a big

Index: ref2.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ref/ref2.tex,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -d -r1.31 -r1.32
*** ref2.tex	2001/08/30 20:51:58	1.31
--- ref2.tex	2001/11/28 07:26:15	1.32
***************
*** 15,19 ****

  The run-time character set depends on the I/O devices connected to the
! program but is generally a superset of \ASCII{}.

  \strong{Future compatibility note:} It may be tempting to assume that the
--- 15,19 ----

  The run-time character set depends on the I/O devices connected to the
! program but is generally a superset of \ASCII.

  \strong{Future compatibility note:} It may be tempting to assume that the
***************
*** 53,57 ****

  A physical line ends in whatever the current platform's convention is
! for terminating lines.  On \UNIX{}, this is the \ASCII{} LF (linefeed)
  character.  On DOS/Windows, it is the \ASCII{} sequence CR LF (return
  followed by linefeed).  On Macintosh, it is the \ASCII{} CR (return)
--- 53,57 ----

  A physical line ends in whatever the current platform's convention is
! for terminating lines.  On \UNIX, this is the \ASCII{} LF (linefeed)
  character.  On DOS/Windows, it is the \ASCII{} sequence CR LF (return
  followed by linefeed).  On Macintosh, it is the \ASCII{} CR (return)
***************
*** 143,147 ****
  such that the total number of characters up to and including the
  replacement is a multiple of
! eight (this is intended to be the same rule as used by \UNIX{}).  The
  total number of spaces preceding the first non-blank character then
  determines the line's indentation.  Indentation cannot be split over
--- 143,147 ----
  such that the total number of characters up to and including the
  replacement is a multiple of
! eight (this is intended to be the same rule as used by \UNIX).  The
  total number of spaces preceding the first non-blank character then
  determines the line's indentation.  Indentation cannot be split over
***************
*** 309,313 ****
  \index{string literal}

! \index{ASCII@\ASCII{}}
  \begin{productionlist}
    \production{stringliteral}
--- 309,313 ----
  \index{string literal}

! \index{ASCII@\ASCII}
  \begin{productionlist}
    \production{stringliteral}
***************
*** 389,393 ****
  \lineii{\e x\var{hh}} {\ASCII{} character with hex value \var{hh}}
  \end{tableii}
! \index{ASCII@\ASCII{}}

  As in Standard C, up to three octal digits are accepted.  However,
--- 389,393 ----
  \lineii{\e x\var{hh}} {\ASCII{} character with hex value \var{hh}}
  \end{tableii}
! \index{ASCII@\ASCII}

  As in Standard C, up to three octal digits are accepted.  However,
***************
*** 597,601 ****
  lexically as delimiters, but also perform an operation.

! The following printing ASCII characters have special meaning as part
  of other tokens or are otherwise significant to the lexical analyzer:

--- 597,601 ----
  lexically as delimiters, but also perform an operation.

! The following printing \ASCII{} characters have special meaning as part
  of other tokens or are otherwise significant to the lexical analyzer:

***************
*** 607,611 ****
  occurrence outside string literals and comments is an unconditional
  error:
! \index{ASCII@\ASCII{}}

  \begin{verbatim}
--- 607,611 ----
  occurrence outside string literals and comments is an unconditional
  error:
! \index{ASCII@\ASCII}

  \begin{verbatim}

Index: ref3.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ref/ref3.tex,v
retrieving revision 1.76
retrieving revision 1.77
diff -C2 -d -r1.76 -r1.77
*** ref3.tex	2001/10/20 04:19:50	1.76
--- ref3.tex	2001/11/28 07:26:15	1.77
***************
*** 280,291 ****
  \index{character}
  \index{byte}
! \index{ASCII@\ASCII{}}

! (On systems whose native character set is not \ASCII{}, strings may use
  EBCDIC in their internal representation, provided the functions
  \function{chr()} and \function{ord()} implement a mapping between \ASCII{} and
  EBCDIC, and string comparison preserves the \ASCII{} order.
  Or perhaps someone can propose a better rule?)
! \index{ASCII@\ASCII{}}
  \index{EBCDIC}
  \index{character set}
--- 280,291 ----
  \index{character}
  \index{byte}
! \index{ASCII@\ASCII}

! (On systems whose native character set is not \ASCII, strings may use
  EBCDIC in their internal representation, provided the functions
  \function{chr()} and \function{ord()} implement a mapping between \ASCII{} and
  EBCDIC, and string comparison preserves the \ASCII{} order.
  Or perhaps someone can propose a better rule?)
! \index{ASCII@\ASCII}
  \index{EBCDIC}
  \index{character set}