[Docstring-checkins] CVS: dps/spec dps-notes.txt,1.25,1.26

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-serv29118

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.25
retrieving revision 1.26
diff -C2 -d -r1.25 -r1.26
*** dps-notes.txt	13 Feb 2002 02:25:29 -0000	1.25
--- dps-notes.txt	15 Feb 2002 22:55:08 -0000	1.26
***************
*** 75,78 ****
--- 75,111 ----
    dps/readers. Potential nastiness.)
  
+ - Add "name" -> "id" attribute conversion.  We must have unique,
+   SGML-ID-friendly id's and a one-to-one mapping for later lookup.
+ 
+   - Add conversion to nodes.document record-keeping code? Or as a new
+     transform?
+ 
+   - Use a "name mangling" scheme (like name "section title" becomes id
+     "section_title", name "1" becomes id "footnote1")?  Or use an
+     arbitrary sequential id?  How to do inter-document references in
+     that case?
+ 
+   - ID everything?  Or only named elements?
+ 
+   - How to do inter-document references in *any* case?
+ 
+   - Perhaps keep a name->id mapping file?  This could be stored
+     permanently, read by subsequent processing runs, and updated with
+     new entries.  
+ 
+ - Considerations for an HTML Writer [#]_:
+ 
+   - Boolean attributes. ``<element boolean>`` is good, ``<element
+     boolean="boolean">`` is bad.  Use a special value in attributes
+     mapping, such as ``None``?
+ 
+   - Escape double-dashes inside comments.
+ 
+   - Put the language code into an appropriate element's LANG
+     attribute (<HTML>?).
+ 
+   .. [#] Source: `HTML 4.0 in Netscape and Explorer`__.
+   __ http://www.webreference.com/dev/html4nsie/index.html
+ 
  
  Coding Conventions