-
Notifications
You must be signed in to change notification settings - Fork 106
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
Exporting to LaTeX #18
Comments
To my understanding html is currently the only output, but other formats are discussed (eg pdf via Webkit). Also once there is a html, one can try create a latex with pandoc. If you can point out a good rendering engine / library for latex, that would be very helpful. |
Exactly. If you give pandoc a try, please let us know how it goes. If HTML is well supported, we might be fine with having Handout always export HTML. In that case, we can provide a few examples on how to combine it with pandoc to export into various formats. Please open a separate issue about conda :) |
Thanks folks @danijar & @epogrebnyak for the responses, maybe if we exported directly to ipynb and then let the users convert that to other formats since ipynb allows for easy conversion to other formats such as html, pdf, latex, etc. (just an idea)
I usually use this to export an ipynb to latex, hope that helps. Also another idea would be to combine forces with this in order to allow for easy export between .py and .ipynb. |
@kirk86 - thanks for giving the clues on the latex workflow. As I understand, the current stand for Handout is one-directional transformation of .py to html, followed by options to convert to other formats. These options seems to be (for issue #9):
In the space of
Any pointers on how people convert from .ipynb to pdf/latex? |
@epogrebnyak thanks for pointing to jupytext.
Alternatively, from inside jupyter menu Download as, then you'll find all the available options. But in my experience it dumps everything (i.e. images, .tex files, etc.) in the same folder that .ipynb is located, while the package I used it keeps things nice tightly in separate folders, for instance images go to their own folder imgs, .tex files to their own tex folder, etc. |
@kirk86 - thanks for pointing out the
|
That's my understanding of it. |
I think it'd be easy to write a LaTeX exporter -- we don't even need a templating library to make a first attempt at this. We should only output LaTeX source in this case. The user can either manually call their LaTeX compiler afterwards or call it from within their script after the We just need to support multiple exporters which is tracked in #9. |
Hi and thanks for this package, I just had a couple of questions if you don't mind me asking since I couldn't find any answers in the readme.
Thanks!
The text was updated successfully, but these errors were encountered: