[Docstring-checkins] CVS: dps/spec dps-notes.txt,1.34,1.35
Status: Pre-Alpha
Brought to you by:
goodger
From: David G. <go...@us...> - 2002-04-13 17:09:23
|
Update of /cvsroot/docstring/dps/spec In directory usw-pr-cvs1:/tmp/cvs-serv16216/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.34 retrieving revision 1.35 diff -C2 -d -r1.34 -r1.35 *** dps-notes.txt 4 Apr 2002 05:53:11 -0000 1.34 --- dps-notes.txt 13 Apr 2002 17:09:21 -0000 1.35 *************** *** 72,93 **** 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. ! ! - Remove dependency on names as sole distinguishing characteristic. ! 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 ! permanently, read by subsequent processing runs, and updated with ! new entries. ("Persistent ID mapping"?) ! ! - When resolving reference IDs from names, we must check for ! non-existent mappings. In the Writer or in a transform? ! - Add support for "refids" attribute on footnotes & citations, for ! backlinks. - Considerations for an HTML Writer [#]_: --- 72,82 ---- dps/readers. Potential nastiness.) ! - Perhaps store a name->id mapping file? This could be stored ! permanently, read by subsequent processing runs, and updated with ! new entries. ("Persistent ID mapping"?) ! - The name->id conversion and hyperlink resolution code needs to be ! checked for correctness and refactored. I'm afraid it's a bit of a ! spaghetti mess now. - Considerations for an HTML Writer [#]_: *************** *** 110,113 **** --- 99,108 ---- .. [#] Source: `HTML 4.0 in Netscape and Explorer`__. __ http://www.webreference.com/dev/html4nsie/index.html + + - Allow for style sheet info to be passed in, either as a <LINK>, or + as embedded style info. + + - Construct a templating system, as in ht2html/yaptu, using directives + and substitutions for dynamic stuff. |