DOC: to_latex braces in headers must be escaped (#60063) #60103
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GregersSR
force-pushed
the
doc/to_latex-braces
branch
from
935e427 to
d5687d0
Compare
|
Thanks @GregersSR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to_latex()does not handle braces in new headers gracefully #60063doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.Any braces used in the headers must be escaped with
{{or}}, and it is not trivial to figure out what goes wrong. I have added that the braces must be escaped, as agreed in the linked issue.