Re: [BRLTTY] changing screen windows

[Lars Bjørndal]

On Sun, Jul 29, 2018 at 01:25:13PM -0500, Cheryl Ann Homiak wrote:
> Is there any way to change screen windows using the braille display
> keyboard? Doing control-a and then the number or control-a and then the
> letter c is what works using the computer keyboard, but trying this doesn't
> work on the braille keyboard; after the control-a the c or the number just
> ends up being written. I am starting to consistently use the
> braille keyboard for input but this is one thing I can not do. On the Mac
> brltty has to be run with screen.

On my Handy Tech Actilino, I change screen by holding the left space bare
and press the letter a in input mode. Then, I type the number. It
works for me.

Hope this helps.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Fedora dracut module

[Lars Bjørndal]

Thank you very much for the build for Fedora 27. You wrote:


> - Original Message -
> > Hi, Jaroslav!
> > 
> > About the BRLTTY-dracut module, you wrote:
> > 
> > > It's in Fedora 28 updates-testing repository. If you have an older Fedora,
> > > e.g. 27, I can built it for you.
> > 
> > I'm currently using Fedora 27 on my systems. Is it possible that we
> > can get a Fedora 27 package to `dnf install'?
> >
> I rebuilt it for f27 (this is the old build, without upstream changes):
> https://jskarvad.fedorapeople.org/brltty/
> 
> I am not going to push this to f27 updates.

I've installed it. I ran dracut -f to update the initramfs. The first
time I booted the machine, I got a message: No input key table. The
next time, nothing happened on the braille display.

Should dracut detect the current configuration of BRLTTY, or do I need
to specify parameters manually?

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Fedora dracut module

[Lars Bjørndal]

Thank you for your quick reply. I'll have a look at it.

Lars

On Fri, Jul 06, 2018 at 06:01:18PM -0400, Dave Mielke wrote:
> [quoted lines by Lars Bjørndal on 2018/07/06 at 17:00 +0200]
> 
> >I've installed it. I ran dracut -f to update the initramfs. The first
> >time I booted the machine, I got a message: No input key table. The
> >next time, nothing happened on the braille display.
> 
> Yes, that's actually what I'd expect as I think he said he used the original
> version, i.e. didn't include my subsequent changes, for the F27 rpm. The
> original version didn't install the key tables.
> 
> A bit of history: When dracut suppport was initially envisioned, I knew
> absolutely nothing about dracut, very little about the initramfs environment,
> etc. Jaroslav, and a clearly very capable intern of his named Tomas, very
> kindly wrote quite a good initial version, but, of course, not being brltty
> users, they wouldn't have known the things that are hidden beneath the 
> surface.
> Their initial version was, however, so good that I was able to very quickly
> understand how it all worked and add what was missing. And, of course, let's
> not forget that I was able to actually test the code with a real braille
> display.
> 
> So, yes, one of the initially missing bits was braille deivce key tables.
> 
> Now we might wonder why he didn't just include the latest code in the F27 rpm.
> I think I may know the answer. I wrote a new command, brltty-lsinc, to support
> one of the capabilities that was needed. This command is only in the
> development stream - it'll be in 5.7. In other words, the brltty-lsinc command
> doesn't exist in the version of brltty used in F27. I myself might argue that
> they should just include the latest brltty code in F27, but that may be a risk
> they wouldn't want to take and may even violate their package update policies.
> 
> >Should dracut detect the current configuration of BRLTTY, or do I need
> >to specify parameters manually?
> 
> You can check .../brltty/Initramfs/Dracut/README in the latest brltty source
> tree for how it all works. The answer to your immediate question is that,
> without extra options, it picks up whatever is configured via brltty.conf.
> 
> -- 
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: d...@mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
> 
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Input from HelpTech Actilino

[Lars Bjørndal]

Hello!

Actilino together with a rpi is a neat solution when you need a
lightweight backpack. I've tried that combination, and for the most, it
works great! However, I miss the possibility to perform the Home and End
keys, for instance in Mutt to go to the first (which is not a problem,
you can type 1) and last message.

I don't have an obvious suggestion for which key combination that's the
best to pick, however.

Thanks,
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Input from HelpTech Actilino

[Lars Bjørndal]

Hi, Mario!

You wrote:

> Lars Bjørndal  writes:
> 
> > My point is that I can do pretty much without a QWERTY keyboard,
> > while using the keyboard on Actilino for input. However, in the
> > defualt keyboard layout, I cannot find a funcion to simulate the Home
> > and End functions.
> 
> What about adding the following to /etc/brltty/Input/ht/joystick.kti:
> 
> bind Left+Action KEY_HOME
> bind Right+Action KEY_END
> bind Up+Action KEY_PAGE_UP
> bind Down+Action KEY_PAGE_DOWN
> 
> Does that work for you?

It sounds like a good idea. I will test it and report back. I was not aware 
that the joystick button can be pushed in one direction and in at the same 
time. Thank you.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Input from HelpTech Actilino

[Lars Bjørndal]

Before we consider other combinations, did you see the key presses in the log 
file I attached to the prevous email? E.g. is it possible that we can detect 
key presses like left+in, are these combinations detected at all by BRLTTY?

If not, we could use the joystick together with a dot, e.g. dot 7 or 8.

Lars

On Wed, Nov 14, 2018 at 02:56:54PM +0100, Mario Lang wrote:
> Lars Bjørndal  writes:
> 
> > Hi, Mario!
> >
> > You wrote:
> >
> >> Lars Bjørndal  writes:
> >> 
> >> > My point is that I can do pretty much without a QWERTY keyboard,
> >> > while using the keyboard on Actilino for input. However, in the
> >> > defualt keyboard layout, I cannot find a funcion to simulate the Home
> >> > and End functions.
> >> 
> >> What about adding the following to /etc/brltty/Input/ht/joystick.kti:
> >> 
> >> bind Left+Action KEY_HOME
> >> bind Right+Action KEY_END
> >> bind Up+Action KEY_PAGE_UP
> >> bind Down+Action KEY_PAGE_DOWN
> >> 
> >> Does that work for you?
> >
> > No, sorry. Nothing happens when I press these combinations. Please find a 
> > debug log attached.
> 
> This is sad, because it would be quite a good binding.
> Do you have any suggestions which key combination to use for these?
> 
> We are a bit stuck since the HandyTech input mode is not the same as
> with most other braille displays.  The reason for this is that we are
> (ab)using the two space keys for typing characters with the control
> and/or meta (alt) modifiers.  This is very useful at times, but also
> means that we don't have classical chord command bindings.
> We could in theory switch over to how chords are done with most other
> displays.
> However, we'd loose control and meta modifiers.
> On the other hand, we'd win bindings like Chord+Dot2+Dot3 (PageUp) and
> Chord+Dot5+Dot6 (PageDown).
> 
> -- 
> CYa,
>   ⡍⠁⠗⠊⠕
> 
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Input from HelpTech Actilino

[Lars Bjørndal]

Hi, Mario

You wrote:
> Lars Bjørndal  writes:
> 
> > However, I miss the possibility to perform the Home and End
> > keys, for instance in Mutt to go to the first (which is not a problem,
> > you can type 1) and last message.
> 
> "miss" compared to what?  How did you perform these actions in the past?

Sorry, I'm afraid I don't understand your question. Anyway, I may have 
expressed myself badly.

My point is that I can do pretty much without a QWERTY keyboard, while using 
the keyboard on Actilino for input. However, in the defualt keyboard layout, I 
cannot find a funcion to simulate the Home and End functions.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Input from HelpTech Actilino

[Lars Bjørndal]

Hi, Mario!

You wrote:

> Lars Bjørndal  writes:
> 
> > My point is that I can do pretty much without a QWERTY keyboard,
> > while using the keyboard on Actilino for input. However, in the
> > defualt keyboard layout, I cannot find a funcion to simulate the Home
> > and End functions.
> 
> What about adding the following to /etc/brltty/Input/ht/joystick.kti:
> 
> bind Left+Action KEY_HOME
> bind Right+Action KEY_END
> bind Up+Action KEY_PAGE_UP
> bind Down+Action KEY_PAGE_DOWN
> 
> Does that work for you?

No, sorry. Nothing happens when I press these combinations. Please find a debug 
log attached.

Lars


brltty.log.gz
Description: application/gzip
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Start & stop BRLTTY with Tasker on Android

[Lars Bjørndal]

I frequently need to start and stop the BRLTTY service on my Android
device. I thought I could use Tasker, an Android automation tool, for
that. My approach is to make a widget on the start screen that toggles
BRLTTY on/off. However, it seems that I cannot find the BRLTTY service
from within Tasker, and so I'm not able to instruct Tasker to interact
with it.

I googled start/stop TalkBack with Tasker, and stumbled over this
atricle:

  


Does anyone happen to know if it simply isn't possible to do such tasks without 
a rooted device?

Thanks - Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Start & stop BRLTTY with Tasker on Android

[Lars Bjørndal]

I see. Thank you.

Lars

On Sat, Jul 20, 2019 at 06:58:37PM -0400, Dave Mielke wrote:
> [quoted lines by Lars Bjørndal on 2019/07/20 at 22:47 +0200]
> 
> >I frequently need to start and stop the BRLTTY service on my Android
> >device. I thought I could use Tasker, an Android automation tool, for
> >that. My approach is to make a widget on the start screen that toggles
> >BRLTTY on/off. However, it seems that I cannot find the BRLTTY service
> >from within Tasker, and so I'm not able to instruct Tasker to interact
> >with it.
> 
> I'm sure that's near (maybe totally) impossible. Perhaps what we ought to do 
> is
> have brltty accept an intent that can be used to release/resume the braille
> device. It would, of course, need a permission that your manifest would have 
> to
> request.
> 
> -- 
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: d...@mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
> 
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Bluetooth

[Lars Bjørndal]

On Tue, Nov 19, 2019 at 06:21:17PM +0100, Mario Lang wrote:
> Lars Bjørndal  writes:
> 
> > I recently installed Fedora 30 to a Raspberry pi 3B+. Now, I have the
> > problem that my Handy Tech Active Braille sometimes will not connect
> > when BRLTTY starts. Instead I get the message Pair  y/n on the
> > display. If I answer
> > yes, I get the pairing question repeatedly, also if I reboot the pi.
> 
> Did you change the firmware on the active star in any way?

I have an Active Braille. No, no changes to the display/firmware.

> To my experience, later versions of the active star firmware do behave
> in unexpected and basically unusable ways when it comes to bluetooth.

Did you talk to Helptech about it? Are you sure it's not the connected devices 
that cause the problem?

> Have you tried to repair it manually?

Yes. Then I get connected the first time, and sometimes also more times.

Yesterday I installed raspbian. That seems to work fine until now.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Bluetooth

[Lars Bjørndal]

I recently installed Fedora 30 to a Raspberry pi 3B+. Now, I have the
problem that my Handy Tech Active Braille sometimes will not connect
when BRLTTY starts. Instead I get the message Pair  y/n on the display. If 
I answer
yes, I get the pairing question repeatedly, also if I reboot the pi.

Previously I ran Fedberry, which is a Fedora distro with a kernel and some
other software from the Rpi community. It happened sometimes that I got
that question then, but then, it was sufficient to restart the braille display
to resolve the problem.

Any ideas on how to solve?

Thanks

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Key bindings for the HandyTech products

[Lars Bjørndal]

Hi!

I too use the cursor up/down functions. They are very important if you for 
instance use an Active braille without an external keyboard.

Thanks

Lars

On Mon, Apr 13, 2020 at 09:43:14PM +0200, Mario Lang wrote:
> [Top-posting to keep the answer short.]
> 
> Hi.
> 
> I personally use the binding of CURSOR_UP and CURSOR_DOWN quite a lot.
> And, as you already said, if I don't want to reach all the way to the
> right, I use the SPACE keys to pan horizontally.
> 
> Sébastien Hinderer  writes:
> 
> > Dear all,
> >
> > This message is addressed to Mario and all the users of the Active Star
> > 40 and perhaps also other HandyTech products.
> >
> > I would like to discuss the binding of the left triple action key. Its
> > lower part is currently bound to cursor down, while its upper part is
> > currently bound to cursor up.
> >
> > I never used these bindings and recently changed them. I bound the lower
> > part to full window right and the upper part to full window left. That
> > may sound counterintuitive and may seem more intuitive to do the binding
> > the other way around, but my idea was to be as close as possible to
> > what one is doing when reading printed braille. When one is doing that,
> > at some point the right hand continues to read on its own while the left
> > one returns to the beginning of the line and goes to the following one,
> > so that the right hand knows where to go when reading is finished.
> >
> > With this bindings, I find the load of my two hands more balanced. It's
> > also convenient when the display is not completely filled to not have to
> > go to the triple action key on the right to go to the next braille
> > window. I realise I could do it with the space keys, too, but I don't
> > find this very convenient.
> >
> > So my question is: what do other users of this input table think about
> > this suggestion? Do you find it odd and think I should just keep it for
> > myself, or do you like it and find it worth including?
> >
> > For those who would like to try, I am attaching the updated version of
> > rockers.kti I am using.
> >
> > To use it, just install it under /etc/xdg/brltty/rockers.kti and restart
> > brltty, it will load the alternative version of the table rather than
> > the default one.
> >
> > Best wishes,
> >
> > Sébastien.
> >
> >
> > ___
> > This message was sent via the BRLTTY mailing list.
> > To post a message, send an e-mail to: BRLTTY@brltty.app
> > For general information, go to: http://brltty.app/mailman/listinfo/brltty
> >
> 
> -- 
> CYa,
>   ⡍⠁⠗⠊⠕
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Being notified when battery level is low

[Lars Bjørndal]

On Tue, Oct 06, 2020 at 10:15:43AM +0200, Sébastien Hinderer wrote:
> Dear all,
> 
> Has someone found a way to be notified when the battery level of a
> laptop becomes low?
> 
> This feature is generally provided by graphical desktops but since I am
> not always running one I would be interested in a way of being notified
> that does not rely on having a rrunning mate session or so.
> 
> I considered including something in my shell prompt, but I don't think
> this will always work as I may be reading a book, so I would not catch
> such an information because I could spend a long period without seeing a
> shell prompt.

wall is your friend if you don't have sound available.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Unicode braille patterns

[Lars Bjørndal]

On Thu, Oct 22, 2020 at 01:00:38AM -0400, Nicolas Pitre wrote:
> On Wed, 21 Oct 2020, Dave Mielke wrote:
> 
> > [quoted lines by Lars Bjørndal on 2020/10/21 at 21:23 +0200]
> > 
> > >I'm working on a project where I need to be able to quickly distinguish
> > >between normal letters and braille patterns in the range 0x2800-0x28FF on
> > >the braille display, with BRLTTY in the console. On
> > >my system, 0x2801 is displayed as dot 1, like a normal a. It's ok if it's
> > >displayed as a question mark or whatever, just for this project. Is
> > >there a simple solution?
> > 
> > I'm not sure what you're trying to do. Brltty shows the right symbols for 
> > the
> > braille patterns. Why should it be doing somethign different with them?
> 
> I think he wants to distinguish a braille 'a' from the regular letter 
> 'a'. Right now they're indistinguishable unless you use DESCCHAR on the 
> whole screen.
> 
> My initial thought was to remove the definition for those unicode 
> braille characters from the braille table, but there doesn't seem to be 
> any such definition.
> 
> So the quick solution would be to execute brltty with the
> -X lx:unicode=no argument to disable unicode altogether. But then you 
> won't be able to use DESCCHAR to identify them either.

Ah thank you so much! I'll try that.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Unicode braille patterns

[Lars Bjørndal]

Hi, list!

I'm working on a project where I need to be able to quickly distinguish
between normal letters and braille patterns in the range 0x2800-0x28FF on
the braille display, with BRLTTY in the console. On
my system, 0x2801 is displayed as dot 1, like a normal a. It's ok if it's
displayed as a question mark or whatever, just for this project. Is
there a simple solution?

Thanks

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] BRLTTY and SSH from Windows

[Lars Bjørndal]

[Mario]
> Lars Bjørndal  writes:
> 
> > I had to reinstall my Windows pc at work. Previously I used BRLTTY and
> > Cygwin SSH to access remote servers. That worked pretty well. Anyway I'd
> > like to ask if it's better, nowadays, to use the linux console in
> > Windows, than using Cygwin.
> 
> I had pretty good results with WSL (1 and 2).  Works pretty nicely, and
> is pretty easy to install.

I'll try it when I have some time.

> > Is it possible to install BRLTTY with apt-get and use it from the
> > Linux console?
> 
> I never tried this.  I use a normal Windows screen reader (JAWS and/or
> NVDA in my case).
> 
> BTW, if all you need is ssh, Windows 10 comes with ssh preinstalled.  So
> depending on your requirements, it might be enough to just use that from
> cmd.

Thanks a lot for that info. I'll try it with BRLTTY for Windows, since I need 
braille and cursor routing keys to work.

I prefere using the screen in 80x25. I think that can be set up in the shortcut 
properties.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] BRLTTY and SSH from Windows

[Lars Bjørndal]

I had to reinstall my Windows pc at work. Previously I used BRLTTY and
Cygwin SSH to access remote servers. That worked pretty well. Anyway I'd
like to ask if it's better, nowadays, to use the linux console in
Windows, than using Cygwin. Is it possible to install BRLTTY with
apt-get and use it from the Linux console?

Thanks, Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] German users: no-break space and dot 7?

[Lars Bjørndal]

Hi, Mario!

I'm curious ablut your request. In Norway the braille authority group is 
discussing if we should define no-breaking space to zero dots. When you read a 
web page, for instance, a sighted person does not distinguish between space and 
no-breaking space. Why would a braille reader like to distinguish between these 
characters?

The Norwegian braille table for BRLTTY, no-generic.ttb, has defined no-breaking 
space as an alias for space.

I'd appreciate if you could explain why you want to define the character to a 
representation other than zero dots.

Thanks in advance,
Lars

On Fri, Dec 04, 2020 at 05:46:24PM +0100, Mario Lang wrote:
> Hi.
> 
> To all german users: I just noticed there is no mapping in de.ttb which
> maps to a sole dot 7.  Any objections to mapping non-breaking spaces to
> dot 7?
> 
> -- 
> CYa,
>   ⡍⠁⠗⠊⠕
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.2 soon.

[Lars Bjørndal]

Hi, Samuel!

You wrote:

> For debian users, I have uploaded a snapshot of 6.2 in the experimental
> distribution (versioned 6.2~pre+dfsg-1) so you can try it easily.

Do you happen to also be responsible for the raspbian version of BRLTTY, do you 
have a corresponding package for that distro?

Thanks

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Problem connecting Handy Tech Actilino on Android

[Lars Bjørndal]

[Dave]

> >With TalkBack I hear a message saying Actilino connected for calls.
> 
> That's an odd message for a braille device.

Actilino both has a speaker and a microphone, and is designed to also be able 
to be used for calls. If I remember correctly, the old main board had two 
different bluetooth addresses for the two features.

> >When searching for devices, there is only one Actilino device available.
> 
> Yes, but if its address changed then brltty will be looking for it via the old
> one, and, therefore, not finding it.

I removed the device also from BRLTTY and readded it, before selecting it again.

I'll check it out more deeply.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Unicode braille patterns

[Lars Bjørndal]

On Thu, Oct 22, 2020 at 10:14:22AM -0400, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2020/10/22 at 01:00 -0400]
> 
> >I think he wants to distinguish a braille 'a' from the regular letter 
> >'a'. Right now they're indistinguishable unless you use DESCCHAR on the 
> >whole screen.
> 
> That's what I thought, but I'm not convinced that that's a good idea.
> 
> >My initial thought was to remove the definition for those unicode 
> >braille characters from the braille table, but there doesn't seem to be 
> >any such definition.
> 
> The support for them is in the core. The order is to look for braille 
> patterns,
> and then in the text table. I suppose we could look in the text table first,
> thus making it possible for the table to define them.

Just a thoght; could the braille pattern characters be set to blink on the 
display, on request?

Thanks

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Android

[Lars Bjørndal]

Hello, list!

[Dave]

> [quoted lines by Lars Bjørndal on 2021/04/18 at 16:33 +0200]
> 
> >After upgrading my Samsung Galaxy S10 to Android 11, a problem did
> >reappear: the messages (SMS messages) are not read with BRLTTY. When I open a
> >message, focus is on the edit box. Going up from there let me read the
> >date and time when I last got a message, but not the associated text.
> >TalkBack reads it perfectly.
> >
> >Is it possible that BRLTTY can start to read it again?
> 
> As before, I'd need you to send me a log of the way the screen looks. The 
> current way to log the screen content is Space + RoutingKey19. Please do that 
> and then send me (privately for security) a copy of your system log.

I'd like to notice you all that with the most recent version for Android, it 
now works as expected. Thanks very much to Dave!

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Automatic switch braille display (WAS: Re: Release 6.0 soon.)

[Lars Bjørndal]

Hello!

[Dave Mielke]

> [quoted lines by Lars Bjørndal on 2019/02/03 at 18:52 +0100]
>
>>Is it possible that v.6 will include the automatic switch between
> braille displays on Android? For instance between two ore more pre
> defined displays?
>
> No, there hasn't been time to work on that yet. As you know, though, releases
> for Android are made (via the latest apk) much more often.

It has been some time since this question came up. The feature would be
nice to have. So this request is a kindly reminder only.

Thanks in advance,
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Key table definition for Modular Evolution

[Lars Bjørndal]

Hi!

I'm using a Handy Tech Modular Evolution 88 braille display. I noticed
that B1+B8+Left/Right didn't activate braille input, as expected. I can
fix this by creating a local table addition, but maybe it should be set
in the defaults for convenience.

Thanks in advance
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Key table definition for Modular Evolution

[Lars Bjørndal]

Hi, Mario!

Thanks for your response!


[Mario Lang]

[...]

> As someone who has used a ME88 for roughly 10 years, I
> personally never wanted to use input mode on it, the keys are just too
> sturdy to be pretty together repeatedly.

Just a short explanation; I want braille input for a small project where I need 
to get a few characters as braille dots, e.g. unicode braille.

Thanks
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Accessible way to slow down music?

[Lars Bjørndal]

On Sat, Mar 27, 2021 at 12:53:03PM +0100, Sébastien Hinderer wrote:
> Dear all,
> 
> I am looking for an accessible tool to slow down a song for which I
> can't hear the notes correctly when it's playing at the normal speed.
> 
> I tried with mplayer but there, slowing down also decreases the
> frequency so that's not working so well.
> 
> Is there a solution that would be accessible? Ideally a text-mode or
> commandline oriented tool would be nice but if there is some graphical
> tool which is accessible enough for this purpose that would also be
> acceptable.

Try: mplayer -speed 0.8 -af scaletempo 

0.8 means 80% of normal speed.

Hope this helps.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Android

[Lars Bjørndal]

Hello Dave and all!

After upgrading my Samsung Galaxy S10 to Android 11, a problem did
reappear: the messages (SMS messages) are not read with BRLTTY. When I open a
message, focus is on the edit box. Going up from there let me read the
date and time when I last got a message, but not the associated text.
TalkBack reads it perfectly.

Is it possible that BRLTTY can start to read it again?

Some years ago I had a private conversation with you regarding the same
problem, and I think I provided a log output that made you able to
correct the issue. Please tell me if you need more information.

Thanks in advance

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Android

[Lars Bjørndal]

Hi, Dave!

You wrote:

[...]

> As before, I'd need you to send me a log of the way the screen looks. The 
> current way to log the screen content is Space + RoutingKey19. Please do that 
> and then send me (privately for security) a copy of your system log.

But my display has only 16 cells / routing keys. What do I do then?

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.4 soon

[Lars Bjørndal]

[Dave]
> [quoted lines by Lars Bjørndal on 2021/08/15 at 19:14 +0200]
> 
> >I get errors when I try to do make inside the Documentation directory:
> >
> >Processing file BRLTTY.sgml
> >nsgmls:/etc/sgml/catalog:7:8:E: cannot open 
> >"/etc/sgml/html401-dtds-4.01-1999122
> >4.6.soc" (No such file or directory)
> 
> It looks like some package needed by linuxdoc-tools is missing. Hopefully, 
> whatever package manager your system uses has a way to ask it which package 
> contains some particular file.

I'm using Fedora 33. `dnf provides 
\*/etc/sgml/html401-dtds-4.01-19991224.6.soc\*' gives
Error: No match

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.4 soon

[Lars Bjørndal]

Hi, Dave!

You wrote:

> Please test the latest development code so that as many problems as possible 
> can be discovered ahead of time.

I get errors when I try to do make inside the Documentation directory:

Processing file BRLTTY.sgml
nsgmls:/etc/sgml/catalog:7:8:E: cannot open "/etc/sgml/html401-dtds-4.01-1999122
4.6.soc" (No such file or directory)
nsgmls:/etc/sgml/catalog:10:8:E: cannot open "/etc/sgml/docbook-simple-F9.cat" (
No such file or directory)
nsgmls:/etc/sgml/catalog:12:8:E: cannot open "/etc/sgml/openjade-1.3.2-30.fc8.so
c" (No such file or directory)
nsgmls:0:1:2:E: unknown declaration type "doctype"
nsgmls:0:3:2:E: "ENTITY" declaration not allowed in prolog
nsgmls:0:4:2:E: "ENTITY" declaration not allowed in prolog
nsgmls:0:5:2:E: "ENTITY" declaration not allowed in prolog
nsgmls:0:6:2:E: "ENTITY" declaration not allowed in prolog

Thanks in advance
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.4 soon

[Lars Bjørndal]

[Dave]

> [quoted lines by Lars Bjørndal on 2021/08/15 at 20:46 +0200]
> 
> >I'm using Fedora 33. 
> 
> So am I, and am not getting that error. I also don't have that file.

