Ensure that when character normalization results in a character with symbol definition, the symbol replacement is spoken#16950
Conversation
WalkthroughThe recent changes across multiple files primarily focus on code formatting and stylistic improvements. These updates include the standardization of string delimiters, whitespace adjustments, and enhancements to function signatures for better readability. While the core functionality and control flow remain unchanged, the overall aesthetics of the codebase have been significantly improved, enhancing maintainability and consistency. Changes
Sequence Diagram(s)%% No sequence diagrams generated as changes are primarily formatting and do not involve new features or control flow modifications.
Recent review detailsConfiguration used: .coderabbit.yml Files selected for processing (2)
Additional context usedPath-based instructions (2)
Additional comments not posted (4)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
|
@seanbudd it looks like @pre-commit-ci is pretty agressive here. I don't know how to tackle that really. |
… in a character with symbol definition, the symbol replacement is spoken
bee00b4 to
d433e16
Compare
978bda0 to
d433e16
Compare
See test results for failed build of commit eec004eec7 |
f962841 to
d433e16
Compare
|
I've had to suspend pre-commit. Hopefully this won't be a problem for long if we avoid PRs to beta. |
|
@coderabbitai resolve |
|
@coderabbitai full review |
Link to issue number:
Fixup for #16622
Summary of the issue:
When unicode normalization of a character (e.g.
·) resulted into a character that had a symbol definition (e.g.·, middle dot), the symbol definition wasn't applied to the normalization. This resulted in NVDA speaking nothing or only the wordnormalized.Description of user facing changes
NVDA will now properly speak the
·character (Greek Ano Teleia) asmiddle dotwhen normalizing. This also applies to other characters where normalization results in a character that's part of the symbol dictionary.Description of development approach
When normalizing a character, ensure it is thrown through
characterProcessing.processSpeechSymbol.Testing strategy:
Known issues with pull request:
None known
Code Review Checklist:
Summary by CodeRabbit
_getSpellingSpeechWithoutCharModefunction to validate the normalization feature under various conditions.