[Docstring-checkins] CVS: dps/spec dps-notes.txt,1.31,1.32

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-serv28911/dps/spec

Modified Files:
	dps-notes.txt 
Log Message:
updated

Index: dps-notes.txt
===================================================================
RCS file: /cvsroot/docstring/dps/spec/dps-notes.txt,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -d -r1.31 -r1.32
*** dps-notes.txt	13 Mar 2002 02:48:34 -0000	1.31
--- dps-notes.txt	16 Mar 2002 06:11:18 -0000	1.32
***************
*** 5,8 ****
--- 5,9 ----
  :Revision: $Revision$

+ .. contents::

  To Do
***************
*** 100,104 ****
      Use IDs instead.

!     - Perhaps get rid of "name" attributes altoghether?

    - Perhaps keep a name->id mapping file?  This could be stored
--- 101,106 ----
      Use IDs instead.

!     - Perhaps get rid of "name" attributes altoghether?  Certainly get
!       rid of the "_:1:_" abominations.

    - Perhaps keep a name->id mapping file?  This could be stored
***************
*** 109,112 ****
--- 111,116 ----
      non-existent mappings.  In the Writer or in a transform?

+ - Add "refids" attribute to all target types, for backlinks.
+ 
  - Considerations for an HTML Writer [#]_:

***************
*** 120,125 ****
      attribute (<HTML>?).

!   - "Class" attributes should have no underscores (CSS requirement).

    .. [#] Source: `HTML 4.0 in Netscape and Explorer`__.
    __ http://www.webreference.com/dev/html4nsie/index.html
--- 124,133 ----
      attribute (<HTML>?).

!   - Docutils identifiers (the "class" and "id" attributes) will
!     conform to the regular expression ``[a-z][-a-z0-9]*``.  See
!     ``docutils.utils.id()``.

+   .. _HTML 4.01 spec: http://www.w3.org/TR/html401
+   .. _CSS1 spec: http://www.w3.org/TR/REC-CSS1
    .. [#] Source: `HTML 4.0 in Netscape and Explorer`__.
    __ http://www.webreference.com/dev/html4nsie/index.html
***************
*** 198,213 ****
  If a document is split up, each segment will need navigation links:
  parent, children (small TOC), previous (preorder), next (preorder).
- 
- 
- Table of Contents
- -----------------
- 
- This runs over the entire tree, and locates <section> elements. It
- produces a <contents> subtree, which can be inserted at the
- appropriate place, with links to the <section> elements. It needs to
- make sure that the links it uses are *real*, so ideally it will use
- the "implicit" link for a section when it exists, and it will have to
- invent one when the implicit link isn't there (presumably because the
- section is the twelfth "Introduction" in the document...).

--- 206,209 ----