Text-Restructured

 view release on metacpan or  search on metacpan

doc/src/latest/reStructuredText.html  view on Meta::CPAN

character from the start-string.</p>
</li>
<li><p class="first">An unescaped backslash preceding a start-string or end-string will
disable markup recognition, except for the end-string of <a class="reference" href="#inline-literals">inline
literals</a>.  See <a class="reference" href="#escaping-mechanism">Escaping Mechanism</a> above for details.</p>
</li>
</ol>
<p>For example, none of the following are recognized as containing inline
markup start-strings:</p>
<ul class="simple">
<li>asterisks: * "*" '*' (*) (* [*] {*} 1*x BOM32_*</li>
<li>double asterisks: **  a**b O(N**2) etc.</li>
<li>backquotes: ` `` etc.</li>
<li>underscores: _ __ __init__ __init__() etc.</li>
<li>vertical bars: | || etc.</li>
</ul>
<p>It may be desirable to use inline literals for some of these anyhow,
especially if they represent code snippets.  It's a judgment call.</p>
<p>These cases <em>do</em> require either literal-quoting or escaping to avoid
misinterpretation:</p>
<pre class="literal-block">*4, class_, *args, **kwargs, `TeX-quoted', *ML, *.txt

doc/src/reStructuredText.rst  view on Meta::CPAN

6. An inline markup end-string must be separated by at least one
   character from the start-string.

7. An unescaped backslash preceding a start-string or end-string will
   disable markup recognition, except for the end-string of `inline
   literals`_.  See `Escaping Mechanism`_ above for details.

For example, none of the following are recognized as containing inline
markup start-strings:

- asterisks: * "*" '*' (*) (* [*] {*} 1*x BOM32_*
- double asterisks: **  a**b O(N**2) etc.
- backquotes: ` `` etc.
- underscores: _ __ __init__ __init__() etc.
- vertical bars: | || etc.

It may be desirable to use inline literals for some of these anyhow,
especially if they represent code snippets.  It's a judgment call.

These cases *do* require either literal-quoting or escaping to avoid
misinterpretation::

t/40_writers/html.init/reStructuredText.html  view on Meta::CPAN

character from the start-string.</p>
</li>
<li><p class="first">An unescaped backslash preceding a start-string or end-string will
disable markup recognition, except for the end-string of <a class="reference" href="#inline-literals">inline
literals</a>.  See <a class="reference" href="#escaping-mechanism">Escaping Mechanism</a> above for details.</p>
</li>
</ol>
<p>For example, none of the following are recognized as containing inline
markup start-strings:</p>
<ul class="simple">
<li>asterisks: * "*" '*' (*) (* [*] {*} 1*x BOM32_*</li>
<li>double asterisks: **  a**b O(N**2) etc.</li>
<li>backquotes: ` `` etc.</li>
<li>underscores: _ __ __init__ __init__() etc.</li>
<li>vertical bars: | || etc.</li>
</ul>
<p>It may be desirable to use inline literals for some of these anyhow,
especially if they represent code snippets.  It's a judgment call.</p>
<p>These cases <em>do</em> require either literal-quoting or escaping to avoid
misinterpretation:</p>
<pre class="literal-block">*4, class_, *args, **kwargs, `TeX-quoted', *ML, *.txt

t/40_writers/html.init/reStructuredText.rst  view on Meta::CPAN

6. An inline markup end-string must be separated by at least one
   character from the start-string.

7. An unescaped backslash preceding a start-string or end-string will
   disable markup recognition, except for the end-string of `inline
   literals`_.  See `Escaping Mechanism`_ above for details.

For example, none of the following are recognized as containing inline
markup start-strings:

- asterisks: * "*" '*' (*) (* [*] {*} 1*x BOM32_*
- double asterisks: **  a**b O(N**2) etc.
- backquotes: ` `` etc.
- underscores: _ __ __init__ __init__() etc.
- vertical bars: | || etc.

It may be desirable to use inline literals for some of these anyhow,
especially if they represent code snippets.  It's a judgment call.

These cases *do* require either literal-quoting or escaping to avoid
misinterpretation::