[Docutils-checkins] docutils/docs/dev todo.txt,1.222,1.223

[Felix W. <fel...@us...>]

Update of /cvsroot/docutils/docutils/docs/dev
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18915

Modified Files:
	todo.txt 
Log Message:
updated

Index: todo.txt
===================================================================
RCS file: /cvsroot/docutils/docutils/docs/dev/todo.txt,v
retrieving revision 1.222
retrieving revision 1.223
diff -u -d -r1.222 -r1.223
--- todo.txt	3 Jun 2004 17:36:10 -0000	1.222
+++ todo.txt	3 Jun 2004 19:28:37 -0000	1.223
@@ -81,7 +81,7 @@
   /usr/local/etc/docutils.conf too?  See the `Filesystem Hierarchy
   Standard`_.
 
-  .. _Filesystem Hierarchy Standard: http://www.pathname.com/fhs.
+  .. _Filesystem Hierarchy Standard: http://www.pathname.com/fhs
 
 * Add _`object numbering and object references` (tables & figures).
   These would be the equivalent of DocBook's "formal" elements.
@@ -193,7 +193,7 @@
   mapping database for cross-references.  Docutils could use a similar
   system for large-scale, multipart documents.
 
-  __ rst/directives.html#including-an-external-document-fragment
+  __ ../ref/rst/directives.html#including-an-external-document-fragment
 
   Aahz's idea:
 
@@ -450,7 +450,8 @@
   ``##`` is useful though.  It allows doc-comments and implementation
   comments.
 
-  .. _additional docstrings: pep-0258.html#additional-docstrings
+  .. _additional docstrings:
+     ../peps/pep-0258.html#additional-docstrings
 
 * HappyDoc uses an initial comment block to set "parser configuration
   values".  Do the same thing for Docutils, to set runtime settings on
@@ -698,9 +699,9 @@
   somehow?  See docutils-develop 2003-02-13.
 
 * Include the _`character entity substitution definition files`
-  `temporarily stored here <tmp/charents>`__, perhaps in a
-  ``docutils/parsers/rst/includes/`` directory.  See `misc.include`_
-  below.
+  `temporarily stored here <http://docutils.sf.net/tmp/charents/>`__,
+  perhaps in a ``docutils/parsers/rst/includes/`` directory.  See
+  `misc.include`_ below.
 
 * Should ^L (or something else in reST) be defined to mean
   force/suggest page breaks in whatever output we have?