Re: what's new in orca 43.0
Howdy Jordan, // I want to see this screen reader get lots of other new future releases where you have ocr support and finally when you feel confident you can try my plugin driven refactoring of orca. its still a WIP but woks quite well. i created an simple OCR plugin there for testing https://www.patreon.com/posts/ocr-plugin-62328158 or you might want to give a shot to OCRdesktop 4, a stand alone applications to analyse applications (and files) using OCR: https://www.patreon.com/posts/ocrdesktop-4-0-62003474 cheers chrys Am 18.10.22 um 15:29 schrieb Jordan Livesey: hello folks, decided to install debian testing, which is the only version of debian I can actually get working on my computer. in doing so I am now running the latest orca, are there any new improvements I should be aware of? I want to see this screen reader get lots of other new future releases where you have ocr support and finally support for calamares, don't get me wrong, love the text based installer but it would be good to have calameres be accessible then those will eventually be upstream
OCRdesktop 3.0 Released
Howdy List, sorry for cross posting, but I thought you might be interested into that. I just released OCRdesktop 3.0 with some very nice stuff :). For those who don't know about OCRdesktop: https://wiki.archlinux.org/title/Ocrdesktop 1. i removed unmaintained "tesserwrap" bindings and use "pytesseract" now. This is very good maintained and is able to use Tesseract 4.1.x and Tesseract 5.0. Last didnt work with tesserwrap anymore cause by broken API. 2. Removed all deprecation warnings, Modernize the code, use spaces instead of Tab and all kind of cleanup goodness. 3. i added an very nice new feature to analyze the color of an given Text and its background. So you can figure what text is highlighted, has the focus and all kind of useful stuff. its off by default and could be used by "-O" flag as parameter. For this we need some new dependency webcolor and scipy. See the full story here: https://www.patreon.com/posts/ocr-desktop-60895292 https://www.patreon.com/posts/color-analyzing-60988555 Where to get: https://github.com/chrys87/ocrdesktop/releases/tag/v3.0 Depencys: - python3 - tesseract - tesseract-lang- - python3-pillow - python-atspi - python-pytesseract - libwnck3 - GTK3 Optional Depencys - python-scipy (for color detection) - python-webcolors (for color detection) I hope you have as much fun while using it as i had while working on it :). have a good day and stay healthy in those crazy times. cheers chrys
Re: Future of Accessibility in Debian
Howdy, Optionally, if you use the command line, check out https://github.com/tspivey/tdsr <https://github.com/tspivey/tdsr> FYI: Fenrir should run on OSX as well using the PTY Terminal emulation backend :). cheers chrys Zitat von Devin Prater : I would definitely recommend the Mac. You’ll still be able to run free software, in an environment like Unix. Optionally, if you use the command line, check out https://github.com/tspivey/tdsr <https://github.com/tspivey/tdsr> It isn’t as powerful as Fenrir or Speak, but it gets the job done well. Also, the graphical utilities that come with the Mac, Safari, Mail, text-edit, are great also. There is spell checking, autocorrect, text replacement, and AppleScripting and Automation, all configurable, throughout the system, not just in your word processor, all accessible with VoiceOver. Of course, there are current bugs. In Safari, you hear “insertion point at (nil)” at the end of every paragraph unless you use the arrow keys, and not VoiceOver navigation, to read. These bugs are usually fixed within the year of a version release, and the releases are often much better than the public beta versions. I seriously hope that Linux stays accessible, because I’d hate to see free software let us down so majorly. But, volunteers are not held to a standard of accessibility, so I will not be shocked if all we have left in Linux is the command line. On Nov 7, 2019, at 6:21 PM, thom...@fastmail.cn wrote: Hi, I have followed the discussion on the orca list lately and the conflicts around GTK 4 accessibility. I guess without getting into the drama of it all, I would just like to ask those who are knowledgeable if they think we will have Linux accessibility going into the future. I guess the issue seems to be that patches are being created for what upstream thinks is a broken system in some ways and it sounds like things like keyboard snooping could cause problems in the future. I honestly don't know enough to understand whether its broken from a design standpoint, however, it at least lets me use the computer. I am not a skilled enough developer to understand all this yet but I rely on accessibility software for my job. I guess I would just like as honest as an answer as possible. If people think accessibility is going to be removed or key parts of the needed infrastructure, I see no other option than to buy a Mac now so that I can continue to operate the computer in the future. I did notice some comments that proposed removing ATK entirely which obviously would leave me dead in the water.. Ultimately, if the end is approaching, I would like to purchase a Mac as soon as possible since I will have to relearn the computer and a new screen reader (VoiceOver and would like as smooth a transition as possible. I love using free software and hope to continue doing so, however, I ultimately have to do what is necessary to keep my job so I can support myself. Thanks for any information and i hope those here can understand my concerns and honestly just not knowing what to do based on not having the technical knowledge to understand entirely what is happening in the different upstream packages.
Re: dbus-broker vs dbus-daemon for the accessibility bus
Howdy, We use dbus-broker exclusive here. No issues at all and like you noted, it seems to perform faster, specially on heavy operations. Cheers chrys > Am 08.10.2019 um 14:29 schrieb thom...@fastmail.cn: > > For those not in the know, dbus-broker is a reimplementation of the > dbus-daemon. > I am very interested in this subject when it comes to the accessibility bus. > I have done two types of tests on debian. This requires building the broker > from source and rebuilding at-spi2-core. Used cpu was an 8550u. > Test 1: Load large pages in Chrome with its accessibility enabled with Orca > on. I find that the accessibility bus often uses up to 50 percent of a core > with the daemon and 30 percent with the broker. You need to use Chrome 77 or > older because a change was recently made to Chrome master which makes it send > far less across the bus when loading a page. World War ii page on wikipedia > works nicely. > Test 2: Put the daemon and broker processes in a cgroup and limit their cpu. > In my unscientific testing, I find that the broker seems to perform a bit > better with less cpu. As you choke off the cpu more and more, the gap widens. > Just curious if anyone has done similar testing on debian or even other > distros. I have a core i7 8550u so I don't notice a huge difference but I > suspect users with less cpu might. I have an older core 2 duo machine. It > would be very interesting to get another of those and do side by side testing. >
Re: webmail and email from command line
Howdy, This is just an mirror for internal backup (in this case also a different commit). So there is only one script. Use storms master as he is the creator. > Am 30.08.2019 um 19:29 schrieb D.J.J. Ring, Jr. : > > Unfortunately there are two fleacoller scripts. > > They should consolidate them, but they aren't going to do that. > > This is one, > https://88.198.55.25/AIT/fleacollar/raw/5941be5d1f1a85e5498f0647b659056ff7fa125f/fleacollar.sh > > But the other one which is difficult to find is more recent. > > Here it is: > > The latest version is at: > https://gitlab.com/stormdragon2976/fleacollar/raw/master/fleacollar.sh > > Unfortunately, it does NOT work with Slint, > > Best wishes, > > > David > > > > >> On Fri, Aug 30, 2019, 12:11 wrote: >> You suggested 'fleacollar.sh' so I downloaded it and used chmod to make >> it executable. Fleacollar.sh is not like any script I have ever seen and >> just making it executable does not make it redallly usable. Has any one >> use it and what changes were made to it to make it usable in a Debian >> console installation of Mutt. >> -- >> >>
Re: Accessible Game that will run on Debian
Howdy, Done :). https://github.com/chrys87/battleship-cli mono and sdl is needed (i dont remember lol its about 10 years old, but the read me tells XD). i figured there is still a precompiled bin in this folder: battleship-cli/battleship/bin/Debug/battleship.bin cd battleship-cli/battleship/bin/Debug/ mono battleship.bin as far as i remember you see the available command-lets with "help" cheers chrys Am 30.07.19 um 15:13 schrieb Vojtěch šmiro: Hello. Yes, you can it will be interresting. You can put your project on Githup. thanks, Vojta. Dne 30.7.2019 v 14:38 chrys napsal(a): Howdy, i made some CLI battleship game for doing som c# playground with mono. if you want i can push it to github cheers chrys Am 30.07.19 um 14:18 schrieb libreaudioga...@fastmail.com: On Tue, Jul 30, 2019, at 3:22 AM, Vojtěch šmiro wrote: Hello. Problem, Python3-pygame has no installation candidate. How to play? When replying to a mailing list post, please include the entire list as others may encounter the same problem as you or be able to help you. This sort of message means that the current package isn't in your version of debian. To understand why this is, fire up a browser to tracker.debian.org and enter python3-pygame in the search box. On the resulting page, select python3-pygame under the binaries heading. On the final page we can see that python3-pygame is only available in Buster, Bullseye, and sid and this can be found with Orca by pressing the Down arrow from the Search button. This means that you must be on Buster or later to play this game. Buster is the current stable version of Debian. I decided not to support python2 in my projets due to its obsolescence in less than a year upstream and python3-pygame being available in the current stable debian. Thanks, Vojta. Someone asked about accessible games but I am not on the list. This game I am working on updating should work well as I tested it under Bullseye which I am currently running as my main os. It was originally written in 2005 by some university students, however, I removed the proprietary pysonic dependency and updated it to python3 so all you should need is python3-pygame. It is a fun adventure game where you explore a house of a crazy doctor who is doing medical experiments. https://github.com/libreaudiogamer/DescentIntoMadness
Re: Accessible Game that will run on Debian
Howdy, i made some CLI battleship game for doing som c# playground with mono. if you want i can push it to github cheers chrys Am 30.07.19 um 14:18 schrieb libreaudioga...@fastmail.com: On Tue, Jul 30, 2019, at 3:22 AM, Vojtěch šmiro wrote: Hello. Problem, Python3-pygame has no installation candidate. How to play? When replying to a mailing list post, please include the entire list as others may encounter the same problem as you or be able to help you. This sort of message means that the current package isn't in your version of debian. To understand why this is, fire up a browser to tracker.debian.org and enter python3-pygame in the search box. On the resulting page, select python3-pygame under the binaries heading. On the final page we can see that python3-pygame is only available in Buster, Bullseye, and sid and this can be found with Orca by pressing the Down arrow from the Search button. This means that you must be on Buster or later to play this game. Buster is the current stable version of Debian. I decided not to support python2 in my projets due to its obsolescence in less than a year upstream and python3-pygame being available in the current stable debian. Thanks, Vojta. Someone asked about accessible games but I am not on the list. This game I am working on updating should work well as I tested it under Bullseye which I am currently running as my main os. It was originally written in 2005 by some university students, however, I removed the proprietary pysonic dependency and updated it to python3 so all you should need is python3-pygame. It is a fun adventure game where you explore a house of a crazy doctor who is doing medical experiments. https://github.com/libreaudiogamer/DescentIntoMadness
Re: loss of speech in speakup when switching between console and gui
Howdy, https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=fenrir right I'll let you know how that goes on Slint. I know about users who run it on windows, BSD and MacOSX ;) so i assume it runs on Slint too. I don't think that can fully replace speakup though ;) oh, i would be interested in why? Thats exact the kind of feedback i m looking for :). There are already a lot of fenrir only users out there :). but mostly on Arch based systems. so at least for them it seems to be able ;). let me know what you think or what is missing. code is nothing fixed or hammered in stone ;) . something off topic, i see in slint you ship KDE plasma. i want to give some attention here on our progress to make it accessible. you and maybe others here might be interested in. see federiks (my mentor) blogpost: http://blogs.fsfe.org/gladhorn/2018/11/05/accessibility-update-kickoff-kicker-and-kwin-improvements/ or see some cherry picked status updates from mailing list: https://mail.kde.org/pipermail/kde-accessibility/2018-October/003245.html https://mail.kde.org/pipermail/kde-accessibility/2018-October/003251.html https://mail.kde.org/pipermail/kde-accessibility/2018-November/003259.html so the next version will have everything _basic_ on place to be able to initial work with KDE for blind people (First time in KDEs history!). of course help is always welcome :). I have only good words to the KDE community. the guys there are very frindly and ready to help out where ever possible. cheers chrys Zitat von Didier Spaier : I have in my TODO list to try fenrir, so thanks for the reminder Chrys. I guess that the PKGBUILD is here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=fenrir I'll let you know how that goes on Slint. I don't think that can fully replace speakup though ;) Anyway the issue of switching between console and graphical modes in Debian remains. Best regards, Didier On 06/11/2018 13:44, ch...@linux-a11y.org wrote: Howdy, i dont want to ditch speakup, but you also may want to try out fenrir :). i got a lot of positive feedback from archLinux users where i can provide an PKGBUILD for. in fact F123 is basing its images for low budget computers on that screenreader. so its very fast too, witout need of digging around in kernel. I m not blind, but i mostly created it based on information and wishes i got from blind users (you may know i.e. storm_dragon, Kyle or deedra from orca list). you can make it go away for GUI or controll it via the remote manager to make it fill the needs at runntime. for pulseaudio i provide some simple setup scripts. I would be happy to see some testers on other distros then archlinux too :). what makes me able fix up issues for other distos like debian too. it can also just run in an GUI terminal without need an 3rd party software like an patched version of screen or tmux. cheers chrys Zitat von Didier Spaier : Hello, this is a follow-up, with bad news. The tests I made that were successful were in console mode (systemctl set-default multi-user.target) However, they failed when in graphical mode: (systemctl set-default graphical.target) I go as far as re installing Debian Buster on bare metal (USB connected hard disk), tried many things including all listed below to no avail: once Orca is running in the Mate desktop if I type Ctrl+Alt+F2 I don't have sound, although espeakup be running. I am sorry, but I already spent too much time trying to understand how audio works in Debian to investigate this issue, so I give up. When lightdm is running but I didn't login yet, I can e.g. type Ctr+Alt+F2 and login in this tty with speech, but as soon as I am logged in through lightdm and orca (and pulse) is started for a regular user I have no more sound. I tried with and without autospawn of pulse, same bad result. I am sorry, but I already spent too much time trying to understand how audio works in Debian to investigate this issue, so I give up. I will just answer questions from Debian folks, if any. Meanwhile, my advice to blind Linux users is to use Slint ;) Best regards, Didier On 02/11/2018 01:42, Samuel Thibault wrote: Hello, (I reordered things a bit to make the story clearer for pulseaudio maintainers in Cc) Didier Spaier, le ven. 02 nov. 2018 01:13:09 +0100, a ecrit: This message is an answer to the thread started by: https://lists.debian.org/debian-accessibility/2018/10/msg0.html @Keith: If you don't use pulseaudio, the issue could be an unexpected consequence of applying since Thu, 03 May 2018 the patch audio-pause: "Pause espeak when the console is switched to a graphical VT" Well, I believe that report is just another case of the well-known issue that once pulseaudio is started in X (e.g. for orca), it holds the ALSA card completely and espeakup can't take it again. The pause patch makes espeakup release the ALSA card so that pulseaudio triggered by Orc
Re: loss of speech in speakup when switching between console and gui
Howdy, i dont want to ditch speakup, but you also may want to try out fenrir :). i got a lot of positive feedback from archLinux users where i can provide an PKGBUILD for. in fact F123 is basing its images for low budget computers on that screenreader. so its very fast too, witout need of digging around in kernel. I m not blind, but i mostly created it based on information and wishes i got from blind users (you may know i.e. storm_dragon, Kyle or deedra from orca list). you can make it go away for GUI or controll it via the remote manager to make it fill the needs at runntime. for pulseaudio i provide some simple setup scripts. I would be happy to see some testers on other distros then archlinux too :). what makes me able fix up issues for other distos like debian too. it can also just run in an GUI terminal without need an 3rd party software like an patched version of screen or tmux. cheers chrys Zitat von Didier Spaier : Hello, this is a follow-up, with bad news. The tests I made that were successful were in console mode (systemctl set-default multi-user.target) However, they failed when in graphical mode: (systemctl set-default graphical.target) I go as far as re installing Debian Buster on bare metal (USB connected hard disk), tried many things including all listed below to no avail: once Orca is running in the Mate desktop if I type Ctrl+Alt+F2 I don't have sound, although espeakup be running. I am sorry, but I already spent too much time trying to understand how audio works in Debian to investigate this issue, so I give up. When lightdm is running but I didn't login yet, I can e.g. type Ctr+Alt+F2 and login in this tty with speech, but as soon as I am logged in through lightdm and orca (and pulse) is started for a regular user I have no more sound. I tried with and without autospawn of pulse, same bad result. I am sorry, but I already spent too much time trying to understand how audio works in Debian to investigate this issue, so I give up. I will just answer questions from Debian folks, if any. Meanwhile, my advice to blind Linux users is to use Slint ;) Best regards, Didier On 02/11/2018 01:42, Samuel Thibault wrote: Hello, (I reordered things a bit to make the story clearer for pulseaudio maintainers in Cc) Didier Spaier, le ven. 02 nov. 2018 01:13:09 +0100, a ecrit: This message is an answer to the thread started by: https://lists.debian.org/debian-accessibility/2018/10/msg0.html @Keith: If you don't use pulseaudio, the issue could be an unexpected consequence of applying since Thu, 03 May 2018 the patch audio-pause: "Pause espeak when the console is switched to a graphical VT" Well, I believe that report is just another case of the well-known issue that once pulseaudio is started in X (e.g. for orca), it holds the ALSA card completely and espeakup can't take it again. The pause patch makes espeakup release the ALSA card so that pulseaudio triggered by Orca can take it. This is considered a better behavior than not getting any audio inside X just because espeakup holds the ALSA card. I then made these changes: 1) Edit /etc/pulse/default.pa to append these lines: load-module module-alsa-sink device=dmix load-module module-alsa-source device=dsnoop So using dmix is not the default in Debian? 2) In /usr/share/alsa, remove the files pukse-alsa.conf and alsa.conf.d/alsa.conf, to avoid setting pulseaudio as the default plugin for applications using Alsa when pulseaudio is running. I made these changes so that applications using pulseaudio and applications using alsa directly can nicely coexist, not stepping on each others toes. I don't know if the modifications I made are acceptable by the Debian authorities though ;) There is no such thing like "Debian authorities". There are the maintainers of the pulseaudio stack, which define a default configuration which aims at the most common case. I don't know why dmix is not part of it, that's with them to be discussed, e.g. in a bug report. Making pulseaudio share the device with alsa thanks to dmix seems like an option indeed, that you could document on http://wiki.debian.org/accessibility I don't know what counterparts there might be to it, again pulseaudio maintainers will know better. I also disabled autostarting of pulseaudio at the user level, appending: "Hidden=true" to the file /etc/xdg/autostart/pukseaudio.desktop but maybe that doesn't matter. Anyway pulseaudio is spawned by the applications that need it. And notably here by Orca, so I don't think that is involved here. But these changes were not sufficient to solve the issue so I had a look at the speakup Debian package. Seeing the aforementioned patch I thought that it could cause the issue. To check I just replaced /usr/bin/espeakup by the binary shipped in Slint and it worked. Ok, so somehow espeakup doesn't manage to take the ALSA card again once pulseaudio is star
Fwd: Fenrir 1.9.2 Released
Howdy List, just to want to share the resutls of Devins (and jeremiah) help. Fenrir runs now on MacOSX, Linux, BSD, and windows (tested via WSL). i will wire up an SAPI and NSS speech backend to give support for the native speech frameworks. thanks for your help and investigation guys. cheers chrys - Weitergeleitete Nachricht von ch...@linux-a11y.org - Datum: Wed, 18 Jul 2018 14:22:25 +0200 Von: ch...@linux-a11y.org Betreff: Re: Fenrir 1.9.2 Released An: debian-accessibility@lists.debian.org Awsome :) thanks! Zitat von Devin Prater : I would be happy to help. I'll be on IRC tomorrow. Devin Prater On Tue, Jul 17, 2018 at 2:09 PM -0500, wrote: Howdy Devin, Ok thanks for the info :). Like noticed i do what i can :).. You own an mac?this is interesting to me sine fenrir should run on mac in pty mode as well. Sadly i dont own an mac. But i want to wire up fenrir for mac. I wonder if you would help me to wire up fenrir for mac? I will fix needed issues but i need ia tester here :). It should also run on windows what i do not own ( of course on cli only) Cheers chrys Zitat von Devin Prater : With attributes, they include italics, bold, underline, things like that. Not too much, but things I would want to know about. They do depend on Braille table. Perhaps NVDA’s Braille implementation can show things possible. On Jul 17, 2018, at 1:09 PM, ch...@linux-a11y.org wrote: Howdy John, For my initial work i created an debug braille driver what just prints the showhn text to stdout. I will take a look at your link. The initial brltty driver works i tested it with storm dragon. He had a braille device. But its verry unpractical to not be able to verify your own code after doing some changes :). With the debug driver i will not be able to emulate braille input. But fenrir is able by design to bind commands to any shortcut also to keyboard what may help as well :). I will fore sure do what i can ;). But help is very welcome to make a perfect job to wire up an best possible result to all :). But foor example devins attribute stuff ; i dont know what attributes have an braille eqvivalent and how they look like. Do they depend on the used braille table? (Just an example of many questions i have) Thanks for your links i will investigate. Cheers chrys Zitat von john doe : On 7/17/2018 7:01 PM, chrys wrote: Howdy Devin, sure thing as soon as i figure how lol. i dont own an braille device so i just can do most of that stuff "blind" lol. for stuff like that it would be really awesome to have someone with python dev skills and braille device on my side :). i m not blind so maybe i m not the best person to say how it needs to be done that it is perfect. i already started the implementation and basic stuff should be doable but its not production ready yet. thats why the default braille driver is currently dummy lol. but basic brltty usage is already implemented and also some needed bits to show up some text on the braille device and flush it. panning should be in place as well. but all untested lol. i will add your request to the list. here the outstanding todos if someone wants to dive in and help out :). Braille Support: [] brailleFocusMode: [] manual = no automatic toggle, command used (text cursor, review cursor, attribute cursor) [] last = follow last used cursor (text cursor, review cursor, attribute cursor) [] print cursor in review [] print cursor in textmode / attribute tracking [] word wrapping (if word does not fit print it at next page) [] command toggle used cursor (in manual brailleFocusMode) [] capture input from braile [] make routing keys assignable by keyboard [] make brailleTable configurable [] tuning for the commands, what should be pinned, what should be flushed, what not shown at all. JFYI same for dectalk :). i want to provide an dectalk speech driver. but i dont own an device. speech drivers designed are really simple. so maybe someone with an device can help out here as well. I don't have the python skills but maybe you could emulate a brail display: https://linux.die.net/man/1/qemu-kvm You could have a look at NVDA which is also written in python: https://github.com/nvaccess -- John Doe - Ende der weitergeleiteten Nachricht -
Re: Fenrir 1.9.2 Released
Howdy Joe, Any hint on how I would use it on Windows? i was not able to try but in theorie it should be possible with small changes in terminal emulation mode since i use pyte to emulate the terminal and this works on all VT100 Terminals. a good way could be this: 1. install all dependecys (for windows it just is python3, pyte, espeak (speech), sox (soundicons)) 2. install bash ( not sure about powershell here, could be worth a try if the basic issues out of the way) 3. get the path of espeak and add it to the generic speech command in config 4. fire up "./fenrir -e" in bash fenrir should spawn an ne bash instance with itself in the middle to grab the information if it works and we fixed the issues we can provide a settings file for windows and and small howto. Any reason why you have file name separated with spaces in the repo (with CLI/Git I would use '-' instead of spaces for 'file' name)? hmm no reason for real, but it also was no issue currently. i can change the ToDo list file and the release notes/ play zone folders to remove the space. thats the only places is see. cheers chrys Zitat von john doe : On 7/17/2018 9:09 PM, ch...@linux-a11y.org wrote: Howdy Devin, Ok thanks for the info :). Like noticed i do what i can :).. You own an mac?this is interesting to me sine fenrir should run on mac in pty mode as well. Sadly i dont own an mac. But i want to wire up fenrir for mac. I wonder if you would help me to wire up fenrir for mac? I will fix needed issues but i need ia tester here :). It should also run on windows what i do not own ( of course on cli only) I have cloned your repo using Cygwin. Any hint on how I would use it on Windows? When time allows I will try it on Debian 9. Any reason why you have file name separated with spaces in the repo (with CLI/Git I would use '-' instead of spaces for 'file' name)? -- John Doe
Re: Fenrir 1.9.2 Released
Awsome :) thanks! Zitat von Devin Prater : I would be happy to help. I'll be on IRC tomorrow. Devin Prater On Tue, Jul 17, 2018 at 2:09 PM -0500, wrote: Howdy Devin, Ok thanks for the info :). Like noticed i do what i can :).. You own an mac?this is interesting to me sine fenrir should run on mac in pty mode as well. Sadly i dont own an mac. But i want to wire up fenrir for mac. I wonder if you would help me to wire up fenrir for mac? I will fix needed issues but i need ia tester here :). It should also run on windows what i do not own ( of course on cli only) Cheers chrys Zitat von Devin Prater : With attributes, they include italics, bold, underline, things like that. Not too much, but things I would want to know about. They do depend on Braille table. Perhaps NVDA’s Braille implementation can show things possible. On Jul 17, 2018, at 1:09 PM, ch...@linux-a11y.org wrote: Howdy John, For my initial work i created an debug braille driver what just prints the showhn text to stdout. I will take a look at your link. The initial brltty driver works i tested it with storm dragon. He had a braille device. But its verry unpractical to not be able to verify your own code after doing some changes :). With the debug driver i will not be able to emulate braille input. But fenrir is able by design to bind commands to any shortcut also to keyboard what may help as well :). I will fore sure do what i can ;). But help is very welcome to make a perfect job to wire up an best possible result to all :). But foor example devins attribute stuff ; i dont know what attributes have an braille eqvivalent and how they look like. Do they depend on the used braille table? (Just an example of many questions i have) Thanks for your links i will investigate. Cheers chrys Zitat von john doe : On 7/17/2018 7:01 PM, chrys wrote: Howdy Devin, sure thing as soon as i figure how lol. i dont own an braille device so i just can do most of that stuff "blind" lol. for stuff like that it would be really awesome to have someone with python dev skills and braille device on my side :). i m not blind so maybe i m not the best person to say how it needs to be done that it is perfect. i already started the implementation and basic stuff should be doable but its not production ready yet. thats why the default braille driver is currently dummy lol. but basic brltty usage is already implemented and also some needed bits to show up some text on the braille device and flush it. panning should be in place as well. but all untested lol. i will add your request to the list. here the outstanding todos if someone wants to dive in and help out :). Braille Support: [] brailleFocusMode: [] manual = no automatic toggle, command used (text cursor, review cursor, attribute cursor) [] last = follow last used cursor (text cursor, review cursor, attribute cursor) [] print cursor in review [] print cursor in textmode / attribute tracking [] word wrapping (if word does not fit print it at next page) [] command toggle used cursor (in manual brailleFocusMode) [] capture input from braile [] make routing keys assignable by keyboard [] make brailleTable configurable [] tuning for the commands, what should be pinned, what should be flushed, what not shown at all. JFYI same for dectalk :). i want to provide an dectalk speech driver. but i dont own an device. speech drivers designed are really simple. so maybe someone with an device can help out here as well. I don't have the python skills but maybe you could emulate a brail display: https://linux.die.net/man/1/qemu-kvm You could have a look at NVDA which is also written in python: https://github.com/nvaccess -- John Doe
Re: Fenrir 1.9.2 Released
Howdy Devin, Ok thanks for the info :). Like noticed i do what i can :).. You own an mac?this is interesting to me sine fenrir should run on mac in pty mode as well. Sadly i dont own an mac. But i want to wire up fenrir for mac. I wonder if you would help me to wire up fenrir for mac? I will fix needed issues but i need ia tester here :). It should also run on windows what i do not own ( of course on cli only) Cheers chrys Zitat von Devin Prater : With attributes, they include italics, bold, underline, things like that. Not too much, but things I would want to know about. They do depend on Braille table. Perhaps NVDA’s Braille implementation can show things possible. On Jul 17, 2018, at 1:09 PM, ch...@linux-a11y.org wrote: Howdy John, For my initial work i created an debug braille driver what just prints the showhn text to stdout. I will take a look at your link. The initial brltty driver works i tested it with storm dragon. He had a braille device. But its verry unpractical to not be able to verify your own code after doing some changes :). With the debug driver i will not be able to emulate braille input. But fenrir is able by design to bind commands to any shortcut also to keyboard what may help as well :). I will fore sure do what i can ;). But help is very welcome to make a perfect job to wire up an best possible result to all :). But foor example devins attribute stuff ; i dont know what attributes have an braille eqvivalent and how they look like. Do they depend on the used braille table? (Just an example of many questions i have) Thanks for your links i will investigate. Cheers chrys Zitat von john doe : On 7/17/2018 7:01 PM, chrys wrote: Howdy Devin, sure thing as soon as i figure how lol. i dont own an braille device so i just can do most of that stuff "blind" lol. for stuff like that it would be really awesome to have someone with python dev skills and braille device on my side :). i m not blind so maybe i m not the best person to say how it needs to be done that it is perfect. i already started the implementation and basic stuff should be doable but its not production ready yet. thats why the default braille driver is currently dummy lol. but basic brltty usage is already implemented and also some needed bits to show up some text on the braille device and flush it. panning should be in place as well. but all untested lol. i will add your request to the list. here the outstanding todos if someone wants to dive in and help out :). Braille Support: [] brailleFocusMode: [] manual = no automatic toggle, command used (text cursor, review cursor, attribute cursor) [] last = follow last used cursor (text cursor, review cursor, attribute cursor) [] print cursor in review [] print cursor in textmode / attribute tracking [] word wrapping (if word does not fit print it at next page) [] command toggle used cursor (in manual brailleFocusMode) [] capture input from braile [] make routing keys assignable by keyboard [] make brailleTable configurable [] tuning for the commands, what should be pinned, what should be flushed, what not shown at all. JFYI same for dectalk :). i want to provide an dectalk speech driver. but i dont own an device. speech drivers designed are really simple. so maybe someone with an device can help out here as well. I don't have the python skills but maybe you could emulate a brail display: https://linux.die.net/man/1/qemu-kvm You could have a look at NVDA which is also written in python: https://github.com/nvaccess -- John Doe
Re: Fenrir 1.9.2 Released
Howdy John, For my initial work i created an debug braille driver what just prints the showhn text to stdout. I will take a look at your link. The initial brltty driver works i tested it with storm dragon. He had a braille device. But its verry unpractical to not be able to verify your own code after doing some changes :). With the debug driver i will not be able to emulate braille input. But fenrir is able by design to bind commands to any shortcut also to keyboard what may help as well :). I will fore sure do what i can ;). But help is very welcome to make a perfect job to wire up an best possible result to all :). But foor example devins attribute stuff ; i dont know what attributes have an braille eqvivalent and how they look like. Do they depend on the used braille table? (Just an example of many questions i have) Thanks for your links i will investigate. Cheers chrys Zitat von john doe : On 7/17/2018 7:01 PM, chrys wrote: Howdy Devin, sure thing as soon as i figure how lol. i dont own an braille device so i just can do most of that stuff "blind" lol. for stuff like that it would be really awesome to have someone with python dev skills and braille device on my side :). i m not blind so maybe i m not the best person to say how it needs to be done that it is perfect. i already started the implementation and basic stuff should be doable but its not production ready yet. thats why the default braille driver is currently dummy lol. but basic brltty usage is already implemented and also some needed bits to show up some text on the braille device and flush it. panning should be in place as well. but all untested lol. i will add your request to the list. here the outstanding todos if someone wants to dive in and help out :). Braille Support: [] brailleFocusMode: [] manual = no automatic toggle, command used (text cursor, review cursor, attribute cursor) [] last = follow last used cursor (text cursor, review cursor, attribute cursor) [] print cursor in review [] print cursor in textmode / attribute tracking [] word wrapping (if word does not fit print it at next page) [] command toggle used cursor (in manual brailleFocusMode) [] capture input from braile [] make routing keys assignable by keyboard [] make brailleTable configurable [] tuning for the commands, what should be pinned, what should be flushed, what not shown at all. JFYI same for dectalk :). i want to provide an dectalk speech driver. but i dont own an device. speech drivers designed are really simple. so maybe someone with an device can help out here as well. I don't have the python skills but maybe you could emulate a brail display: https://linux.die.net/man/1/qemu-kvm You could have a look at NVDA which is also written in python: https://github.com/nvaccess -- John Doe
Re: Fenrir 1.9.2 Released
Howdy Devin, sure thing as soon as i figure how lol. i dont own an braille device so i just can do most of that stuff "blind" lol. for stuff like that it would be really awesome to have someone with python dev skills and braille device on my side :). i m not blind so maybe i m not the best person to say how it needs to be done that it is perfect. i already started the implementation and basic stuff should be doable but its not production ready yet. thats why the default braille driver is currently dummy lol. but basic brltty usage is already implemented and also some needed bits to show up some text on the braille device and flush it. panning should be in place as well. but all untested lol. i will add your request to the list. here the outstanding todos if someone wants to dive in and help out :). Braille Support: [] brailleFocusMode: [] manual = no automatic toggle, command used (text cursor, review cursor, attribute cursor) [] last = follow last used cursor (text cursor, review cursor, attribute cursor) [] print cursor in review [] print cursor in textmode / attribute tracking [] word wrapping (if word does not fit print it at next page) [] command toggle used cursor (in manual brailleFocusMode) [] capture input from braile [] make routing keys assignable by keyboard [] make brailleTable configurable [] tuning for the commands, what should be pinned, what should be flushed, what not shown at all. JFYI same for dectalk :). i want to provide an dectalk speech driver. but i dont own an device. speech drivers designed are really simple. so maybe someone with an device can help out here as well. cheers chrys Am 17.07.2018 um 15:57 schrieb Devin Prater: Thanks for considering Braille support. If poss,bl, please send attributes of characters or words, if they have a braille equivalent, to the braille display. -- Sent from Gmail Mobile
Re: pulseaudio and espeakup
Howdy, maybe this is the same issue i had with fenrir. fenrir outputs its sound to a pulse instance as root and orca fires the sound via the pulse instance of the user. i wired up a small setup script that configures the root pulseaudio instance to stream its sound to the user instance. so both can talk at same time without locking a hardware. https://github.com/chrys87/fenrir/blob/master/tools/configure_pulse.sh it needs to be run once as user and once as root to configure both parts. then a restart is requred to bring all pulse intances on pair with the new config. maybe this helps in anyway cheers chrys Zitat von Samuel Thibault : Michael A Ray, le ven. 04 mai 2018 13:18:08 +0100, a ecrit: Perhaps a way to try is to run speech-dispatcher in TCP socket mode in a docker container. Well, I don't think a container is needed, you can just run speech-dispatcher as a system service. And the problem is not there, but rather: how will it be able to access the sound card? Unless it is running as the same user as other pulseaudio sources, there will be a conflict on the grabbing of the card. But one problem I anticipate is the way to persuade Orca that SD is there and does not need to be launched by it. That is already handled by speech-dispatcher when configure appropriately. Samuel
Fenrir 1.9.2 Released
Howdy List, Like already told i want to release more often to bring the lastest stuff more fast to you. i want to announce fenrir 1.9.2 quite small change in number but a lot of new cool stuff :). I will use github tracker to handle my todo list and bugs now :). so feel free to use it ;). https://github.com/chrys87/fenrir/issues Changes: Important Note: systemd file is now not shipped by setup.py anymore and needs to be brought in place manualy. this is an ongoing work to make the setup.py more plattform independ (BSD, VoidLinux doesnt use systemd) the startup files (systemd, runit) could be found here: https://github.com/chrys87/fenrir/tree/master/autostart Overall: - import X clipboard into fenrir using xclip - imporove accuracy of speak history (arrow up/ down in bash/ irssi/ tintin and all others) - numlock/ capslock/ rolllock does not run out of sync with its announcements now. the smaller code should also gain a performance boost. - variouse speedups and bugfixes New Barrier Mode - add barrier mode - respect pseudo CLI window borders like used in many CLI applications to not speak overlapping pseudo windows (i. e. pdmenu, mc, dialog or finch) - toggle for barrier mode - soundicon for barrier mode when enter and leave the barrier detection Attribute Handling: - lot higher accuracy for hilight tracking - soundicon for "has attribute". it bells a sound now when the current attributes are different from default and previous attributes while cursoring/ review arround by char - toggle for the has attribtue soundicon - unify code for attribute handling "attributeManager" - overall improved attribute code PTY - Terminal emulation: - multitap shortcuts (press a key multible timse fast to fire a different command) - lot of fixes - speedup work (more to come, want to split out all this into an own process using the processManager) this brings the PTY emulation on pair with VCSA screen driver i18n: - portuguese language added (thanks to F123 and frinds!) Whats next - forcast? I have currently 5 big tasks on my todo list: - table review mode (speak headline and cell content to have an better idea of output of ps and stuff example: "PID:12345 command:/bin/bash" insteed of word or line review "PID, command, 12345, /bin/bash") - settings/ confgiuration "dialog" to configure fenrir on runtime - braille support (partial done) - advanced say all functionality (read a man or stuff like that until no next page exist, place review cursor on current spoken word) - improved installation if anyone is interested in dive in or has preferences what he/she wants to see in next release, let me know. if not, i would start with table review mode. cheers chrys and F123 Team
Re: Fenrir 1.9 released
Howdy, thanks for reporting that. I updated the links. cheers chrys Am 10.06.2018 um 20:35 schrieb Paul Gevers: Hi Chrys, Thanks for notifying us. I see we don't have a watch file in the fenrir package so we don't notice these changes. On 08-06-18 00:48, chrys wrote: i write you to notify that i just released an new fenrir release: https://github.com/chrys87/fenrir/releases/tag/1.9 Maybe you want to update the version also on what we consider the homepage of the package: https://linux-a11y.org/index.php?page=fenrir-screenreader? It now points to 1.5.1. Paul
Re: Fenrir 1.9 released (fwd)
Howdy, this is very debian specific now. since this is not related to fenrir but install an software via pip at all. i add the diabian list here. cheers chrys. Am 10.06.2018 um 01:54 schrieb Linux for blind general discussion: Well Chrys, I thought your suggestion would work, but what I got was Traceback (most recent call last): File "/usr/local/bin/pip3", line 7, in from pip._internal import main ModuleNotFoundError: No module named 'pip._internal' Chime ___ Blinux-list mailing list blinux-l...@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Fenrir 1.9 released
Hi Samuel, Hi List i write you to notify that i just released an new fenrir release: https://github.com/chrys87/fenrir/releases/tag/1.9 there is a new dependencies: pyte (python-pyte) needed for terminal emulation using "fenrir -e" make fenrir run in an gnome-terminal or mate-terminal xclip for share fenrir clipboard with X Optional (experimental, not recommented) pyttsx3(python-pyttsx3) for an new experimental optional driver backend for speech releast notes # We are pleased to announce the immediate availability of Fenrir 1.9! You can download it from [the github page](https://github.com/chrys87/fenrir). ## What is it? Fenrir is a console screen reader written in python3. It is in user space, so does not have to be compiled into the kernel like other options such as acscynth or speakup. Features include speech and sound icon output with braille support coming soon. Copy and paste with clipboards with definable history, currently 10. Desktop, laptop, and PTY keyboard layouts that are easy to learn and use. Learn mode, spellcheck with definable dictionaries, and definable windows for applications. Version 1.9 is recommended for use in production invironments, however, if you would like to help test and/or develop Fenrir, you may wish to install the latest version from git. Fenrir is released under the LGPL license, so it will remain open source and free, but you may use it for closed source work invironments. For more information, and to find out more about accessibility solutions for Linux, check out http://linux-a11y.org We are also available on irc at irc.netwirc.tk in room #a11y the manual is installed locally as a man page or available on [Fenrir's home page](http://linux-a11y.org/index.php?page=fenrir-screenreader) ## What's New * much higher accuracy * better handling for threads/ processes * lot of bugfixes * german translation * performance enhancements (it runs quite nicely on the raspberry Pi) * The ability to paste to the X clipboard (requires xclip) * The generic speech driver is the default. * initial Highlight tracking mode (work in progress) * Sound alert if you remove or add a keyboard * Copy last utterance to clipboard * Improved Headline Seperator and Multiple Character Support * Toggle automatic speaking of indentation level * PTY Screen driver (to use xterm and other terminal emulators)
Re: xclip problem
Howdy, sorry maybe its not that helpful that it should but: fenrir (sadly i canot say anything about speakup :/) solves the issue by providing an: export clipboard to file -> does not need and display but creats an special file in /tmp for sharing command. no X is needed for this. it also have an command (using xclip) to place throw the current fenrir clipboard in X (display is here needed as well) cheers chrys Am 20.12.2017 um 18:04 schrieb Jude DaShiell: When I use xclip it's with speakup running not orca so no display exists. Unfortunately xclip cannot handle a run without a display being set. I tried copying a link in speakup with xclip so I could run it in firefox with orca and link my computer to my dropbox account but that's not possible. Any other approaches to this where I could get a display set or find a better utility than xclip to get this done? --
Re: xclip problem
howdy, ah sorry maybe i misunderstand you. fenrir solfes the "search display" problem by bruteforcing displays from 0 to 10 for sure this does not help you but just to complete my last message. cheers chrys Am 21.12.2017 um 01:50 schrieb Jude DaShiell: I've given up on xclip. I tried exporting that DISPLAY value and others and each time that crashed dropboxd when I tried running it in /home/jude/.dropbox-dist/ as a test to be sure the display was found. The closest I ever got to a dropbox login without copying that url and running it from a javascript-enabled browser was after I installed dropbox and ran itfrom applications internet dropbox and that login didn't work either. Apparently that crashes orca sometimes but one time I did a run I found circles in the email and password fields for logging onto the site. Lots of ajax on that page too. I'm going to start trying things with the dropbox clones since this is going nowhere and with one of those clones I may be able to link my google drive account and if that happens I can do without dropbox it is too much trouble just doing the basic things! On Wed, 20 Dec 2017, Jude DaShiell wrote: Date: Wed, 20 Dec 2017 17:57:40 From: Jude DaShiell <jdash...@panix.com> To: debian-accessibility@lists.debian.org Subject: re: xclip problem Resent-Date: Wed, 20 Dec 2017 22:57:58 + (UTC) Resent-From: debian-accessibility@lists.debian.org In order to find my DISPLAY I started up x, then ran mate-terminal and typed echo $DISPLAY >dn.txt. Then I powered down and started up in console mode and found :0.0 in dn.txt. If I didn't do this right, I'll know shortly. --
Fwd: [fenrir-screenreader] Re: Which key is the fenrir key on a laptop layout?
Howdy, i recognized that on debians fenrir package "python-evdev" is missing as dependency. Maybe someone with .deb skills is able to fix that :). cheers chrys Weitergeleitete Nachricht Betreff: [fenrir-screenreader] Re: Which key is the fenrir key on a laptop layout? Datum: Thu, 9 Nov 2017 02:55:23 + Von:ch...@linux-a11y.org Antwort an: fenrir-screenrea...@freelists.org An: fenrir-screenrea...@freelists.org Howdy, Its me again, Additional : Take care that you need the oython3 version not the python2 version of python-evdev. That means drpending on your system it could named python3-evdev insteed of python-evdev. This depends on the defailt of your used distro Cheers Chrys Am Donnerstag 9. November 2017 schrieb chrys: Howdy my frind, fenrir supports "multible fenrir keys" by default it is the following (configurable in /etc/fenrir/settings/settings.conf) are the fenrir keys fenrirKeys=KEY_KP0,KEY_META,KEY_INSERT what means: keypad 0, super or insert (all of them are recogniced as fenrir keys) take care that you need python-evdev need installed (what is currently on debian systems missing as dependency) here you need to install it manual currently ( i will report this to the debian a11y team) for debian you can install it with sudo apt-get intall python-evdev evdev is the linux "event device" system. this is needed by fenrir to capture and consume input events. python-evdev are the bindings for python (in what fenrir is written) to this event device system. the minimum version is python-evdev 0.6.4. what distro are you using, how do you installed it? fenrir needs python >= 3.3 with that installed you can install it via pip on any distro with (python packager) with: sudo install fenrir-screenreader this will install everyting for dependecies. cheers chrys what means keypad 0, windows key and insert key, all of that Am 09.11.2017 um 03:11 schrieb Doug Smith: > Ok, here goes the first message on this list. I am trying to put fenrir on my girlfriend's laptop, but cannot get it to > respond to any kind of input. The problem is that I am not sure which key is the fenrir key if I set the keyboard > layout to laptop. > > I cannot access the linux accessibility community on here because of a firewall they have on this in-house network and > they really went too far with it. If I can find out which key this is I can get fenrir on my girlfriend's laptop and > get it fixed up for her. > > > > Thanks. > > > > Website: https://linux-a11y.org Wiki: https://wiki.linux-a11y.org/doku.php?id=fenrir Code: https://github.com/chrys87/fenrir IRC Live Support: Network: irc.linux-a11y.org Room: #a11y Yæìס¶ÚlÿùbìZ×\¨®¢(m¶?ÿ¤X§»µ×*+÷hêa¦'}éë°¨uèm¶?þæÜ¢oܼ¬ó¿ßzzâ¬B.+ÞJêi¢»MzÜ(®H«rX§»µ×*+(uy===
New Email List for the Fenrir Screenreader
Howdy y'all, There's now a new email list for Fenrir support. For info, and to subscribe, please visit: https://www.freelists.org/list/fenrir-screenreader E-Mail: fenrir-screenrea...@freelists.org cheers chrys
Re: It is impossible to read the terminal when installing in Russian
Ah sry maybe i mixed unicode and UTF8 then. Anyway. If some can test this with fenrir let me know Cheers Chrys Am Mittwoch 1. November 2017 schrieb Samuel Thibault: > Hello, > > ch...@linux-a11y.org, on mer. 01 nov. 2017 15:21:49 +, wrote: > > since the kernel itself does not support unicode. > > The kernel does support unicode. Only speakup doesn't yet. > > Samuel > >
Re: It is impossible to read the terminal when installing in Russian (fwd)
Howdy, What problem installing fenrir do you have currently ? sudo pip3 install fenrir-screenreader Does the trick verry simple here. Its also packed for debian testing and archlinux. How can i improve the situation for you? (or for anyone else here?) Cheers Chrys Am Mittwoch 1. November 2017 schrieb Jude DaShiell: > would an install using fenrir work better now or will it work better in > future? > > > -- > > > -- Forwarded message -- > Date: Wed, 1 Nov 2017 09:40:05 > From: Samuel Thibault <sthiba...@debian.org> > To: ? ??? <aarnaa...@gmail.com> > Cc: debian-accessibility@lists.debian.org > Subject: Re: It is impossible to read the terminal when installing in Russian > Resent-Date: Wed, 1 Nov 2017 13:40:24 + (UTC) > Resent-From: debian-accessibility@lists.debian.org > > Hello, > > ? ???, on mer. 01 nov. 2017 14:21:49 +0300, wrote: > > I install debean 9 in text mode. when i choice Russian language espeak > > switched > > to Russian, but read very strange. > > speakup doesn't support unicode in general yet, unfortunately. > > Samuel > >
Re: fenrir-screenreader installation with pip3
Howdy, Seems that the configure script of python-dbus can not detect your intallation, nor setuptools recognice that you already have the bindings installed. Very strange... what happens if you try to import dbus in pyhton? 1 open python by typing "python" into an shell. 2 import dbus by typing "import dbus" into python does an error appear or is it done without any output (success). not sure why your configuration cannot found properly here. If the import works, you can try installing fenrir via the "install.sh" script manually. its not the recommented way because it will not be able to update, nor install the dependencys but it may also work. in that case any dependency must installed manually. cheers chrys Am 29.10.2017 um 01:53 schrieb Doug Smith: Ok, here is a strange one. I have, over the past couple of days been trying to get fenrir to install on this kali system. This is all I need to have a talking command line terminal interface. I have tried pip3 install fenrir-screenreader just as I should have. I have attached the resulting typescript file for the attempted installation. Dbus is installed and there seem to be about 3 instances of it running. I did not kill off any of them because I know nothing as yet about dbus. I even have the python-dbus and the python3-dbus packages installed so the situation I am mentioning is absolutely impossible. If I am doing something wrong I would like to know what it is so that I can fix it and complete the installation and configuration of my system. As you can see in the attached typescript file, some of the things the configure script checks for seem to be missing along with the existing dbus. I don't know what these are and what extra packages I need to install. I have also upgraded the setuptools which are included with the interpreter thinking this might have something to do with it. I have looked on line and have found nothing about this problem. I am sending the typescript file along so that someone might be able to help me find out what else needs to be installed. I hope to get this resolved soon and get fenrir up and talking so that I can easily have a command line screen reader. Thanks for the help.
Re: When will a working version of fenrir screen reader come back to testing?
Howdy, whoops i forgott something to say: first of all you need to install: - sox (for soundicons) - speech-dispatcher (for speech) - python-speechd (for speech) with your packagemaager. it should look like this sudo apt-get install sox speech-dispatcher python-speechd cheers chrys Zitat von ch...@linux-a11y.org: Howdy Doug, if fenrir 1.5 is not available in your distribution you can install it via pip3. i uploaded it to the pypi repository. # 1. install it via pip3 sudo pip3 install fenrir-screenreader # 2. if you have pulse running you need to configure it (run it once for root, and once as your user to configure pulse). you dont need this su -c "/usr/share/fenrir/tools/configure_pulse.sh" /usr/share/fenrir/tools/configure_pulse.sh # 3. if you want to use speech-dispatcher this needs a settings profile for user root. su -c "spd-conf" # just hit enter for all the questions, but for output module select alsa or pulse (whatever you use). # otherwhise speech-dispatcher is not able to start. maybe restart to update the settings for all the pulse instances. sudo systemctl start fenrir done.. you find the settings in /etc/fenrir/settings/settings.conf where you can configure the speech engine and a lot of other stuff. fenrir currently supports 3 different speech methods: - speech-dispatcher "speechdDriver" (default) - espeak "espeakDriver" (via python-espeak) - generic "genericDriver" (via calling an subprocess) as long the wiki is down for maintaince (i will bring it back in the next 24 hours) fenrir offers an manpage version of the wiki: man fenrir for any other assistance feel free to join us on IRC: network:irc.linux-a11y.org room:#a11y cheers chrys Zitat von Doug Smith <romans1...@minister.com>: Ok, here is a good one. I wonder when fenrir screen reader will bemaking a comeback appearance in testing. I have found it impossible to get speakup activated again once the module speakup_soft.ko was moved back to staging. I am using kali linux which is a debian derivative and it is based on testing. I would like to get my command line side of things talking again as soon as possible, but I cannot get anything other than silence out of speakup since kali 2017.2, and it is really frustrating. If it is possible to get speakup talking again, I will take that as I am more familiar with speakup than fenrir. Thanks. -- Romans 10 9 That if thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved.
Re: When will a working version of fenrir screen reader come back to testing?
Howdy Doug, if fenrir 1.5 is not available in your distribution you can install it via pip3. i uploaded it to the pypi repository. # 1. install it via pip3 sudo pip3 install fenrir-screenreader # 2. if you have pulse running you need to configure it (run it once for root, and once as your user to configure pulse). you dont need this su -c "/usr/share/fenrir/tools/configure_pulse.sh" /usr/share/fenrir/tools/configure_pulse.sh # 3. if you want to use speech-dispatcher this needs a settings profile for user root. su -c "spd-conf" # just hit enter for all the questions, but for output module select alsa or pulse (whatever you use). # otherwhise speech-dispatcher is not able to start. maybe restart to update the settings for all the pulse instances. sudo systemctl start fenrir done.. you find the settings in /etc/fenrir/settings/settings.conf where you can configure the speech engine and a lot of other stuff. fenrir currently supports 3 different speech methods: - speech-dispatcher "speechdDriver" (default) - espeak "espeakDriver" (via python-espeak) - generic "genericDriver" (via calling an subprocess) as long the wiki is down for maintaince (i will bring it back in the next 24 hours) fenrir offers an manpage version of the wiki: man fenrir for any other assistance feel free to join us on IRC: network:irc.linux-a11y.org room:#a11y cheers chrys Zitat von Doug Smith <romans1...@minister.com>: Ok, here is a good one. I wonder when fenrir screen reader will be making a comeback appearance in testing. I have found it impossible to get speakup activated again once the module speakup_soft.ko was moved back to staging. I am using kali linux which is a debian derivative and it is based on testing. I would like to get my command line side of things talking again as soon as possible, but I cannot get anything other than silence out of speakup since kali 2017.2, and it is really frustrating. If it is possible to get speakup talking again, I will take that as I am more familiar with speakup than fenrir. Thanks. -- Romans 10 9 That if thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved.
Re: Debian accessibility news
Howdy, you can find information on http://linux-a11y.org/ and https://wiki.linux-a11y.org/ SOPS: https://github.com/chrys87/simple-orca-plugin-system/releases/tag/1.01 Plugins installed by default: - read clipboard - read current workspace number - Plugin manager other available plugins: - audiogame_launcher.sh (by storm) - translate_clipboard.py (translate the clipboard into any language -> using translate-shell) - weather.sh (tell the weather info using weather CLI) - toggle-debug.py (toggle debug on/off at run-time) - acpi.sh (announce battery) - removePageLoadMessage.py (removes some unwanted messages for some people while browsing) - battery.py (battery and loading announcement) - wlan.sh (read wifi information, name, signal) - getVolume-pulse.sh and getVolume-alsa.sh (say volume in percent) - toggle-keyboard-layout.py (switch between laptop and desktop layout, maybe you plug an keyboard on your laptop and want to toggle it then) - orca-version.sh (simply announce the current orca version) - yahoo_weather.sh (say weather info using yahoo website) and its really easy to extend since any shell script could be used to announce information. but its also powerful because you can write code to manipulate orca itself (only python) some of the plugins may need some manual changes (like language in translation or zip code for weather) but the needed changes are really easy. OCRdesktop: https://github.com/chrys87/ocrdesktop/releases/tag/1.01 OCRPDF: https://github.com/chrys87/ocrpdf/releases/tag/0.5 >>Is this the same as or similar to ocrmypdf? yea its something similar but it its thought to integrate it into the right click menu of an file browser. it will bring up a gui with the result imediately Fenrir (i will release version 1.5 next week with a _lot_ of fixes and enhancements to version 1.06, so i just post the master here and i already have some awesome stuff in pipeline for 2.0) https://github.com/chrys87/fenrir for people that dont want to have the awsome SOPS i also have a stand alone version of the "read clipboard" code for an orca-customizations.py here: https://github.com/chrys87/orca-clipboard-cust/blob/master/orca-customizations.py (it can read the text, number of objects (files, links and so on) or image data (similar to the SOPS version). cheers chrys Am 25.08.2017 um 14:10 schrieb Paul Gevers: Hi, Thanks for letting us know. On 08/25/17 13:32,ch...@linux-a11y.org wrote: - OCRdesktop (useful reading pictures or interact with non accessible software) https://wiki.linux-a11y.org/doku.php?id=ocrdesktop And indeed already mentioned on the TODO list: https://wiki.debian.org/accessibility-devel#TODO_Packaging - SOPS (Simple Orca Plugin System, provides stuff like read clipboard to orca) https://wiki.linux-a11y.org/doku.php?id=simple_orca_plugin_system Not mentioned yet. - OCRPDF (just a small read that damn scanned PDF viewer) Is this the same as or similar to ocrmypdf? https://tracker.debian.org/pkg/ocrmypdf - fenrir (still a early bird but useable for most cases if you manage the installation lol) https://wiki.linux-a11y.org/doku.php?id=fenrir_user_manual Already in Debian (testing and unstable) https://tracker.debian.org/pkg/fenrir Paul
Re: Debian accessibility news
Howdy, i dont want to start a rant lol but: for ArchLinux this is not totaly correct. There is Talkingarch as useable installation medium (its not an fully customized distro but just an accessible installation medium that could been used to create an accessible operationg system setup). Maybe its an good to know some of my software or add it to the repo (some people find that stuff very helpful): - OCRdesktop (useful reading pictures or interact with non accessible software) https://wiki.linux-a11y.org/doku.php?id=ocrdesktop - SOPS (Simple Orca Plugin System, provides stuff like read clipboard to orca) https://wiki.linux-a11y.org/doku.php?id=simple_orca_plugin_system - OCRPDF (just a small read that damn scanned PDF viewer) - fenrir (still a early bird but useable for most cases if you manage the installation lol) https://wiki.linux-a11y.org/doku.php?id=fenrir_user_manual more stuff is comming ;) cheers chrys Zitat von MENGUAL Jean-Philippe <mengualjean...@free.fr>: Morally speaking, Debian is simply the most accessible distro today. So it is an example in itself. And it is the only distro where in decisionsal processes, accessibility is considered as a matter (eg choice of desktop environment). Ubuntu stopped specific devs in accessibility, Fedora is not really accessible at install, using a non-universal desktop; Manjaro does not seem to do accessibility, neither arch. It is so right that some devs decided using specialized distros such as Vinux. So I think Debian does its role in free software. Le 24/08/2017 à 23:01, Samuel Wales a écrit : moral leadership can be powerful all by itself. On 8/24/17, Samuel Thibault <sthiba...@debian.org> wrote: Samuel Wales, on jeu. 24 août 2017 13:46:35 -0700, wrote: practically everything in debian is an upstream issue, except e.g. pm, installer, repo, right? Yes. actually no -- policy is a debian issue. :) i'd like debian to be a sort of moral leader if nothing else. debian articulates a goal. i'd like accessibility to be part of that. Yes, but only for what Debian is supposed to act on. It's not supposed to modif software. Patching over issues is fine enough, provided that the patches are also sent upstream. But whole features of upstream software are not supposed to be developped within Debian. Samuel -- signature_jp_2 Logo Hypra JEAN-PHILIPPE MENGUAL DIRECTEUR TECHNIQUE ET QUALITÉ 102, rue des poissonniers, 75018, Paris Tel : +331 84 73 06 61 <tel:+33184730661> Mob : +336 76 34 93 37 <tel:+33676349337> jpmeng...@hypra.fr <mailto:jpmeng...@hypra.fr> www.hypra.fr <http://www.hypra.fr/> Facebook Hypra <https://www.facebook.com/hyprasoftware/> Twitter Hypra <https://twitter.com/Hypra_> Linkedin Jean-Philippe <https://fr.linkedin.com/in/jean-philippe-mengual-800133135>
