Open GoogleCodeExporter opened 9 years ago
This isn't an issue that's specific to epub. Pandoc's latex parser is only
partial (as the documentation says), and one of the constructs that is not
handled is \include.
Perhaps \include will be supported in a later version, but it would require
architectural changes, because the latex parser is "pure" -- it doesn't do IO.
In the mean time, you can workaround by preprocessing your latex file with a
short script that replaces \include statements with the contents of the files.
Original comment by fiddloso...@gmail.com
on 18 Mar 2011 at 5:29
It would be less surprising if pandoc would bail out with an error, instead of
completing successfully. The latter looks like indicating to the user that it
has done a conversion, where in fact it hasn't done anything even close to that.
Original comment by imaginea...@gmail.com
on 21 Mar 2011 at 9:19
It would be excellent if there were a simple options to turn off the symbol
escaping. Particularly in latex, and allow any \latex code remain proper
\latex. Leaving any escaping that must be done to the author.
Original comment by amr...@gmail.com
on 18 Dec 2012 at 11:24
Original issue reported on code.google.com by
imaginea...@gmail.com
on 18 Mar 2011 at 10:12