Hi Jean-philippe and all, The list is set up to reply directly to the sender, so in this case, I remembered to paste in the list address instead of your direct one. Harri, can the list be set to reply to the list by default? Jean-philippe, if it was only effecting Command Mode, and it wasn't too difficult for Harri to implement, I could support that. I just know from my years as a Braille instructor, that the contextual use of Braille is rather involved and I'm amazed that any program can handle all the exceptions, and MBraille does an excellent job at this. I couldn't imagine trying to program this, so if it can be done and is made clear it is only in Command Mode, that would work. I suspect though, that it might end up meaning all commands would be uncontracted, but let's hear from Harri on that. Richard, "It is better to fail in originality than to succeed in imitation." Herman Melville My web site: https://www.turner42.com From: Jean-philippe Rykiel <jprykiel@gmail.com> Sent: Sunday, February 8, 2026 7:13 AM To: Richard Turner <richardturner42@outlook.com> Subject: Re: [MBraille-Test] Re: v0.9.6 fix version out Hey Richard. 1st of all, I think this list is behaving a bit strangely. You replied to me in private instead of to the whole list, and it happens to me too, I don't know why, so Harri and the other list members didn't see your reply I believe. Okay, let me try to advocate this little request a little more. In fact, I may have expressed myself wrongly. It is the command mode as a whole that doesn't need contractions. So really the idea would be to disable contractions while command mode is on. If this was working the way I think it should, it would just save you one keystroke. The reason I thought of it is because I was trying to execute my fr command, and it never worked until I realised it was expanding as friend. The word friend was not spoken because I didn't insert a space after I typed fr, and I believe words are not spoken when you swipe down in command mode. So I don't know if you're seeing my point, but I think it would make the whole command process simpler, and not more complicated, without you having to think of disabling contractions at all. Tell me, what disadvantage would it have for you if this feature was implemented? Best regards, JPR http://www.jprykiel.com<http://www.jprykiel.com/> https://www.youtube.com/c/jprykiel http://soundcloud.com/ryksounet https://www.youtube.com/c/jprykielhttp://facebook.com/jeanphilipperykiel Le 08/02/2026 à 13:53, Richard Turner a écrit : I would hate that solution. the dot 5,6 solves the issue with no complicated hoops to jump through. Braille is complicated enough in my opinion. Richard "Reality is the leading cause of stress for those who are in touch with it." -- Jane Wagner, from The Search for Signs of Intelligent Life in the Universe. My web site: https://www.turner42.com<https://www.turner42.com/> Sent from my iPhone 16 Pro On Feb 8, 2026, at 1:55 AM, Jean-philippe Rykiel via MBraille-Test <mbraille-test@lists.mpaja.com><mailto:mbraille-test@lists.mpaja.com> wrote: Hey Harri. What did you think of my idea which was to disable contractions for the 1st word after common mode has been turned on? Is it doable, and do you think it's a good one? Here is an example in which it would be handy. I set up a new command alias, just as you suggested, fr to expand as lang fr. It works perfectly, except that if contraction is on, fr will expand as friend, in English braille, so I had to backup a few characters to erase the unwanted ones, or I could have pressed dots 56 to disable contractions for this word. Tell me what you think. Cheers, JPR http://www.jprykiel.com<http://www.jprykiel.com/> https://www.youtube.com/c/jprykiel http://soundcloud.com/ryksounet https://www.youtube.com/c/jprykielhttp://facebook.com/jeanphilipperykiel Le 08/02/2026 à 10:03, Harri Pasanen via MBraille-Test a écrit : Hi everyone, You should soon have a mail from Firebase about the new release to be installed. That mail has changelog entry of fixes done. Version 0.9.5 was a brave new release with some serious issues. My AI helpers had introduced a subtle bug and I had to use my meat brain to hunt it down and fix it. No matter which AI I asked to fix it for me, they all failed. So I guess score 1 for humanity, yay! :-) Known things remaining on my plate: * Settings accessibility is still overly complex. Problem is that when I fixed the accessible navigation, in TalkBack the actual switch toggles stopped working, while VoiceOver was fine. So some more work remains there. * Johanna reported that longer texts do no get fully copied to clipboard when moving away from MBraille. This seems to be a symptom of the same problem as before, affecting newer devices. My venerable 7 year old iPad works, so to reinvestigate. Best regards, Harri _______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com<mailto:mbraille-test@lists.mpaja.com> To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com<mailto:mbraille-test-leave@lists.mpaja.com> _______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com<mailto:mbraille-test@lists.mpaja.com> To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com<mailto:mbraille-test-leave@lists.mpaja.com>