You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried successfully to convert a tex-file with sagemath included.
Unfortunately i had to change the ending from tex to txt. The Testfile is attached below.
I am new to tex4ebook, so i do not know, what is going on behind, but i experience the following glitches.
Comiling with tex4ebook test.tex produces errors
tex4ebook -x test.tex in the first step works
Afterwords sage has to be envoked. That works
tex4ebook -x test.tex produces an error in the second step
tex4ebook test.tex afterwords works. When the process produced all necessary pictures the -x option works as well without any error.
Hopefully someone can reproduce the problem and show some inside why this happens and how to avoid it?
See the original testfile and the shortend error-log
In the first steps i ended up with a cut epub-file.
Now i can not reproduce the error myself again. Now it works in all steps without the -x flawlessly.
Are there some caches? Or what could be the reason?
The errors had been warnings about the domfilter and cut of the epub file i half, leaving the whole file unusable.
[WARNING] domfilter: DOM parsing of testch5.xhtml failed:
[WARNING] domfilter: ...ive/2022/texmf-dist/tex/luatex/luaxml/luaxml-mod-xml.lua:175: Unbalanced Tag (/mtext) [char=12730]
You certainly don't need the -x option, this is necessary only if you use commands that require XeTeX. I think your document should work even with the default PDFTeX driver, or with the -l option. Anyway, I've found that the issue with MathML is caused by the \TeX command used in math text. The following configuration file should fix that:
I tried successfully to convert a tex-file with sagemath included.
Unfortunately i had to change the ending from tex to txt. The Testfile is attached below.
I am new to tex4ebook, so i do not know, what is going on behind, but i experience the following glitches.
Hopefully someone can reproduce the problem and show some inside why this happens and how to avoid it?
See the original testfile and the shortend error-log
test.txt
ErrorLog.txt
The text was updated successfully, but these errors were encountered: