Preserve non-breaking hyphens in Word resume imports - #141
Merged
ralyodio merged 1 commit intoSep 21, 2026
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
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.
A Word resume that stores a non-breaking hyphen as
<w:noBreakHyphen/>currently importscustomer-facingascustomerfacingandend-to-endasendtoend. The importer reads text, tabs and breaks inside runs, but drops this visible character.This change maps the Word element to Unicode U+2011, preserves it across run boundaries, and retains emphasis when the hyphen is the only character in its run. Literal hyphens, tabs and line breaks keep their existing behavior. A small DOCX fixture and its readable XML source cover the cases.
Validation on upstream
282feb11e9cc401f17cba450e6783de2b36dd048: three new regressions fail before the fix while the control passes. Afterward, the TypeScript build and all six related DOCX import/emphasis tests pass.The element's visible-hyphen semantics are documented by Microsoft's Open XML reference.
Submitted under the advertised valid bug-fix PR reward. Please review it for eligibility; no reward or acceptance is presumed. Existing reward application and payment details remain in the established conversation, using native SOL on Solana mainnet, with the net amount to be confirmed before payment.