[Docstring-checkins] CVS: dps/spec pep-0258.txt,1.9,1.10

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/docstring/dps/spec
In directory usw-pr-cvs1:/tmp/cvs-serv15664/dps/spec

Modified Files:
	pep-0258.txt 
Log Message:
fixed whitespace

Index: pep-0258.txt
===================================================================
RCS file: /cvsroot/docstring/dps/spec/pep-0258.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** pep-0258.txt	13 Apr 2002 17:00:21 -0000	1.9
--- pep-0258.txt	18 Apr 2002 02:53:42 -0000	1.10
***************
*** 183,188 ****
      specifies:

!         A future statement must appear near the top of the module. The
!         only lines that can appear before a future statement are:

          * the module docstring (if any),
--- 183,188 ----
      specifies:

!         A future statement must appear near the top of the module.
!         The only lines that can appear before a future statement are:

          * the module docstring (if any),
***************
*** 315,320 ****
      Examples:

!     - Standalone/Raw/Plain: Just read a text file and process it. The
!       reader needs to be told which parser to use. Parser-specific
        readers?

--- 315,320 ----
      Examples:

!     - Standalone/Raw/Plain: Just read a text file and process it.  The
!       reader needs to be told which parser to use.  Parser-specific
        readers?

***************
*** 324,339 ****

      - PEP: RFC-822 headers, "PEP xxxx" and "RFC xxxx" conversion to
!       URIs. Either interpret PEPs' indented sections or convert existing
!       PEPs to reStructuredText (or both?).

      - Wiki: Global reference lookups of "wiki links" incorporated into
!       transforms. (CamelCase only or unrestricted?) Lazy indentation?

      - Web Page: As standalone, but recognize meta fields as meta tags.
!       Support for templates of some sort? (After <body>, before </body>?)

      - FAQ: Structured "question & answer(s)" constructs.

!     - Compound document: Merge chapters into a book. Master TOC file?

--- 324,341 ----

      - PEP: RFC-822 headers, "PEP xxxx" and "RFC xxxx" conversion to
!       URIs.  Either interpret PEPs' indented sections or convert
!       existing PEPs to reStructuredText (or both?).

      - Wiki: Global reference lookups of "wiki links" incorporated into
!       transforms.  (CamelCase only or unrestricted?)  Lazy
!       indentation?

      - Web Page: As standalone, but recognize meta fields as meta tags.
!       Support for templates of some sort?  (After <body>, before
!       </body>?)

      - FAQ: Structured "question & answer(s)" constructs.

!     - Compound document: Merge chapters into a book.  Master TOC file?

***************
*** 407,411 ****
      Examples:

!     - XML: Various forms, such as DocBook. Also, raw doctree XML.

      - HTML
--- 409,413 ----
      Examples:

!     - XML: Various forms, such as DocBook.  Also, raw doctree XML.

      - HTML