From e15eb35fd0a038aead785a57526157e6745e0b09 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Wed, 10 Nov 1999 16:13:25 +0000 Subject: Use \citetitle as appropriate. --- Doc/mac/libmac.tex | 9 +++++---- Doc/mac/libmacfs.tex | 4 ++-- Doc/mac/mac.tex | 18 ++++++++++-------- Doc/ref/ref.tex | 21 ++++++++++++--------- Doc/ref/ref1.tex | 6 +++--- Doc/ref/ref3.tex | 33 +++++++++++++++------------------ 6 files changed, 47 insertions(+), 44 deletions(-) diff --git a/Doc/mac/libmac.tex b/Doc/mac/libmac.tex index 1301c01..ad21192 100644 --- a/Doc/mac/libmac.tex +++ b/Doc/mac/libmac.tex @@ -31,8 +31,8 @@ implemented as functions in the module. Not all operations possible in parameters will occasionally be different in Python (input and output buffers, especially). All methods and functions have a \code{__doc__} string describing their arguments and return values, and for -additional description you are referred to \emph{Inside Macintosh} or -similar works. +additional description you are referred to \citetitle{Inside +Macintosh} or similar works. The following modules are documented here: @@ -92,8 +92,9 @@ One additional function is available: This module is the Macintosh implementation of the \module{os.path} module. It is most portably accessed as -\module{os.path}\refstmodindex{os.path}. Refer to the \emph{Python Library -Reference} for documentation of \module{os.path}. +\module{os.path}\refstmodindex{os.path}. Refer to the +\citetitle[../lib/lib.html]{Python Library Reference} for +documentation of \module{os.path}. The following functions are available in this module: \function{normcase()}, diff --git a/Doc/mac/libmacfs.tex b/Doc/mac/libmacfs.tex index 86d8d0d..15ddfde 100644 --- a/Doc/mac/libmacfs.tex +++ b/Doc/mac/libmacfs.tex @@ -16,7 +16,7 @@ Manager, \program{finder} aliases and the Standard File package. Whenever a function or method expects a \var{file} argument, this argument can be one of three things:\ (1) a full or partial Macintosh pathname, (2) an \pytype{FSSpec} object or (3) a 3-tuple \code{(\var{wdRefNum}, -\var{parID}, \var{name})} as described in \emph{Inside +\var{parID}, \var{name})} as described in \citetitle{Inside Macintosh:\ Files}. A description of aliases and the Standard File package can also be found there. @@ -202,7 +202,7 @@ resource. \subsection{FInfo Objects \label{finfo-objects}} -See \emph{Inside Macintosh: Files} for a complete description of what +See \citetitle{Inside Macintosh: Files} for a complete description of what the various fields mean. \begin{memberdesc}[FInfo]{Creator} diff --git a/Doc/mac/mac.tex b/Doc/mac/mac.tex index ab47003..096ba11 100644 --- a/Doc/mac/mac.tex +++ b/Doc/mac/mac.tex @@ -24,16 +24,18 @@ \noindent This library reference manual documents Python's extensions for the -Macintosh. It should be used in conjunction with the \emph{Python -Library Reference}, which documents the standard library and built-in -types. +Macintosh. It should be used in conjunction with the +\citetitle[../lib/lib.html]{Python Library Reference}, which documents +the standard library and built-in types. This manual assumes basic knowledge about the Python language. For an -informal introduction to Python, see the \emph{Python Tutorial}; the -\emph{Python Reference Manual} remains the highest authority on -syntactic and semantic questions. Finally, the manual entitled -\emph{Extending and Embedding the Python Interpreter} describes how to -add new extensions to Python and how to embed it in other applications. +informal introduction to Python, see the +\citetitle[../tut/tut.html]{Python Tutorial}; the +\citetitle[../ref/ref.html]{Python Reference Manual} remains the +highest authority on syntactic and semantic questions. Finally, the +manual entitled \citetitle[../ext/ext.html]{Extending and Embedding +the Python Interpreter} describes how to add new extensions to Python +and how to embed it in other applications. \end{abstract} diff --git a/Doc/ref/ref.tex b/Doc/ref/ref.tex index 93acc11..b0636fb 100644 --- a/Doc/ref/ref.tex +++ b/Doc/ref/ref.tex @@ -32,15 +32,18 @@ extensive standard library are available in source or binary form without charge for all major platforms, and can be freely distributed. This reference manual describes the syntax and ``core semantics'' of -the language. It is terse, but attempts to be exact and complete. The -semantics of non-essential built-in object types and of the built-in -functions and modules are described in the \emph{Python Library -Reference}. For an informal introduction to the language, see the -\emph{Python Tutorial}. For \C{} or \Cpp{} programmers, two additional -manuals exist: \emph{Extending and Embedding the Python Interpreter} -describes the high-level picture of how to write a Python extension -module, and the \emph{Python/C API Reference Manual} describes the -interfaces available to C/C++ programmers in detail. +the language. It is terse, but attempts to be exact and complete. +The semantics of non-essential built-in object types and of the +built-in functions and modules are described in the +\citetitle[../lib/lib.html]{Python Library Reference}. For an +informal introduction to the language, see the +\citetitle[../tut/tut.html]{Python Tutorial}. For C or +\Cpp{} programmers, two additional manuals exist: +\citetitle[../ext/ext.html]{Extending and Embedding the Python +Interpreter} describes the high-level picture of how to write a Python +extension module, and the \citetitle[../api/api.html]{Python/C API +Reference Manual} describes the interfaces available to +C/\Cpp{} programmers in detail. \end{abstract} diff --git a/Doc/ref/ref1.tex b/Doc/ref/ref1.tex index 23bc05d..c35f157 100644 --- a/Doc/ref/ref1.tex +++ b/Doc/ref/ref1.tex @@ -29,9 +29,9 @@ text. Every Python implementation comes with a number of built-in and standard modules. These are not documented here, but in the separate -\emph{Python Library Reference} document. A few built-in modules are -mentioned when they interact in a significant way with the language -definition. +\citetitle[../lib/lib.html]{Python Library Reference} document. A few +built-in modules are mentioned when they interact in a significant way +with the language definition. \section{Notation\label{notation}} diff --git a/Doc/ref/ref3.tex b/Doc/ref/ref3.tex index 503b03b..cb861cd 100644 --- a/Doc/ref/ref3.tex +++ b/Doc/ref/ref3.tex @@ -629,28 +629,25 @@ dictionary; \member{__class__} is the instance's class. \ttindex{__class__}} \item[Files] -A file object represents an open file. File objects are created by the -\function{open()} built-in function, and also by -\function{os.popen()}, \function{os.fdopen()}, and the -\method{makefile()} method of socket objects (and perhaps by other -functions or methods provided by extension modules). The objects -\code{sys.stdin}, \code{sys.stdout} and \code{sys.stderr} are -initialized to file objects corresponding to the interpreter's -standard input, output and error streams. See the \emph{Python -Library Reference} for complete documentation of file objects. -\obindex{file} -\indexii{C}{language} -\index{stdio} -\bifuncindex{open} -\withsubitem{(in module os)}{\ttindex{popen()}} -\withsubitem{(socket method)}{\ttindex{makefile()}} +A file\obindex{file} object represents an open file. File objects are +created by the \function{open()}\bifuncindex{open} built-in function, +and also by +\withsubitem{(in module os)}{\ttindex{popen()}}\function{os.popen()}, +\function{os.fdopen()}, and the +\method{makefile()}\withsubitem{(socket method)}{\ttindex{makefile()}} +method of socket objects (and perhaps by other functions or methods +provided by extension modules). The objects +\ttindex{sys.stdin}\code{sys.stdin}, +\ttindex{sys.stdout}\code{sys.stdout} and +\ttindex{sys.stderr}\code{sys.stderr} are initialized to file objects +corresponding to the interpreter's standard\index{stdio} input, output +and error streams. See the \citetitle[../lib/lib.html]{Python Library +Reference} for complete documentation of file objects. \withsubitem{(in module sys)}{ \ttindex{stdin} \ttindex{stdout} \ttindex{stderr}} -\ttindex{sys.stdin} -\ttindex{sys.stdout} -\ttindex{sys.stderr} + \item[Internal types] A few types used internally by the interpreter are exposed to the user. -- cgit v0.12