Add a braille setting for Chinese word segmentation - #20642
Conversation
|
HI cc @keyang556 |
|
OK, I'll test it. |
|
Fixed, thank you. |
|
Thanks @keyang556 |
|
I don't know, if possible, off by default in zhtw table(or nvda language), but on by default in zhcn table? |
|
Based on the discussion in #20471, I plan to narrow the scope of #20642 as follows:
I understand the suggestion to retain an override for zh-TW. However, I propose not to expose one because the issue reporter confirmed that Taiwanese users generally prefer no word separators and that an option is not needed for most users. This keeps #20471 focused on restoring the expected zh-TW behavior while retaining user control for Mainland Chinese braille. |
|
This version is great. |
| @@ -3676,8 +3688,7 @@ You may toggle through the available paragraph styles from anywhere by assigning | |||
| ##### Word Segmentation Standard {#WordSegmentationStandard} | |||
|
|
|||
| This setting controls how NVDA determines word boundaries when navigating by word. | |||
There was a problem hiding this comment.
I think adding this sentence might clarify this setting better for users who do not need/use it.
| This setting controls how NVDA determines word boundaries when navigating by word. | |
| This setting controls how NVDA determines word boundaries when navigating by word. | |
| This affects how script languages without spaces break up text into words, sentences and paragraphs |
Link to issue number:
Fixes #20471
Summary of the issue:
Chinese word segmentation is always used with Chinese braille output tables.
Some users need to disable this behavior and let the selected braille table translate the original text directly.
Description of user facing changes:
A "Use Chinese word segmentation" checkbox has been added to the Braille settings category.
It is enabled by default to preserve the existing behavior and only affects Chinese braille output tables.
Context-sensitive help and User Guide documentation are included.
Description of developer facing changes:
There are no public API changes.
Description of development approach:
The change follows the conventions of existing Braille settings and preserves the current behavior by default.
Testing strategy:
Manual testing should cover the following:
F1on the setting and confirm that the corresponding User Guide section opens.Known issues with pull request:
None known.
Code Review Checklist: