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

Indicate spelling errors in braille #3022

Closed
nvaccessAuto opened this issue Feb 22, 2013 · 4 comments
Closed

Indicate spelling errors in braille #3022

nvaccessAuto opened this issue Feb 22, 2013 · 4 comments
Labels
close/duplicate component/braille enhancement p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@nvaccessAuto
Copy link

Reported by albzan on 2013-02-22 15:55

  • Braille attributes now are displayed using Emphasis Opcodes defined on liblouis tables. By this way you get extra symbols in 8-dots braille representation. Using 7 and 8 dots instead of opcodes also for Bold, Italic, underline, misspelling attributes, the number of chars is the same of what you have on the screen.
  • Now braille attributes are displayed only if the speech read them. Is it possible to show braille attributes independently?
  • Now misspellings are not displayed using attributes.
    Blocking NVDA should indicate misspelled words on The Braille display by The blinking first character of The mispelled word #3469
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2013-02-24 03:16
Font attributes are displayed the way the table defines them. If they should be indicated using dots 7 and 8, the table should indicate this. Most contracted tables are 6 dot tables and braille authorities don't tend to define 8 dot contracted tables. This is something that should be discussed within the liblouis project.

I think using dots 7 and 8 to indicate spelling errors would be confusing, since tables may use dots 7 and 8 individually themselves and dots 7 and 8 together indicate selection. They definitely need to be indicated with a word or something, though.

Separate document formatting configuration for speech and braille is covered by #1885 (though the scope of that ticket needs to be expanded a bit).

I'm morphing this to just cover indication of spelling errors.
Changes:
Changed title from "independent braille attributes using 7 and 8 dots" to "Indicate spelling errors in braille"

@nvaccessAuto
Copy link
Author

Comment 2 by albzan on 2013-02-24 09:49
Hello,

First of all thank you for your reply

You wrote:

Font attributes are displayed the way the table defines them. If they should be indicated using dots 7 and 8, the table should indicate this. Most contracted tables are 6 dot tables and braille authorities don't tend to define 8 dot contracted tables. This is something that should be discussed within the liblouis project.

In liblouis documentation about opcodes at:
http://liblouis.googlecode.com/svn/documentation/liblouis.html#Emphasis-Opcodes

there isn't any specification how to add dot 7 and 8 to show attributes. You can add a special symbol before or after the (start or end) of word, phrase, paragraph, but you cannot specify a pattern for a specific char (to say add extra 7 and 8 dots for chars in bold, italic or underline).

In addition to that all the others screen readers (WE,JFW) have a quick way to enable / disable each specific attribute and selection marking. You can select if you want to mark with 7 and 8 dots the selection, bold, italic, underline, spelling error, combinations of them, all or none. Now in NVDA you can't do this easly. That because if you want to show bold and hide italic you have always to edit the braille table.

For this reason it is useful to be able to define braille attributes into braille table, but it's better if you allow also to manage those indiplendently, like selection, using |= DOT7 | DOT8.

@dkager
Copy link
Collaborator

dkager commented Feb 5, 2017

See also #6785 which is more generic (also covers comments and revisions).

@Adriani90
Copy link
Collaborator

Actually I would close this in favor of #6785 and #7608. There are good suggestions there to cover this.
Regarding display of atributes separately in speech and braille, there is already issue #1885.
Please continue discussions on the coresponding issues. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
close/duplicate component/braille enhancement p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Development

No branches or pull requests

5 participants