Pandoc 1.8.1.1 fails do deal with LaTeX documents using \include when generating EPUB files

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a LaTeX document with one or more \include-d "sub-documents"
2. Run "pandoc -o /tmp/blah.epub input-doc.tex"
3. Look at the resulting EPUB file

What is the expected output? What do you see instead?
I was expecting to see the text of the included documents (one chapter per 
document), instead, I see a single page, listing the names of the individual 
files in { } pairs (like: {chapter1} {chapter2} {chapter3} ...)

What version of the product are you using? On what operating system?

Version 1.8.1.1, linux. Built via "cabal install pandoc" on March 17th, 2011.

Please provide any additional information below.

Original issue reported on code.google.com by imaginea...@gmail.com on 18 Mar 2011 at 10:12

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

I have created a simply python gist to get around this
https://gist.github.com/kmader/947c7ed134ccf95bc264

Original comment by kevinma...@gmail.com on 11 May 2015 at 9:06