I would like to suggest a straightforward enhancement for reST.
An option to be added to the conf.py file:

line_break="a_string"

If the option is missing there will be no change in the current
processing flow, i.e. no integrity issue with previous versions.
If the option is set, reST will substitute all end line "a_string"
with line break in the HTML document, i.e. <br>.

The reasoning is that a lot of documentations are more instructive
rather than descriptive, in particular the one that I am developing.

Hope it will be worth of implementing it.

Thank all,
Marin

Christophe de VIENNE wrote:
Hi, and Happy new Year to all !

2008/12/31 MIM <[email protected]>:
  
* Item 1a.  \
   Item 1b.
* Item 2.

should be the more appropriate way to handle long lines.
    
This is not the way Rest has been thought.

When you write documentation, most of the lines are long lines. So
writing a \ would quickly become a nightmare.

If you really need two lines in you item you can write this :

* Item 1a

   Item 1b
* Item 2.



Christophe



  


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sphinx-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to