Thanks for your information. It seems that I had an /etc/sgml/catalog file that 
was the source for the error. It was created by the package sgml-common, but 
even renaming the file and reinstalling that package didn't create a new one. 
With an empty file, it worked.

I tried also building BRLTTY with mock, with the spec/source rpm based on the 
source package from Fedora 34. I got thiss error:

/usr/bin/install -c -m 644 ./../brltty.pc /builddir/build/BUILDROOT/brltty-6.4-1
.fc33.x86_64/usr/lib64/pkgconfig/brltty.pc
../getrevid -p "revision_identifier=" ../ >>/builddir/build/BUILDROOT/brltty-6.4
-1.fc33.x86_64/usr/lib64/pkgconfig/brltty.pc
getrevid: unrecognized source repository type: ../
getrevid: revision identifier not known
make[1]: *** [Makefile:1204: install-pkgconfig-file] Error 3

Do you happen to know what that means?

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.4 soon

[Lars Bjørndal]

Hi, Dave!

You wrote:

> [quoted lines by Lars Bjørndal on 2021/08/18 at 14:58 +0200]
> 
> >I'm experiencing that, if I disconnect the device and then reconnect it, it 
> >takes significant longer before BRLTTY gets aware of it and starts to use it.
> 
> Significantly longer than what?

The 6.3 release packaged by the Fedora team.

> Which specific model is the braille device?

Help Tech (Handy Tech) Modular Evolution 88

> Are you using USB or Bluetooth?

USB

If needed, I can reinstall the old package to double check.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.4 soon

[Lars Bjørndal]

Hi

You wrote:

> [quoted lines by Lars Bjørndal on 2021/08/18 at 21:45 +0200]
> 
> >> Significantly longer than what?
> >
> >The 6.3 release packaged by the Fedora team.

It turned out that prevous version, the version in Fedora 33, was 6.1.

> There shouldn't be any difference as I don't think there's been any changes 
> to any of the involved code.
> 
> >If needed, I can reinstall the old package to double check.
> 
> Well ... it'd be good to kow for sure.

I'm sorry, there was no difference between the two versions in question. I must 
have experienced the quick reconnect with another display. So please forgive me 
that I bothered you with this.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] 6.4 soon

[Lars Bjørndal]

[Dave]

> Please test the latest development code so that as many problems as possible 
> can be discovered ahead of time.

Tested on Fedora 33 with an Help Tech Modular Evolution 88 display.

I'm experiencing that, if I disconnect the device and then reconnect it, it 
takes significant longer before BRLTTY gets aware of it and starts to use it.

It's not a big problem at all, but I thought I'd like to mention it in case you 
whould consider investigate.

Thanks
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Preferences menu

[Lars Bjørndal]

[Dave]
> [quoted lines by Lars Bjørndal on 2021/09/05 at 10:55 +0200]
> 
> >The problem is to enter the preferences menu, so that he can lower the
> >sounds volume from BRLTTY. Is that currently possible without connecting
> >another braille display to do that task?
> 
> On an Orbit, pressing the joystick causes the dot keys to emulate the six 
> Baum display keys. So, I'm expecting that pressing dots 3,4,6 while the 
> joystick is pressed will emulate display keys 3+4+6. That's the binding to 
> toggle the autospeak setting on/off. What I'm suggesting is to toggle 
> autospeak on and then navigate the menu with speech.

Thank you! Good idea! I'll look into the Baum key table then, to figure out how 
to enter/leave the preferences menu and how to navigate it.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Preferences menu

[Lars Bjørndal]

Hi list!

A friend of mine has an Orbit writer, which is a small braille keyboard.
When connected to BRLTTY, it's detected as an Orbit reader 20.
He has successfully connected the keyboard to BRLTTY for Android.

The problem is to enter the preferences menu, so that he can lower the
sounds volume from BRLTTY. Is that currently possible without connecting
another braille display to do that task?

Thanks

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] I'm not able to use my Orbit Writer keyboard any more

[Lars Bjørndal]

I've used an Orbit Writer keyboard with BRLTTY for a long time, also
after starting to use a new Sony Xperia phone some weeks ago. After installing a
Samsung Galaxy Watch 4 to test, however, the keyboard stopped working.
I'm using the Google play version of BRLTTY, but I'm not certain on when
I started to use that version.

Something that concerns me, is that after re-pairing the keyboard, I have
a Settings button. The new dialog that opens, has Forget and Connect.
Pressing Connect does not seem to work.

When BRLTTY starts and the keyboard is selected in BRLTTY, and turned
on, no startup sound comes from BRLTTY.

I've checked the channel and that the SRP protocol is selected.

Hope someone have a hint on how to solve the problem.

Thanks in advance - Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] I'm not able to use my Orbit Writer keyboard any more

[Lars Bjørndal]

Hello!

I have still problem connecting an Orbit Writer keyboard to BRLTTY.

From the log:

12-16 20:23:58.855 W/brltty  (27662): Bluetooth: begin device discovery
12-16 20:23:58.858 W/brltty  (27662): Bluetooth: remember discovered device: 
Addr:0007802B0966 Paired:yes Name:Active Braille AB4/A3-16525
12-16 20:23:58.858 W/brltty  (27662): Bluetooth: remember discovered device: 
Addr:603AAF83855E Paired:yes Name:Galaxy Watch4 Classic (2GTX)
12-16 20:23:58.859 W/brltty  (27662): Bluetooth: remember discovered device: 
Addr:34885D728B6D Paired:yes Name:Logitech K810
12-16 20:23:58.859 W/brltty  (27662): Bluetooth: remember discovered device: 
Addr:5CB6CC865C76 Paired:yes Name:Orbit Reader 20 0111
12-16 20:23:58.860 W/brltty  (27662): Bluetooth: remember discovered device: 
Addr:3C6816550C9D Paired:yes Name:M300-XT v1.03
12-16 20:23:58.860 W/brltty  (27662): Bluetooth: end device discovery
12-16 20:23:58.860 E/brltty  (27662): hidOpenBluetoothDevice error 38: Function 
not implemented
12-16 20:23:58.860 W/brltty  (27662): Bluetooth: discovering serial port channel
12-16 20:23:58.860 W/brltty  (27662): Bluetooth: serial port channel 
discovered: 0
12-16 20:23:58.860 W/brltty  (27662): Bluetooth: RFCOMM channel: 0
12-16 20:23:58.860 W/brltty  (27662): Bluetooth: serial port channel neither 
specified nor discovered

The Active Braille works perfectly with BRLTTY, but not Orbit Writer.

Please tell me if I can do anything more to find the problem.

Thanks, Lars

On Tue, Dec 14, 2021 at 07:35:05PM +0100, Lars Bjørndal wrote:
> Hi, list!
> 
> I wrote:
> 
> > I've used an Orbit Writer keyboard with BRLTTY for a long time, also
> > after starting to use a new Sony Xperia phone some weeks ago. After 
> > installing a
> > Samsung Galaxy Watch 4 to test, however, the keyboard stopped working.
> 
> I don't think that connecting the watch has anything to do with the Orbit 
> keyboard problem.
> 
> > I'm using the Google play version of BRLTTY, but I'm not certain on when
> > I started to use that version.
> 
> [...]
> 
> > When BRLTTY starts and the keyboard is selected in BRLTTY, and turned
> > on, no startup sound comes from BRLTTY.
> > 
> > I've checked the channel and that the SRP protocol is selected.
> 
> I've now tested the keyboard with BrailleBack, and it works. I suppose the 
> problem has something to do with BRLTTY. What can be done to fix the problem?
> 
> Thanks in advance
> Lars
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] I'm not able to use my Orbit Writer keyboard any more

[Lars Bjørndal]

Hi, list!

I wrote:

> I've used an Orbit Writer keyboard with BRLTTY for a long time, also
> after starting to use a new Sony Xperia phone some weeks ago. After 
> installing a
> Samsung Galaxy Watch 4 to test, however, the keyboard stopped working.

I don't think that connecting the watch has anything to do with the Orbit 
keyboard problem.

> I'm using the Google play version of BRLTTY, but I'm not certain on when
> I started to use that version.

[...]

> When BRLTTY starts and the keyboard is selected in BRLTTY, and turned
> on, no startup sound comes from BRLTTY.
> 
> I've checked the channel and that the SRP protocol is selected.

I've now tested the keyboard with BrailleBack, and it works. I suppose the 
problem has something to do with BRLTTY. What can be done to fix the problem?

Thanks in advance
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] BRLTTY disconnects a serial converter

[Lars Bjørndal]

Hi, list!

I need to use a serial converter to produce braille on an old embosser.
I'm using a Raspberry pi and a serial converter. If the converter is
connected at boot up; I get the following output from dmesg:

[   20.964405] usbcore: registered new interface driver ftdi_sio
[   20.964494] usbserial: USB Serial support registered for FTDI USB Serial 
Device
[   20.965023] ftdi_sio 1-1.1.3:1.0: FTDI USB Serial Device converter detected
[   20.965241] usb 1-1.1.3: Detected FT232BM
[   20.966606] usb 1-1.1.3: FTDI USB Serial Device converter now attached to 
ttyUSB0
...
[   23.393568] usb 1-1.1.3: usbfs: interface 0 claimed by ftdi_sio while 
'brltty' sets config #1
[   23.400898] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now 
disconnected from ttyUSB0
[   23.401068] ftdi_sio 1-1.1.3:1.0: device disconnected

The braille display is connected through bluetooth. Is this something
that can be solved from BRLTTYs side?

If I connect the converter after boot up, it sometimes works, and
sometimes leads to a system crash. If it works, and the braille display
goes into sleep mode, the converter disconnects again when the display
wakes up.

Thanks, Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] [OT] Braille display recommendation

[Lars Bjørndal]

[Aura Kelloniemi]

> I reconsider the Actie Braille 2021, because it has many advantages. But am I
> right that the Active Braille series don't have an SD reader, which means that
> I would need to use a proprietary tool to transfer files to/from the internal
> storage, if I wish to utilize the note taker.

You can pill out the SD card from Active Braille, copy files to/from Linux and 
re-insert it.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Windows

[Lars Bjørndal]

[Dave]

> [quoted lines by Lars Bjørndal on 2023/10/11 at 08:28 +0200]
> 
> >When I run brltty, I get BRLTTY.exe: Cannot open //etc/brltty.conf.
> >
> >Isn't the path wrong here, starting with two slashes?
> 
> No, because brltty for Windows is built using MinGW which recognizes the 
> slashes.

Ok, thank you. I've recently upgraded my Windows box from Win 10 to Win 11. I 
previously used brltty 6.3 on Win 10, but was not able to start it in Win 11. I 
tried v.6.6, and then I got the message that brltty couldn't find the 
//etc/brltty.conf, even though the file is in the proper location.

My approach is to run ssh from the DOS prompt (cmd). But the braille display 
(Handy Tech Modular Evolution 88) didn't show anything before I switched to 
legacy mode in the shortcut for cmd.exe. When running ssh from there, I got 
lots of terminal problems when connecting to the server.

I will be out of office for some time now, but will come back to this when I'm 
back. Hope to find a solution.

Thanks,
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Windows

[Lars Bjørndal]

Hi!

I downloaded the brltty-win-6.6-0-libusb-1.0.zip from
https://brltty.app/download.html, extracted the files and directories
inside brltty-win-6.6-0-libusb-1.0 into c:\brl.

When I run brltty, I get BRLTTY.exe: Cannot open //etc/brltty.conf.

Isn't the path wrong here, starting with two slashes?

Thanks,

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Input from a physical keyboard

[Lars Bjørndal]

On Android you can conect a physical bluetooth keyboard, and use it for
input. If input is set to Google keyboard, the physical keyboard works
perfectly well.
If input is set to BRLTTY, however, the selected keyboard layout isn't
honored, which means that if I press the key to the right of the letter
l, with Norwegian keyboad layout is selected, semicolon is produced,
and not the Norwegian letter ø, as expected.

Another difference is that it takes very long time from I press a key
until the letter is announced by TalkBack.

I hope that can be fixed.

Thanks in advance
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Input from a physical keyboard

[Lars Bjørndal]

Thank you. Please note, in case it's useful information for you: Some versions 
ago, with TalkBack on, I had the same problem also with GBoard (Google 
keyboard). I repported the bug, and it became fixed.

Lars


On Sat, Jul 09, 2022 at 02:56:16PM -0400, Dave Mielke wrote:
> [quoted lines by Lars Bjørndal on 2022/07/09 at 13:28 +0200]
> 
> >On Android you can conect a physical bluetooth keyboard, and use it for
> >input. If input is set to Google keyboard, the physical keyboard works
> >perfectly well.
> >If input is set to BRLTTY, however, the selected keyboard layout isn't
> >honored, which means that if I press the key to the right of the letter
> >l, with Norwegian keyboad layout is selected, semicolon is produced,
> >and not the Norwegian letter ø, as expected.
> 
> Yes, that's predictable. It's because the layout is a Google Keyboard setting 
> - not a global settinf. Also, brltty has no control over how the external 
> keyboard behaves. I'll have a look to see if brltty can support setting the 
> external keyboard layout.
> 
> -- 
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: d...@mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Paste in console

[Lars Bjørndal]

Hello, list!

I can't paste from the braille display any more (Help Tech Modular
Evolution 88. Could it be a hardware error?

I notice when I'm writing this message that the cursor routing keys
doesn't work either, and neither do the left triple action key up/down.
In command learn mode, brltty reports the correct behavior of the
respective keys.

I've attached a debug log file.

Lars
2023-03-26@18:12:15.356 [brltty] BRLTTY 6.5 rev BRLTTY-6.5 [https://brltty.app/]
2023-03-26@18:12:15.356 [brltty] Console Encoding: UTF-8
2023-03-26@18:12:15.356 [brltty] lock descriptor allocated: 
queue-discarded-elements
2023-03-26@18:12:15.356 [brltty] Log Level: debug
2023-03-26@18:12:15.356 [brltty] Messages Locale: nb_NO.utf8
2023-03-26@18:12:15.356 [brltty] Messages Domain: brltty
2023-03-26@18:12:15.356 [brltty] Messages Directory: /usr/share/locale
2023-03-26@18:12:15.356 [brltty] Autospeak Threshold: none
2023-03-26@18:12:15.356 [brltty] Privilege Parameter: path=
2023-03-26@18:12:15.356 [brltty] Privilege Parameter: scfmode=
2023-03-26@18:12:15.356 [brltty] Privilege Parameter: shell=
2023-03-26@18:12:15.356 [brltty] Privilege Parameter: user=
2023-03-26@18:12:15.356 [brltty] environment variable set: PATH: /usr/bin
2023-03-26@18:12:15.356 [brltty] environment variable set: SHELL: /bin/sh
2023-03-26@18:12:15.356 [brltty] can't isolate namespaces
2023-03-26@18:12:15.357 [brltty] default unprivileged user not configured
2023-03-26@18:12:15.357 [brltty] executing as the invoking user: root
2023-03-26@18:12:15.357 [brltty] checking XDG runtime directory: /run/user/0
2023-03-26@18:12:15.357 [brltty] XDG runtime directory exists: /run/user/0
2023-03-26@18:12:15.357 [brltty] environment variable set: XDG_RUNTIME_DIR: 
/run/user/0
2023-03-26@18:12:15.357 [brltty] not claiming state directories
2023-03-26@18:12:15.357 [brltty] working directory changed: /var/lib/brltty
2023-03-26@18:12:15.357 [brltty] environment variable set: HOME: /var/lib/brltty
2023-03-26@18:12:15.357 [brltty] starting host command: /usr/sbin/modprobe -q 
pcspkr
2023-03-26@18:12:15.361 [brltty] host command exit status: 0: /usr/sbin/modprobe
2023-03-26@18:12:15.361 [brltty] starting host command: /usr/sbin/modprobe -q 
uinput
2023-03-26@18:12:15.364 [brltty] host command exit status: 0: /usr/sbin/modprobe
2023-03-26@18:12:15.864 [brltty] path not group readable: /dev/uinput
2023-03-26@18:12:15.864 [brltty] path not group writable: /dev/uinput
2023-03-26@18:12:15.864 [brltty] can't set supplementary groups
2023-03-26@18:12:15.865 [brltty] group not joined: 0(root)
2023-03-26@18:12:15.865 [brltty] group not joined: 5(tty)
2023-03-26@18:12:15.865 [brltty] group not joined: 18(dialout)
2023-03-26@18:12:15.865 [brltty] group not joined: 63(audio)
2023-03-26@18:12:15.866 [brltty] group not joined: 475(input)
2023-03-26@18:12:15.866 [brltty] group not joined: 483(brlapi)
2023-03-26@18:12:15.866 [brltty] group not joined: 495(pulse-access)
2023-03-26@18:12:15.866 [brltty] pushed command environment: initial
2023-03-26@18:12:15.867 [brltty] report listener registered: 0: 
handleUpdateBrailleDeviceOnline
2023-03-26@18:12:15.867 [brltty] program exit event added: screen-data
2023-03-26@18:12:15.867 [brltty] Working Directory: /var/lib/brltty
2023-03-26@18:12:15.867 [brltty] Configuration File: /etc/brltty.conf
2023-03-26@18:12:15.867 [brltty] Preferences File: brltty.prefs
2023-03-26@18:12:15.867 [brltty] loading preferences file: 
/var/lib/brltty/brltty.prefs
2023-03-26@18:12:15.867 [brltty] file opened: /var/lib/brltty/brltty.prefs fd=6
2023-03-26@18:12:15.867 [brltty] file opened: /var/lib/brltty/brltty.prefs fd=6
2023-03-26@18:12:15.867 [brltty] program exit event added: tunes
2023-03-26@18:12:15.867 [brltty] tune thread state change: 0 -> 1
2023-03-26@18:12:15.868 [brltty] tune thread state change: 1 -> 3
2023-03-26@18:12:15.868 [brltty] regions: text=0.0 status=0.0
2023-03-26@18:12:15.868 [brltty] shifts: full=1 half=0 vertical=5
2023-03-26@18:12:15.868 [brltty] Updatable Directory: /var/lib/brltty
2023-03-26@18:12:15.868 [brltty] Writable Directory: /run/brltty
2023-03-26@18:12:15.868 [brltty] Drivers Directory: /usr/lib64/brltty
2023-03-26@18:12:15.868 [brltty] Tables Directory: /etc/brltty
2023-03-26@18:12:15.868 [brltty] compiling text table: 
/etc/brltty/Text/no-generic.ttb
2023-03-26@18:12:15.868 [brltty] file opened: /etc/brltty/Text/no-generic.ttb 
fd=10
2023-03-26@18:12:15.868 [brltty] including data file: 
/etc/brltty/Text/no-generic.ttb
2023-03-26@18:12:15.868 [brltty] file opened: /etc/brltty/Text/ltr-latin.tti 
fd=11
2023-03-26@18:12:15.868 [brltty] including data file: 
/etc/brltty/Text/ltr-latin.tti
2023-03-26@18:12:15.868 [brltty] file opened: /etc/brltty/Text/ltr-alias.tti 
fd=12
2023-03-26@18:12:15.868 [brltty] including data file: 
/etc/brltty/Text/ltr-alias.tti
2023-03-26@18:12:15.869 [brltty] file opened: /etc/brltty/Text/ctl-latin.tti 
fd=11
2023-03-26@18:12:15.869 [brltty] including data file: 
/etc/brltty/Text/ctl-latin.tti

Re: [BRLTTY] Paste in console

[Lars Bjørndal]

Replying to myself

> I can't paste from the braille display any more (Help Tech Modular
> Evolution 88. Could it be a hardware error?
> 
> I notice when I'm writing this message that the cursor routing keys
> doesn't work either, and neither do the left triple action key up/down.
> In command learn mode, brltty reports the correct behavior of the
> respective keys.
> 
> I've attached a debug log file.

The problem is linked to a kernel update. With kernel 6.1.18-100.fc36.x86_64 
all works as expected. Booting with kernel-6.2.7-100.fc36.x86_64, the problem 
occured.

Thanks, Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Paste in console

[Lars Bjørndal]

Thank you!

[chrys87]

> sudo sysctl dev.tty.legacy_tiocsti=1

Worked perfectly.

Lars

> Am 26.03.23 um 18:18 schrieb Lars Bjørndal:
> > Hello, list!
> > 
> > I can't paste from the braille display any more (Help Tech Modular
> > Evolution 88. Could it be a hardware error?
> > 
> > I notice when I'm writing this message that the cursor routing keys
> > doesn't work either, and neither do the left triple action key up/down.
> > In command learn mode, brltty reports the correct behavior of the
> > respective keys.
> > 
> > I've attached a debug log file.
> > 
> > Lars
> > 
> > ___
> > This message was sent via the BRLTTY mailing list.
> > To post a message, send an e-mail to: BRLTTY@brltty.app
> > For general information, go to: http://brltty.app/mailman/listinfo/brltty
> 
> 
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] repairing is necessary

[Lars Bjørndal]

Thank you, Maria!

You wrote:

[...]

> Personally, while I've had some pleasant experiences with Bluetooth, all
> my devices are wired these days.  It is just that tad bit more stable,
> and fewer things to care about/maintain.

Yes, wired is more stable. But on the go, I use an rpi with pijuice hat, a BT 
keyboard and a braille display, all to get a working SSH client. Including the 
battery pack, this is four devices. Maybe one day it.ll be possible to replace 
the rpi bit with an app on the mobile phone.

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] printing unicode braille patterns on BrailleBlazer printer

[Lars Bjørndal]

Hi, Peter!

You wrote:

> To recap I have output which mixes ascii and unicode braille patterns
> and I need to print these on an ancient printer (a Braille Blazer from
> 1998) which seems to understand North American Braille Computer Code
> (nabcc). It's an 8-dot printer and the notation I'm using has a lot of
> dot 8 (i.e high bit set). The translation seems to work, i.e checking
> the dot patterns that correspond to the 8-bit characters *after*
> translation seem to match the original. I can't, however, print them.
> This is over a USB-parallel adapter. Things with dot 8 present don't
> seem to be printing correctly. A capital b (dots 1 2 7) will appear
> before each such character and frequently the printed character will
> be offset by 0x80 from the desired, as iff the high bit was being
> ignored. I suspect this is either a printer or Linux device driver
> problem  but in case anyone has either a brltty explanation or
> workaround I thought I'd try here. Any pointers very much appreciated.

I don't know your printer, but most of them has either a menu or a possibility 
to set parameters through sending esc codes, e.g. the esc char followed by some 
characters. Did you try to turn the embosser into 8 dot mode. I suppose the 
default is 6 dot. You may also check which character set the embosser supports.

Hope this helps.

Lars

> Dave Mielke writes:
> >[quoted lines by peter.julien.ray...@gmail.com on 2023/01/22 at 16:39 +1100]
> >
> >>Can brltty help with a mapping between the unicode braille patterns and 
> >>whatever encoding this printer is using? 
> >
> >This command should do what you're looking for:
> >
> >   brltty-trtxt -6 -i en-nabcc -o en-nabcc outputFile
> >
> >The -6 option removes dots 7 and 8. If you'd like to keep those dots then 
> >don't use it.
> >
> >The -i and -o options specify the input and output text tables to use.
> >
> >-- 
> >I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> >Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
> >EMail: d...@mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> >Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> 
> -- 
> Peter Rayner (he/him), Honorary Professorial Fellow, University of Melbourne
> mobile +61 402 752 379
> zoom id 4431343191, join at  
> 
> mail-to: peter.julien.ray...@gmail.com
> google scholar: 
> 
> I acknowledge the Traditional Custodians of the land on which I work, the 
> Wurundjeri people of the Kulin nation, and pay my respect to their Elders, 
> past and present
> I am sending this email when convenient for me, please only respond when 
> convenient for you
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] repairing is necessary

[Lars Bjørndal]

Hello!

I've a Raspberry Pi 3B+ connected to a Handy Tech Active Braille braille
display. I use it with BRLTTY only, no graphical UI. After switching from 
Raspberry pi OS Bullseye 32-bit to bookworm
64-bit, I experience from time to time that I have to use bluetoothctl's
remove device command, followed by scan, pair and trust to
reactivate the connections with the display. Is there something I can do
to prevent this from happening so that I have a more stable solution?

Thanks,

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Raspberry Pi OS, Bookworm

[Lars Bjørndal]

Hi, list!

How is BRLTTY supposed to auto start and connect to a braille display
through bluetooth on this distor?

I chose a basic image, installed BRLTTY, enabled the systemd unit,
paired the device. If I start brltty manually with -b ht and -d
bluetooth:, then all works. But just to start the systemd unit
as root, doesn't seem to work. Th /etc/brltty.conf has the appropriate
braille-device and braille-driver entries in place (actually the same
file worked on an earlier distro).

Thanks
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Raspberry Pi OS, Bookworm

[Lars Bjørndal]

Thank you. When I uncommented the `braill-driver ht` line in the 
/etc/brltty.conf and removed the bluetoot adresses in the braille-device entry, 
all works.

Lars

