Re: Rendering math in Leo

[Edward K. Ream]

On Sun, Jun 10, 2018 at 9:36 PM, Thomas Passin  wrote:

> To contribute to this thread after many months:
>
> Actually, python-markdown does support math via mathjax
>
​...
​


>
> But the real problem, as I see it, with the markdown package is not the
> math but that it does not add a stylesheet to the html output.  And I don't
> feel like figuring one out.  It's just too tedious.
>

​Thanks for this.  I've just added a link to this discussion to #633
.

For now, I've decided to stick with reStructuredText to generate Sphinx
sources, to this doesn't have a high priority.

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Thomas Passin]

To contribute to this thread after many months:

Actually, python-markdown does support math via mathjax, if you install 
mdx_math and use it as one of the extensions.  mdx_math is just a python 
file - you can install it using pip - so it will work on any python 
installation.  To use it in viewrendered and vr2, create a @setting  node 
with the headline

@string view-rendered-md-extensions = mdx_math

You also have to do one more thing, though, which is to cause the html 
output to emit the right mathjax script elements, so that mathjax gets 
loaded.  I conditionally add the following the the html generated by 
markdown:

MD_MATHJAX_SCRIPT = r'''
MathJax.Hub.Config({
  config: ["MMLorHTML.js"],
  jax: ["input/TeX", "output/HTML-CSS", "output/NativeMML"],
  extensions: ["MathMenu.js", "MathZoom.js"],
  "HTML-CSS": { fonts: ["TeX"] }
});

https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.4/MathJax.js";>
'''

_script_header = MD_MATHJAX_SCRIPT if 'type="math/tex' in html else 
''
html = _script_header + 'body{background-color:%s;}\n' 
%(self.md_background_color) + html

But the real problem, as I see it, with the markdown package is not the 
math but that it does not add a stylesheet to the html output.  And I don't 
feel like figuring one out.  It's just too tedious.

On Friday, October 20, 2017 at 11:24:03 AM UTC-4, Terry Brown wrote:
>
> On Fri, 20 Oct 2017 07:05:44 -0700 (PDT) 
> "Edward K. Ream" > wrote: 
>
> > Leo can already render LaTex math markup using reStructuredText 
>
> ...
> Not sure but markdown.py may not handle math.  But an obvious 
> alternative is to use pandoc for markdown -> html, which definitely 
> supports math. 
>
> Cheers -Terry 
>
>
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Edward K. Ream]

On Fri, Oct 27, 2017 at 12:15 AM, Matt Wilkie  wrote:

> Jumping in for just pandoc part of the thread: I happened upon `pypandoc`
> today when looking in to better formatting of the Leo PyPi page overview:
> https://pypi.python.org/pypi/pypandoc. A simple implementation of which
> is in https://github.com/leo-editor/leo-editor/commit/
> 75d0cc0c605c1a298eac0d0bcfb0b4a5e8285ac6. It reads a markdown file from
> disk and returns an rST version. Quick, simple.
>
> Just raising here in case the library relevant to general Leo-pandoc
> integration. (And BTW, don't bother with the pypi package named `pandoc`,
> it's not pandoc the program/library, it's just documentation.)
>

​Thanks for this heads up.

In a similar vein, Jupyter uses pygments as part of
the syntax coloring process.​ It's easy to write new lexers
, and it may even be possible
to graft (monkey-patch?) a general Leo-directives lexer onto existing
lexers.  I have just created #565
 to explore this
possibility.

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Matt Wilkie]

Jumping in for just pandoc part of the thread: I happened upon `pypandoc`
today when looking in to better formatting of the Leo PyPi page overview:
https://pypi.python.org/pypi/pypandoc. A simple implementation of which is
in
https://github.com/leo-editor/leo-editor/commit/75d0cc0c605c1a298eac0d0bcfb0b4a5e8285ac6.
It reads a markdown file from disk and returns an rST version. Quick,
simple.

Just raising here in case the library relevant to general Leo-pandoc
integration. (And BTW, don't bother with the pypi package named `pandoc`,
it's not pandoc the program/library, it's just documentation.)

Matt


On Tue, Oct 24, 2017 at 10:49 AM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:

