summaryrefslogtreecommitdiff
path: root/docutils/docs/dev
diff options
context:
space:
mode:
authormilde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04>2019-10-29 22:48:34 +0000
committermilde <milde@929543f6-e4f2-0310-98a6-ba3bd3dd1d04>2019-10-29 22:48:34 +0000
commit981a74df7f0d290684e30443a0e586cc75a6b84a (patch)
tree72e108cd43ac71c8bc02d2f15b4c084aef3353bf /docutils/docs/dev
parentd99bb15425e033d19fd0c6b68223e67ce6991cce (diff)
downloaddocutils-981a74df7f0d290684e30443a0e586cc75a6b84a.tar.gz
Update/expand documentation of element attribute types.
git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk@8407 929543f6-e4f2-0310-98a6-ba3bd3dd1d04
Diffstat (limited to 'docutils/docs/dev')
-rw-r--r--docutils/docs/dev/testing.txt9
1 files changed, 8 insertions, 1 deletions
diff --git a/docutils/docs/dev/testing.txt b/docutils/docs/dev/testing.txt
index dbf50dcee..6336f16e7 100644
--- a/docutils/docs/dev/testing.txt
+++ b/docutils/docs/dev/testing.txt
@@ -252,7 +252,7 @@ reader, parser and writer.
Now run ``test_functional.py``. The test will fail, of course,
because you do not have an expected output yet. However, an output
file will have been generated in ``functional/output/``. Check this
-output file for validity and correctness. Then copy the file to
+output file for validity [#]_ and correctness. Then copy the file to
``functional/expected/``.
If you rerun ``test_functional.py`` now, it should pass.
@@ -265,6 +265,13 @@ actual output for validity and correctness, copy it to
``functional/expected/`` (overwriting the old expected output), and
commit the change.
+.. [#] The validity of `Docutils XML` can be tested with
+ ``xmllint <document-referencing-local-Docutils-DTD>.xml --valid --noout``.
+
+ .. note: the ``--dtdvalid`` and ``--nonet`` options did not help override
+ a reference to the PUBLIC "docutils.dtd" if there is a local version
+ on the system (e.g. /usr/share/xml/docutils/docutils.dtd in Debian).
+
.. _default configuration file: