Update base.tex.j2 for macro compatibility with newer versions of Pandoc

[PetalAdrift]

Added the macro \pandocbounded that is used by newer versions of pandoc.

[PetalAdrift]

Sorry about closing the previous PR on accident. Opened a new one.

[krassowski]

@PetalAdrift thank you! How can we test this PR? Is there a test that you could add to ensure this is tested on CI?

[PetalAdrift]

@krassowski Sorry, I am not too familiar with the terminology (or Git, actually). Is there a link to relevant documentation on tests used for nbconvert?

[krassowski]

It may not be much but:

• https://github.com/jupyter/nbconvert/blob/main/CONTRIBUTING.md#testing
• https://github.com/jupyter/nbconvert/tree/main/tests

[gabemorris12]

When is this going to be implemented? It's been months, and nbconvert for latex still only works with pandoc 3.2 or older.

[PetalAdrift]

For now you can just make the change to your files locally.

[gabemorris12]

For now you can just make the change to your files locally.

That is fine for me, but I have about a hundred students each semester that have to setup jupyter to successfully convert a notebook to a pdf via latex. I'd hate to redo my setup process only for the solution to finally have been implemented later.

[PetalAdrift]

I guess one solution is to just just pandoc. It doesn't look as nice (subjective opinion), but it gets the job done.

[ChristofKaufmann]

@PetalAdrift Maybe I can help a bit to write a simple test. I have not tried it, but you would have to add in tests/exporters/test_latex.py a function like:

    @onlyif_cmds_exist("pandoc")
    def test_template_contains_pandocbounded(self):
        """
        Does the template contain the pandocbounded command for compatibility with pandoc >= 3.2.1?
        """
        (output, resources) = LatexExporter().from_filename(self._get_notebook())
        assert r"\newcommand*\pandocbounded" in output

Either follow the instructions to test it locally before committing or commit and let CI test it. In the CI test output, you should see about here a new test named test_template_contains_pandocbounded.

@krassowski Would that simple test be enough for you? It is actually just testing that the code, which this PR adds, is there. So it does not make much sense. Maybe it would be better to add e.g. \pandocbounded{check} in rawtest.ipynb and try to compile it with a new test in test_pdf.py . What is your opinion?