Repository navigation
fix: type precomposed NFC and drop leftover zero-width spaces - #12
Merged
Merged
Conversation
Vietnamese output to Chromium/Electron page fields and Safari was forced to combining-diacritic (NFD) form by the unicodeCombiningOutput workaround. It rendered correctly but broke website search: Blink stores the decomposed scalars while sites compare precomposed text. All Unicode-class typing output is now canonically composed (NFC) at the KeySynthesizer emission boundary, with deletion bookkeeping derived from the normalized form. Legacy TCVN3/VNI Windows/CP1258 output is exempt. The workaround and its forced override are removed, so the user's typing-encoding setting is honored in every app.
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
1 participant
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.
Vietnamese output to Chromium/Electron page fields and Safari was forced to combining-diacritic (NFD) form by the unicodeCombiningOutput workaround. It rendered correctly but broke website search: Blink stores the decomposed scalars while sites compare precomposed text.
All Unicode-class typing output is now canonically composed (NFC) at the KeySynthesizer emission boundary, with deletion bookkeeping derived from the normalized form. Legacy TCVN3/VNI Windows/CP1258 output is exempt. The workaround and its forced override are removed, so the user's typing-encoding setting is honored in every app.