Mario said, of the assertion that cut-and-paste is a function of the
application, not the terminal:
That sounds more like an excuse than a solution to me :-)
I know what you mean. However, it is true that many console
applications provide their own keystrokes for text selection, which is
Olaf Schmidt wrote:
[David Bolter, Dienstag, 1. Februar 2005 15:02]
Richard, it would be great to know if you are successful using GOK with
KMousetool. It might be the case that you would want to change to
Direct mode while using KMousetool...
That's right. We tested to ensure that
Oana said that you had to rename the other GNOME_Speech_*.server files
in /usr/lib/bonobo/servers if you wanted to force gnopernicus to use
Festival instead of other drivers.
Although this brute-force approach _will_ work, it should not be
necessary. If you are able to use gnopernicus as-is,
Peter said:
I think the right kludge involves using Gnopernicus' (or Orca's) knowledge of
what is on the screen and moving the mouse either relative to that knowledge
(preferred kludge variant), or as an absolute pixel percentage relative to the
window (Orca script to click the mouse 33% of the
Hi Øyvind:
GNOME has more than one way to magnify. You didn't really tell us how you
started the magnifier, or what you were expecting to see.
The most powerful magnification services are via 'gnopernicus', which is what runs if you
select Screen Reader and Magnifier from the
By the way - I gave some rather complex, though incomplete instructions
here.
I recommend that anyone new to the GNOME accessibility features read the
Accessibility Guide for GNOME 2.8 which can be found at the following
URI, for more information.
http://gnome.org/learn/access-guide/2.8/
Kenny said (of checking the br_active gconf key:
For the record: I configured my console screan reader to use software speech
through speech-dispatcher or I couldn't run this test.
You don't have to be running GNOME's gui in order to run gconftool-2. I
would have thought that power-cycling
Hi Kenny:
If the clock is causing gnopernicus to speak every second even when
'seconds' display is off, this sounds like a regression (we fixed
something like this once before). I have filed this bug on the issue:
http://bugzilla.gnome.org/show_bug.cgi?id=167393
Email me privately if you want
Anditya said:
When I try to do test-speech, it is not able to start it by saying No
server selected.
From this, and the other error message, it sounds as though ORBit2 is not installed. You need libbonobo and ORBit2 in order to use speech (or any GNOME accessibility, in fact). This is a bit
George Kraft wrote:
...
Can a jhbuild built gnome-speech be expected to run okay with the normal
package installation of festival on the host system?
Answer is yes, as far as I am aware.
- Bill
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
--
--
Bill Haneman
Gnome Accessibility Project
Sun Microsystems Ireland
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
Zsolnai Laszlo wrote:
Hello,
Check before starting festival_client if festival is running in the
background:
Note that this is only necessary when diagnosing festival_client
problems, no one should need to do this as part of normal GNOME
accessibility operation.
- Bill
ps aux|grep 'festival
Aditya Pandey wrote:
Also, may be you could try changing the oafserver iid from
OAFIID:GNOME_Speech_SynthesisDriver_Festival:proto0.3
to OAFIID:GNOME_Speech_SynthesisDriver_Festival:proto0.2
present in /usr/lib/bonobo/servers/ or /usr/local/lib/bonobo/servers.
Since test-speech is already
George asked:
Is there a gnome accessibility IRC channel?
Yes, there's irc.freestandards.org, channel #a11y. Also, anyone can
create a channel on irc.gnome.org/irc.gimp.net, so you can create #a11y
if you want to chat with folks on the gnome irc network.
- Bill
Jan Buchal wrote:
Hello,
I would like use gnopernicus with Czech festival voice. In gnopernicus
setting I do not find any possibility change it. The gnopernicus offer
two English voice only. However my festival use more as these voices.
Spanish an Czech for example. What i need setup in
Zsolnai Laszlo wrote:
Hello,
Originally in the gnome-speech's Festival driver these twoo english
voices are hardcoded.
Fernando Herrera wrote a very nice patch in order to solve this problem.
See this link:
http://mail.gnome.org/archives/gnome-accessibility-list/2005-February/msg00112.html
Zsolnai Laszlo wrote:
Hello,
In any case it was a big impulse for me. The result is, that we will
start with developing a pluggin for Gnome speech which will communicate
to Speech dispatcher as its client via SSIP. I hope that can bring a big
profit.
Currently gnome-speech can handle only software
Aditya Pandey wrote:
Ok, found and fixed it. The freetts-synthesis-driver turned out to be
a script which defines its own classpath.
Bad value was:
Jan Buchal wrote:
If I start gnopernicus it speak only some messages. Switch to window,
create new window etc. for example but not speak a content. However if
I press CTRL-ESCAPE, then gnopernicus speak correctly. This is necessary
do in every new window.
This is very strange, as CTRL-ESCAPE
Hi Aditya
The 'fuzzy locale matching' was added to gnome-speech version 0.3.5,
released in August 2004. Perhaps your Fedora-core version is older.
- Bill
Aditya Pandey wrote:
When I pass language as en on Sun Desktop system machine, getVoices
API (test-speech) returns the voices (like
, there are available for public view at
http://developer.gnome.org/projects/gap/sanity-testing/index.html
best regards,
- Bill
Jason White wrote:
On Tue, 26 Apr 2005, Bill Haneman wrote:
I'd be grateful for anything that distros or other maintainers can do to
help expedite getting these patches
Hi Krister:
Fullscreen magnification can be used without a second monitor now, and
it does work reasonably well, especially if you have a recent X server
(preferably XOrg 11.6.8.1).
You will need to enable the dummy driver which gives you a virtual
second screen, and then you can magnify
Hi Ian
Welcome to the list! Firstly I hope that someone on the list can
provide you with enough specific information to enable you to install
Linux+GNOME without any hitches. Personally I don't track the Ubuntu
distro mailing lists, so I don't know what specific issues people may
have had
Hi Darragh:
First, I think you'll need to turn off sound events, because they can
conflict with speech on some systems.
gconftool-2 -s -t bool /desktop/gnome/sound/event_sounds false
Then make sure esd is on:
gconftool-2 -s -t bool /desktop/gnome/sound/enable_esd true
There should be a
HI Darragh
I'm afraid that YaST (the graphical version, at least) is not
accessible, because of the way it is constructed and implemented. The
YaST graphical toolkit does not talk to the gnome accessibility
infrastructure, and I don't believe that it can be made to do so without
of
gaim to the terminal window when it launches, to confirm that libgail
and atk-bridge are both being loaded successfully?
thanks
Bill
On Wed, 2005-08-10 at 21:19 +0100, Bill Haneman wrote:
HI Cody:
The problems you are having are related but have slightly different root
causes. In order
Peter Korn wrote:
Hi guys,
I rather like David's idea.
Yes; also I think the notion of user profiles makes sense. We could
have various accessibility-scenario-related sets of gconf setting
grouped together in user profiles, and this generic mechanism could help
with usability for users
Hi Jan:
Please be more specific about use of ISO-Latin2. Gnopernicus currently
supports UTF-8 internationalization. It also supports the use of UTF-8
for speech, provided a suitable speech engine is available. Its braille
internationalization is currently somewhat limited; a complete
by one
braille cell, so I am not sure which non-ASCII characters can be
implemented. Perhaps its just a matter of building the appropriate
braille table for your mapping of 8-bit characters to Latin-2.
Remus?
Bill
Jan Buchal wrote:
BH == Bill Haneman [EMAIL PROTECTED] writes
Samuel Thibault wrote:
Concerning the dependencies of a common transcription library, I am
afraid it would be difficult to do without glib: there are few good
portable libraries that I know which can handle unicode (IBM ICU, Apache
apr, Qt...) and glib is one of the most complete and IMHO
Hi Carlos:
Perhaps we should move further technical discussion to the
gnome-accessibility-devel list.
One comment I'd like to make concerns the relationship of X (the X
server and apis) to the magnification issues we face. Because X is
quite a mature standard and a central part of our
Hello everyone:
I would like to draw your attention to a statement which the Gnome and KDE
Accessibility Projects, and the Free Standards Group's Accessibility Workgroup
(FSGA), have prepared regarding
the plans and intentions of their projects with respect to interoperability and
Darragh:
I've used gnome-speech drivers for Theta with very good results. So far
this seems to be the best choice for quality, cost, and reliability so
far. However, I don't know what the availability of the Theta voices is
like at the moment, as Cepstral has moved to a new product which
Hi Hank:
That's Theta, T H E T A. Cepstral, the company that produces them, is
now producing voices for their new engine, called 'Swift'. You can hear
demos of the voices here:
http://www.cepstral.com/demos/
I am not sure how accessible that web page is, but it looks like a
standard
Because Speech Dispatcher uses GPL and not LGPL, it is limited in terms
of what drivers it can support due to license incompatibility issues. I
believe we have a speech dispatcher driver contributed for gnome-speech
that is in the queue for integration as time permits.
Bill
Kenny Hitt
Hi Jason:
If you want your magnifier to follow the mouse in fullscreen mode, you
need to specify the -m option along with the others on your command
line. Otherwise, it's just awaiting instructions from some other client
such as gnopernicus.
Note also that for more featureful
Hi Olivier:
I believe the message should say now running, instead of not
running. A couple of things to look out for; note that you will have
to restart your bonobo-activation-server after adding a new gnome-speech
driver, before it will appear in the list of available drivers. Also,
it
On Thu, 2005-09-29 at 18:27, Sébastien Hinderer wrote:
Hi Sun folks other listers.
Hi Sebastien and all:
Bill Haneman :
Samuel Thibault wrote:
...
They say open source is not accessible, which is wrong, but what is
true is open source is not yet really
]
[mailto:[EMAIL PROTECTED] On Behalf Of Sébastien
Hinderer
Sent: Thursday, September 29, 2005 12:35 PM
To: gnome-accessibility-list@gnome.org
Subject: Re: Gnome and support for the visually impaired
Hi Sun folks other listers.
Bill Haneman :
Samuel Thibault wrote:
...
They say open source
product) that can be selected as preferences.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Haneman
Sent: Tuesday, October 04, 2005 10:09 AM
To: Jason Grieves
Cc: gnome-accessibility-list@gnome.org
Subject: Re: few questions
Jason Grieves wrote:
Hi
Hi Jason:
I think I understand your writeup a bit better. I still think that it
would be nice if we could fold it into the Accessibility Guide somehow -
perhaps as an appendix or chapter? Because the Accessibility Guide is a
hypertext document, we could use links to lead the reader/user to
Aditya Pandey wrote:
Hi
Prior to acquiring some of speech synthesizers, I am trying to find
out more on them. Is there a some text available on gnome-speech
supported speech synthesizers like their download/purchase links,
comparison on features/pricing etc.?
Since we don't want to
Jason:
I believe the problem is Firefox - and I think this has come up on this
list before. It seems that Firefox is not nearly as accessible as the
mozilla 1.7 series, even without the still-outstandinf Sun accessibility
fixes.
Bill
Jason Grieves wrote:
Hello,
I have Firefox compiled
Willem
Sun Mozilla should be your best bet. I am not sure you've explained
what problems you are encountering as you try to run it; of course we
need information about your distro, platform, versions, etc. before we
can help.
regards
Bill
Willem van der Walt wrote:
Hi,
Which browser,
Peter:
You should install gnome-common after you make it. After that the
autogens of the other packages should work fine. Note also that you
will need gnome-mag as well, and working, recent gnome2 development
packages for the gnome core and desktop modules.
Bill
Peter Rayner wrote:
Hi Terrence:
There are currently issues with using the magnifier in horizontal
splitscreen mode, i.e. at the bottom of the screen, as opposed to the
left or right hand side. See bugzilla bug 171465
http://bugzilla.gnome.org/show_bug.cgi?id=171465 It sounds as if this
problem is what you are
Also Terrence:
The no speech problem is probably due to changes in the festival
speech synthesis system which require you to modify a file called
festival.scm. Please see the recent archives of this list for
discussion of no speech with Festival issues. Knowing your distro
will help us
Hi Godspeed
If 'none of the options are working' in gnopernicus then I believe that
your machine is not configured properly. It may be that one or more
packages required for accessibility were omitted from the packages.
A few things to point out: you should be running the Gnome desktop, not
Hi Darragh:
Festival changed the way it uses the network in recent releases. I
believe the file '/etc/festival.scm' needs to be edited to add
permissions to localhost.
Here is a pointer to one of the list archive articles, if this is indeed
your problem:
Hi Jason
The GNOME_ACCESSIBILITY environment variable has been deprecated for
years, so there's still possibly some mystery in your setup. Are you
sure you had the /gnome/desktop/interface/accessibility gconf key set to
true ? The latter is the recommended way of enabling assistive
Hi Michael:
I'd suggest reading the Gnome Accessibility Guide, in particular the
Appendices, and also the Gnopernicus manual. This information may help
you in setting up fullscreen magnification.
Also note that, if you are using Festival as your text-to-speech engine,
you will need to modify
Michael/All:
I forgot to include the URI for the Gnome Accessibility Guide:
http://gnome.org/learn/access-guide/2.10/
It's also available with most Gnome distributions, from the Help browser
select Desktop and then Accessibility Guide.
Bill
___
Hi Jason, Cody:
About Java and the bridges:
As Jason mentioned before, there are two 'java access bridges'. One is
for Windows, and if you are running on Windows you will need to make
sure your screen reader supports the Java Access Bridge for Windows in
order for it to work.
If you are
remus draica wrote:...
The other problem is that currently, unless I am mistaken, gnopernicus'
braille tables are 8 bit tables, and gnopernicus always assumes Latin-1.
That's right.
Latin-2 is also 8-bit, so in theory the current gnopernicus architecture
could handle this, but it
Hi Julian:
[EMAIL PROTECTED] wrote:
Good morning, We are developing an application that allows to manipulate
the main menu of GNOME desktop using some speech commands GERvoice.
After making a study of the possible tools that allow the communication
between two applications (the GERvoice
Hi Alexandra and Cody:
Ada, I think there could be some confusing aspects to your answer, or
perhaps you misunderstood Cody... you said:
2. What is teh command to make gnopernicus work with gaim messenger?
A: There isn't a special command for your problem. Installing a new version
of
Janina's right of course, just restarting the X server (or logging out!)
should have solved the problem.
It's probably a good idea to log out and back in after replacing a core
component like the at-spi-registry anyway.
best regards,
Bill
Janina Sajka wrote:
Luke Yelavich writes:
On
or
go through a process of killing them one by one.
Will
On Dec 7, 2005, at 11:25 AM, Bill Haneman wrote:
Janina's right of course, just restarting the X server (or logging
out!) should have solved the problem.
It's probably a good idea to log out and back in after replacing a
core
Henrik Nilsen Omma wrote:
Hi all,
I've written up a fairly detailed review of GOK here:
https://wiki.ubuntu.com/Accessibility/Reviews/GOK
It is meant partially as an introduction to those who don't know the
program, but mainly as a critical look that can hopefully stimulate
discussion and
Hi Henrik:
The reason that StickyKeys is needed is not only because of general key
combinations like the one you mention (Control-Alt-X) but also because
of the interaction with CapsLock, etc. In general the only way to
accurately reflect what the X server will do with key events is to ask
Henrik/All:
Sorry for re-posting the URI for the sanity-test documents, I see now
that you referenced them inline. Thanks a bunch! I look forward to
reading your test scheme.
Bill
___
gnome-accessibility-list mailing list
svs drozo wrote:
Hi,
I would need to set up an environment in which two different hosts have
the two parts of at-spi, I mean, the clients in one of them and the
server in the other, is that possible? How can I do it?
Hi:
If you only want the client to be on one host, and the applications
Hi Pedro:
While I think this has been suggested before, I think that it is a good
idea; especially if it's designed to allow sending the output to a named
pipe, serial port, or perhaps even convert to HTTP and send output that
way. It would allow more ways to debug the speech output itself.
Hi Jude:
Are you sure you have gnome-common installed? Looks to me as though you
are missing the 'gnome-autogen.sh' script which I believe is provided
with gnome-common. Gnome-common is a dependency of ALL gnome cvs builds.
Bill
Jude DaShiell wrote:
After having checked gnopernicus and
Hi Ginn:
Thanks for answering Naveen.
Could you make sure he knows that the solution of removing GTK_MODULES
is a temporary one? We are still telling accessibility users to set
this variable in the environment, since they need it in order to make
other important applications accessible.
Hi Don:
This certainly 'smells' like a permissions problem. I believe the
Festival gnome-speech server relies on the ability to write to a
particular port, perhaps 7000? I am sure someone else on the list can
provide that detail. My guess is that root has write access to that
port, but
On Sun, 2006-02-12 at 22:27, Luke Yelavich wrote:
...
Did you specify the prefix for the gnopernicus configure script? For
example ./configure --prefix=/usr? if you didn't, I have a feeling that
is why it can't find the DECtalk server but test-speech can.
Luke/all:
gnopernicus doesn't use
On Tue, 2006-02-21 at 01:21, Davyd Madeley wrote:
Quoting Dana Olson [EMAIL PROTECTED]:
Will Gnome have some method to disable Slow Keys from constantly
popping up when you hold down a key for a few seconds?
You can turn this off from the Keyboard Accessibility preferences
dialog. As you
Henrik:
I think Flite uses the same file format. ( Will, please correct me if
I'm wrong). It also requires a Java JRE, are you planning to include
Java in the live CD?
BTW, in the past, Java was required for OpenOffice.org accessibility,
but that's not true of the latest version.
Bill
On
On Fri, 2006-02-24 at 13:09, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
Henrik:
I think Flite uses the same file format. ( Will, please correct me if
I'm wrong).
By same format you mean the same speech files? So what is the main
benefit of F-lite, a smaller memory footprint
Hi Satyam:
In the case of gnopernicus and orca (which are the two freely available
screenreaders for our graphical platform today), as Samuel said, not
every user prefers a given screen reader. One of the things which orca
provides, which gnopernicus does not, is comprehensive
Hi Everyone:
As a few of you may already be aware, I will be on a leave of absence
for two months, starting immediately after today. In my absence, please
direct questions regarding Gnome accessibility to the
gnome-accessibility-list@gnome.org, and questions specific to
accessibility development
Hi Chris:
The answer is, don't implement sticky keys in your keyboard. You
should be using the system-wide StickyKeys settings and feature instead
(as GOK does).
Interfering with the normal operation of the system wide setting (i.e
clashing with it as your app does), is itself an accessibility
users.
best regards
Bill
On Mon, 2006-06-26 at 13:30, Ashu Sharma wrote:
On 6/26/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-06-26 at 08:19, Ashu Sharma wrote:
Hi,
There was discussion about making use of ATK on KDE, rather
than
on this aspect of gnome-a11y and
fix my program so it is not an accessibility violation.
I suggest you use the system gconf keys for sticky keys.
regards
Bill
On 26/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
Hi Chris:
The answer is, don't implement sticky keys in your keyboard. You
should
On Mon, 2006-06-26 at 23:05, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote:
Bill, is it an accessibility violation to have unusable accessibility
tools?
Are you going to say something helpful?
OK, I should
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote:
Chris Jones wrote:
...
In other words I cannot spend the summer making gnome-a11y suitable
for my needs. What I need is a temporary work around until after the
SoC when I could find time to work on this aspect of gnome-a11y and
, and the reason you
are warned not to use GOK via the system core pointer.
Bill
On 26/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote
Chris Jones wrote:
...
In other words I cannot spend the summer making gnome-a11y suitable
for my needs
.
On 26/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote:
Chris Jones wrote:
...
In other words I cannot spend the summer making gnome-a11y suitable
for my needs. What I need is a temporary work
On Tue, 2006-06-27 at 10:57, Olivier BERT wrote:
I'm currently working on Speech Dispatcher backend for Orca. This
bypasses the Gnome Speech layer completely. Since Speech Dispatcher
offers several speech synthesizers not supported by Gnome Speech,
Does Speech Dispatcher support something
method must be found to solve the issue.
We'll be able to help you better if you are a little more open to our
suggestions.
Bill
Bill Haneman said:
Bear in mind that ANY onscreen keyboard that uses the mouse will fail to
work properly when used to pop up menus, etc. via keyboard navigation
Hi Hynek, All:
I'm not sure I agree that speech engines should not do their own audio
output. While I think you have identified some real problems with that
approach, it's not clear that the .wav file approach has a low enough
latency. If tests show that latency is not a problem, then passing
Hi Chris:
There's no good solution to the share a dock area problem. We
recommend that you don't use both top and bottom panels when running an
onscreen keyboard, for this reason.
The straightforward solution is to remove either the top or bottom
panel, and then use that edge to dock your
characters.
Bill
On 29/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
Reading the gconf values isn't a fully robust solution, since the panel
is not the only thing that might use _NET_WM_STRUTS.
It's not apathy, it just that fixing this the right way would require
new WM API.
Bill
On Mon, 2006-07-17 at 23:59, Brett Clippingdale wrote:
Linux Screen Reader (LSR) was presented at the Linux Desktop
Developers' Conference today as part of a talk titled Accessibility
Enablement and Usability for GTK Applications.
Of particular interest to all developers is a short
Manish:
Please check the recent list archives for info on firefox work. There
is also a mozilla accessibility development mailing list,
[EMAIL PROTECTED]
Here's a quotation from a recent email thread on Firefox accessibility:
Yes.
Firefox 1.5 or 2.0 will work better if you set GTK_MODULES
On Mon, 2006-07-24 at 11:21, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
Hi Petra:
In the most recent versions of Gnome, assistive technology support is on
by default. The access keys idea is a reasonable one, and I think it
would greatly improve the Ubuntu accessibility experience
On Mon, 2006-07-24 at 11:58, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
The new onscreen keyboard does not meet the needs of many
mobility-impaired users. GOK should be bundled with the LiveCD - once
some configuration issues are dealt with.
Do you have any specific use cases
On Mon, 2006-07-24 at 12:41, Henrik Nilsen Omma wrote:
Our plan is to go ahead with the new
technology and deal with the problems as they arise.
If by this you mean that you will ship SOK in preference to GOK in
Ubuntu, I think you are making a mistake.
Bill
On Mon, 2006-07-24 at 13:42, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
On Mon, 2006-07-24 at 12:41, Henrik Nilsen Omma wrote:
Our plan is to go ahead with the new
technology and deal with the problems as they arise.
If by this you mean that you will ship SOK
installing it by default.
I disagree - we went to a lot of trouble to make GOK work as well as
possible out of the box. That said, we felt we needed to warn end-users
of potential conflicts with the core pointer, thus the warning dialogs
(easily suppressed, as I have pointed out before).
Bill
Bill
with no choice.
- Hide quoted text -
On 24/07/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-07-24 at 15:10, Chris Jones wrote:
...
It is possible to detect when pointer grabbing occurs so work arounds
are quite possible I should think.
Not as far as I can tell. X just doesn't allow
On Mon, 2006-07-24 at 16:38, Chris Jones wrote:
Bill Haneman said:
I don't recall ever refusing to fix any corepointer
issues, for instance - at the time you asked, there were multiple
research efforts under way to try and address them.
Maybe I put that too strongly. You stated
Hi Jude:
Don't use twm or icewm as window managers - for best results you'll want
to install and run the Gnome desktop env which includes the metacity
window manager. Starting gnome-session after startx may work for
you.
regards
Bill
On Fri, 2006-07-28 at 01:00, Jude DaShiell wrote:
So far
Hi Olaf!
I appreciate that kttsd can have many useful applications. I differ
with your statement below, however:
But screen readers do not help partially sighted users, users with learning
difficulties, or people who simply love to have system notifications or IRC
messages spoken.
On Wed, 2006-08-16 at 20:44, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
Actually in the Windows world all of those are frequent use cases for
screen readers. In conjunction with magnification or onscreen
highlighting, screen readers can be especially useful for partially
sighted users
Hi Chris:
Zero-conf is of course the ideal, glad you've achieved it for SOK.
I am hoping that by using Xevie (via at-spi-registryd - since Xevie only
allows ONE client per session :-( and at-spi-registryd needs XEvie for
its own purposes), we can change GOK so that the default out-of-the-box
On Thu, 2006-08-17 at 11:40, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
Olaf implied that there was a concern with XEvie interfering with the
core pointer.
No, I meant to say that interfering with the core pointer is the intended
behaviour for most use cases of on-screen keyboards
On Thu, 2006-08-17 at 12:05, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
Actually, my point is that this affects ALL use cases of on-screen
keyboards.
I don't see why this should be the case.
Imagine a case where an on-screen keyboard is used for entering text in
another language
Hi Olaf:
On Wed, 2006-08-16 at 21:23, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
That strikes me as a surprising statement. Of course it depends on what
you mean by partially sighted.
The people I am familiar with for example have light allergy. Large bright
areas on the screen hurts
1 - 100 of 152 matches
Mail list logo
