Make braille word wrap configurable #1946

Closed
nvaccessAuto opened this Issue Nov 21, 2011 · 6 comments

2 participants

@nvaccessAuto

Reported by kredh on 2011-11-21 17:53
When browsing through a text with a braille display, the too long words at the end of the line are not cut: they apear on a different line. This behaviour may be better for some, but not for everybody. Moreover, this behaviour was introduced by a recent snapshot (this problem just doesn't exist on 2011.3rc1).

If you wish to keep this behaviour, could you please add a new checkbox in the braille settings to cancel it?

Thanks

@nvaccessAuto

Comment 1 by jteh on 2011-11-21 20:54
Just to clarify, you prefer that words always be split; i.e. always consume the entire display if possible? The majority of users don't like this, as it makes fluent reading awkward. This is why I changed it, but we can make it configurable if some users prefer the older behaviour.

@nvaccessAuto

Comment 2 by orcauser on 2011-11-22 11:12
Unconfirmed.
Configurable please.
Useful when you want to be sure of the layout of a line, such as checking indentation of lines, and when you try to align things visually.

@nvaccessAuto

Comment 3 by jteh (in reply to comment 2) on 2011-11-22 11:22
Replying to orcauser:

Useful when you want to be sure of the layout of a line, such as checking indentation of lines, and when you try to align things visually.

I don't follow. This isn't related to word wrap, which just causes words that won't fit on the display to be pushed to the next braille "window". The start of lines is unaffected.

@nvaccessAuto

Comment 4 by orcauser (in reply to comment 3) on 2011-11-22 12:08
Replying to jteh:

I don't follow. This isn't related to word wrap, which just causes words that won't fit on the display to be pushed to the next braille "window". The start of lines is unaffected.

ok, here is a real life example,

For tables in the userguide, we use to have a sighted contributer that made the vertical lines align on successive rows, so that it would be easier for her to see what is going on.

If I insert/modify a line, at the moment I can use the start of the line and depending now many displays I scroll forward, know exactly where I am relative to the start of the line.
Otherwise I would have to depend on the editor to provide me the column number of the insersion point.

Disregarding my examples, I think it is still useful to have this as an option. When i use to use Jaws, I use to be frustrated about these sort of issues when dealing with precisely formatted lines.

I do agree with you that the new behaviour should be the default.

Thanks

@nvaccessAuto

Comment 5 by jteh on 2011-11-22 12:13
Changes:
Changed title from "Braille: at the end of line, too long words don't apear" to "Make braille word wrap configurable"
Milestone changed from None to 2012.1

@nvaccessAuto

Comment 6 by jteh on 2011-12-12 06:20
efab8fc
Changes:
State: closed

@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2012.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment