<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.kde.devel.accessibility">
    <title>gmane.comp.kde.devel.accessibility</title>
    <link>http://blog.gmane.org/gmane.comp.kde.devel.accessibility</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2332"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2331"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2330"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2329"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2327"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2325"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2315"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2308"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2301"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2299"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2297"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2292"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2285"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2283"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2282"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2276"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2274"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2266"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2263"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2262"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2332">
    <title>KMag</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2332</link>
    <description>&lt;pre&gt;  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&amp;lt; at &amp;gt;verizon.net





---_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>George Isaksen</dc:creator>
    <dc:date>2013-04-30T21:17:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2331">
    <title>CFP: INTERACT 2013 Workshop on Rethinking Universal Accessibility - deadline: 20-May</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2331</link>
    <description>&lt;pre&gt;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  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;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)

&lt;/pre&gt;</description>
    <dc:creator>Simone DJ Barbosa</dc:creator>
    <dc:date>2013-04-24T11:21:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2330">
    <title>Review Request 110104: Allow the user to testthe bell settings</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2330</link>
    <description>&lt;pre&gt;
-----------------------------------------------------------
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&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Christoph Feck</dc:creator>
    <dc:date>2013-04-20T15:52:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2329">
    <title>ANNOUNCE: at-spi2-atk 2.8.1 released</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2329</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;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
&lt;/pre&gt;</description>
    <dc:creator>Mike Gorse</dc:creator>
    <dc:date>2013-04-15T18:07:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2327">
    <title>Review Request 109977: Temporarily disable KMousetool when holding down some key modifier</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2327</link>
    <description>&lt;pre&gt;
-----------------------------------------------------------
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&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Akshay Ratan</dc:creator>
    <dc:date>2013-04-12T15:22:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2325">
    <title>Packaging of 4.0</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2325</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;gmail.com

Thanks, I hope to hear back from you!
_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>shawn graham</dc:creator>
    <dc:date>2013-04-12T05:30:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2315">
    <title>Review Request 109473: Added a counter to prevent a never ending loop if a job cannot connect to speech dispatcher.</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2315</link>
    <description>&lt;pre&gt;
-----------------------------------------------------------
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&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Ovidiu-Florin Bogdan</dc:creator>
    <dc:date>2013-03-13T22:50:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2308">
    <title>Review Request 109353: Modified the Talker Widget. Made the List of languages and synthesizers non editable.</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2308</link>
    <description>&lt;pre&gt;
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109353/
-----------------------------------------------------------

Review request for KDE Accessibility.


Description
-------

Edited the kcmkttsmgr/talkerwidget.ui file.
Set the Edit trigers for the list to: NoEditTriggers;


Diffs
-----

  kcmkttsmgr/talkerwidget.ui 0387501 

Diff: http://git.reviewboard.kde.org/r/109353/diff/


Testing
-------


Thanks,

Ovidiu-Florin Bogdan

_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Ovidiu-Florin Bogdan</dc:creator>
    <dc:date>2013-03-08T13:50:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2301">
    <title>ANNOUNCE: AT-SPI 2.7.5 released</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2301</link>
    <description>&lt;pre&gt;AT-SPI 2.7.5 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.7/
http://download.gnome.org/sources/at-spi2-atk/2.7/
http://download.gnome.org/sources/pyatspi/2.7/

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-SPI 2.7.5

* Added ATSPI_ROLE_LEVEL_BAR to correspond with the new atk role.

* Fixed various compiler warnings.


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&amp;lt; at &amp;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
&lt;/pre&gt;</description>
    <dc:creator>Mike Gorse</dc:creator>
    <dc:date>2013-02-05T16:51:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2299">
    <title>simon listens api</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2299</link>
    <description>&lt;pre&gt;Hello Peter,
I'm considering developing a Windows application for language teaching
software. Is it possible to use Simon for that? Here are my questions:
- do you have any API? what technology?
- how can I build the software for Win7, Win8, maybe Win XP? Are there
any guides/tutorials on that?
- can Simon give a more extensive response in hearing a phrase, e.g.
accent check, speaking fluency and alike

Looking forward to your answer
BR
WW.
&lt;/pre&gt;</description>
    <dc:creator>Wlodek Wiszka</dc:creator>
    <dc:date>2013-02-04T14:38:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2297">
    <title>Simon with ArchLinux</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2297</link>
    <description>&lt;pre&gt;I'd like to get Simon 0.4.0 working with Arch Linux which is a very
popular rolling distribution.
Simon is in the unsupport Arch User Repository right now at version
0.3.0, but I'd like to update it to 0.4.0 and want to have all my duck
in a row.
Do I need to require all of the Sphinx packages? (sphinxbase,
pocketsphinx, sphinxtrain, sphinx4 and cmuclmtk)
Do I need to require voxforge. The AUR has a voxforge-am-julius
package that seems to be for the Julius speech system. Do I need to
redo voxforge for simon, or is it not required for simon to function?

Sorry about all the questions. I like the look of Simon and want to
try it, but If I'm going to do it I might as well get it all working
for others as well ;-)

Thanks

&lt;/pre&gt;</description>
    <dc:creator>Mark Coolen</dc:creator>
    <dc:date>2013-02-01T14:39:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2292">
    <title>I need help to create a shadow dictionary inCatalan</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2292</link>
    <description>&lt;pre&gt;
  Hi

  I am creating a shadow dictionary for Catalan language (another collaborator 
will do in Spanish) and I have doubts as to the format. (We are told that it 
will review a linguist.) I think this is correct, see below, but do not know 
how to add terminal information.

Alcanó  [Alcanó]  a l k a n O
Alcanar  [Alcanar]  a l k a n a r
Alcarràs  [Alcarràs]  a l k a R A s
alcista  [alcista]  a l c i s t a
alcistes  [alcistes]  a l c i s t e s
alcohòlica  [alcohòlica]  a l k o O- l i k a
alcohòlic  [alcohòlic]  a l k o O- l i k

  Thank you for your help.

  Regards
  Toni
&lt;/pre&gt;</description>
    <dc:creator>Antoni Bella Pérez</dc:creator>
    <dc:date>2013-01-26T12:57:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2285">
    <title>ANNOUNCE: at-spi2-core 2.7.4 released</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2285</link>
    <description>&lt;pre&gt;At-spi2-core 2.7.4 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.7/

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-SPI 2.7.4

* [core] Fix some ref count leaks.

* [core] Some functions that return accessibles now propagate errors.


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&amp;lt; at &amp;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
&lt;/pre&gt;</description>
    <dc:creator>Mike Gorse</dc:creator>
    <dc:date>2013-01-14T23:31:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2283">
    <title>Oops</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2283</link>
    <description>&lt;pre&gt;Clicked on a mail from the ml admin to accept the review request e-mail and
accidentally accepted the spam that came right after.  My bad.

BR,
Jeremy
_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Jeremy Whiting</dc:creator>
    <dc:date>2013-01-13T16:00:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2282">
    <title>Yahoo!奇摩新聞 - 請問有誰買過博士襪?使用過的感覺如何? - Yahoo!奇摩知識+</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2282</link>
    <description>&lt;pre&gt;Dr. Paul æ¨è¦çä¸éå¥½è¥ªå­ (Paul&amp;lt; at &amp;gt;yahoo.com)å¯äºä¸ç¯æ°èçµ¦ä½  
(æªç¢ºèªé»å­éµä»¶ä½å)
------------------------------------------------------------
ç§äººè¨æ¯:

ç¶²åç±çè¨è« Dr. Paul å£ç¢æ¨è¦ä¸åå£«è¥ª 

 æ ¹ææ¥æ¬å°å®¶ç ç©¶é¡¯ç¤º è³æ¯äººçç¬¬äºåå¿è!! 

 ææä½ çè³-ä¿è­·ä½ çè³ ãæèéæ°£ã ãä¿æèé©ã 

 MITåè³ªä¿è­èæ¥æ¬åç´ æºè«å°·å°¬çè«éæå»-ç­ä½ ä¾é«é©!!  


 æä¸é¢Yahoo é¨è½æ ¼ä½¿ç¨èè¦è­ 

 http://tw.myblog.yahoo.com/good-sox/article?mid=7


 å®æ¹ç¶²ç«âé»æé²å¥ï½ç«å³é«é© 
 

 http://baid.us/jqun    PaulYLZPHFZJEAHMDDX




é¤è­ + æè + èé© + å¥åº·
============================================================
YLZPHFZJEAHMDDX

è«åæèª°è²·éåå£«è¥ª?ä½¿ç¨éçæè¦ºå¦ä½? - Yahoo!å¥æ©ç¥è­+

http://tw.knowledge.yahoo.com/question/question?qid=1512020203511

============================================================
Yahoo!æ°è 
http://hk.news.yahoo.com/
_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>mailbot&lt; at &gt;tw.knowledge.yahoo.com</dc:creator>
    <dc:date>2013-01-13T14:12:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2276">
    <title>packaging simon (and other kde tools)</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2276</link>
    <description>&lt;pre&gt;Howdy!

I'm right now rolling up an APT package of simon 0.4 for SprezzOS, having
rolled 4.9.4 packages for much of the rest of KDE today. SprezzOS 1
hopefully drops late tonight complete with an up-to-date KDE stack.

Just letting you know because you asked on your Simon 0.4 announcement page
:). Have a great 2013!

The packaging materials will live here:

  https://github.com/dankamongmen/sprezzos-world/tree/master/packaging/simon

feel free to share them.

&lt;/pre&gt;</description>
    <dc:creator>nick black</dc:creator>
    <dc:date>2013-01-01T12:43:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2274">
    <title>Request translation fixes for Simon</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2274</link>
    <description>&lt;pre&gt;
  Hello

  I found some messages with HTML tags that overlap the default font of the 
desktop. It might be true somewhere but in the screenshot (attached) I do not.

&amp;lt;body style=\" font-family:'DejaVu Sans'; font-size:9pt; font-" "weight:400; 
font-style:normal;\"&amp;gt;

simon     -&amp;gt; 2 messages
simond   -&amp;gt; 2 messages
simonlib -&amp;gt; 1 message


  Another:

  Two configuration modules, with the translation well represented in the app 
but not in his System Settings module.

wrong (nothing is translated):
  System Settings -&amp;gt; Accessibility -&amp;gt; Speech Model Compilation
  System Settings -&amp;gt; Accessibility -&amp;gt; KSimond
correct:
  System Settings -&amp;gt; Accessibility -&amp;gt; Simond


  Regards
  Toni_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Antoni Bella Pérez</dc:creator>
    <dc:date>2012-12-23T12:34:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2266">
    <title>ANNOUNCE: AT-SPI 2.7.3 released</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2266</link>
    <description>&lt;pre&gt;AT-SPI 2.7.3 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.7/
http://download.gnome.org/sources/at-spi2-atk/2.7/
http://download.gnome.org/sources/pyatspi/2.7/

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-SPI 2.7.3

* [core] Atspi_accessible_get_index_in_parent no longer returns -1 if the
   object's parent is not cached (BGO#688057).

* [core/atk] Re-register applications and keystroke listeners if the registry
   goes away and then returns.

* [core] Fix atspi_device_listener_new_simple.

* [core] Fix some compiler warnings.

* [core] Build: use gobject-introspection's Makefile instead of rolling our own.

* [core] Fix a crash when parsing events without detail when there is a
   listener for the event that names a specific detail value.

* [core] Fix crash when removing hung processes.

* [core] Fix deregistering of applications.

* [core] A few documentation fixes.

* [atk] Stop using deprecated glib functions.

* [atk] Fix a few memory leaks.


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&amp;lt; at &amp;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
&lt;/pre&gt;</description>
    <dc:creator>Mike Gorse</dc:creator>
    <dc:date>2012-12-17T22:27:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2263">
    <title>Hello ????</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2263</link>
    <description>&lt;pre&gt;Hello. Anybody out there?  I;ve beeen ssubscribed for ar least  3 weeks and 
gaven;t seen a single message except for thr one I sent and nobody answerred.


Bob S
&lt;/pre&gt;</description>
    <dc:creator>Bob Stia</dc:creator>
    <dc:date>2012-12-17T02:31:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2262">
    <title>jovie and mbrola</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2262</link>
    <description>&lt;pre&gt;Hello KDE people,

I am new to this list and hoping my first post will reach somebody. 
aaaaaaaaaaaaaaaaai am legally blind and find it almost impossible to read 
very large fonts and type ccoherebtly. 

I eun two versions of openSSUSE. 11.3 with KDE3 aba 12.2 with LDE4. I have 
installed Festival and espeak on both systems. I have also installed mbrola 
and CMU voices (correcctly, I hope) on both systems.

In 11.3 KDE3 uses KTTS with Feestival. In 12.2 KDE4 usea Jovie. Both work, but 
only with their own horrible barely intelligible voices. I cannot get KTTS to 
seee the espeak synthesizer nor Jovie to see the Festical synthesizer. 
Neither czn see the mbrola or CMU voices.

It is important to me to get these TTS screen readerss working satisfactorily 
as my blindness progressees.

Thank You

Bob S
&lt;/pre&gt;</description>
    <dc:creator>Bob Stia</dc:creator>
    <dc:date>2012-12-13T01:15:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2257">
    <title>[RFC] sketch of simple and accessible kwin deco</title>
    <link>http://comments.gmane.org/gmane.comp.kde.devel.accessibility/2257</link>
    <description>&lt;pre&gt;Please ensure to CC
- kwin&amp;lt; at &amp;gt;kde.org
- kde-accessibility&amp;lt; at &amp;gt;kde.org
- kde-artists&amp;lt; at &amp;gt;kde.org

Attached, red is comments


Target: "one size fits all"

- no pixmaps / images
- no gradients (both impact network performace)
- no antialiasing (vesa enhanced ;-)
- no shaping (makes compositing "expensive")
- strong indication (accessibility, no compositing need)
- relying on contrast, not colors (accessibility)
- tabbing support
- not looking entirely dull ;-)

Notice that this is a few minutes inkscape sketch "text not centered" is not important ;-)

Comments, suggests for improvement?

Cheers,
Thomas_______________________________________________
kde-accessibility mailing list
kde-accessibility&amp;lt; at &amp;gt;kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
&lt;/pre&gt;</description>
    <dc:creator>Thomas Lübking</dc:creator>
    <dc:date>2012-11-27T16:07:47</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.kde.devel.accessibility">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.kde.devel.accessibility</link>
  </textinput>
</rdf:RDF>
