Re: [Docutils-develop] emphasis/strong within literal_block?

[Bill B. <bb...@co...>]

On Tuesday, Dec 24, 2002, at 15:32 US/Eastern, Benja Fallenstein wrote:
> IMHO that wouldn't be worth it-- I don't see this as something used by 
> many users, and it is hackish anyway, because it messes up the 
> alignment of lines-- if I write a UML diagram as ASCII art, I'd have 
> to write:
>
> +---------+
> | *MyClass* |
> +---------+
>
> to put the "MyClass" in italics (at least, as far as I understand 
> parsed-literal I have to) for showing that it is an abstract class. 
> Also, I may have to escape asterisks etc. in the code. So, I don't 
> think it is generally useful enough to warrant its own syntax...

I'm not sure I understand that line of reasoning.  Your example-- bold 
text in ASCII art-- isn't currently possible if I understand things 
correctly (big if, still)?

A specific example: In the article I'm writing, I have examples of 
working with an interactive interpreter.  I want the output of the 
interpreter to be italicized, but-- outside of that-- I want the rest 
of it to be treated as a /pre/ block:

-- excerpt -- 

For example:

.. parsed-literal::
     % *python*
     Python 2.2 (#1, 07/14/02, 23:25:09)
     [GCC Apple cpp-precomp 6.14] on darwin
     Type "help", "copyright", "credits" or "license" for more 
information.
     >>> *from foo import bar*
     >>> *print "foobar"*
     foobar

-- end excerpt -- 

I'd rather simply have the 'For example:' be 'For example:;' (as 
opposed to the normal 'For example::').

The request for ':;' was explicitly because it will not require any 
changes [that I can think of] to existing REST source.  Specifically, 
it will not require escaping * characters unless you explicitly request 
a parsed-literal block.

It is merely a slight chunk of easily ignored syntactic sugar to give a 
hint to the docutils engine-- like the use of _, ``, ::, etc...

b.bum