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

Heading/cells positioning problem and cell output wrapping #4945

Closed
jdfreder opened this issue Jan 29, 2014 · 1 comment
Closed

Heading/cells positioning problem and cell output wrapping #4945

jdfreder opened this issue Jan 29, 2014 · 1 comment
Assignees
Milestone

Comments

@jdfreder
Copy link
Member

Migrated from https://github.com/ipython/nbconvert/issues/93
Original author @montefra


When converting a notebook to latex I've noticed two issues comparing the notebook with the pdf created by latex. The dvi opened with okular has the same layout but the cells show a black background instead of the light gray of the pdf. I'm on Kubuntu 12.10, ipython 0.13.1, nbconvert from today's master. I see the same using latex and pdflatex.

The problems:

  1. Heading 4 are converted to paragraphs and are all out of place with respect to the cells where they should be. It seems that markdown cells are where they have to be.
  2. the output of the cells is within verbatim, thus long lines go out of the boundaries. This tex.stackexchange suggests spverbatim or listings as possible substitutes. If any of the two comes with (most) of latex distribution might be worth thinking about using it

ps: I hope that it is possible to get the dvi.

@jdfreder jdfreder self-assigned this Mar 3, 2014
@jdfreder
Copy link
Member Author

Hi @montefra, the latex templates and nbconvert have been completely re-worked since the merge into IPython master. I just tested running latex on the output of ipython nbconvert notebook.ipynb --to latex and I was able to get a working .dvi file that renders almost the same as the pdf output from pdflatex. If you can verify that you still have a problem, please tell me and I will re-open the issue.

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

No branches or pull requests

1 participant