updated

git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk@1548 929543f6-e4f2-0310-98a6-ba3bd3dd1d04

1 files changed, 32 insertions, 22 deletions

diff --git a/docutils/docs/dev/todo.txt b/docutils/docs/dev/todo.txt
index 96650ea7b..eab2208fe 100644
--- a/docutils/docs/dev/todo.txt
+++ b/docutils/docs/dev/todo.txt
@@ -338,6 +338,10 @@ General
   with examples of every setting (possibly commented).  It's currently
   sparse, requiring doc lookups.
 
+* Add internationalization to footer boilerplate text (resulting from
+  "--generator", "--source-link", and "--date" etc.), allowing
+  translations.
+
 
 Documentation
 -------------
@@ -929,36 +933,42 @@ when used in a document.
     Add an option to include topics in the TOC?  Another for sidebars?
     See docutils-develop 2003-01-29.
 
-  - _`misc.include`: "encoding" option?  Take default from runtime
-    settings.  Use Input component to read it in?
+  - _`misc.include`:
+
+    - "encoding" option?  Take default from runtime settings.  Use
+      Input component to read it in?
+
+    - Option to select a range of lines?
 
-    Option to select a range of lines?
+    - Option to label lines?
 
-    Option to label lines?
+    - Default directory for "built-in includes", using the C syntax
+      ``#include <name>``?
 
-    Default directory for "built-in includes", using the C syntax
-    ``#include <name>``?
+          Use C-preprocessor semantics for locating include files?
+          E.g., ``.. include:: file.txt`` will read another file into
+          the current one, relative to the current file's directory,
+          and ``.. include:: <standard>`` will read a standard include
+          file from ``docutils/include/``.  (Should "quotes" be
+          required around non-standard include files?)
 
-        Use C-preprocessor semantics for locating include files?
-        E.g., ``.. include:: file.txt`` will read another file into
-        the current one, relative to the current file's directory, and
-        ``.. include:: <standard>`` will read a standard include file
-        from ``docutils/include/``.  (Should "quotes" be required
-        around non-standard include files?)
+          -- http://sf.net/mailarchive/message.php?msg_id=1938401
 
-        -- http://sf.net/mailarchive/message.php?msg_id=1938401
+      I now think that ``docutils/parsers/rst/include/`` is a better
+      place for these files, since they're reStructuredText-specific.
 
-    I now think that ``docutils/parsers/rst/include/`` is a better
-    place for these files, since they're reStructuredText-specific.
+      Keeping standard data files together with the package code makes
+      sense to me.  It seems much less complex to implement than a
+      separate system data directory, such as ``/usr/share/docutils``.
+      Any reason a system data directory should be used?  How does
+      Distutils handle data files?
 
-    Keeping standard data files together with the package code makes
-    sense to me.  It seems much less complex to implement than a
-    separate system data directory, such as ``/usr/share/docutils``.
-    Any reason a system data directory should be used?  How does
-    Distutils handle data files?
+      How about an environment variable, say RSTINCLUDEPATH or
+      RSTPATH?  This could be combined with a setting/option to allow
+      user-defined include directories.
 
-    For a specific application, see the discussion of `character
-    entity substitution definition files`_ above.
+      For a specific application, see the discussion of `character
+      entity substitution definition files`_ above.
 
 * Implement directives.  Each of the list items below begins with an
   identifier of the form, "module_name.directive_function_name".  The