Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA Sends \n and \r Characters Incorrectly to the Synthesizer #17536

Closed
Jykke67 opened this issue Dec 16, 2024 · 0 comments
Closed

NVDA Sends \n and \r Characters Incorrectly to the Synthesizer #17536

Jykke67 opened this issue Dec 16, 2024 · 0 comments
Milestone

Comments

@Jykke67
Copy link

Jykke67 commented Dec 16, 2024

Steps to reproduce:

  1. Start NVDA with debug logging enabled.
  2. Type in text in any editor containing several linefeeds (\n or \r).
  3. Read the text by Say All from the very beginning and see from the log what is transfered to the synthesizer.

Actual behavior:

Tests made by @burmancomp and @irrah69 show that \n and \r characters are transfered as spaces to the synthesizer, not as control characters as expected.

Expected behavior:

The \n and \r characters should be transfered as they are to the synthesizer in order to be correctly handled by it like causing a pause during Say All.

NVDA logs, crash dumps and other attachments:

Not available.

System configuration

NVDA installed/portable/running from source:

NVDA installed.

NVDA version:

NVDA 2024.4.1rc1.

Windows version:

Windows 11 Pro updated from Windows 10 Pro (64-bit).

Name and version of other software in use when reproducing the issue:

Notepad, Notepad++, Mozilla Thunderbird or any text editor.

Other information about your system:

Desktop with 32 GB RAM etc.

Other questions

Does the issue still occur after restarting your computer?

Yes.

Have you tried any other versions of NVDA? If so, please report their behaviors.

Latest alphas, their behavior ist similar to NVDA 2024.4.1rc1.

If NVDA add-ons are disabled, is your problem still occurring?

Probably, because NVDA add-ons have no impact on this.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.

@Jykke67 Jykke67 closed this as completed Dec 16, 2024
@github-actions github-actions bot added this to the 2025.1 milestone Dec 16, 2024
@Jykke67 Jykke67 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant