http://blog.gmane.org/gmane.comp.kde.devel.accessibility hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2337 <pre>Thanks for the reply Jeremy. Sorry for the delay in replying, your explanation has clarified my confusion. It's really too bad that we can't make all these things work co-hesively. Maybe some day, but that doesn't help people like me today. Bob Stia </pre> Bob Stia 2013-05-16T20:54:56 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2336 <pre>Bob, The Qt app you are referring to is KMag? at any rate, any screen reader (Orca, some kde based equivalent) uses at-spi2-atk to get accessible names and descriptions for gtk based applications. Orca (which uses gtk) also uses that to get accessible names and descriptions from Qt based applications if they are exposed by QT_ACCESSIBILITY being set in your environment. at-spi2-atk is not an application itself, but a library that other applications use, so installing it, or upgrading it to the latest released version on your system isn't likely to change how KMag or festival/espeak, etc. work. It may make orca work better for your case if you are using orca, but it shouldn't affect KMag or festival or espeak since they don't use that library. I hope that helps clarify things a bit. BR, Jeremy On Mon, May 13, 2013 at 1:20 PM, Bob Stia &lt;rnr&lt; at &gt;pasco.org&gt; wrote: _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Jeremy Whiting 2013-05-13T21:09:16 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2335 <pre>some GTK applications like Firefox and Thunderbird. My question is could I install At-spi2-atk 2.8.1 in my system to use the screen reader on Firefox and Thunderbird, or would the QT app accomplish the same result. Bob Stia _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Bob Stia 2013-05-13T19:20:29 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2334 <pre>Hi Bob, at-spi2-atk is the communication bridge between an application that implements ATK (an accessibility framework) and an accessibility tool, like an screen reader. For example, GTK implements ATK, so thanks to at-spi2-atk, any application written in GTK, like Gedit, is accessible through Orca, an screen reader. So, if you want your ATK-compliant to be accessible, you need that module. Having said so, take into account that KDE doesn't implement ATK. They have their own accessibility framework, and there are an equivalent bridge, called at-spi2-qt. Thanks to it, the accessibility support of several qt apps are improving, and are being possible to be accessed by Orca. So if you want to use Qt applications with Orca screen reader, you would need that module. I hope have been clear enough Best regards On 2013-05-12 19:28, Bob Stia wrote: </pre> Piñeiro 2013-05-13T16:12:25 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2333 <pre>barely read the screen or my keyboard. My wife is typing this for me. I use open suse 11.3 and 12.1 with KDE3 and 12.2 with KDE4. I much prefer KDE3. I use festival and espeak for TTS and Kmag. But each of these has limited use. I saw this announcement back in April and am trying to figure out what it is. I understand that it is a D-Bus application, but I don't understand what it does to help my accessibility. Is it a user or developer application? I visited the download site and saw that it is a Gnome application. I also visited the WIKI site and it appears to be for developers. My question is can I, as a user, download and use this application, to better enable me in the use of my computor. I would also like to know how it will aid me specifically. Bob Stia </pre> Bob Stia 2013-05-12T18:28:04 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2332 <pre> Hi, My name is George, and I am legally blind. I have what is known as macular degeneration. My central vision is gone, and I depend on my peripheral vision and the windows XP magnifier to do computer tasks. I find that a "Desktop Magnifier" DOES NOT work. I tried KMag, but it lacks some attributes that would help people afflicted with macular degeneration. This brings me to why I contacted you. Can the KMag utility be configured to work similar to the windows XP magnifier? That is : 1) Always on top, with one difference: It would reduce the bounds of the Desktop area available for applications. This way, other running applications would be forced to resize to fit below the magnifier viewing area. 2) The controls and the magnified viewing area would be separate. The settings menu could be placed on a panel app on the taskbar or System Tray. This would ensure the best use of the viewable area. I hope you have a solution to this problem, and would like to hear your thoughts on this matter as soon as possible. Thank you. George Isaksen George.isaksen&lt; at &gt;verizon.net ---_______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> George Isaksen 2013-04-30T21:17:46 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2331 <pre>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CALL FOR PAPERS Workshop on Rethinking Universal Accessibility: A broader approach considering the digital gap http://sipt07.si.ehu.es/WS/RethinkingUA/ Cape Town, South Africa, 2 Sep 2013 In conjunction with INTERACT 2013, 2-6 Sep 2013 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Submission deadline: 20 May 2013 Submission types: - position papers (four pages) - regular papers (eight pages) Papers should be submitted via EasyChair at: https://www.easychair.org/conferences/?conf=wsrua2013 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BACKGROUND Universal Accessibility aims at including all people with disabilities in the target population for user-centered design. It is usually focused on the needs of people with disabilities, frequently including elderly people. Current advancements in the Design for all concept may require complex equipment, advanced network environments, or computer training. Therefore, these products or services may fall out the access of many people with disabilities because economical, technological or formative restric-tions. This is a frequent situation in developing countries, but it is becoming common also in developed countries where poverty and emigration are frequently associated with barriers to access to assistive technologies and services. This Workshop aims at rethinking the concept of Universal Accessibility in order to find ways to include all excluded people with disabilities. It is organized on behalf of the IFIP WG 13.3 HCI and Disability for HCI for academics, designers, managers, etc., interested in creating methodologies, tools and products for a wider market, considering ethic and social requirements. Thus, the main objective of this workshop is to discuss the possibility of broadening the Universal Accessibility concept to include geopolitical and socio-economical circumstances. Experiences in fighting the Digital Gap will especially be welcome. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SUBMISSIONS This one-day workshop is open to researchers and practitioners with experience or interest in Universal Accessiblity. Submissions will be selected based on relevance to the workshop topics, on originality, and on insightfulness. ~~~~~~ Topics: This workshop will focus on theoretical and practical work on the impact of economical, technological, social, political, etc., issues in universal accessibility. Real experiences in fighting info-exclusion will be particularly welcome. Authors of submissions should carefully explain how the work and results presented contribute to enhance and broaden the Universal Access concept. - Can the Universal Accessibility concept be extended in order to include people with disabilities also affected by other barriers such as poverty, illiteracy, lack of access to advanced technology, etc.? - Is it possible to create accessibility guidelines that also consider affordable devices, deprecated technology, cultural issues, and illiteracy? - Is it possible to separate the accessibility for people with disabilities to the accessibility of the rest of the population? ~~~~~~~~~~~~~~~~ Submission Types: Two types of contributions are expected: - Position papers (four pages), containing opinions and proposals to be discussed at the workshop - Regular papers (eight pages), presenting results of research activities fighting infoexclusion due to socio-economical or geopolitical reasons, affecting people with disabilities All submissions should follow the LNCS format, whose instructions are available at: http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0 Authors should submit their work via EasyChair, at: https://www.easychair.org/conferences/?conf=wsrua2013 ~~~~~~~~~~~ Publication: Accepted regular papers will be invited to submit an extension to Springer's Universal Access in the Information Society journal for a Special Issue on Rethinking Universal Accessibility. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPORTANT DATES May 20th 2013. Submission deadline May 26th 2013. Notification to authors Jun 1st 2013. Participants registration deadline Jun 26th 2013. Summision of the camera-ready version Sep 2th 2013. Workshop 2014. UAIS Special Issue publication ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ORGANISATION - Julio Abascal, Computer Architecture and Technology Department. University of the Basque Country UPV/EHU, Spain. - Simone D. J. Barbosa, Informatics Department. PUC-Rio, Brazil. - Andrew Dearden, is a Reader in e-SocialAction within the Communication &amp; Computing Research Centre. Sheffield Hallam University, UK. - Anirudha Joshi, Industrial Design Centre, IIT Bombay, India. - Daniel Orwa Ochieng, School of Computing and Informatics in the University of Nairobi, Kenya. - Gerhard Weber, Technische Universität Dresden, Germany. Chair of IFIP WG 13.3 HCI and disabilities. - Panayiotis Zaphiris, Department of Multimedia and Graphic Arts. Cyprus University of Technology. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WEBSITE AND CONTACT Additional and updated information can be found at the workshop website, at: http://sipt07.si.ehu.es/WS/RethinkingUA/ For further information, contact: - Julio Abascal [julio*abascal at ehu*es] or - Simone DJ Barbosa [simone at inf*puc-rio*br] (where asterisk is dot) </pre> Simone DJ Barbosa 2013-04-24T11:21:42 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2330 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/110104/ ----------------------------------------------------------- Review request for KDE Accessibility. Description ------- Add a "Test Bell" button to test the current Bell settings. This addresses bug 164111. http://bugs.kde.org/show_bug.cgi?id=164111 Diffs ----- kcontrol/access/kcmaccess.h 4a7823f kcontrol/access/kcmaccess.cpp c4681d4 Diff: http://git.reviewboard.kde.org/r/110104/diff/ Testing ------- Thanks, Christoph Feck _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Christoph Feck 2013-04-20T15:52:06 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2329 <pre>At-spi2-atk 2.8.1 is now available for download at: http://download.gnome.org/sources/at-spi2-atk/2.8/ What is AT-SPI2 =============== AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus protocol for providing and accessing application accessibility information. The project includes a library for bridging the D-Bus protocol to the ATK API, allowing Gtk based applications to be made accessible. It also contains a client (AT) side library in C and a wrapper for Python. What's changed in at-spi2-atk 2.8.1 * Fix memory leak in socketadaptor.c (BGO#696733) * Fix a crash when handling a D-Bus method reply after deinitialization. Where can I get more information about AT-SPI2 ============================================== The project wiki is available at: http://www.a11y.org/d-bus How can I contribute to AT-SPI2? ================================ We need help testing with Gnome accessibility technologies, improving performance, and generally tying up loose ends. The above-referenced page contains a list of known issues that should be fixed. IRC : #a11y on Gimpnet E-Mail: accessibility-atspi&lt; at &gt;lists.linux-foundation.org Development repositories can be found at: git://git.gnome.org/pyatspi2 git://git.gnome.org/at-spi2-core git://git.gnome.org/at-spi2-atk </pre> Mike Gorse 2013-04-15T18:07:36 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2328 <pre>Hi, On 04/13/2013 11:09 AM, shawn graham wrote: Without further information, there is sadly nothing I can help you with. It's kinda "normal" to develop new packages for the current development release of the distribution. If there is demand, the package can probably easily be backported to earlier versions. I am not aware of any issues with the packages in the PPA. At one point there was a problem with a then recently released Ubuntu versions but they were fixed rather quickly once they were pointed out. Of course, I might have missed something but at least I am certain that there were / are no open reported issues. Best regards Peter </pre> Peter Grasch 2013-04-13T16:35:12 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2327 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/109977/ ----------------------------------------------------------- Review request for KDE Accessibility. Description ------- With reference to bug: https://bugs.kde.org/show_bug.cgi?id=145877 This is a patch which implements key modifiers to temporarily disable KMouseTools whenever user feel the need to do so. Users had filed the bug stating that KMouseTool does make them uncomfortable when they are browsing on net etc due to automated clicks. This patch provides a drop down menu to select a particular key out of 5 options, after which user can just hold that key to temporarily disable the automated mouse click. Diffs ----- kmousetool/kmousetool.h 245d3ef kmousetool/kmousetool.cpp ead190e kmousetool/kmousetoolui.ui e0e2ec3 kmousetool/main.cpp aa3a264 kmousetool/mtstroke.h f8a7563 kmousetool/mtstroke.cpp ad899f2 Diff: http://git.reviewboard.kde.org/r/109977/diff/ Testing ------- Yes Thanks, Akshay Ratan _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Akshay Ratan 2013-04-12T15:22:56 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2326 <pre>Hi, On 04/12/2013 07:30 AM, shawn graham wrote: Very impressive. Please contact me if you need some help with this, Thanks for your interest in Simon. I think a Simon package for Ubuntu is already available for the &gt;= Raring, but I haven't tested it yet. You can find it here: https://launchpad.net/ubuntu/+source/simon/0.4.0-0ubuntu1 Best regards, Peter </pre> Peter Grasch 2013-04-12T10:34:37 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2325 <pre>Hello My name is Shawn Graham. I am a virtual infrastructure/network engineer and developer (mostly working with virtual environments, vpn and software routers). I have however on several occasions had to package things in the Debian format. I don't remember having allot of complications with the process. Your application is admittedly much more complex than what i was building however i would be more than willing to work up a virtual environment for doing this. I could automate most of this i would think. If im thinking this out correctly i could automate the git download and the dpkg build process and fire that off with a cron job. I have a few friends that have MS and similar diseases. I am trying to build them machines that will allow them to use the computer desktop. Im compiling 0.4 on a Ubuntu 12.04 vm. I'll let you know how it goes. I'm assuming if i can get it to compile i have all the necessary dev packages installed and should be able to package from the same machine. Give me a call or email back if you would like to discuss this more. 209-743-1034 shawnggraham&lt; at &gt;gmail.com Thanks, I hope to hear back from you! _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> shawn graham 2013-04-12T05:30:22 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2324 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 03/30/2013 05:18 PM, Parthasarathy Gopavarapu wrote: Sure (on both questions, btw). In what direction do you want to go, exactly? Let's also continue this conversation on the mailing list, if you don't mind. Best regards, Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRV/uvAAoJEFCPmK2EvjqqSKsP/R8uMgHZ4T6l62MjEChjRldD VEySpCL6UnbIKel0uYMVmuBE2+RcRlGln7onosWQ6mMyuUUWIFQHh16EN4xXUAee imNmCEpaMMQ6j4F1o3nsg1uKpSRkgAi2owPQ7ZnkHYHfGLzZsQI5r/9LKI+ESR2y Cz6/ljj+WZwaEKyjrd4H9V43j6DM7gsLPtdAY8Czjfh8f+ETpUPrhCBAjQN4dAMv piXo2iB83l6cBsNIO9qqYB80dwbC3HWUIiQQYotZFqRoF0jsEliujQeNXDE9BvvL XEB4s+apHZY6JDQQ5UYId15IbdxHxisfraIcjy207sTHUuLKKRt+D+DsDmfY9Ozb 95paouLJhhXWHjieol+4cg6K1mra4ykZyRnsHSe+sRDzFw0yXrL+WHocSxq7CPBY 8VQ8OoFCNunQV8nxn6FT0TH1sVS6Q9xoN3XT6wDnejc+TW+aZlZp516VzgbIw7BS 6A7ULh9euUit5q1g3f+vExJK7mG7jJtxZ0w0XDywsm6JVvppNxgZzlEnceGh8RGQ AOsMrmDh6iS5O4Q8T7Du67CtbL2moTkeRF3h9omS0X4TCyJK3LhW3gLXfYFw49ns BzlCdz+Yc9G9s1OjQBjfpkz6pJDjMqjfK4vgln2MM2ykqc9bhTIgtgtx+tY0fn4H ge0aOrvOdcLHr4vJ5cxB =lV8i -----END PGP SIGNATURE----- </pre> Peter Grasch 2013-03-31T09:02:39 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2323 <pre>&lt; snip sopme&gt; to make them much more usable like KTTS or JOVIE for sight impaired Hello Peter and thanks for your reply. It is good that you have included Simon into the project. That is a speech-to-text app. Correct? That will be very useful to vision impaired users. But, as you suggested there are other apps that require (polishing), such as KTTS and Jovie. There are two areas for improvements. I run KTTS on openSUSE 11.3 with KDE3 and Festival and openSUSE 12.2 with Jovie and espeak on KDE4. The first area is the voice (kal)which is used. It is horrible with no inflection and sounds like R2D2. It is, I believe an 8bit diphone but I know very little about how the voices are constructed. I do know however, how they sound to the listener. Apple has some very good voices. There are better voices out there for Linux such as, ambrola which is a Belgian app. They are much better than the "kal voice". Much better yet are the Cmu voices (Carnegie Mellon University). They are far superior but very large and take alot of space.That is a small price to pay for visually impaired users especially in these days of huge HDs.The problem is that neither KTTS nor Jovie will use them. there are some how-to's on the internet but seem to appy only to Debian and the like. There is nothing that integrates them into KTTS or Jovie. As far as I can tell it is all command line stuff. Not good for a visualy impaired user. There should be a simple easy way to incorporate better voices into KTTS and Jovie . The second area is there should be universal use in all apps and desktop functions. Presently they are only useful in Konqueror and Kate or copying text to the clipboard, then opening the KTTS manager window and asking to speak the clipboard contents, which is very cumbersome. You should be able to use it for all apps, like Kmail and KPDF, etc.. I hope that my suggestions above will be adopted as a project in the GSoC and thank my wife for typing this long message for me. Bob Stia </pre> Bob Stia 2013-03-25T21:41:48 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2322 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Bob, On 03/25/2013 02:20 AM, Bob Stia wrote: I have already added a project idea for Simon, which is part of kde-accessibility. But you're right, there appear to be very few accessibility related projects this year. I suspect, it's mostly a matter of (the few) mentors having too little time. But if you have ideas that you would like to talk about, please do it here, on the mailing list. It's always good to hear from the target user group and you might even coax someone into mentoring! Best regards, Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRUDGOAAoJEFCPmK2EvjqqhfcP/jb7uUC0UUmkZImvR+l5/rq4 ghinUqU1tmTy2FtErVtRdep8GYbPBNwaSIivy+LOGHVnjFljypeTnZW9j6Utptm+ LAu5z8lp6PmgD87wFhSwoOZ75pEGZ8wAEBiD4dhz8xzn6bXKmAQV4Ga6NvMZsa6W Ln9fMliVSWOwUTOAk0xHdBUzPzmNDC9nYueG8MBUKSvRNgpTd8aYoMu/YPKmIfYi XzDeM/9M8JF/Ai6aUdgLioL+9edoJ8Svk1eaVyfXtaEM3MOv0T5h7Q6fruOcvCI0 GAjRp6hlhIXTtNt+5LoBk/KT2c4HUBSSIqIgjOjjl2g00NUK+dO1ce0zhC5brknm WWSWUQFBH2J4QkfHXqzq4Arm1k5yxqhZmTDN2UJwEXbOI8kONxOYH1jiuhPJ06PV boqoXWh2vik3i8CKQHqMt7VHBy6DsebNK9AZg2HvEtGFOKBcjRKOdQ47TpxtuJzD c8yA19CgN5l6Aa7ljrPVAFpXJpfnjvKsxsTP1dw5S7laIN9iemGZLvx2DylmM6xC h4qUr3uyQ/56PoGKLa3r4lfLeP/wzIlqHJEnFheuaEWbkFzdHb5fttG5ScQxmttr 0qVjoLOkHqtoYxPNd/Ng8+YvfkP3jj5TBGCAaA5IOebZmh0x7tN3jaPQ9Lg9ajGE 1KM+egjKtSHBMCdkB5nH =bKen -----END PGP SIGNATURE----- </pre> Peter Grasch 2013-03-25T11:14:22 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2321 <pre>Hello Lydia It;s good that youu havr posted to remind people and are searching for ideas. But why did you choose the Accessability list to do thar? After visiting the sites you suggested, I cciuld find no projects pertaining to accessability. That's too bad brcaise there are accessability apps that could use a great deal of poliahing to make them much more usable like KTTS or JOVIE for sight impaired people like myself. (please excuse any typos because I cannot srr the fonts very well) I also did not see any place wwhere a user could make auggestions for consideration. I cold outline the areas and specific needs if anyone were interested. Thanks for thinking about this. Bob S </pre> Bob Stia 2013-03-25T01:20:59 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2318 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/109473/ ----------------------------------------------------------- (Updated March 13, 2013, 11:40 p.m.) Status ------ This change has been discarded. Review request for KDE Accessibility. Description ------- If a job cannot connect to speech dispatcher it would have tried to connect again and again for ever. Stuck in a never ending loop. I have limited the loop to only 10 tries. Also replaced KTTS and KTTSD with Jovie in a few places in the documentation/comments. Diffs ----- jovie/jovie.h 5f0c3b7 jovie/speaker.cpp 3aea565 Diff: http://git.reviewboard.kde.org/r/109473/diff/ Testing ------- Thanks, Ovidiu-Florin Bogdan _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Ovidiu-Florin Bogdan 2013-03-13T23:40:26 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2317 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/109473/ ----------------------------------------------------------- (Updated March 13, 2013, 11 p.m.) Review request for KDE Accessibility. Description (updated) ------- If a job cannot connect to speech dispatcher it would have tried to connect again and again for ever. Stuck in a never ending loop. I have limited the loop to only 10 tries. Also replaced KTTS and KTTSD with Jovie in a few places in the documentation/comments. Diffs (updated) ----- jovie/jovie.h 5f0c3b7 jovie/speaker.cpp 3aea565 Diff: http://git.reviewboard.kde.org/r/109473/diff/ Testing ------- Thanks, Ovidiu-Florin Bogdan _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Ovidiu-Florin Bogdan 2013-03-13T23:00:26 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2316 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/109473/#review29165 ----------------------------------------------------------- jovie/jovie.h &lt;http://git.reviewboard.kde.org/r/109473/#comment21772&gt; Please don't mix the comment changes and whitespace changes with the bug fix. jovie/speaker.cpp &lt;http://git.reviewboard.kde.org/r/109473/#comment21770&gt; This wont work because you reinitialize count to 0 every time the while loop loops. Move the int count = 0; line outside the loop. - Jeremy Paul Whiting On March 13, 2013, 4:50 p.m., Ovidiu-Florin Bogdan wrote: _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Jeremy Paul Whiting 2013-03-13T22:59:18 http://permalink.gmane.org/gmane.comp.kde.devel.accessibility/2315 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/109473/ ----------------------------------------------------------- Review request for KDE Accessibility. Description ------- If a job cannot connect to speech dispatcher it would have tried to connect again and again for ever. Stuck in a never ending loop. I have limited the loop to only 10 tries. Diffs ----- jovie/jovie.h 5f0c3b7 jovie/speaker.cpp 3aea565 Diff: http://git.reviewboard.kde.org/r/109473/diff/ Testing ------- Thanks, Ovidiu-Florin Bogdan _______________________________________________ kde-accessibility mailing list kde-accessibility&lt; at &gt;kde.org https://mail.kde.org/mailman/listinfo/kde-accessibility </pre> Ovidiu-Florin Bogdan 2013-03-13T22:50:34 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.kde.devel.accessibility