Re: Speech-dispatcher update
As far as I can tell, you should simply have to set
RUN_SPEECHD=yes
ind /etc/default/speech-dispatcher.
The init scriptp of speech-dispatcher should take care of setting up
the necessary directory in /var/run.
Best regards, Lukas
Storm Dragon writes ("Speech-dispatcher update"):
> Hi,
> If you try the fix I wrote about last night, there is one problem. I
> turned on the computer this morning and the /var/run/speech-dispatcher
> folder was missing. I had no speech. Fortunately, I had memorized the
> Orca preferences enough to be able to switch back to Gnome speech
> services. I had to recreate the /var/run/speech-dispatcher and change
> the permissions back to 777 and it worked again. So, if you used my
> workaround, be sure to switch back to gnome speech services before
> shutting down. I logged out and back in with no problems last night, it
> only happened when I completely shut the system down.
> Storm
>
>
> --
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
>
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: gnome, skype, and orca
Josh writes ("gnome, skype, and orca"):
> Or is there an alternative that emulates basic skype features using your
> skype account that works with Orca?
Sortof, yes:
http://vmiklos.hu/project/bitlbee-skype/
It is somewhat commplicated to setup and you will need some sighted
help to get started. The chat part of skype should work pretty well
wiht this. The docs mention some support for managing calls as well,
but I have not yet had a chance to test it myself.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: speech dispatcher
> On Thu, Mar 06, 2008 at 04:48:49AM EST, mike coulombe wrote: > > Hi, I installed speech dispatcher on one of my ubuntu systems today. > > After rebooting, I don't see speech-dispatcher in the orca list of choices. > > Has anyone else noticed this. Make sure you have the python-speechd package installed as well. Best regards, Lukas -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: problems playing music when orca is running.
mike coulombe writes ("problems playing music when orca is running."):
> Hi, I notice when trying to play a song when orca is running all sound is
> lost.
> Exiting the music does get orca to speak again. I haven't tried this for
> awhile, but thought I red awhile ago that port audio was suppose to correct
> this problem.
> It doesn't matter if software mixing is enabled or not, the result
is the same. If this is suppose to work, is there another setting that
has to be made. Thanks Mike.
Gutsy still uses portaudio 18, so things have not changed with respect
to audio mixing. You have at least two options: either use speech-dispatcher or
try the aoss trick with gnome-speech as discussed before for example
on the orca list.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: speech-dispatcher
mike coulombe writes ("speech-dispatcher"):
> Hi, I notice when speech-dispatcher is running yasr doesn't work. Is there a
> way to correct this problem. I use yasr because dosemu doesn't work with orca.
What tts system are you using with yasr? If you have a reasonably new
version of yasr, it can use speech-dispatcher just like orca. If you
are using yasr with eflite, you must make sure you use a version of
flite with the alsa patch.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: orca not reading some administration screens
Pranav Lal writes ("orca not reading some administration screens"):
> I am running Ubuntu 7.04 in a virtual machine. When I start orca, I find
> that it does not read certain system administration screens. For example,
> if I try the menu item labelled "networks", I am able to enter my password
> and, after that, orca does not read any text on the screen. This is a
> nuisance since I need to configure some of these settings.
This is a well known problem. Try the following:
http://live.gnome.org/Orca/SysAdmin
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: customising orca for different applications
Pranav Lal writes ("customising orca for different applications"):
> Is it possible to customise orca for a particular application? For example,
> in ubuntu 7.04, I have an option of using various open office programs. I
> would like orca to speak differently in these programmes. It is this
> possible to do?
Not sure if this is what you want, but You can press
Control+Insert+Space to bring up an application specific settings
dialog.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: flopy discs
mike coulombe writes ("flopy discs"):
> Hi , has anyone made a boot flopy from the svm file on the live cd.
> If so how do I do this under linux.
This has nothing to do with accessibility. Your chance of getting an
answer would be higher in a more suitable forum. For now, try:
sudo dd if=sbm.bin of=/dev/fd0
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: how do you get rid of downloaded packages
mike coulombe writes ("how do you get rid of downloaded packages"):
> Hi, when you download and install a package, I assume the actual package is
> still on the system.
> How do you cleanup to get rid of them, and does anyone know where they are
> incase I want to save the packages to use on another system.
sudo apt-get clean
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: logging in as root
In order to be able to login as root via gdm, you will have to edit
the gdm configuration file. See the instructions on enabling the root
account on the following page:
http://live.gnome.org/Orca/UbuntuEdgyEft
The instructions are for Edgy, but they should work for Feisty too.
Best regards, Lukas
mike coulombe writes ("logging in as root"):
> Hi, I followed the instructions to add a password to login as root.
> How does this work at the login screen. Typing root pressing inter and then
> entering the password doesn't work.
> Using my login name and the root password didn't work either.
> So how is this suppose to be done.
> Thanks Mike.
> X-Antivirus: avast! (VPS 000742-0, 05/21/2007), Outbound message
> X-Antivirus-Status: Clean
>
>
> --
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
>
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Question about speech-dispatcher inclusion
Unlike the original poster, I find the gnome-speech driver for espeak
to work ok, but it probably very much depends on the machine, in
particular on the sound card. That said, I believe that
speech-dispatcher should seriously be considered for inclusion, be it
only for the fact that it will give us Alsa audio playback for all
supported synths. I see Alsa support as a very strong requirement
nowadays. It would be very nice to solve this problem in one place
only instead of in every synth. When going with speech-dispatcher, it
would be desirable to replace the current generic driver for espeak
with one that uses espeak natively.
The alternative is to try to improve Alsa support in portaudio in order to
fix the sound problems some people experience with the gnome-speech
driver for espeak.
Best regards, Lukas
Henrik Nilsen Omma writes ("Re: Question about speech-dispatcher inclusion"):
> Hi,
>
> An interesting post that seems to have gone unanswered. I'm not the most
> qualified to write about speech drivers, but I'll give my view.
>
> We opted to go with the gnome-speech option because of some limitations
> in speech-dispacher and because the Orca speech-dispacher driver was
> still in alpha when we made the decision. We certainly did not want the
> Orca -> Gnome-speec -> speech-dispatcher -> espeak chain that some
> people were using at the time.
>
> How are you running it now, with the Orca SD driver? What would be the
> advantage of writing a direct espeak driver for Orca? (I ask because I
> don't know, not rhetorically)
>
> I generally a fan of the idea of speech-dispatcher, the flexibility it
> gives. But it's fair to ask if we need the extra layer if we can have
> direct drivers for espeak and festival? These will after all be the
> mainstay of our offering.
>
> Henrik
>
> Michael Curran wrote:
> > Hi all,
> >
> > I have just started using Ubuntu as of a few days ago.
> >
> > I have been using Debian and Gentoo (all with speakup) for many years, but
> > this is my first time at being able to simply install a Linux OS all with a
> > working and accessible GUI.
> >
> > Congrats to the Ubuntu Accessibility team so far for making this a reality.
> > And of course well done to the Orca team for making an ever improving
> > screen
> > reader for Gnome.
> >
> > As the subject line says, I have a query about speech-dispatcher's
> > inclusion
> > in Ubuntu.
> >
> > Is there a reason why speech-dispatcher can not be included on the Desktop
> > live cd? I have tried both 6.10 and 7.04 and this seems to be the case.
> >
> > I absolutly love ESpeak (for many reasons). But putting in the 7.04 live cd
> > and having Orca come up talking with ESpeak the way it did made mee quite
> > disappointed to see ESpeak used in this state.
> >
> > The problem was the responsiveness, and the jumpyness.
> >
> > As I understand, Orca was using gnome-speech, with a gnome-speech driver
> > for
> > ESpeak.
> >
> > I am not blaiming the author of that driver, I'm sure there must be
> > limitations to gnome-speech to have it act in this way.
> >
> > But, as soon as I installed Ubuntu successfully, I quickly installed
> > speech-dispatcher, and told Orca to use that instead.
> >
> > Straight away, absolutely wonderful. Using Orca was pretty much as
> > responsive as using NVDA, or Jaws or Window Eyes or Hal, on Windows.
> >
> > Because I have only just joined this list, and only just started using
> > Ubuntu, I'm sure I have missed why speech-dispatcher isn't included on the
> > live cd. But, I really do think that we must push for it to be.
> >
> > Or another option is to write an Orca synth driver for ESpeak directly.
> > But,
> > so far, my dealings with gnome-speech havn't been that good. Even with
> > festival its still a little jumpy.
> >
> > Its fine to have an accessible operating system, but I always feel the most
> > important thing is responsiveness. Using Speakup, you press a key things
> > just happen, using NVDA or Jaws etc, things just happen. But trying to use
> > Orca with a slow synth driver, its seriously like walking through fog. You
> > know where you are if you move carefully and slowly, but you can't just run
> > like the wind.
> >
> > I know that Orca is much better than this, but using it with the espeak
> > gnome-speech driver, it wasn't that enjoyable.
> >
> > Another surprising thing was that when I changed to speech-dispatcher,
> > because espeak is forced by speech-dispatcher to use aplay, I was able to
> > play sound files in Gnome quite nicely, and still have Orca talking.
> >
> > Where as with gnome-speech, I think that wasn't working, at least on my
> > system anyways.
> >
> > I am thinking of spending some of my time, when I'm not developing NVDA
> > that
> > is, to perhaps work on Unbuntu Accessibility if I can. Perhaps one thing I
> > could do is look at writing an espeak driver for Orca, or perhaps try and
> > work out the issues that exist in gnom
Re: [orca-list] Setting up a dual boot with Ubuntu & XP
Henrik Nilsen Omma writes ("Re: [orca-list] Setting up a dual boot with Ubuntu
& XP"):
> ...
> the Grub bootloader that lets you choose Ubuntu or Windows. If you do
> nothing it will boot Ubuntu after 10 seconds. To get to Windows you must
> press the down arrow 5-6 times to get to the end of the list and press
> Enter. (hm, we should try to get some beeps in grub)
The only way I know to get beeps in grub is to add bell characters
(^G) into some of the labels. The problem is complicated by the
fact that the beep is heard when the cursor hits such an entry as well
as when it leaves it.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: sharing folders
mike coulombe writes ("sharing folders"):
> Ok, I found the problem I was having, but don't know how to solve it.
> If you press the ap key when a folder is marked you get a context menu.
> One of the choices is share this folder. Up to this point orca works fine.
> However, after pressing enter the screen goes back to your browser. When my
> daughter did this she used the mouse and got another menu after clicking on
> the share this folder that gave choices to not share it, share it in windows
> networks and so on.
> My question is how can this be made accessible to those of us who use a
> screen reader.
It already is accessibel if you create a .orbitrc file for root in the
way it has been discussed here before. Alternatively, you can install
the samba package and add something like the following to the file
/etc/samba/smb.conf:
[sharedfolder]
path = /home/youruser/shared
comment = my shared folder
available = yes
browseable = yes
public = yes
writable = yes
Then do:
/etc/init.d/samba restart
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: firefox
mike coulombe writes ("firefox"):
> Hi, does anyone have the link to the nightly builds of firefox.
> I seem to have lost the one I had.
Hi Mike,
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: speakup
mike coulombe writes ("speakup"):
> Hi, Is there a volume control key for speakup.
> I have always used yasr, but saw another post and got it working on ubuntu.
> The problem is the sound volume is very low.
> I know I can edit the file, but it seems to me speakup has a key to increase
> the volume.
Yes, the keys are Insert+1 and Insert+2, but they seem to have no
effect when speakup is used with speech-dispatcher.
The reason why the volume is so low is that the configuration file
/etc/speech-dispatcher/modules/espeak-generic.conf
is incorrect. Here are the correct settings:
GenericVolumeAdd50
GenericVolumeMultiply 50
Edit the above file and do:
sudo /etc/init.d/speech-dispatcher reload
The volume keys still will not work but at least the volume is now at
the sensible level.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: ubuntu and speakup
Michael Weaver writes ("ubuntu and speakup"):
> I would like to get Feisty working with Speakup.
> How do I go about doing this and how do I change to a text console?
If you have a hardware synth, load the speakup module suitable for
your synth. If you do not have a hardware synth, you will have to
install the speechd-up package. This should also install
speech-dispatcher. Then you must load the speakup_sftsyn module:
sudo modprobe speakup_sftsyn
> I notice that CTRL ALT F1 etc doesn't seem to work on my laptop.
What do you mean by does not work? What happens and what do you expect
to happen?
> Is there a difference between the terminal option under the
> accessories menu in Gnome and doing the CTRL ALT F1 or whatever?
Very much so. The Terminal option in the menu basically opens a window
in in wich a shell is running. Doing Control+Alt+F1 on the other hand
will switch away from the graphical user interface (the X window
system) and bring you to the linux console. The latter is where you
can use speakup.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Using espeak with alsa via aoss (was: speech dispatcher)
Guy Schlosser writes ("Re: speech dispatcher"):
> I have the same problem. My volume is too low, and I cannot hear
> system sounds or play music files. If you figure it out, please let
> me know. :)
I do not know your reasons for trying speech-dispatcher, but if you
are just doing so to get Alsa audio playback, you may first want to
gry the following recipie for using espeak via aoss:
http://mail.gnome.org/archives/orca-list/2007-April/msg00375.html
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Using GUI system administration tools with orca
Guy Schlosser writes ("Re: installing ubuntu 7.4 with speech"):
> Hey there Christian, maybe you or someone on the list can answer a
> question for me. Why is it that when I go into something like
> network administration from the applications menu, I lose speech? Is
> there a way to keep my speech in these apps? As with before, any
> help would be greatly appreciated.
See:
http://live.gnome.org/Orca/SysAdmin
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: ORCA Through A USB Device?
Joanmarie Diggs writes ("Re: ORCA Through A USB Device?"):
> > So can Orca output to a USB device?
>
> I've never tried this as I do not have such a device. Sorry! However,
> the question I assume is really how does one get gnome-speech to use an
> alternative device? Hopefully someone here knows the answer.
As far as I know, gnome-speech does not do any audio playback itself,
but relies on the tts engines to do so themselves. Thus, one would
have to find out how to make for example espeak use a different audio
device.
In Feisty espeak uses portaudio 18 wich in turn uses OSS to play
audio. From a quick glance at the portaudio and espeak source, it
seems they will always default to /dev/dsp, if it is available. so,
one would probably have to recompile espeak to make it use another
device than the one offered by portaudio as the default, for example
/dev/dsp1.
Another way of course is to somehow get the USB device to be /dev/dsp.
Maybe unloading the modules for both sound devices and then reloading
only the module for the USB device might do the trick. Do "lsmod" to
see which modules are loaded, The modules for the sound cards start
with "snd_".
Moreover, speech-dispatcher offers options in its config files to choose the
audio
output device to use.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: need an off-line build dep for orca under ubuntu, is it possible?
krishnakant Mane writes ("Re: need an off-line build dep for orca under ubuntu,
is it possible?"):
> I did not get what you are trying to suggest.
My suggestions was that you build a debian/Ubuntu binary package that tracks
orca svn head. You will end up with a file like:
gnome-orca-svn+20070425_i386.deb
I do not know what the official naming convention for such a package
would be but something along the line of the above.
This way you will not have to install anything additional on the
target machines. You would just do:
dpkg -i gnome-orca-svn+20070425_i386.deb
> what I am worried is how to simulate the apt-get build-dep gnome-orca
> without the internet connection?
You will not need this once you have built the package, i.e. the
build dependencies are not needed to install the binary package.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: need an off-line build dep for orca under ubuntu, is it possible?
krishnakant Mane writes ("need an off-line build dep for orca under ubuntu, is
it possible?"):
> hello,
> in context to the questions asked by mohomad and the answers, I have
> a pritty streight forward question.
> I keep on going to schools in some rural areas of India. and for the
> blind people out there, ubuntu with orca seams to me as the best
> solution.
> can some one tell me if I can do an off-line (without internet ) build
> and configuration of orca under feisty?
Just build a debian binary package of the latest svn revision of orca
before you go and you can simply install it offline. No need to build
it from scratch on every machine. Use the current package in Ubuntu as
a basis for your package. For information on building Debian packages:
http://www.debian.org/doc/maint-guide/
It seems that several people would be interested in such an orca
package that tracks svn trunk, so you might consider making it
available publicly.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: can't set up the build environment for Orca on Ubuntu
> > Mohammed Al-shar' wrote: > >> anyway, my problem is when I issue "sudo apt-get build-dep gnome-orca" it > >> tells me: > >> e: could not open file > >> /var/lib/apt/lists/jo.archive.ubuntu.com_ubuntu_dists_feisty_universe_fource_Fources > >>- open (2 no such file or directory) Run: apt-get update and try again. Best regards, Lukas -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [orca-list] can't access the package manager to install softwares, orca not speaking.
Janina Sajka writes ("Re: [orca-list] can't access the package manager to
install softwares, orca not speaking."):
> Is synaptek accessible? I am not aware it's been updated to use
> gtk2.
Synaptic uses gtk2 and is accessible. The problem is probably that for
installing packages, one must become root at some point and then, orca
will no longer be able to communicate with the program. A fix for
Feisty has been posted some time ago. It involved adding some lines to
root's .orbitrc file. I have not tried this myself and do not know if
this is still the recommended solution. In this particular case, using
apt-get on the console is probably easier indeed.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: upgrade instructions needed
Jude DaShiell writes ("upgrade instructions needed"):
> Using gnome-orca's screen reader how do I use either apt-get or aptitude
> to get my system from edgeyeft to feisty fawn?
The update instructions for Edgy to Feisty are at:
http://www.ubuntu.com/getubuntu/upgrading
Their is a section called:
"Manual command-line upgrade (not recommended) "
This uses apt-get. Because this is not the recommended way of
updating, I was wondering if the server update method would be
accessible. However, it seems that the required package
"update-manager-core" is not part of Edgy. Has anyone tried to get
this package from Feisty and then followed the instructions on the
above page in the section "Network upgrade for Ubuntu servers,
(recommended) "? To make it clear, I want to update a desktop system,
but consider using the method for servers because I need something
that works from the command line.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Minimal ubiquity frontend (was: Ultimate plans for the sudo fix .orbitrc?)
Al Puzzuoli writes ("Re: Ultimate plans for the sudo fix .orbitrc?"):
> Although the installer is one area where this issue is still a barrier to
> equal access, it is only one of many. For example, consider a typical user
> ...
Hi Al,
Thank you for your reply. I now realize that screen reader access
across user accounts is a general problem that when solved will help
in various areas aprart from mere installation. I guess my problem is
more with the graphical installer itself than with the way it has to
bestartedd. Once started, I found it so unresponsive on slow machines
that it was virtually impossible to get through the steps of the
install. The information actually required from the user is very
little, which is why I would muchlike to have the option of doing even
somthing like:
$ sudo ubiquity text --language English --City Zurich --keyboard de_CH \
--hostname mybox --user jimmy --root-fs /dev/hda5 --swap
/dev/hda6
Then it could ask for jimmy's password and start with the
installation. Where can I find documentation about what methods
aminimal ubiquity frontend must implement?
Thanks and best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Ultimate plans for the sudo fix .orbitrc?
Al Puzzuoli writes ("Ultimate plans for the sudo fix .orbitrc?"):
> Just wondering how the Ubuntu team ultimately plans to handle the sudo
> accessibility stuff for the release of Feisty? The fix to the Gnome
> components themselves is pretty much finished; but, there's still the issue
> of a couple esoteric settings that need to be added to the .orbitrc file of
> the root account's home directory in order for that fix to be relevant.
> Granted, the task of jumping into gnome-terminal and hand creating the needed
> .orbitrc is quite painless for even moderately experienced users of Linux;
> However, if for a few moments, we look at this from the perspective of a
> newbie coming from windows, who has never even seen a dos prompt, and just
> wants to install ubuntu, or perhaps tweak some network settings on an already
> installed system... Well, you only get one chance to make a first impression.
>
Maybe, it would be easier altogether to have a text based alternative frontend
for ubiquity on the live CD, that would simply ask a few questions, maybe with
completion wia readline for things like city and language. I do not
mean a curses application but more like something "orca -t" does. I
looked at the ubiquity source code and it seems one would simply have
to implement a "Frontend" class that implements some interfaces,
though I am not 100 % sure which ones are required for a minimal
frontend. Things like partitioning would have to be done manually before
starting ubiquity with this frontend, so it could be really simple.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Orca on laptops.
Tomas Cerha writes ("Re: Orca on laptops."):
> Hello, I'm using CapsLock as another Ctrl key. It is configurable
> through Gnome keyboard properties dialog (before it was there I used a
> modified xkb layout to achieve that). Without any deeper knowledge, I'd
> assume that this is not a hardware feature, when one is able to remap
> the key easily. Just a hint... Best regards, Tomas.
Indeed, The caps lock key can easily be remapped. I for example use it
as another Control key, because it is more easily reachable than the
one in the bottom left corner of the keyboard. There are plenty of
HowTos on the web that explain how to remap this key both under X and
the Linux console. The locking behaviour is therefore certainly not a
property of the hardware. CapsLock is just like any other key.
The AltGr key is not suitable as a general modifier key for orca on
many international keyboard layouts. It is needed on some layouts to
type characters as common as @ \ | [ ] { } ~ and '.
I would therefore say that CapsLock is the more suitable choice of the
two as a default orca modifier key on laptops.
Best regards, Lukas
--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