> Upps. This is the last part of the sentence:
>
>
> On 24/10/17 12:29, Offray Vladimir Luna Cárdenas wrote:
> >
> > Yes, I know that @language md is available. I'm trying to suggest
> > better integration making Markdown (Pandoc's variant) the default
> > choice for documentation, following Jupyter (and almost every body
> > else example). I'm generally against ad-populum argument (something is
> > good, because is popular), but in the case of Pandoc's Markdown, I
> > think they have
> >
>
> reached a sweet spot between a format that is light, complete, popular
> and extensible.
>
>
> --
> 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 leo-editor+unsubscr...@googlegroups.com.
> To post to this group, send email to leo-editor@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Offray Vladimir Luna Cárdenas]

Upps. This is the last part of the sentence:


On 24/10/17 12:29, Offray Vladimir Luna Cárdenas wrote:
>
> Yes, I know that @language md is available. I'm trying to suggest
> better integration making Markdown (Pandoc's variant) the default
> choice for documentation, following Jupyter (and almost every body
> else example). I'm generally against ad-populum argument (something is
> good, because is popular), but in the case of Pandoc's Markdown, I
> think they have
>

reached a sweet spot between a format that is light, complete, popular
and extensible.


-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Offray Vladimir Luna Cárdenas]

Hi,


On 24/10/17 03:50, Edward K. Ream wrote:
> On Mon, Oct 23, 2017 at 6:59 PM, Offray Vladimir Luna Cárdenas
> > wrote:
>
> I second Terry's idea of going with Markdown, particularly Pandoc's
> variant, which is pretty mature and with an active community
> discussing
> a lot of details to support a complete writing & publishing workflow,
> the ubiquity advantage with a lot of variants everywhere (Ghost, Stack
> Overflow, GitHub, Fossil). 
>
>
> ​Some of Leo's recent documentation files use @language md.  See this
> FAQ entry
> .
> As mentioned in this FAQ, I use @button make-md-heads to generate a
> TOC.  Perhaps this process could be automated.

Yes, I know that @language md is available. I'm trying to suggest better
integration making Markdown (Pandoc's variant) the default choice for
documentation, following Jupyter (and almost every body else example).
I'm generally against ad-populum argument (something is good, because is
popular), but in the case of Pandoc's Markdown, I think they have

>
> Recently, at our local hackerspace [1] we
> opened the Data Journalism Handbook [2][2a] as a Grafoscopio document
> and produced a PDF (13 Mb) [3] from a Pandoc's Markdown file
> (500Kb) [4]
> generated from a single Grafoscopio notebook/outline (600 Kb). This
> workflow was pretty well supported by Pandoc's Markdown.
>
>
> ​It's difficult to follow the links because I don't understand Spanish.

You don't need to. We have make an English translation available in the
repository [1], for the general introduction, but we follow a "local
first" approach, favoring local language and culture, which seems
reasonable after (mostly) teaching myself English to become part of
several communities and experimenting first hand the English monopoly in
science and tech (see a critical look at [2]). The important issue is
that you can produce a nice looking long PDF from a single small, self
referential & programmable outline file, using what Pandoc and such (Leo
inspired) outlining technology has to offer. This is not available now
in the Jupyter world and you need to go with the pile of files approach.
That's why offering bridging powerful Leo outlining and Jupyter is
important.
[1] http://mutabit.com/repos.fossil/mapeda/
[2] https://aeon.co/essays/how-did-science-come-to-speak-only-english

> ​
>
>
> I proposed some Qt Web technology to show markdown (including math)
> inside Leo nodes. Maybe the IPython Qt Console, which supports this
> rendering could be inspiring here[6], but I don't know about the math
> rendering support in that case..
>
>
> ​Exactly.  I have been thinking of "borrowing" the IPython Qt Console
> approach.  Iirc, there are many complex details behind the scenes
> involved in piping the results to the console. Such details may be
> simpler within Leo, or not.
>
> In any event, the general goal is to make /all/ rendering as simple as
> possible in Leo. This is why I am proposing that we read the users
> manuals for other systems, looking for /goals/. Only after we have a
> clear idea of what we want does it make sense to look into how to do
> it.  This was an Aha that came to me on vacation.
>

Seems clever. I keep an eye on Jupyter, Clojure, Org Mode, Leo, Haskell,
and curiously,  indie video games, by browsing manuals and looking
videos and this is an important source of inspiration for Grafoscopio.

