moved "Importing Namespaces" to the dumpster -- discarded

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

1 files changed, 33 insertions, 34 deletions

diff --git a/sandbox/package-doc/multiple-input-files.txt b/sandbox/package-doc/multiple-input-files.txt
index d45b857ae..46a02f953 100644
--- a/sandbox/package-doc/multiple-input-files.txt
+++ b/sandbox/package-doc/multiple-input-files.txt
@@ -272,35 +272,6 @@ For instance, one could make "docs/ref/restructuredtext.txt" known as
     .. alias:: spec = docs/ref/restructuredtext.txt
 
 
-Importing Namespaces
---------------------
-
-While namespaces should generally be available without explicitly
-importing them (in order to avoid length headers), it would probably
-be handy to have a means of inserting all targets of another namespace
-into the current one (similar to Python's "from module import \*").
-The disadvantage is that it may cause confusion.
-
-Contenders for the syntax::
-
-    .. import:: namespace   (Pythonic)
-
-    .. import-targets:: namespace   (more verbose)
-
-    .. using:: namespace    (like C++)
-
-Or, provided that we use "``.. namespace:: short-name <- namespace``",
-and "```namespace -> target`_``" as reference syntax, this would be a
-logical fit::
-
-    .. namespace:: <- namespace
-    `-> target`_                   (instead of `namespace -> target`_)
-
-The advantage of this syntax is that we can prohibit importing more
-than one namespace, which might cause confusion.  Importing only one
-namespace might be a handy shortcut though.
-
-
 Qualifier Syntax
 ----------------
 
@@ -349,11 +320,10 @@ Implementation
 In order to parse sub-documents, we need to instantiate a new parser.
 
 This is made possible by turning the reader, parser, and writer
-parameters to the publisher into classes (or callbacks) instead of
-instances.
-
-The Parser must know about the Reader (or about the Publisher) and
-calls Reader.parse_[sub]document in order to parser sub-documents.
+parameters of the Publisher into classes (or callbacks) instead of
+instances.  The Parser must know about the Reader (or about the
+Publisher) and calls Reader.parse_[sub]document in order to parser
+sub-documents.
 
 
 Dumpster
@@ -437,6 +407,35 @@ which file ```-> html4css1`_`` links to) -- this may be significant
 since reStructuredText should be readable in its source form.
 
 
+Importing Namespaces
+--------------------
+
+While namespaces should generally be available without explicitly
+importing them (in order to avoid length headers), it would probably
+be handy to have a means of inserting all targets of another namespace
+into the current one (similar to Python's "from module import \*").
+The disadvantage is that it may cause confusion.
+
+Contenders for the syntax::
+
+    .. import:: namespace   (Pythonic)
+
+    .. import-targets:: namespace   (more verbose)
+
+    .. using:: namespace    (like C++)
+
+Or, provided that we use "``.. namespace:: short-name <- namespace``",
+and "```namespace -> target`_``" as reference syntax, this would be a
+logical fit::
+
+    .. namespace:: <- namespace
+    `-> target`_                   (instead of `namespace -> target`_)
+
+The advantage of this syntax is that we can prohibit importing more
+than one namespace, which might cause confusion.  Importing only one
+namespace might be a handy shortcut though.
+
+
 Caching
 -------