Hello Samuel,
Executive summary:
All test cases I used with mini.iso passed in that once a sound card
selection was made that sound card selection was allowed into the
installer proper.
Details:
Case 1: logitech only connected to computer,
case 2: usb speakers only connected to computer,
Case
Le 28/11/2016 à 01:18, Samuel Thibault a écrit :
> MENGUAL Jean-Philippe, on Sun 27 Nov 2016 03:07:31 +0100, wrote:
>> But I'd like to know how we could implement chromevox.
>
> I guess you mean package it? Well, I guess there are ways to package
> chromium plugins, it's "just" a matter of doin
MENGUAL Jean-Philippe, on Sun 27 Nov 2016 03:07:31 +0100, wrote:
> But I'd like to know how we could implement chromevox.
I guess you mean package it? Well, I guess there are ways to package
chromium plugins, it's "just" a matter of doing it.
Samuel
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Nov 2016 00:30:23 +0100
Source: espeakup
Binary: espeakup espeakup-udeb
Architecture: source amd64
Version: 1:0.80-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team
Changed-By: Samu
espeakup_0.80-3_amd64.changes uploaded successfully to localhost
along with the files:
espeakup_0.80-3.dsc
espeakup_0.80-3.debian.tar.xz
espeakup-dbgsym_0.80-3_amd64.deb
espeakup-udeb_0.80-3_amd64.udeb
espeakup_0.80-3_amd64.buildinfo
espeakup_0.80-3_amd64.deb
Greetings,
Your D
Hello,
Jude DaShiell, on Sun 27 Nov 2016 16:59:20 -0500, wrote:
> No speech from the installer either.
Ok.
I have checked with other setups, and in some cases there is a race
indeed. I have fixed it, could you test this image:
http://dept-info.labri.fr/~thibault/tmp/mini.iso
Samuel
Le 27/11/2016 à 22:05, Jude DaShiell a écrit :
>> From my braille notes:
> 1) download:
> http://the-brannons.com/kgejglhpjiefppelpmljglcjbhoiplfn.json
Done
> 2) as root or equivalent:
> mkdir /usr/lib/chromium-browser/extensions
Done, but rather /usr/lib/chromium instead of chromium-browser,
Last time I did this it was on talkingarch, and the classic chromevox
came up so far as I could tell. A way may exist to turn on
chromevox-next once chromevox-classic is running, but this is something
I do not yet know if it is possible or how to do that. If the chromevox
tutorial was updated
No speech from the installer either. In all failure cases, I never
produced an installed system.
On Sun, 27 Nov 2016, Samuel Thibault wrote:
Date: Sun, 27 Nov 2016 15:50:09
From: Samuel Thibault
To: debian-accessibility@lists.debian.org
Subject: Re: stretch testing sound card picker finding
Jude DaShiell wrote:
> I forgot one critical detail, copy .json file you downloaded to
> /usr/lib/chromium-browser/extensions/ before downloading and installing
> chromium.
Does this give you the "classic" version of ChromeVox, or the new one (known
as ChromeVox Next), which will replace the for
From my braille notes:
1) download:
http://the-brannons.com/kgejglhpjiefppelpmljglcjbhoiplfn.json
2) as root or equivalent:
mkdir /usr/lib/chromium-browser/extensions
3) download chromium package.
4) run chromium package and wait since the first time it runs it will
download then start up chrom
I forgot one critical detail, copy .json file you downloaded to
/usr/lib/chromium-browser/extensions/ before downloading and installing
chromium.
On Sun, 27 Nov 2016, MENGUAL Jean-Philippe wrote:
Date: Sat, 26 Nov 2016 21:07:31
From: MENGUAL Jean-Philippe
To: Debian Accessibility Team
Subje
Hello,
Jude DaShiell, on Sun 27 Nov 2016 15:45:46 -0500, wrote:
> Result: failure, though I got the message to select the correct sound
> board the rest of debian did not come up speaking for installation.
Do you mean that you got speech from within the installer, but you didn't
get speech fr
Hardware used:
a set of logitech 3.5MM jack connected speakers,
a set of usb power and data connected speakers,
Test cases:
1) logitech speakers only connected through center plug on sound card.
Result: success sound board was detected and once selected the rest of
debian came up talking for
Thanks.
--
Your message dated Sun, 27 Nov 2016 15:07:13 +0100
with message-id <20161127140713.gj8...@var.home>
and subject line Re: Bug#845758: espeak-ng: please provide espeak
has caused the Debian Bug report #845758,
regarding espeak-ng: please provide espeak
to be marked as done.
This means that you claim
"Then, tell me how to get VMWare, or/and how to make VBox accessible."
excuse me?
the vmware gui are accessible
i dont remember if virtualbox gui are accessible
Den 2016-11-27 kl. 13:18, skrev Odd Martin Baanrud:
On 11/27/2016 01:03 PM, mattias wrote:
what? have debian team removed the --
On 11/27/2016 01:03 PM, mattias wrote:
> what? have debian team removed the --curses switch from qemu?
Maintainers doesn't remove anything from binaries.
> why use qemu anyway?
Because it's accessible.
> use vmware instead or virtualbox
Then, tell me how to get VMWare, or/and how to make VBox
what? have debian team removed the --curses switch from qemu?
why use qemu anyway?
use vmware instead or virtualbox
because qemu are slow
ok ok qemu vms are easy backed up
Den 2016-11-27 kl. 12:59, skrev Odd Martin Baanrud:
Hello,
On 11/27/2016 01:11 AM, Samuel Thibault wrote:
Why maki
Hello,
On 11/27/2016 01:11 AM, Samuel Thibault wrote:
> Why making it off-list?
As far as I understand, a qemu VM is built using a huge bunch of
options, and I thaught such a discussion was a bit off topic according
to accessibility.
Do I missunderstand something?
I mean, is a VM actually built
20 matches
Mail list logo
