[Python-checkins] python/dist/src/Doc/lib libdatetime.tex, 1.53, 1.53.2.1 libmmap.tex, 1.9, 1.9.4.1 libstdwin.tex, 1.26, 1.26.4.1 libxmlrpclib.tex, 1.18.2.2, 1.18.2.3 tkinter.tex, 1.27.2.2, 1.27.2.3

fdrake at users.sourceforge.net fdrake at users.sourceforge.net
Wed Jan 19 04:42:13 CET 2005


Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26451/Doc/lib

Modified Files:
      Tag: release24-maint
	libdatetime.tex libmmap.tex libstdwin.tex libxmlrpclib.tex 
	tkinter.tex 
Log Message:
fix a bunch of spelling errors
(closes SF patch #1104868)


Index: libdatetime.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libdatetime.tex,v
retrieving revision 1.53
retrieving revision 1.53.2.1
diff -u -d -r1.53 -r1.53.2.1
--- libdatetime.tex	15 Nov 2004 03:50:16 -0000	1.53
+++ libdatetime.tex	19 Jan 2005 03:42:09 -0000	1.53.2.1
@@ -23,7 +23,7 @@
 time adjustment.  Whether a naive \class{datetime} object represents
 Coordinated Universal Time (UTC), local time, or time in some other
 timezone is purely up to the program, just like it's up to the program
-whether a particular number represents meters, miles, or mass.  Naive
+whether a particular number represents metres, miles, or mass.  Naive
 \class{datetime} objects are easy to understand and to work with, at
 the cost of ignoring some aspects of reality.
 

Index: libmmap.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libmmap.tex,v
retrieving revision 1.9
retrieving revision 1.9.4.1
diff -u -d -r1.9 -r1.9.4.1
--- libmmap.tex	6 Jun 2004 16:51:46 -0000	1.9
+++ libmmap.tex	19 Jan 2005 03:42:09 -0000	1.9.4.1
@@ -35,7 +35,7 @@
 taken from the specified file.  Assignment to an
 \constant{ACCESS_READ} memory map raises a \exception{TypeError}
 exception.  Assignment to an \constant{ACCESS_WRITE} memory map
-affects both memory and the underlying file.  Assigment to an
+affects both memory and the underlying file.  Assignment to an
 \constant{ACCESS_COPY} memory map affects memory but does not update
 the underlying file.
 

Index: libstdwin.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libstdwin.tex,v
retrieving revision 1.26
retrieving revision 1.26.4.1
diff -u -d -r1.26 -r1.26.4.1
--- libstdwin.tex	12 Aug 2003 00:01:16 -0000	1.26
+++ libstdwin.tex	19 Jan 2005 03:42:09 -0000	1.26.4.1
@@ -114,7 +114,7 @@
 \end{funcdesc}
 
 \begin{funcdesc}{getscrmm}{}
-Return the screen size in millimeters.
+Return the screen size in millimetres.
 \end{funcdesc}
 
 \begin{funcdesc}{fetchcolor}{colorname}

Index: libxmlrpclib.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libxmlrpclib.tex,v
retrieving revision 1.18.2.2
retrieving revision 1.18.2.3
diff -u -d -r1.18.2.2 -r1.18.2.3
--- libxmlrpclib.tex	1 Jan 2005 00:34:53 -0000	1.18.2.2
+++ libxmlrpclib.tex	19 Jan 2005 03:42:09 -0000	1.18.2.3
@@ -5,7 +5,7 @@
 \moduleauthor{Fredrik Lundh}{fredrik at pythonware.com}
 \sectionauthor{Eric S. Raymond}{esr at snark.thyrsus.com}
 
-% Not everyting is documented yet.  It might be good to describe 
+% Not everything is documented yet.  It might be good to describe 
 % Marshaller, Unmarshaller, getparser, dumps, loads, and Transport.
 
 \versionadded{2.2}

Index: tkinter.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/tkinter.tex,v
retrieving revision 1.27.2.2
retrieving revision 1.27.2.3
diff -u -d -r1.27.2.2 -r1.27.2.3
--- tkinter.tex	19 Jan 2005 03:25:46 -0000	1.27.2.2
+++ tkinter.tex	19 Jan 2005 03:42:09 -0000	1.27.2.3
@@ -731,7 +731,7 @@
 Screen distances can be specified in either pixels or absolute
 distances.  Pixels are given as numbers and absolute distances as
 strings, with the trailing character denoting units: \code{c}
-for centimeters, \code{i} for inches, \code{m} for millimeters,
+for centimetres, \code{i} for inches, \code{m} for millimetres,
 \code{p} for printer's points.  For example, 3.5 inches is expressed
 as \code{"3.5i"}.
 



More information about the Python-checkins mailing list