Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ePub version contains verbose metadata from LaTeX conversion #5

Open
machawk1 opened this issue May 11, 2018 · 4 comments
Open

ePub version contains verbose metadata from LaTeX conversion #5

machawk1 opened this issue May 11, 2018 · 4 comments

Comments

@machawk1
Copy link
Contributor

Following the procedure in the README and the sample epub in the repo, there exists extraneous remnants of the conversion process in various parts of the document, namely at the beginning.

screen shot 2018-05-10 at 10 32 42 pm

@machawk1
Copy link
Contributor Author

A few of the issues that are causing this have to do with latexml having an issue using the polyglossia package, which affects other dependent commands (like \setotherlanguage). I (re)installed the package using tlmgr install polyglossia but the issue remains.

This makes me also question whether other LaTeX packages that I have installed that are successfully being imported would cause issues with the ePub conversion process. I am not familiar enough with LaTeX's package management system to resolve this without some research but a solution (albeit heavy but more compatible) lies in Dockerizing the compilation process or to realize something akin to Python's virtualenv.

@deobald
Copy link
Owner

deobald commented May 25, 2018

@machawk1 I'm also open to figuring out a different way to render the Sanskrit... or giving up on it entirely. Since it only comprises one word of the entire essay, it was a lot of effort to get it to render as text which, frankly, just might not be worth it in the long run.

@machawk1
Copy link
Contributor Author

I am working on finding a solution to this. The core issue is the lack of bindings for polyglossia in latexml. Here is a more fundamental (mwe.tex) example to replicate the error:

\documentclass{article}

\usepackage{polyglossia}
\setmainlanguage{english}
\setotherlanguage{sanskrit}

\newfontfamily\devanagarifont[Scale=MatchUppercase]{Kohinoor Devanagari}

\begin{document}

\foreignlanguage{sanskrit}{संस्कार} (sanskaar)

\end{document}

...then the error:

$ latexml --dest=mwe.xml mwe.tex
latexml (LaTeXML version 0.8.2)
processing started Sat May 26 11:36:55 2018

(Digesting TeX mwe...
(Loading /usr/local/Cellar/latexml/0.8.2/libexec/lib/perl5/LaTeXML/Package/TeX.pool.ltxml...
(Loading /usr/local/Cellar/latexml/0.8.2/libexec/lib/perl5/LaTeXML/Package/eTeX.pool.ltxml... 0.01 sec)
(Loading /usr/local/Cellar/latexml/0.8.2/libexec/lib/perl5/LaTeXML/Package/pdfTeX.pool.ltxml... 0.01 sec) 0.18 sec)
(Processing content /tmp/vipassana-for-hackers/mwe.tex...
(Loading /usr/local/Cellar/latexml/0.8.2/libexec/lib/perl5/LaTeXML/Package/LaTeX.pool.ltxml... 0.22 sec)
(Loading /usr/local/Cellar/latexml/0.8.2/libexec/lib/perl5/LaTeXML/Package/article.cls.ltxml... 0.03 sec)
Warning:missing_file:polyglossia Can't find binding for package polyglossia
	at /tmp/vipassana-for-hackers/mwe.tex; line 4 col 16
	Anticipate undefined macros or environments
	search paths are /tmp/vipassana-for-hackers
	In Core::Definition::Constructor[\usepac... from LaTeX.pool.ltxml line 581

Error:undefined:\setmainlanguage The token T_CS[\setmainlanguage] is not defined.
	at /tmp/vipassana-for-hackers/mwe.tex; line 4 col 16
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7fc22e1fd290] at /tmp/vipassana-for-hackers/mwe.tex; line 4 col 16

Error:undefined:\setotherlanguage The token T_CS[\setotherlanguage] is not defined.
	at /tmp/vipassana-for-hackers/mwe.tex; line 5 col 17
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7fc22e1fd290] at /tmp/vipassana-for-hackers/mwe.tex; line 5 col 17

Error:undefined:\newfontfamily The token T_CS[\newfontfamily] is not defined.
	at /tmp/vipassana-for-hackers/mwe.tex; line 7 col 14
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7fc22e1fd290] at /tmp/vipassana-for-hackers/mwe.tex; line 7 col 14

Error:undefined:\devanagarifont The token T_CS[\devanagarifont] is not defined.
	at /tmp/vipassana-for-hackers/mwe.tex; line 7 col 29
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7fc22e1fd290] at /tmp/vipassana-for-hackers/mwe.tex; line 7 col 29

Error:undefined:\foreignlanguage The token T_CS[\foreignlanguage] is not defined.
	at /tmp/vipassana-for-hackers/mwe.tex; line 11 col 16
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7fc22e1fd290] at /tmp/vipassana-for-hackers/mwe.tex; line 11 col 16
	 <= Core::Definition::Constructor[\begin{... <= Core::Stomach[@0x7fc22e1fd290] <= ...
 1.39 sec) 1.58 sec)
(Building...
(Loading compiled schema /usr/local/Cellar/latexml/0.8.2/libexec/lib/perl5/LaTeXML/resources/RelaxNG/LaTeXML.model... 0.02 sec). 0.06 sec)
(Rewriting... 0.00 sec)
(Finalizing... 0.00 sec)
Conversion complete: 1 warning; 5 errors; 5 undefined macros[\newfontfamily, \devanagarifont, \setotherlanguage, \setmainlanguage, \foreignlanguage]; 1 missing file[polyglossia.sty].
processing finished Sat May 26 11:36:57 2018

I will continue to try to resolve the issue using the latter mwe. If that is not possible, I will look for another solution to render the Sanskrit as you suggested, @deobald.

@deobald
Copy link
Owner

deobald commented May 28, 2018

Cool! Good luck, @machawk1. Here's hoping if you can sort out bindings for polyglossia they'd be useful for other folks as well. Are you speaking to anyone from the latexml / polyglossia / indic fonts communities? I wouldn't mind following the conversation there, if you are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants