[BRLTTY] Would it be easy to make compression of spaces optional?

[Michael Whapples]

Hello,
I don't know in the case of brltty, however I would have thought there 
might be some things which need considering. Here are some questions 
which occur to me:
* What should the spacing be if the contracted Braille is shorter than 
the original text? Should the number of spaces in the terminal be 
inserted or should it be something else? I imagine the first option 
would still lead to tables being a mess, so how does brltty determine 
what spacing to use?
* What happens when the contracted Braille is longer than the original 
text? An example of this might be is the text were a number and number 
signs are being used.
* How should it determine whether a single space is a small column 
separation or a space between words? IE. If the contracted Braille were 
shorter than the original text and there is a single space, should a 
single space be inserted or should it be padded so the next word lines 
up where it is in the original?

Its actually wanting things to line up as they do on the screen which 
makes me stick with computer Braille when using brltty, then all 
characters line up with each other as they should, contracted Braille 
looses this.

Michael Whapples
On 29/05/2012 19:23, Lee Maschmeyer wrote:
> Hi folks,
>
> In English grade 2 braille most consecutive spaces (except those
> preceding the cursor) are compressed into one. This comes in handy as
> it keeps things from being scattered over the display. Often I switch
> to grade two specifically to get this compression.
>
> Once in awhile, though, it's a disadvantage. Right now I have a
> document set up in three columns. Using grade two on this results in a
> virtually unreadable mess.
>
> With these submenus we have now would it be easy to put in a switch so
> we could turn off the consecutive space elimination facility? Of
> course I could read it in computer braille but I kind of like grade
> two. :-)
>
> Only if it's trivial to do though,
>