Cases #2495
Merged
Cases #2495
Conversation
This file contains 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
… attribute is allowed; likewise careful in setNodeBox,setNodeFont
…ase, more closely mimicing modern latex
…ncluded in base LaTeX
dginev
approved these changes
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR makes
\MakeUppercase,\MakeLowercasemore consistent with current LaTeX implementation, particularly as to using Unicode mappings rather than\uccode,\lccode. The mechanisms used for defining mappings and exclusion rely on control sequences being robust (beingprotectedand redirecting through a cs with space appended), so a number of commands have been updated.In the process a couple of other patches: Definition's alias is now consistently a
Token, rather than string; reduced unnecessary debugging noise, warnings, etc.