Viewrendered can render *@latex* nodes in a restricted way. I was reminded
of this by an issue of @LewisNeal <https://github.com/LewisNeal>. VR3 does
not at present but it would be easy to duplicate VR's capability. I have
two questions about it before I move to enable it in VR3. One is minor,
the other more existential. The minor one first:
The code claims that in Windows/python the rendering is not available. But
all the rendering code does is to insert the node's text into a basic html
string that includes an import for the MathJax script. That does not
depend on Windows or the python version in any way. So why is this
restriction there? It makes me think that @latex nodes used to be able to
do more at some time in the past.
The more existential question is: what is this capability for, anyway?
What is the use case? It must mostly be for rendering math, but math almost
always requires some text along with it. Mathjax can render plain text
using the *\\text{}* macro, but this is awkward and limited.
VR3 can already render math in ReStructured and Markdown text pages, and
can mix text and math more easily. I think that full latex rendering -
beyond what Mathjax can do - is not going to be in the cards for VR/VR3.
You would have to use a full-fledged latex processor, and they are very
slow and finicky about the content. TexWorks, for example, sometimes
requires manual input to deal with hiccups.
So before I enable *@latex *nodes in VR3, I'd appreciate some guidance
about how people want to use it.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/7742fb8b-c266-456d-ad0e-d526fb89677bn%40googlegroups.com.
