You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current latex/pdflatex functionality of jupyter-book enables building pdf files via LaTeX compilation for books. However some authors would like to have more control over the LaTeX process and it would be helpful to have a more readable intermediate tex file.
Value / benefit
Enables author's more control over the compilation phase when building latex -> pdf
Implementation details
We currently make use of sphinx-jupyterbook-latex to alter the sphinx abstract syntax tree using transforms and post-transforms to enable building via the default sphinx LaTeX writer. This is coordinated with other packages like sphinx-multitoc-numbering to enable support for part/chapter structures provided by jupyter-book
This is a good strategy as we get improvements from sphinx development, in addition to not having to maintain our own LaTeX builder/writer in sphinx. It would nice to retain this approach (if possible).
I think for the majority of use cases - focusing on myst:md to pdf is the best approach (to build a tool that doesn't require any interaction with tex) but it would be nice to enable a --readable option to the latex builder
jb build <project> --builder=latex --readable
Tasks to complete
enable turning pygments syntax highlighting off and use minted with direct placement of code in LaTeX (tex) file
simply the use of \sphinx macros
The text was updated successfully, but these errors were encountered:
Description / Summary
The current
latex
/pdflatex
functionality ofjupyter-book
enables buildingpdf
files via LaTeX compilation for books. However some authors would like to have more control over the LaTeX process and it would be helpful to have a more readable intermediatetex
file.Value / benefit
Enables author's more control over the
compilation
phase when buildinglatex
->pdf
Implementation details
We currently make use of sphinx-jupyterbook-latex to alter the
sphinx
abstract syntax tree usingtransforms
andpost-transforms
to enable building via the default sphinx LaTeX writer. This is coordinated with other packages like sphinx-multitoc-numbering to enable support forpart
/chapter
structures provided byjupyter-book
This is a good strategy as we get improvements from
sphinx
development, in addition to not having to maintain our own LaTeX builder/writer insphinx
. It would nice to retain this approach (if possible).I think for the majority of use cases - focusing on
myst:md
topdf
is the best approach (to build a tool that doesn't require any interaction withtex
) but it would be nice to enable a--readable
option to thelatex
builderTasks to complete
pygments
syntax highlighting off and useminted
with direct placement of code in LaTeX (tex) file\sphinx
macrosThe text was updated successfully, but these errors were encountered: