Hi,
I am replying to myself, as the situation as evolved:
The first file sent to elyxer was probably a little too complex. I
killed
python after 40 minutes running full on one CPU.
This is the one I'm mostly interested on.
I found that the problem is not due to that file in particular but that
any equation in "display" mode result in that CPU hogging. The very same
equations pass well is "inline" mode.
You can find attached a very basic test file for it. I do not now if
it's due to something on my machine (antivirus, configuration) or to my
LyX defaults (e.g. defaulting to using KOMA-script classes, own margins...)
FIXED bx 0.25
[...]
3-
There is one place in my file where I used the "\unittwo" tip given
in LyX
docs (Appendix A "Typographic Advice" of Math docs).
The \unit tag is not supported yet. If you send me a sample doc I will
try to make it work.
In the attached file, the second equation uses it.
FIXED by 0.25
Congratulations for fixing that so fast. So I could test the speed of
elyxer, and it is +/- instantaneous for a document of 11 pages with
figures and 58 equations (not counting the inline ones).
Having written html pages many years ago at the university, I am totally
amazed by the quality of the equations. No MathML, and still, no images.
Multiline equations, "case" equations, fractions with fractions in
numerator & denominator, integrals.... everything looks fine.
Now, let's challenge you for 0.26 ;-)
I have a few unconverted stuff:
- \tan and \arctan
- \overrightarrow (quite useful for some things like gradient)
- \ldots (that the ellipsis, AKA the three dots ...)
- \max (and probably \min)
And for a distant future version
- \gtrsim (and its friends, AMS math symbols).
I tested the result on both Firefox and IE8, and both work fine.
Congratulations for this nice work.
Best regards,
Olivier
