summaryrefslogtreecommitdiffstats
path: root/doc/tools/doxybuilder_funcs.py
diff options
context:
space:
mode:
authorBen Kaduk <kaduk@mit.edu>2012-11-28 14:19:43 -0500
committerBen Kaduk <kaduk@mit.edu>2012-12-10 13:01:07 -0500
commit8bff1e50c28b6f11b771add7bd7d4a57419a567b (patch)
treed61dd973acd51feb628120172de6882bcb34289d /doc/tools/doxybuilder_funcs.py
parent4e0d270faad7fabd773cb159b8cb8e03adb19462 (diff)
downloadkrb5-8bff1e50c28b6f11b771add7bd7d4a57419a567b.tar.gz
krb5-8bff1e50c28b6f11b771add7bd7d4a57419a567b.tar.xz
krb5-8bff1e50c28b6f11b771add7bd7d4a57419a567b.zip
Reformat RST to avoid sphinx warnings
Old versions of docutils will see inline markup (e.g., :ref:`foo`) at the beginning of a line in the content of a directive block and attempt to interpret that markup as options or arguments to the directive. RST intended as inline markup (as opposed to modifying the behavior of the directive) will not be interpretable in this context, and causes Sphinx to emit a warning. Work around this behavior by always leaving a blank line before the content of a directive block, forcing it to be interpreted as content and not options or arguments. The buggy behavior was only encountered in note environments, but for consistency of style, also reformat warning and error blocks. Note the new style constraint in doc/README. ticket: 7469 (new) title: doc buildslave generates sphinx warnings tags: pullup target_version: 1.11
Diffstat (limited to 'doc/tools/doxybuilder_funcs.py')
0 files changed, 0 insertions, 0 deletions