nvaccess
"expand to computer braille for the word at the cursor" option not translating punctuation, not reverting dot 7 caps indicator
Steps to reproduce:
- Enable the option in the title.
- Type some text, such as PHP code, so that punctuation preceeds a word. Example: if($myVar == 5)
- Place your cursor at the start of the line.
Actual behavior:
the word "myVar" changes to computer braille. The parenthesis and dollar sign do not.
Place your cursor at the end of the line, so the line goes back to contracted braille. Note that the letter V, which should be capitalized, now has a dot 6 in front of it as well as retaining its dot 7 capitalization indicator.
Expected behavior:
Given the wording of the option, I expect the symbols to translate as well. Perhaps I'm mistaken? Also, when reverting to contracted, the dot 7 should go away.
System configuration
NVDA installed/portable/running from source:
portable
NVDA version:
2019.3 beta 1
Windows version:
10, 1903
Name and version of other software in use when reproducing the issue:
N/A (happens everywhere)
Other information about your system:
Input: UEB contracted. Output: UEB contracted. Display: Orbit 20.
Other questions
Does the issue still occur after restarting your PC?
yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No, I only noticed this today as I hadn't yet disabled this option on my beta setup.
I create a try build with Liblouis 3.14: https://ci.appveyor.com/api/buildjobs/9mygyd54ej87jmgt/artifacts/output%2Fnvda_snapshot_try-liblouis3.14-20251%2C29adcc36.exe
Could you guys test this and see whether it's fixed?
On which tables it needs to be tested?
Which languages?
@leonardder
From: Leonard de Ruijter [email protected] Sent: Wednesday, June 3, 2020 10:18 AM To: nvaccess/nvda [email protected] Cc: Subscribed [email protected] Subject: Re: [nvaccess/nvda] "expand to computer braille for the word at the cursor" option not translating punctuation, not reverting dot 7 caps indicator (#10603)
I create a try build with Liblouis 3.14: https://ci.appveyor.com/api/buildjobs/9mygyd54ej87jmgt/artifacts/output%2Fnvda_snapshot_try-liblouis3.14-20251%2C29adcc36.exe
Could you guys test this and see whether it's fixed?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/10603#issuecomment-638007440 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVCDE426NHGGWCSBKIZ5O3RUX2KTANCNFSM4JY7D3AQ . https://github.com/notifications/beacon/ACVCDE4YTE73DQCYJEMQSELRUX2KTA5CNFSM4JY7D3A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEYDTREA.gif
It seems to happen with UEB, for example. I think it would be best if @mehgcap could try to reproduce this if possible.
Ok... so there are the results with the example text from the first issue. here we go! if($myVar == 5) If i put the cursor after the word var, i get the braille translated text in the grade 2 braille, respectively. If i put the cursor on the digit 5, it translates to it's eight-dot counterpart. If i put the cursor on any of the punctuation, i haven't got any counterparts in eight-dot braille. If i put the cursor at the beginning, i get the word myVar translated in the computer braille, without the preceeding punctuation.
I've tested it with the try-build mentioned. Hope it helps.
I can confirm that the try build does not fix the issue.
In my opinion, we should change the default for expand to computer braille to False. It causes too much issues, also for other tables.
In my opinion, we should disable this altogether, until the proper resolver of the issue is found.
From: Leonard de Ruijter [email protected] Sent: Thursday, June 4, 2020 4:23 PM To: nvaccess/nvda [email protected] Cc: zstanecic [email protected]; Comment [email protected] Subject: Re: [nvaccess/nvda] "expand to computer braille for the word at the cursor" option not translating punctuation, not reverting dot 7 caps indicator (#10603)
I can confirm that the try build does not fix the issue.
In my opinion, we should change the default for expand to computer braille to False. It causes too much issues, also for other tables.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/10603#issuecomment-638843933 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVCDEYUDIVTW5HGWBZ5XPDRU6N3RANCNFSM4JY7D3AQ . https://github.com/notifications/beacon/ACVCDE6V5HGXVDPOPJCZR4LRU6N3RA5CNFSM4JY7D3A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEYJ7YHI.gif
@mehgcap, @aaclause, @zstanecic are you still having this issue with NvDA 2024.2? It seems the Liblouis issue has been fixed in 3.20.