Cheers,

Offray

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Edward K. Ream]

On Tue, Oct 24, 2017 at 8:25 AM, Terry Brown  wrote:

> I've added a pandoc renderer to leo_edit_pane,


​Excellent.  As I understand it, pandoc allows us to be more agnostic about
the markup and outputs.

Some work will be required to fully integrate pandoc into Leo. For example,
perhaps it is time to consider support for markdown and pandoc into the
(horribly complex) rst3 command.  For example, I would like rst to create a
TOC automatically for markdown input.

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Terry Brown]

I've added a pandoc renderer to leo_edit_pane, but just at the moment
it's not rendering math, although it's math aware,

$ a + b = \frac{1}{2} $

renders as

a + b =

as opposed to the markdown.py renderer, which just renders it as is.

Will try and sort it out.

Cheers -Terry

On Tue, 24 Oct 2017 03:50:12 -0500
"Edward K. Ream"  wrote:

> On Mon, Oct 23, 2017 at 6:59 PM, Offray Vladimir Luna Cárdenas <
> off...@riseup.net> wrote:
> 
> > I second Terry's idea of going with Markdown, particularly Pandoc's
> > variant, which is pretty mature and with an active community
> > discussing a lot of details to support a complete writing &
> > publishing workflow, the ubiquity advantage with a lot of variants
> > everywhere (Ghost, Stack Overflow, GitHub, Fossil).
> 
> 
> ​Some of Leo's recent documentation files use @language md.  See this
> FAQ entry
> .
> As mentioned in this FAQ, I use @button make-md-heads to generate a
> TOC. Perhaps this process could be automated.
> 
> Recently, at our local hackerspace [1] we
> > opened the Data Journalism Handbook [2][2a] as a Grafoscopio
> > document and produced a PDF (13 Mb) [3] from a Pandoc's Markdown
> > file (500Kb) [4] generated from a single Grafoscopio
> > notebook/outline (600 Kb). This workflow was pretty well supported
> > by Pandoc's Markdown.
> >
> 
> ​It's difficult to follow the links because I don't understand
> Spanish.​
> 
> >
> > I proposed some Qt Web technology to show markdown (including math)
> > inside Leo nodes. Maybe the IPython Qt Console, which supports this
> > rendering could be inspiring here[6], but I don't know about the
> > math rendering support in that case..
> >
> 
> ​Exactly.  I have been thinking of "borrowing" the IPython Qt Console
> approach.  Iirc, there are many complex details behind the scenes
> involved in piping the results to the console. Such details may be
> simpler within Leo, or not.
> 
> In any event, the general goal is to make *all* rendering as simple as
> possible in Leo. This is why I am proposing that we read the users
> manuals for other systems, looking for *goals*. Only after we have a
> clear idea of what we want does it make sense to look into how to do
> it.  This was an Aha that came to me on vacation.
> 
> Edward
> 

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Edward K. Ream]

On Mon, Oct 23, 2017 at 6:59 PM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:

> I second Terry's idea of going with Markdown, particularly Pandoc's
> variant, which is pretty mature and with an active community discussing
> a lot of details to support a complete writing & publishing workflow,
> the ubiquity advantage with a lot of variants everywhere (Ghost, Stack
> Overflow, GitHub, Fossil).


​Some of Leo's recent documentation files use @language md.  See this FAQ
entry
. As
mentioned in this FAQ, I use @button make-md-heads to generate a TOC.
Perhaps this process could be automated.

Recently, at our local hackerspace [1] we
> opened the Data Journalism Handbook [2][2a] as a Grafoscopio document
> and produced a PDF (13 Mb) [3] from a Pandoc's Markdown file (500Kb) [4]
> generated from a single Grafoscopio notebook/outline (600 Kb). This
> workflow was pretty well supported by Pandoc's Markdown.
>

​It's difficult to follow the links because I don't understand Spanish.​

>
> I proposed some Qt Web technology to show markdown (including math)
> inside Leo nodes. Maybe the IPython Qt Console, which supports this
> rendering could be inspiring here[6], but I don't know about the math
> rendering support in that case..
>

​Exactly.  I have been thinking of "borrowing" the IPython Qt Console
approach.  Iirc, there are many complex details behind the scenes involved
in piping the results to the console. Such details may be simpler within
Leo, or not.

In any event, the general goal is to make *all* rendering as simple as
possible in Leo. This is why I am proposing that we read the users manuals
for other systems, looking for *goals*. Only after we have a clear idea of
what we want does it make sense to look into how to do it.  This was an Aha
that came to me on vacation.

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Offray Vladimir Luna Cárdenas]

I second Terry's idea of going with Markdown, particularly Pandoc's
variant, which is pretty mature and with an active community discussing
a lot of details to support a complete writing & publishing workflow,
the ubiquity advantage with a lot of variants everywhere (Ghost, Stack
Overflow, GitHub, Fossil). Recently, at our local hackerspace [1] we
opened the Data Journalism Handbook [2][2a] as a Grafoscopio document
and produced a PDF (13 Mb) [3] from a Pandoc's Markdown file (500Kb) [4]
generated from a single Grafoscopio notebook/outline (600 Kb). This
workflow was pretty well supported by Pandoc's Markdown.

I proposed some Qt Web technology to show markdown (including math)
inside Leo nodes. Maybe the IPython Qt Console, which supports this
rendering could be inspiring here[6], but I don't know about the math
rendering support in that case..

=== Extra Links:
[1] http://hackbo.co/
[2] http://datajournalismhandbook.org/
[2a] http://mutabit.com/repos.fossil/mapeda/
[3] http://mutabit.com/repos.fossil/mapeda/uv/mapeda.pdf
[4] http://mutabit.com/repos.fossil/mapeda/doc/tip/mapeda.markdown
[5] http://mutabit.com/repos.fossil/mapeda/doc/tip/mapeda.ston
[6] https://ipython.org/ipython-doc/3/interactive/qtconsole.html

Cheers,

Offray


On 20/10/17 10:24, Terry Brown wrote:
> On Fri, 20 Oct 2017 07:05:44 -0700 (PDT)
> "Edward K. Ream"  wrote:
>
>> Leo can already render LaTex math markup using reStructuredText 
> Although I quite like reStructuredText my impression is that it has all
> but lost the competition for market share to markdown.  GitHub,
> obviously, favors markdown.  I suspect Jupyter does too.  R-markdown is
> the literate analysis markup of choice for R focused work.  Pandoc
> (backend for at least R-markdown if not others) seems to have more
> markdown extensions for handling citations, math, tables of content,
> etc. than it does reStructuredText extensions.  Maybe Sphinx still
> favors reStructuredText?
>
> The leo_edit_pane view widget currently uses markdown.py to convert
> markdown to HTML for viewing in a QWebkit / QTheOtherHTMLWidget pane.
> Not sure but markdown.py may not handle math.  But an obvious
> alternative is to use pandoc for markdown -> html, which definitely
> supports math.
>
> Cheers -Terry
>
>> .
>>  
>> But not very well.
>>
>> Enter the following in any body pane, and look at the results in the 
>> viewrendered pane. Blank lines are significant in some places:
>>
>> @language rst
>>
>> \int_{b^a} \, x^2 \, dx: :math:`\int_{b^a} \, x^2 \, dx`
>>
>> d/dx \int_{0^x}\,f(u)\,du=f(x): :math:`d/dx \int_{0^x}\,f(u)\,du=f(x)`
>>
>> \int_{0^x}: :math:`\int_{0^x}`
>>
>> block:
>>
>> .. math::
>>
>> x + 5 = -3
>>
>> \int_{b^a} \, x^2 \, dx
>>
>> d / dx \, \left(\int_{0^x} f(u)\,du\right)=f(x)
>>
>> d / dx (\int_{0^x} f(u)\,du ) = f(x)
>>
>> y_k(\mathbf{x},\mathbf{w}) = p(C_1|\mathbf{x})
>> 
>> Alignment with  in \\begin{equation}:
>>
>> .. math::
>>
>> \begin{equation}
>> x + 5 = -3 \\
>> \int_{b^a} \, x^2 \, dx\\
>> d / dx \left(\int_{0^x} f(u)\,du\right)=f(x)\\
>> d / dx (\int_{0^x} f(u)\,du) = f(x)\\
>> y_k(\mathbf{x},\mathbf{w}) = p(C_1|\mathbf{x})
>> \end{equation}
>> 
>> Inline: :math:`y_k(\mathbf{x},\mathbf{w}) = p(C_1|\mathbf{x})`
>>
>> Inline: :math:`(\sum_{t=0}^{N}\,f(t,k))/N`
>> 
>> The final output will be a vector :math:`Y` with :math:`K` elements, 
>> :math:`y_k`, where
>> :math:`y_k(\mathbf{x},\mathbf{w}) = p(C_1|\mathbf{x})` is the
>> probability that node
>> :math:`k` is in class :math:`C_1` and
>> :math:`p(C_2|\mathbf{x}) = 1-p(C_1|\mathbf{x})`
>>
>> This is kinda cool, but it has serious problems. The first two are
>> visual:
>>
>> - The rendering is poor for integrals, \int, and sums, \sum.
>>
>> - There is no easy control over font size.  It may be possible using
>> css for rST.
>>
>> Worse, there are at least two serious markup incompatibilities:
>>
>> - \frac does not render as in Jupyter or the mathjax viewer 
>> .
>>
>> - The :math:`` syntax is clumsy.  In contrast, Jupyter
>> notebooks use $$.
>>
>> *Summary*
>>
>> These kinds of incompatibilities will substantially limit the appeal
>> of rST :math: markup.
>>
>> More generally, Leo is faced with a never-ending task of playing as
>> well as possible with existing apps, tools and languages. This task
>> requires continuous invention, so it could be called a source of
>> pleasure ;-)
>>
>> Edward 
>>


-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit 

Re: Rendering math in Leo

[Edward K. Ream]

On Friday, October 20, 2017 at 9:05:44 AM UTC-5, Edward K. Ream wrote:

> Leo can already render LaTex math markup using reStructuredText 
.
 
But not very well.

The viewrendered plugin can also render @pyplot nodes, provided you have 
matplotlib installed. Not sure how many people know this ;-)

Rev 897a802 adds some examples of @pyplot nodes to test.leo.  For example, 
here is top-level of the node:
@pyplot matplotlib animate_decay.
Note the @others:

# http://matplotlib.org/1.5.1/examples/animation/animate_decay.html
import numpy as np
import matplotlib.pyplot as plt
import matplotlib.animation as animation

@others

# global data.
fig, ax = plt.subplots()
line, = ax.plot([], [], lw=2)
ax.grid()
xdata, ydata = [], []
ani = animation.FuncAnimation(
fig, run, data_gen, blit=False, interval=10,
repeat=False, init_func=init)

plt.ion()
# sets interactive mode. Prevents this message:
# QCoreApplication::exec: The event loop is already running
plt.show()

Imo, a comprehensive review of Leo's existing capabilities is in order, not 
just for tips when Leo opens. I have the feeling that some important 
generalizations and simplifications are possible...

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Rendering math in Leo

[Edward K. Ream]

On Fri, Oct 20, 2017 at 10:24 AM, Terry Brown  wrote:

> On Fri, 20 Oct 2017 07:05:44 -0700 (PDT)
> "Edward K. Ream"  wrote:
>
> > Leo can already render LaTex math markup using reStructuredText
>
> Although I quite like reStructuredText my impression is that it has all
> but lost the competition for market share to markdown.  GitHub,
> obviously, favors markdown.  I suspect Jupyter does too.
> ​
> R-markdown is
> the literate analysis markup of choice for R focused work.  Pandoc
> (backend for at least R-markdown if not others) seems to have more
> markdown extensions for handling citations, math, tables of content,
> etc. than it does reStructuredText extensions.  Maybe Sphinx still
> favors reStructuredText?
>
> The leo_edit_pane view widget currently uses markdown.py to convert
> markdown to HTML for viewing in a QWebkit / QTheOtherHTMLWidget pane.
> Not sure but markdown.py may not handle math.  But an obvious
> alternative is to use pandoc for markdown -> html, which definitely
> supports math.
>

​Thanks for this.  It looks like pandoc, and par​particularly pandoc's
flavor of markdown ,
should do nicely. It requires the tex_math_dollars extension, but
presumably that's not a big deal.

It does look like we need support for pandoc in the rst3 plugin...

Edward

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.