On Wed, Dec 06, 2023 at 07:33:11PM -0500, Dave Mielke wrote:
> [quoted lines by Lars Bjørndal on 2023/12/06 at 21:59 +0100]
> 
> >des. 06 21:51:47 bri brltty[1195]: brltty: hidOpenBluetoothDevice error 38: 
> >Function not implemented
> >des. 06 21:51:47 bri brltty[1195]: brltty: hidOpenBluetoothDevice error 38: 
> >Function not implemented
> 
> It looks like brltty has been built without Bluetooth support.
> 
> -- 
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: d...@mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Raspberry Pi OS, Bookworm

[Lars Bjørndal]

Hi!

[Dave]
> [quoted lines by Lars Bjørndal on 2023/12/05 at 09:18 +0100]
> 
> >I chose a basic image, installed BRLTTY, enabled the systemd unit,
> >paired the device. If I start brltty manually with -b ht and -d
> >bluetooth:, then all works. But just to start the systemd unit
> >as root, doesn't seem to work. Th /etc/brltty.conf has the appropriate
> >braille-device and braille-driver entries in place (actually the same
> >file worked on an earlier distro).
> 
> Which systemctl command(s) did you use to start brltty?

systemctl enable brltty
systemctl start brltty

> Also, what does systemctl status say?

● brltty.service - Braille Device Support
 Loaded: loaded (/lib/systemd/system/brltty.service; enabled; preset: 
enabled)
 Active: active (running) since Wed 2023-12-06 21:50:36 CET; 1min 11s ago
   Docs: man:brltty(1)
 http://brltty.com/
Process: 1194 ExecStartPre=/bin/sh -c PIDFILE=/run/brltty-initramfs.pid ; 
if [ -s $PIDFILE ]; then kill $(cat $PIDFILE) ; rm -f $PIDFILE ; fi 
(code=exited, status=0/SUCCESS)
   Main PID: 1195 (brltty)
  Tasks: 6 (limit: 1571)
CPU: 355ms
 CGroup: /system.slice/brltty.service
 └─1195 /bin/brltty --no-daemon

des. 06 21:51:47 bri brltty[1195]: brltty: hidOpenBluetoothDevice error 38: 
Function not implemented
des. 06 21:51:47 bri brltty[1195]: brltty: hidOpenBluetoothDevice error 38: 
Function not implemented
des. 06 21:51:47 bri brltty[1195]: hidOpenBluetoothDevice error 38: Function 
not implemented
des. 06 21:51:47 bri brltty[1195]: hidOpenBluetoothDevice error 38: Function 
not implemented
des. 06 21:51:47 bri brltty[1195]: hidOpenBluetoothDevice error 38: Function 
not implemented

...

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Testing a live image in qemu with braille output

[Lars Bjørndal]

I have created a Fedora live image that don't come up as expected.
Because I'm not able to read the screen output when booting, I thogught
I could run it as a virtual machine in qemu, and read the output with
braille from the host system. Could that be a working strategy, and how
do I accomplish it? I have no GUI running.

Thanks

Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] Windows 11

[Lars Bjørndal]

Sorry, I forgot the log file. Attahced.

On Fri, Mar 29, 2024 at 09:08:37PM +0100, Lars Bjørndal wrote:
> Hi, Dave and all!
> 
> I've tried BRLTTY on Widows 11 with a Handy Tech Modular Evolution 88
> display connected. I can get BRLTTY working when running the command prompt as
> admin user. Running it as a normal user, however, gives a 'missing
> braille message acknowledgement' message. Se attached log file
> (gzipped).
> 
> I suppose this is due to new restrictions to the com port usage that
> have been added in Windows 11, and that's maybe nothing BRLTTY can do
> about it. BRLTTY worked in Windows 10 as normal user. I thought
> I should report it here and hope someone have a solution or workaround.
> 
> Thanks,
> Lars
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty


brltty.log.gz
Description: application/gzip
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

[BRLTTY] Windows 11

[Lars Bjørndal]

Hi, Dave and all!

I've tried BRLTTY on Widows 11 with a Handy Tech Modular Evolution 88
display connected. I can get BRLTTY working when running the command prompt as
admin user. Running it as a normal user, however, gives a 'missing
braille message acknowledgement' message. Se attached log file
(gzipped).

I suppose this is due to new restrictions to the com port usage that
have been added in Windows 11, and that's maybe nothing BRLTTY can do
about it. BRLTTY worked in Windows 10 as normal user. I thought
I should report it here and hope someone have a solution or workaround.

Thanks,
Lars
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [BRLTTY] brltty 6.6 under windows not working?

[Lars Bjørndal]

Thank you for pointing this out. On Windows 11, I've only tested BRLTTY 6.6 
with a Handy Tech Modular Evolution braille display in cmd (console). I'm only 
able to get it working if I start cmd as administrator. Otherwise I get 
permission errors.

Lars

On Tue, May 21, 2024 at 05:45:25AM -0500, Paul Scott wrote:
> I think that brltty does work on window but not with nvda and jaws. As far as 
> I
> know brltty 6.4 is used  in narrators. Lastly I use brltty 6.6 frequently with
> window CMD console. My suggestion is use older nvda version such as 2022. Hope
> it helps.
> 
> On Tue, May 21, 2024, 1:54 AM Mario Lang  wrote:
> 
> Hi.
> 
> None of our active devs really use Windows on a regular basis.
> I wonder if it was a good idea to port to that platform, since that
> raises expectations on the user side.
> 
> 
> Simon Eigeldinger <[1]simon.eigeldin...@vol.at> writes:
> 
> > Hi,
> >
> > Have redone that with admin privileges.
> > Forgot about that. :-)
> > Seems we have the same errors.
> > attached is the file.
> > Greetings,
> > Simon
> >
> >
> > Am 20.05.2024 um 01:18 schrieb Jason J.G. White:
> >> On 19/5/24 16:02, Simon Eigeldinger wrote:
> >>> I tried brltty versions 6.3, 6.4, 6.5 and 6.6.
> >>>
> >>> Attached is the brltty.log of brltty 6.6.
> >> There appear to be Windows USB errors. Did you run it with
> >> administrative privilege? I suspect this isn't the issue, but we
> >> might as well check.
> >> I'm not running Windows, so that's the limit of my ability to help.
> >> ___
> >> This message was sent via the BRLTTY mailing list.
> >> To post a message, send an e-mail to: [2]BRLTTY@brltty.app
> >> For general information, go to: [3]http://brltty.app/mailman/listinfo/
> brltty
> >
> >
> > ___
> > This message was sent via the BRLTTY mailing list.
> > To post a message, send an e-mail to: [4]BRLTTY@brltty.app
> > For general information, go to: [5]http://brltty.app/mailman/listinfo/
> brltty
> >
> 
> --
> CYa,
>   ⡍⠁⠗⠊⠕
> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: [6]BRLTTY@brltty.app
> For general information, go to: [7]http://brltty.app/mailman/listinfo/
> brltty
> 
> 
> References:
> 
> [1] mailto:simon.eigeldin...@vol.at
> [2] mailto:BRLTTY@brltty.app
> [3] http://brltty.app/mailman/listinfo/brltty
> [4] mailto:BRLTTY@brltty.app
> [5] http://brltty.app/mailman/listinfo/brltty
> [6] mailto:BRLTTY@brltty.app
> [7] http://brltty.app/mailman/listinfo/brltty

> ___
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty

___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty