Hi,
On 16/02/17 17:04, Edward K. Ream wrote:
[...]
Another idea: use markdown instead of rST
<http://stackoverflow.com/questions/2471804/using-sphinx-with-markdown-instead-of-rst>,
and (maybe) purge the discussion of rST from the intro. The great
advantage of markdown is that it is html behind the scenes, so things
like flowing text around graphics can be done easily. Also, a simple
script, found in LeoDocs.leo, creates markdown TOCs automatically. No
need for the rst3 command at all.
I'm in favor of markdown also. Particularly Pandoc's markdown flavor
[1]. It brings the simplicity and ubiquity of markdown and adds
extensibility via Yaml and parsers, hackeable in several languages
(including Python, of course).
I'm writing Grafoscopio Manual, as an interactive Grafoscopio notebook,
using Pandoc. These are early alphas in native format[2], markdown[3]
and PDF[4], of what can be done and seem a sensible approach to Leo.
[1] http://pandoc.org/
[2] http://mutabit.com/repos.fossil/grafoscopio/artifact/a86a41e66543e86f
[3]
http://mutabit.com/repos.fossil/grafoscopio/artifact/72ac90e809fd5998b7abd79d71e45b703c534914?txt=1
[4]
http://mutabit.com/repos.fossil/grafoscopio/raw/Docs/En/Books/Manual/manual.pdf?name=e1897649dcd2109aa46dc9caea846c8b0b4909e0
This is a great discussion we are having.
I agree :-).
Offray
Ps: Markdown is easier to type because doesn't require underlining like
reST and is less sensible to white space.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
