From e865d212ffa1684207616d71ce7c5a9abd5e6684 Mon Sep 17 00:00:00 2001 From: goodger Date: Sun, 30 May 2004 18:55:49 +0000 Subject: [PATCH] updated git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk/docutils@2143 929543f6-e4f2-0310-98a6-ba3bd3dd1d04 --- docs/ref/rst/directives.txt | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/ref/rst/directives.txt b/docs/ref/rst/directives.txt index 9f0f11952..4d72e4c24 100644 --- a/docs/ref/rst/directives.txt +++ b/docs/ref/rst/directives.txt @@ -443,9 +443,14 @@ constructs a literal block where the text is parsed for inline markup. It is equivalent to a `line block`_ with different rendering: typically in a typewriter/monospaced typeface, like an ordinary literal block. Parsed literal blocks are useful for adding hyperlinks -to code examples. However, care must be taken with the text, because -inline markup is recognized; there is no protection from parsing. -Backslash-escapes may be necessary in places. +to code examples. + +However, care must be taken with the text, because inline markup is +recognized and there is no protection from parsing. Backslash-escapes +may be necessary to prevent unintended parsing. And because the +markup characters are removed by the parser, care must also be taken +with vertical alignment. Parsed "ASCII art" is tricky, and extra +whitespace may be necessary. For example, all the element names in this content model are links:: -- 2.11.4.GIT