Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Fri, Sep 20, 2019 at 8:46 AM Greg Kroah-Hartman wrote: > > On Wed, Sep 18, 2019 at 01:30:33PM -0700, Gregory Nowak wrote: > > > Extra line between each attribute (before the "What:" line) would be > > > nice. > > > > In a previous post above, you wrote: > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > Anyway, please put the Description: lines without a blank after that, > > > with the description text starting on that same line. > > > > I understood that to mean that the description text should start on > > the same line, and the blank lines after the description text should > > be removed. I've put them back in. Someone more familiar with the > > speakup code will have to dig into it to resolve the TODO items I > > suppose. > > No problem, this looks good to me. If someone wants to turn this into a > patch adding it to the drivers/staging/speakup/ directory, I'll be glad > to take it and it will allow others to fill in the TODO entries easier. Thank you. I'll create a patch soon.
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Wed, Sep 18, 2019 at 01:30:33PM -0700, Gregory Nowak wrote: > > Extra line between each attribute (before the "What:" line) would be > > nice. > > In a previous post above, you wrote: > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > Anyway, please put the Description: lines without a blank after that, > > with the description text starting on that same line. > > I understood that to mean that the description text should start on > the same line, and the blank lines after the description text should > be removed. I've put them back in. Someone more familiar with the > speakup code will have to dig into it to resolve the TODO items I > suppose. No problem, this looks good to me. If someone wants to turn this into a patch adding it to the drivers/staging/speakup/ directory, I'll be glad to take it and it will allow others to fill in the TODO entries easier. thanks, greg k-h
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Wed, Sep 18, 2019 at 08:16:42AM +0200, Greg Kroah-Hartman wrote: > On Tue, Sep 17, 2019 at 06:03:53PM -0700, Gregory Nowak wrote: > > On Tue, Sep 17, 2019 at 10:01:18AM +0200, Greg Kroah-Hartman wrote: > > > On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote: > > > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > > > > I have attached the descriptions. > > > > > > > > > > > > Attachment is missing :) > > > > > > > > > > I saw it :) > > > > > > > > > > Anyway, please put the Description: lines without a blank after that, > > > > > with the description text starting on that same line. > > > > > > > > > > thanks! > > > > > > > > > > greg k-h > > > > > > > > It's attached. Hope the indentation is OK. > > > > > > Alignment is a bit off, you forgot a tab after "Description:" > > > > > > And you have some trailing whitespace in the document :( > > > > > > thanks, > > > > > > greg k-h > > > > > > > I put in the tabs after "Description:" and did the best I could to fix > > the alignment, and to find and get rid of the white space. If the > > alignment is still off, or if there is still white space I missed, > > could someone else please correct that? Thanks. > > Extra line between each attribute (before the "What:" line) would be > nice. In a previous post above, you wrote: On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > Anyway, please put the Description: lines without a blank after that, > with the description text starting on that same line. I understood that to mean that the description text should start on the same line, and the blank lines after the description text should be removed. I've put them back in. Someone more familiar with the speakup code will have to dig into it to resolve the TODO items I suppose. On Wed, Sep 18, 2019 at 03:28:05PM +0200, Didier Spaier wrote: > Trailing white spaces removed in attachment. > Alignment LGTM. Thank you. This is the copy I put the blank lines into, and am attaching with the original file name. Greg N -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. What: /sys/accessibility/speakup/bell_pos KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. What: /sys/accessibility/speakup/bleeps KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls whether one hears beeps through the PC speaker when using speakup's review commands. TODO: what values does it accept? What: /sys/accessibility/speakup/bleep_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? What: /sys/accessibility/speakup/cursor_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. What: /sys/accessibility/speakup/delimiters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:TODO: What: /sys/accessibility/speakup/key_echo KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. What: /sys/accessibility/speakup/keymap KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Speakup keymap remaps keys to Speakup functions. It uses a
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Tue, Sep 17, 2019 at 06:03:53PM -0700, Gregory Nowak wrote: > On Tue, Sep 17, 2019 at 10:01:18AM +0200, Greg Kroah-Hartman wrote: > > On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote: > > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > > > I have attached the descriptions. > > > > > > > > > > Attachment is missing :) > > > > > > > > I saw it :) > > > > > > > > Anyway, please put the Description: lines without a blank after that, > > > > with the description text starting on that same line. > > > > > > > > thanks! > > > > > > > > greg k-h > > > > > > It's attached. Hope the indentation is OK. > > > > Alignment is a bit off, you forgot a tab after "Description:" > > > > And you have some trailing whitespace in the document :( > > > > thanks, > > > > greg k-h > > > > I put in the tabs after "Description:" and did the best I could to fix > the alignment, and to find and get rid of the white space. If the > alignment is still off, or if there is still white space I missed, > could someone else please correct that? Thanks. Extra line between each attribute (before the "What:" line) would be nice. Also fixing the TODO items :) thanks, greg k-h
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Tue, Sep 17, 2019 at 10:01:18AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote: > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > > I have attached the descriptions. > > > > > > > > Attachment is missing :) > > > > > > I saw it :) > > > > > > Anyway, please put the Description: lines without a blank after that, > > > with the description text starting on that same line. > > > > > > thanks! > > > > > > greg k-h > > > > It's attached. Hope the indentation is OK. > > Alignment is a bit off, you forgot a tab after "Description:" > > And you have some trailing whitespace in the document :( > > thanks, > > greg k-h > I put in the tabs after "Description:" and did the best I could to fix the alignment, and to find and get rid of the white space. If the alignment is still off, or if there is still white space I missed, could someone else please correct that? Thanks. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. What: /sys/accessibility/speakup/bell_pos KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. What: /sys/accessibility/speakup/bleeps KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls whether one hears beeps through the PC speaker when using speakup's review commands. TODO: what values does it accept? What: /sys/accessibility/speakup/bleep_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? What: /sys/accessibility/speakup/cursor_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. What: /sys/accessibility/speakup/delimiters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:TODO: What: /sys/accessibility/speakup/key_echo KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. What: /sys/accessibility/speakup/keymap KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Speakup keymap remaps keys to Speakup functions. It uses a binary format. A special program called genmap is needed to compile a textual keymap into the binary format which is then loaded into /sys/accessibility/speakup/keymap. What: /sys/accessibility/speakup/no_interrupt KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. What: /sys/accessibility/speakup/punc_all KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description:This is a list of all the punctuation speakup should speak when punc_level is set to four.
Re: Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Ah it looks like the spaces after Description: need to be converted into tabs. Thanks, Okash On Tue, Sep 17, 2019 at 10:35 PM Okash Khawaja wrote: > > Hi Greg, > > You're right, I got none of those emails. Thanks. Is it all taken care of? > > Best regards, > Okash > > On Tue, Sep 17, 2019 at 4:56 AM Gregory Nowak wrote: > > > > Hi Okash, > > I just realized the below didn't go to you directly along with the > > other addresses. > > > > Greg > > > > > > - Forwarded message from Gregory Nowak - > > > > Date: Mon, 16 Sep 2019 15:38:48 -0700 > > From: Gregory Nowak > > To: Greg Kroah-Hartman > > Cc: de...@driverdev.osuosl.org, Simon Dickson , > > "Speakup is a screen review system for Linux." > > , linux-kernel@vger.kernel.org, John > > Covici > > > > Subject: Re: [HELP REQUESTED from the community] Was: Staging status of > > speakup > > > > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > > I have attached the descriptions. > > > > > > > > Attachment is missing :) > > > > > > I saw it :) > > > > > > Anyway, please put the Description: lines without a blank after that, > > > with the description text starting on that same line. > > > > > > thanks! > > > > > > greg k-h > > > > It's attached. Hope the indentation is OK. > > > > Greg > > > > > > -- > > web site: http://www.gregn.net > > gpg public key: http://www.gregn.net/pubkey.asc > > skype: gregn1 > > (authorization required, add me to your contacts list first) > > If we haven't been in touch before, e-mail me before adding me to your > > contacts. > > > > -- > > Free domains: http://www.eu.org/ or mail dns-mana...@eu.org > > > > What: /sys/accessibility/speakup/attrib_bleep > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: Beeps the PC speaker when there is an attribute change such as > > foreground or background color when using speakup review > > commands. One = on, zero = off. > > What: /sys/accessibility/speakup/bell_pos > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: This works much like a typewriter bell. If for example 72 is > > echoed to bell_pos, it will beep the PC speaker when typing > > on > > a line past character 72. > > What: /sys/accessibility/speakup/bleeps > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: This controls whether one hears beeps through the PC speaker > > when using speakup's review commands. > > TODO: what values does it accept? > > What: /sys/accessibility/speakup/bleep_time > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: This controls the duration of the PC speaker beeps speakup > > produces. > > TODO: What are the units? Jiffies? > > What: /sys/accessibility/speakup/cursor_time > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: This controls cursor delay when using arrow keys. When a > > connection is very slow, with the default setting, when > > moving > > with the arrows, or backspacing etc. speakup says the > > incorrect > > characters. Set this to a higher value to adjust for the > > delay > > and better synchronisation between cursor position and > > speech. > > What: /sys/accessibility/speakup/delimiters > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: Delimit a word from speakup. > > TODO: add more info > > What: /sys/accessibility/speakup/ex_num > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: TODO: > > What: /sys/accessibility/speakup/key_echo > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: Controls if speakup speaks keys when they are typed. One = on, > > zero = off or don't echo keys. > > What: /sys/accessibility/speakup/keymap > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: Speakup keymap remaps keys to Speakup functins. It uses a > > binary > > format. A special program called genmap is needed to > > compile a > > textual keymap into the binary format which is then loaded > > into > > /sys/accessibility/speakup/keymap. > > What: /sys/accessibility/speakup/no_interrupt > > KernelVersion: 2.6 > > Contact:spea...@linux-speakup.org > > Description: Controls if typing interrupts output from speakup. With > > no_interrupt set to zero, typing on the keyboard will
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 16, 2019 at 03:38:48PM -0700, Gregory Nowak wrote: > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > > I have attached the descriptions. > > > > > > Attachment is missing :) > > > > I saw it :) > > > > Anyway, please put the Description: lines without a blank after that, > > with the description text starting on that same line. > > > > thanks! > > > > greg k-h > > It's attached. Hope the indentation is OK. Alignment is a bit off, you forgot a tab after "Description:" And you have some trailing whitespace in the document :( thanks, greg k-h
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > > I have attached the descriptions. > > > > Attachment is missing :) > > I saw it :) > > Anyway, please put the Description: lines without a blank after that, > with the description text starting on that same line. > > thanks! > > greg k-h It's attached. Hope the indentation is OK. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. What: /sys/accessibility/speakup/bell_pos KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. What: /sys/accessibility/speakup/bleeps KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This controls whether one hears beeps through the PC speaker when using speakup's review commands. TODO: what values does it accept? What: /sys/accessibility/speakup/bleep_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? What: /sys/accessibility/speakup/cursor_time KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. What: /sys/accessibility/speakup/delimiters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/key_echo KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. What: /sys/accessibility/speakup/keymap KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Speakup keymap remaps keys to Speakup functins. It uses a binary format. A special program called genmap is needed to compile a textual keymap into the binary format which is then loaded into /sys/accessibility/speakup/keymap. What: /sys/accessibility/speakup/no_interrupt KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. What: /sys/accessibility/speakup/punc_all KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: This is a list of all the punctuation speakup should speak when punc_level is set to four. What: /sys/accessibility/speakup/punc_level KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: Controls the level of punctuation spoken as the screen is displayed, not reviewed. Levels range from zero no punctuation, to four, all punctuation. One corresponds to punc_some, two corresponds to punc_most, and three as well as four both correspond to punc_all. Some hardware synthesizers may have different levels each corresponding to three and four for punc_level. Also note that if punc_level is set to zero, and key_echo is set to
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > I have attached the descriptions. > > Attachment is missing :) > > Samuel Samuel, check the message that came to you directly, and it should be there. The speakup list rejects attachments. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 16, 2019 at 03:47:28PM +0200, Samuel Thibault wrote: > Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > > I have attached the descriptions. > > Attachment is missing :) I saw it :) Anyway, please put the Description: lines without a blank after that, with the description text starting on that same line. thanks! greg k-h
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Okash Khawaja, le dim. 15 sept. 2019 19:41:30 +0100, a ecrit: > I have attached the descriptions. Attachment is missing :) Samuel
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Sun, Sep 15, 2019 at 2:43 PM Greg Kroah-Hartman wrote: > > On Sat, Sep 14, 2019 at 10:08:35PM +0100, Okash Khawaja wrote: > > On Mon, Sep 9, 2019 at 3:55 AM Gregory Nowak wrote: > > > > > > On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote: > > > > Sorry, I have only now got round to working on this. It's not complete > > > > yet but I have assimilated the feedback and converted subjective > > > > phrases, like "I think..." into objective statements or put them in > > > > TODO: so that someone else may verify. I have attached it to this > > > > email. > > > > > > I think bleeps needs a TODO, since we don't know what values it accepts, > > > or > > > what difference those values make. Also, to keep things uniform, we > > > should replace my "don't know" for trigger_time with a TODO. Looks > > > good to me otherwise. Thanks. > > > > Great thanks. I have updated. > > > > I have two questions: > > > > 1. Is it okay for these descriptions to go inside > > Documentation/ABI/stable? They have been around since 2.6 (2010). Or > > would we prefer Documentation/ABI/testing/? > > stable is fine. > > thanks, > > greg k-h Thanks Samuel and Greg. I have attached the descriptions. There are still some files marked with TODO, whose descriptions are incomplete or missing. Thanks, Okash sysfs-driver-speakup Description: Binary data
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Sat, Sep 14, 2019 at 10:08:35PM +0100, Okash Khawaja wrote: > On Mon, Sep 9, 2019 at 3:55 AM Gregory Nowak wrote: > > > > On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote: > > > Sorry, I have only now got round to working on this. It's not complete > > > yet but I have assimilated the feedback and converted subjective > > > phrases, like "I think..." into objective statements or put them in > > > TODO: so that someone else may verify. I have attached it to this > > > email. > > > > I think bleeps needs a TODO, since we don't know what values it accepts, or > > what difference those values make. Also, to keep things uniform, we > > should replace my "don't know" for trigger_time with a TODO. Looks > > good to me otherwise. Thanks. > > Great thanks. I have updated. > > I have two questions: > > 1. Is it okay for these descriptions to go inside > Documentation/ABI/stable? They have been around since 2.6 (2010). Or > would we prefer Documentation/ABI/testing/? stable is fine. thanks, greg k-h
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Hello, Okash Khawaja, le sam. 14 sept. 2019 22:08:35 +0100, a ecrit: > 2. We are still missing descriptions for i18n/ directory. I have added > filenames below. can someone can add description please: There are some descriptions in the "14.1. Files Under the i18n Subdirectory" section of spkguide.txt Samuel
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Mon, Sep 9, 2019 at 3:55 AM Gregory Nowak wrote: > > On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote: > > Sorry, I have only now got round to working on this. It's not complete > > yet but I have assimilated the feedback and converted subjective > > phrases, like "I think..." into objective statements or put them in > > TODO: so that someone else may verify. I have attached it to this > > email. > > I think bleeps needs a TODO, since we don't know what values it accepts, or > what difference those values make. Also, to keep things uniform, we > should replace my "don't know" for trigger_time with a TODO. Looks > good to me otherwise. Thanks. Great thanks. I have updated. I have two questions: 1. Is it okay for these descriptions to go inside Documentation/ABI/stable? They have been around since 2.6 (2010). Or would we prefer Documentation/ABI/testing/? 2. We are still missing descriptions for i18n/ directory. I have added filenames below. can someone can add description please: What: /sys/accessibility/speakup/i18n/announcements KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/chartab KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/ctl_keys KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/function_names KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/states KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/characters KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/colors KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/formatted KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/key_names KernelVersion: 2.6 Contact:spea...@linux-speakup.org Description: TODO Thanks, Okash
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote: > Sorry, I have only now got round to working on this. It's not complete > yet but I have assimilated the feedback and converted subjective > phrases, like "I think..." into objective statements or put them in > TODO: so that someone else may verify. I have attached it to this > email. I think bleeps needs a TODO, since we don't know what values it accepts, or what difference those values make. Also, to keep things uniform, we should replace my "don't know" for trigger_time with a TODO. Looks good to me otherwise. Thanks. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Sorry, I have only now got round to working on this. It's not complete yet but I have assimilated the feedback and converted subjective phrases, like "I think..." into objective statements or put them in TODO: so that someone else may verify. I have attached it to this email. Next step will be to convert the format to match Documentation/ABI/ requirements. Thanks, Okash On Wed, Aug 21, 2019 at 11:23 PM Gregory Nowak wrote: > > On Wed, Aug 21, 2019 at 09:39:25AM -0700, Okash Khawaja wrote: > > Hi Greg N, > > > > Would like to send this as a patch as Greg K-H suggested? If not, I > > can do that with your email in Authored-by: tag? > > > > Thanks, > > Okash > > Hi Okash and all, > feel free to submit the patch with my email in the Authored-by: > tag if that's OK. Thanks, and good luck on your presentation. > > Greg > > > -- > web site: http://www.gregn.net > gpg public key: http://www.gregn.net/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > If we haven't been in touch before, e-mail me before adding me to your > contacts. > > -- > Free domains: http://www.eu.org/ or mail dns-mana...@eu.org > ___ > Speakup mailing list > spea...@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup attrib_bleep Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. bell_pos This works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. bleeps This controls whether one hears beeps through the PC speaker when using speakup's review commands. bleep_time This controls the duration of the PC speaker beeps speakup produces. TODO: What are the units? Jiffies? cursor_time This controls cursor delay when using arrow keys. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. Set this to a higher value to adjust for the delay and better synchronisation between cursor position and speech. delimiters Delimit a word from speakup. TODO: add more info ex_num TODO: key_echo Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. keymap Speakup keymap remaps keys to Speakup functins. It uses a binary format. A special program called genmap is needed to compile a textual keymap into the binary format which is then loaded into /sys/accessibility/speakup/keymap. no_interrupt Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. punc_all This is a list of all the punctuation speakup should speak when punc_level is set to four. punc_level Controls the level of punctuation spoken as the screen is displayed, not reviewed. Levels range from zero no punctuation, to four, all punctuation. One corresponds to punc_some, two corresponds to punc_most, and three as well as four both correspond to punc_all. Some hardware synthesizers may have different levels each corresponding to three and four for punc_level. Also note that if punc_level is set to zero, and key_echo is set to one, typed punctuation is still spoken as it is typed. punc_most This is a list of all the punctuation speakup should speak when punc_level is set to two. punc_some This is a list of all the punctuation speakup should speak when punc_level is set to one. reading_punc Almost the same as punc_level, the differences being that reading_punc controls the level of punctuation when reviewing the screen with speakup's screen review commands. The other difference is that reading_punc set to three speaks punc_all, and reading_punc set to four speaks all punctuation, including spaces. repeats A list of characters speakup repeats. Normally, when there are more than three characters in a row, speakup just reads three of those characters. For example, ".." would be read as dot, dot, dot. If a . is added to the list of characters in repeats, ".." would be read as dot, dot, dot, times six. say_control If set to one, speakup speaks shift, alt and control when those keys are pressed. If say_control is set to zero, shift, ctrl, and alt are not spoken when they are pressed. say_word_ctl TODO: silent TODO: spell_delay This controls how fast a word is spelled when speakup's say word review command is pressed twice quickly to speak the current word being reviewed. Zero just speaks the letters one after another, while values one through four seem to introduce more of a pause between the spelling of each letter by speakup. synth
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Wed, Aug 21, 2019 at 09:39:25AM -0700, Okash Khawaja wrote: > Hi Greg N, > > Would like to send this as a patch as Greg K-H suggested? If not, I > can do that with your email in Authored-by: tag? > > Thanks, > Okash Hi Okash and all, feel free to submit the patch with my email in the Authored-by: tag if that's OK. Thanks, and good luck on your presentation. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Thu, Jul 25, 2019 at 3:49 AM John Covici wrote: > > I think the program is genmap, I have it in my init sequence, but I > am not sure it does anything at this point. > > On Thu, 25 Jul 2019 00:04:07 -0400, > Chris Brannon wrote: > > > > Gregory Nowak writes: > > > > > keymap > > > I believe this is the currently active kernel keymap. I'm not sure of > > > the format, probably what dumpkeys(1) and showkey(1) use. Echoing > > > different values here should allow for remapping speakup's review > > > commands besides remapping the keyboard as a whole. > > > > AFAIK the Speakup keymap is just for remapping keys to Speakup > > functions. It's a binary format, not related to dumpkeys etc. You need > > a special program to compile a textual keymap into something that can be > > loaded into /sys/accessibility/speakup/keymap. I may have source for > > that lying around here somewhere. This is "here there be dragons" > > territory. I think the only specification of the format is in the > > source code. > > > > -- Chris > > ___ > > Speakup mailing list > > spea...@linux-speakup.org > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > cov...@ccs.covici.com > ___ > Speakup mailing list > spea...@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup Hi Greg N, Would like to send this as a patch as Greg K-H suggested? If not, I can do that with your email in Authored-by: tag? Thanks, Okash
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
the cursor_time option (I think) controls a cursor delay when you do the arrow keys.I think the delimiters are what delimit a word fr speakup, I changed it to space only, so it would work better for me. On Wed, 24 Jul 2019 23:53:52 -0400, Gregory Nowak wrote: > > On Fri, Jul 12, 2019 at 05:46:23PM -0700, Gregory Nowak wrote: > > On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote: > > > Hello, > > > > > > To readers of the linux-speakup: could you help on this so we can get > > > Speakup in mainline? Neither Okash or I completely know what user > > > consequences the files in /sys/accessibility/speakup/ have, so could > > > people give brief explanations for each file (something like 3-6 lines > > > of explanation)? > > > > I have a recollection of documenting most of this on the speakup list > > in response to a similar query a number of years ago. Unfortunately, > > the speakup mailing list archives aren't easily searchable, and I > > don't have a local copy of that mail. > > > > Kirk, doing grep with a few of the file names in > > /sys/accessibility/speakup against the list's mbox file archive should > > find that message if it's in fact there. If you can please find it, > > and post the date when it was sent, we can provide a URL to that > > thread as a starting point. If my recollection is wrong, and such a > > message isn't in the archives, I'll write up what I know about. > > I've located the message I was thinking of in the archives, but that > describes some speakup key commands, not > /sys/accessibility/speakup. So, here's what I know, and hopefully > someone else can fill in the rest. > > attrib_bleep > Beeps the PC speaker when there is an attribute change such as > foreground or background color when using speakup review commands. One > = on, zero = off. I'm not currently at a machine with a working PC > speaker, so can't test this right now. > > bell_pos > As far as I know, this works much like a typewriter bell. If for > example 72 is echoed to bell_pos, it will beep the PC speaker when > typing on a line past character 72. Again, no PC speaker at the moment > here, so can't actually test this. > > bleeps > Not 100% sure, but I believe this controls whether one hears beeps > through the PC speaker when using speakup's review commands. If no one > jumps in on this, I'll experiment when at a machine with a working PC > speaker, and will reply back with details. > > bleep_time > Again, not 100% sure, but I believe this controls the duration of the > PC speaker beeps speakup produces. I'm not sure of the units this is > in either, possibly jiffys. I'll come back with more details on this > one if no one else does. > > cursor_time > Don't know. > > delimiters > Don't know. I've tried echoing various characters to this and looking > for differences when reviewing the screen, but no luck. > > ex_num > Don't know. > > key_echo > Controls if speakup speaks keys when they are typed. One = on, zero = > off or don't echo keys. > > keymap > I believe this is the currently active kernel keymap. I'm not sure of > the format, probably what dumpkeys(1) and showkey(1) use. Echoing > different values here should allow for remapping speakup's review > commands besides remapping the keyboard as a whole. > > no_interrupt > Controls if typing interrupts output from speakup. With no_interrupt > set to zero, typing on the keyboard will interrupt speakup if for > example the say screen command is used before the entire screen is > read. With no_interrupt set to one, if the say screen command is used, > and one then types on the keyboard, speakup will continue to say the > whole screen regardless until it finishes. > > punc_all > This is a list of all the punctuation speakup should speak when > punc_level is set to four. > > punc_level > Controls the level of punctuation spoken as the screen is displayed, > not reviewed. Levels range from zero no punctuation, to four, all > punctuation. As far as I can tell, one corresponds to punc_some, two > corresponds to punc_most, and three as well as four seem to both > correspond to punc_all, though I do stand to be corrected. I am using > the soft synthesizer driver, so it is possible that some hardware > synthesizers have different levels each corresponding to three and four > for punc_level. Also note that if punc_level is set to zero, and > key_echo is set to one, typed punctuation is still spoken as it is > typed. > > punc_most > This is a list of all the punctuation speakup should speak when > punc_level is set to two. > > punc_some > This is a list of all the punctuation speakup should speak when > punc_level is set to one. > > reading_punc > Almost the same as punc_level, the differences being that reading_punc > controls > the level of punctuation when reviewing the screen with speakup's > screen review commands. The other difference is that reading_punc set > to three speaks punc_all, and reading_punc set to four speaks all >
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
I think the program is genmap, I have it in my init sequence, but I am not sure it does anything at this point. On Thu, 25 Jul 2019 00:04:07 -0400, Chris Brannon wrote: > > Gregory Nowak writes: > > > keymap > > I believe this is the currently active kernel keymap. I'm not sure of > > the format, probably what dumpkeys(1) and showkey(1) use. Echoing > > different values here should allow for remapping speakup's review > > commands besides remapping the keyboard as a whole. > > AFAIK the Speakup keymap is just for remapping keys to Speakup > functions. It's a binary format, not related to dumpkeys etc. You need > a special program to compile a textual keymap into something that can be > loaded into /sys/accessibility/speakup/keymap. I may have source for > that lying around here somewhere. This is "here there be dragons" > territory. I think the only specification of the format is in the > source code. > > -- Chris > ___ > Speakup mailing list > spea...@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Thu, Jul 25, 2019 at 08:11:04AM +0200, Willem van der Walt wrote: > Hi, > I have added a few things inline in Greg's message, mainly regarding the > bleeps and cursor_time. This is a great start, can someone turn this into the correct format that we need for Documentation/ABI/ ? thanks, greg k-h
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Hi, I have added a few things inline in Greg's message, mainly regarding the bleeps and cursor_time. FWIW, Willem On Wed, 24 Jul 2019, Gregory Nowak wrote: [The e-mail server of the sender could not be verified (SPF Record)] On Fri, Jul 12, 2019 at 05:46:23PM -0700, Gregory Nowak wrote: On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote: Hello, To readers of the linux-speakup: could you help on this so we can get Speakup in mainline? Neither Okash or I completely know what user consequences the files in /sys/accessibility/speakup/ have, so could people give brief explanations for each file (something like 3-6 lines of explanation)? I have a recollection of documenting most of this on the speakup list in response to a similar query a number of years ago. Unfortunately, the speakup mailing list archives aren't easily searchable, and I don't have a local copy of that mail. Kirk, doing grep with a few of the file names in /sys/accessibility/speakup against the list's mbox file archive should find that message if it's in fact there. If you can please find it, and post the date when it was sent, we can provide a URL to that thread as a starting point. If my recollection is wrong, and such a message isn't in the archives, I'll write up what I know about. I've located the message I was thinking of in the archives, but that describes some speakup key commands, not /sys/accessibility/speakup. So, here's what I know, and hopefully someone else can fill in the rest. attrib_bleep Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. I'm not currently at a machine with a working PC speaker, so can't test this right now. bell_pos As far as I know, this works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. Again, no PC speaker at the moment here, so can't actually test this. Yes, it works as you say, a verry short beep happens at the echoed position. bleeps Not 100% sure, but I believe this controls whether one hears beeps through the PC speaker when using speakup's review commands. If no one jumps in on this, I'll experiment when at a machine with a working PC speaker, and will reply back with details. Yes, when 0 is echoed to /sys/accessibility/speakup/bleeps, review beeps stop. the default seem to be 3, so I suppose it controls more than just on or off. When set to zero, the bell still sounds when, e.g. in a terminal at a bash prompt, one press backspace. > bleep_time Again, not 100% sure, but I believe this controls the duration of the PC speaker beeps speakup produces. I'm not sure of the units this is in either, possibly jiffys. I'll come back with more details on this one if no one else does. Yes, it seems to control the time as you say, verry small units though. It was 30 and I could set it to 180, but not 360. At 180, the bleeps are clearly a little longer, but not much. cursor_time Don't know. As far as I know, one can set cursor_time to a higher value when working e.g. over a slow connection. When a connection is very slow, with the default setting, when moving with the arrows, or backspacing etc. speakup says the incorrect characters. I am not 100% sure though, but seem to recall having used such a setting in the past when working over dialup. delimiters Don't know. I've tried echoing various characters to this and looking for differences when reviewing the screen, but no luck. ex_num Don't know. key_echo Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. keymap I believe this is the currently active kernel keymap. I'm not sure of the format, probably what dumpkeys(1) and showkey(1) use. Echoing different values here should allow for remapping speakup's review commands besides remapping the keyboard as a whole. no_interrupt Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. punc_all This is a list of all the punctuation speakup should speak when punc_level is set to four. punc_level Controls the level of punctuation spoken as the screen is displayed, not reviewed. Levels range from zero no punctuation, to four, all punctuation. As far as I can tell, one corresponds to punc_some, two corresponds to punc_most, and three as well as four seem to both correspond to punc_all, though I do stand to be corrected. I am using the soft synthesizer driver, so it is possible that some hardware synthesizers have different levels each corresponding to three and four for punc_level. Also note that if
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Gregory Nowak writes: > keymap > I believe this is the currently active kernel keymap. I'm not sure of > the format, probably what dumpkeys(1) and showkey(1) use. Echoing > different values here should allow for remapping speakup's review > commands besides remapping the keyboard as a whole. AFAIK the Speakup keymap is just for remapping keys to Speakup functions. It's a binary format, not related to dumpkeys etc. You need a special program to compile a textual keymap into something that can be loaded into /sys/accessibility/speakup/keymap. I may have source for that lying around here somewhere. This is "here there be dragons" territory. I think the only specification of the format is in the source code. -- Chris
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Fri, Jul 12, 2019 at 05:46:23PM -0700, Gregory Nowak wrote: > On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote: > > Hello, > > > > To readers of the linux-speakup: could you help on this so we can get > > Speakup in mainline? Neither Okash or I completely know what user > > consequences the files in /sys/accessibility/speakup/ have, so could > > people give brief explanations for each file (something like 3-6 lines > > of explanation)? > > I have a recollection of documenting most of this on the speakup list > in response to a similar query a number of years ago. Unfortunately, > the speakup mailing list archives aren't easily searchable, and I > don't have a local copy of that mail. > > Kirk, doing grep with a few of the file names in > /sys/accessibility/speakup against the list's mbox file archive should > find that message if it's in fact there. If you can please find it, > and post the date when it was sent, we can provide a URL to that > thread as a starting point. If my recollection is wrong, and such a > message isn't in the archives, I'll write up what I know about. I've located the message I was thinking of in the archives, but that describes some speakup key commands, not /sys/accessibility/speakup. So, here's what I know, and hopefully someone else can fill in the rest. attrib_bleep Beeps the PC speaker when there is an attribute change such as foreground or background color when using speakup review commands. One = on, zero = off. I'm not currently at a machine with a working PC speaker, so can't test this right now. bell_pos As far as I know, this works much like a typewriter bell. If for example 72 is echoed to bell_pos, it will beep the PC speaker when typing on a line past character 72. Again, no PC speaker at the moment here, so can't actually test this. bleeps Not 100% sure, but I believe this controls whether one hears beeps through the PC speaker when using speakup's review commands. If no one jumps in on this, I'll experiment when at a machine with a working PC speaker, and will reply back with details. bleep_time Again, not 100% sure, but I believe this controls the duration of the PC speaker beeps speakup produces. I'm not sure of the units this is in either, possibly jiffys. I'll come back with more details on this one if no one else does. cursor_time Don't know. delimiters Don't know. I've tried echoing various characters to this and looking for differences when reviewing the screen, but no luck. ex_num Don't know. key_echo Controls if speakup speaks keys when they are typed. One = on, zero = off or don't echo keys. keymap I believe this is the currently active kernel keymap. I'm not sure of the format, probably what dumpkeys(1) and showkey(1) use. Echoing different values here should allow for remapping speakup's review commands besides remapping the keyboard as a whole. no_interrupt Controls if typing interrupts output from speakup. With no_interrupt set to zero, typing on the keyboard will interrupt speakup if for example the say screen command is used before the entire screen is read. With no_interrupt set to one, if the say screen command is used, and one then types on the keyboard, speakup will continue to say the whole screen regardless until it finishes. punc_all This is a list of all the punctuation speakup should speak when punc_level is set to four. punc_level Controls the level of punctuation spoken as the screen is displayed, not reviewed. Levels range from zero no punctuation, to four, all punctuation. As far as I can tell, one corresponds to punc_some, two corresponds to punc_most, and three as well as four seem to both correspond to punc_all, though I do stand to be corrected. I am using the soft synthesizer driver, so it is possible that some hardware synthesizers have different levels each corresponding to three and four for punc_level. Also note that if punc_level is set to zero, and key_echo is set to one, typed punctuation is still spoken as it is typed. punc_most This is a list of all the punctuation speakup should speak when punc_level is set to two. punc_some This is a list of all the punctuation speakup should speak when punc_level is set to one. reading_punc Almost the same as punc_level, the differences being that reading_punc controls the level of punctuation when reviewing the screen with speakup's screen review commands. The other difference is that reading_punc set to three speaks punc_all, and reading_punc set to four speaks all punctuation, including spaces. repeats a list of characters speakup repeats. Normally, when there are more than three characters in a row, speakup just reads three of those characters. For example, ".." would be read as dot, dot, dot. If a . is added to the list of characters in repeats, ".." would be read as dot, dot, dot, times six. say_control If set to one, speakup speaks shift, alt and control when those keys are pressed. Perhaps more keys are spoken, but those three are
Re: [HELP REQUESTED from the community] Was: Staging status of speakup
On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote: > Hello, > > To readers of the linux-speakup: could you help on this so we can get > Speakup in mainline? Neither Okash or I completely know what user > consequences the files in /sys/accessibility/speakup/ have, so could > people give brief explanations for each file (something like 3-6 lines > of explanation)? I have a recollection of documenting most of this on the speakup list in response to a similar query a number of years ago. Unfortunately, the speakup mailing list archives aren't easily searchable, and I don't have a local copy of that mail. Kirk, doing grep with a few of the file names in /sys/accessibility/speakup against the list's mbox file archive should find that message if it's in fact there. If you can please find it, and post the date when it was sent, we can provide a URL to that thread as a starting point. If my recollection is wrong, and such a message isn't in the archives, I'll write up what I know about. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
[HELP REQUESTED from the community] Was: Staging status of speakup
Hello, To readers of the linux-speakup: could you help on this so we can get Speakup in mainline? Neither Okash or I completely know what user consequences the files in /sys/accessibility/speakup/ have, so could people give brief explanations for each file (something like 3-6 lines of explanation)? The i18n/ files have been already documented in section 14.1 of the spkguide.txt, so we do not need help for them. Thanks! Samuel Greg KH, le ven. 12 juil. 2019 10:38:19 +0200, a ecrit: > Can you make up a patch to create a > drivers/staging/speakup/sysfs-speakup file with the needed information? > That way it will be much easier to determine exactly what these sysfs > files do and my review can be easier, and perhaps not needed at all :)
