Add regression test for Unicode preservation in IA subject imports #11639
+0
−0
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
Author
|
I’ve opened a pull request related to this issue #11637. |
Contributor
|
You might want to double check that your branch contains all the commits that you intended, because it appears empty. |
github-actions
bot
added
the
Needs: Response
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.
This PR adds a regression test to assert that Unicode characters in subjects
are preserved during IA imports.
While investigating #11637, I traced Unicode handling through MARC parsing,
edition building, and import validation, and did not find any ASCII
normalization or character stripping on the Open Library side. Adding this
test helps make the issue reproducible and prevents future regressions
without guessing at a fix.
Related: #11637