handle ASCII characters in abstract #6156
Open
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
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.
Closes #6153 .
What this PR does:
Unescapes ASCII characters like $#13; (which is carriage return).
The mods display gem has additional handling around dealing with HTML encoding, and the unescape method is called before the text is passed on to the Mods Display component(see https://github.com/sul-dlss/mods_display/blob/main/app/helpers/mods_display/record_helper.rb#L103 ).
Note: These changes affect only abstract. Question: Do we want to address other content as well on the page or is this change sufficient?