Add ability to report start of paragraphs in braille#16906
Conversation
See test results for failed build of commit 062c99a010 |
|
@coderabbitai review |
WalkthroughThe recent changes introduce a feature in NVDA that allows users to indicate the start of paragraphs in braille when the "reading by paragraph" option is enabled. This functionality enhances accessibility by providing clearer context, making it easier for users who rely on braille output to understand textual structures. Changes
Assessment against linked issues
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 (
|
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
user_docs/en/userGuide.md (1)
2166-2169: Ensure clarity and consistency.The new section introducing the option to show paragraph starts in Braille settings is clear and concise. However, consider rephrasing for better readability and consistency with the rest of the document.
- If enabled and read by paragraph is checked, two spaces will be displayed to indicate paragraph start. + If enabled and "Read by paragraph" is checked, two spaces will be displayed to indicate the start of a paragraph.
|
|
||
| ##### Show paragraphs start {#BrailleSettingsShowParagraphStart} | ||
|
|
||
| - If enabled and "Read by paragraph" is checked, two spaces will be displayed to indicate the start of a paragraph. |
There was a problem hiding this comment.
- remove leading dash
- Link the "Read by paragraph" option
| - If enabled and "Read by paragraph" is checked, two spaces will be displayed to indicate the start of a paragraph. | |
| If enabled and "[Read by paragraph](#BrailleSettingsReadByParagraph)" is checked, two spaces will be displayed to indicate the start of a paragraph. |
Moreover, it would be worth rephrasing this paragraph with a bit more details. But I am not familiar with "Read by paragraph" option and will not be able to test on a braille display before next week, so I won't be able to make a detailed suggestion.
Maybe something like the following (to be adapted and polished):
When "Read by paragraph" option is enabled, we face [issueToBeDescribed, e.g. difficulty to identify paragraph start].
Enabling this option enable to mitigate this issue adding two spaces at the beginning of paragraphs.
Co-authored-by: Cyrille Bougot <cyrille.bougot2@laposte.net>
|
@CyrilleB79 , thanks for your review. I think I've addressed all your suggestions. Let me know if I should apply any other changes. |
Co-authored-by: Luke Davis <8139760+XLTechie@users.noreply.github.com>
|
@XLTechie , thanks for your review. I've applied your suggestions. Let me know if I should fix other things. |
|
These days I'm testing this in my daily reading. I've observed that, once, when scrolling down the braille display, two spaces haven't been shown at the start of the paragrahp and I needed to scroll up and down. This may be related to a separate issue, since sometimes the first character is not shown and scrolling up and down is needed. I thought that trying to set two spaces as the paragraph start indicator may fix this issue, but it doesn't work. |
See test results for failed build of commit 754c785426 |
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
See test results for failed build of commit 535ff1f155 |
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
|
@seanbudd , many thanks for explaining the reason to make the option about paragraph markers an integer. I didn't realise that s.making pilcrows translatable makes this necessary. |
See test results for failed build of commit bcbbfd3fe1 |
See test results for failed build of commit 9c870b2bc4 |
See test results for failed build of commit ee5eb7a416 |
|
@seanbudd , seems that we can not assign a value to PILCROW in the enum class using pgettext or _(). So I've created a new function in braille.py to get the text corresponding to the paragraphStartMarker, and from this functon this can be made translatable. |
| # Translators: This is a paragraph start marker used in braille. | ||
| # The default symbol is the pilcrow, | ||
| # a symbol also known as "paragraph symbol" or "paragraph marker". | ||
| # This symbol should translate in braille via LibLouis automatically. | ||
| # If there is a more appropriate character for your locale, | ||
| # consider overwriting this (e.g. for Ge'ez ፨). | ||
| # You can also use Unicode Braille such as ⠘⠏. | ||
| # Ensure this is consistent with other strings with the context "paragraphMarker". |
There was a problem hiding this comment.
this comment should be deleted now that it has been moved to getParagraphStartMarker
| optionsEnum="ReviewRoutingMovesSystemCaretFlag", behaviorOfDefault="NEVER") | ||
| readByParagraph = boolean(default=false) | ||
| paragraphStartMarker = option("", " ", "¶", default="") | ||
| paragraphStartMarker = integer(min=0, max=2, default=0) |
There was a problem hiding this comment.
this change is no longer necessary if the pilcrow is not translatable
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
|
pre-commit.ci run |
|
@seanbudd , I've addressed your comments. Please let me know if anything else needs to be done. |
Link to issue number:
Closes #16895
Summary of the issue:
NVDA should have an option to indicate paragraphs in braille, so that reading, especially books or long pieces of text, can be more comfortable and meaningful.
Description of user facing changes
Description of development approach
Testing strategy:
Tested manually:
Known issues with pull request:
None
Code Review Checklist:
Summary by CodeRabbit
Summary by CodeRabbit
New Features
Documentation
Bug Fixes