Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp220722ybe; Wed, 18 Sep 2019 15:58:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqwwq+4f+2Ierhgp4lY9Ynj1WlHGHcXi2ddKWU9dxoxzbcDrT/g9bfpU36my4ZR8JmSZi3XP X-Received: by 2002:a50:eb41:: with SMTP id z1mr209462edp.261.1568847481542; Wed, 18 Sep 2019 15:58:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568847481; cv=none; d=google.com; s=arc-20160816; b=jcW0Gu4JDlWsDEwSi6Dd32BrhwmxXsvGf+FYgwV4co2VHm3XwG8Rmt2PcRY29G/hDv 7aoF1t48rIVp1GlnQ5lIJiaEqU4CVb/K3wSPcqJU5/rehMOnRjFkWbrkdSPMtLyOKTu5 h+Iqrvgejq9iX/B6JNYozLqZz7C2cwhAKExK5LXg52+OgnV5h6zNCsKuIZyw7PDSdacF 6R0Etki2x665CbsXoKSyPuFBhWKCZ1Ig4ma/OhfHtwMRMBdBajuGC9WPPl1h9fXVoNOs 3YtFSATF0B7O17gZeyN5PbHxy/5yfEwR2B2yB17PD9KxpQc8acGSQCdNGFWSR9EceaHB Jp4Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=cLMxxCxK6M6/OVPVprkH2YSV88F9BnnAK9rx6Uzo/kI=; b=x1xnVRT3LqtGRo/kOKsMneAFLL/dnTt3Udn5Pq7Zod+6QABWl3cihlA9/SZCxlHaNr jeYLb+I6TzfHV2eDMtSJGmlR3osON7e36c/t+6ivF15s5FDQy0L/famiDJwuJhPrNPSq JMUH6mOOI8KNkAgqo/OzdzFRjkvAdAzNkak9ugShHBR+4EFOovC/VlNmsQY49Rn05fO/ /prFa0Rsmk0jb1t/cZLnEAy21FI6NlPJhA+xeVF661mVVuGojr2ZCwBnGNgLlBHSvowk I3Z1HvADVp42UXCE4IQTv6qluXnY+ldgJhI/YBT3E5ZuxUO+yW8D6LNmayl7yjXW3mQ6 5bNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gregn.net header.s=default header.b="cs/KMyjk"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w34si4316563edc.252.2019.09.18.15.57.38; Wed, 18 Sep 2019 15:58:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gregn.net header.s=default header.b="cs/KMyjk"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387742AbfIRUai (ORCPT + 99 others); Wed, 18 Sep 2019 16:30:38 -0400 Received: from vserver.gregn.net ([174.136.110.154]:47672 "EHLO vserver.gregn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387578AbfIRUag (ORCPT ); Wed, 18 Sep 2019 16:30:36 -0400 Received: from vbox.gregn.net (unknown [IPv6:2001:470:d:6c5:185f:e355:60da:a61d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vserver.gregn.net (Postfix) with ESMTPSA id A857A97E; Wed, 18 Sep 2019 13:31:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gregn.net; s=default; t=1568838676; bh=SdzKzMSnWRvOGZKprIQTs1ghm+tx+9uH09FSIY/XCUA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cs/KMyjkbD8qJBnWcnZsuz2EI25Pks7xxNr4W3WfSaDQQgPFTA5LtlZhJA7FrUcfr bPQk1jA2FacNt5vcX2FEhFkYXHKgGgjGai7PQC/X4VidrgQHa0w2LYxYxx0KX+jNLB d7VmqneOQwRcjWTWnOJs63/1EG/zfcq+Bb3tOiso500gyUNPfwh5DtG6GJx4yofwro YJWbm40p6wAGSWCaKqhE3qeGLa08qXxF8TarQ5A/xvB0ShAID4KXyPNtgDvyBxSZCY 1tiYfONAvoILKXQNQ9Hms7Izvbx6V3Ne91O3Cziia6UW2xqFnfhFaLLGToE2/EBLC7 kFadPnZePkDfQ== Received: from greg by vbox.gregn.net with local (Exim 4.84_2) (envelope-from ) id 1iAgav-0001eG-SS; Wed, 18 Sep 2019 13:30:33 -0700 Date: Wed, 18 Sep 2019 13:30:33 -0700 From: Gregory Nowak To: Greg Kroah-Hartman Cc: devel@driverdev.osuosl.org, Simon Dickson , "Speakup is a screen review system for Linux." , linux-kernel@vger.kernel.org, John Covici , Samuel Thibault , okash.khawaja@gmail.com, Didier Spaier Subject: Re: [HELP REQUESTED from the community] Was: Staging status of speakup Message-ID: <20190918203032.GA3987@gregn.net> References: <20190909025429.GA4144@gregn.net> <20190915134300.GA552892@kroah.com> <20190916134727.4gi6rvz4sm6znrqc@function> <20190916141100.GA1595107@kroah.com> <20190916223848.GA8679@gregn.net> <20190917080118.GC2075173@kroah.com> <20190918010351.GA10455@gregn.net> <20190918061642.GB1832786@kroah.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <20190918061642.GB1832786@kroah.com> X-PGP-Key: http://www.gregn.net/pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-Virus-Scanned: clamav-milter 0.101.4 at vserver X-Virus-Status: Clean Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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-manager@EU.org --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=sysfs-driver-speakup What: /sys/accessibility/speakup/attrib_bleep KernelVersion: 2.6 Contact: speakup@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: speakup@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: speakup@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: speakup@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: speakup@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: speakup@linux-speakup.org Description: Delimit a word from speakup. TODO: add more info What: /sys/accessibility/speakup/ex_num KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/key_echo KernelVersion: 2.6 Contact: speakup@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: speakup@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: speakup@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: speakup@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: speakup@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 one, typed punctuation is still spoken as it is typed. What: /sys/accessibility/speakup/punc_most KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This is a list of all the punctuation speakup should speak when punc_level is set to two. What: /sys/accessibility/speakup/punc_some KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This is a list of all the punctuation speakup should speak when punc_level is set to one. What: /sys/accessibility/speakup/reading_punc KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: 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. What: /sys/accessibility/speakup/repeats KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: 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. What: /sys/accessibility/speakup/say_control KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: 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. What: /sys/accessibility/speakup/say_word_ctl KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/silent KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/spell_delay KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: 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. What: /sys/accessibility/speakup/synth KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the synthesizer driver currently in use. Reading synth returns the synthesizer driver currently in use. Writing synth switches to the given synthesizer driver, provided it is either built into the kernel, or already loaded as a module. What: /sys/accessibility/speakup/synth_direct KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Sends whatever is written to synth_direct directly to the speech synthesizer in use, bypassing speakup. This could be used to make the synthesizer speak a string, or to send control sequences to the synthesizer to change how the synthesizer behaves. What: /sys/accessibility/speakup/version KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Reading version returns the version of speakup, and the version of the synthesizer driver currently in use. What: /sys/accessibility/speakup/i18n/announcements KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This file contains various general announcements, most of which cannot be categorized. You will find messages such as "You killed Speakup", "I'm alive", "leaving help", "parked", "unparked", and others. You will also find the names of the screen edges and cursor tracking modes here. What: /sys/accessibility/speakup/i18n/chartab KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO What: /sys/accessibility/speakup/i18n/ctl_keys KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Here, you will find names of control keys. These are used with Speakup's say_control feature. What: /sys/accessibility/speakup/i18n/function_names KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Here, you will find a list of names for Speakup functions. These are used by the help system. For example, suppose that you have activated help mode, and you pressed keypad 3. Speakup says: "keypad 3 is character, say next." The message "character, say next" names a Speakup function, and it comes from this function_names file. What: /sys/accessibility/speakup/i18n/states KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This file contains names for key states. Again, these are part of the help system. For instance, if you had pressed speakup + keypad 3, you would hear: "speakup keypad 3 is go to bottom edge." The speakup key is depressed, so the name of the key state is speakup. This part of the message comes from the states collection. What: /sys/accessibility/speakup/i18n/characters KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Through this sys entry, Speakup gives you the ability to change how Speakup pronounces a given character. You could, for example, change how some punctuation characters are spoken. You can even change how Speakup will pronounce certain letters. For further details see '12. Changing the Pronunciation of Characters' in Speakup User's Guide (file spkguide.txt in source). What: /sys/accessibility/speakup/i18n/colors KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: When you use the "say attributes" function, Speakup says the name of the foreground and background colors. These names come from the i18n/colors file. What: /sys/accessibility/speakup/i18n/formatted KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This group of messages contains embedded formatting codes, to specify the type and width of displayed data. If you change these, you must preserve all of the formatting codes, and they must appear in the order used by the default messages. What: /sys/accessibility/speakup/i18n/key_names KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Again, key_names is used by Speakup's help system. In the previous example, Speakup said that you pressed "keypad 3." This name came from the key_names file. What: /sys/accessibility/speakup// KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: In `/sys/accessibility/speakup` is a directory corresponding to the synthesizer driver currently in use (E.G) `soft` for the soft driver. This directory contains files which control the speech synthesizer itself, as opposed to controlling the speakup screen reader. The parameters in this directory have the same names and functions across all supported synthesizers. The range of values for freq, pitch, rate, and vol is the same for all supported synthesizers, with the given range being internally mapped by the driver to more or less fit the range of values supported for a given parameter by the individual synthesizer. Below is a description of values and parameters for soft synthesizer, which is currently the most commonly used. What: /sys/accessibility/speakup/soft/caps_start KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This is the string that is sent to the synthesizer to cause it to start speaking uppercase letters. For the soft synthesizer and most others, this causes the pitch of the voice to rise above the currently set pitch. What: /sys/accessibility/speakup/soft/caps_stop KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This is the string sent to the synthesizer to cause it to stop speaking uppercase letters. In the case of the soft synthesizer and most others, this returns the pitch of the voice down to the currently set pitch. What: /sys/accessibility/speakup/soft/delay_time KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/soft/direct KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Controls if punctuation is spoken by speakup, or by the synthesizer. For example, speakup speaks ">" as "greater", while the espeak synthesizer used by the soft driver speaks "greater than". Zero lets speakup speak the punctuation. One lets the synthesizer itself speak punctuation. What: /sys/accessibility/speakup/soft/freq KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the frequency of the speech synthesizer. Range is 0-9. What: /sys/accessibility/speakup/soft/full_time KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/soft/jiffy_delta KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: This controls how many jiffys the kernel gives to the synthesizer. Setting this too high can make a system unstable, or even crash it. What: /sys/accessibility/speakup/soft/pitch KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the pitch of the synthesizer. The range is 0-9. What: /sys/accessibility/speakup/soft/punct KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the amount of punctuation spoken by the synthesizer. The range for the soft driver seems to be 0-2. TODO: How is this related to speakup's punc_level, or reading_punc. What: /sys/accessibility/speakup/soft/rate KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the rate of the synthesizer. Range is from zero slowest, to nine fastest. What: /sys/accessibility/speakup/soft/tone KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the tone of the speech synthesizer. The range for the soft driver seems to be 0-2. This seems to make no difference if using espeak and the espeakup connector. TODO: does espeakup support different tonalities? What: /sys/accessibility/speakup/soft/trigger_time KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: TODO: What: /sys/accessibility/speakup/soft/voice KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the voice used by the synthesizer if the synthesizer can speak in more than one voice. The range for the soft driver is 0-7. Note that while espeak supports multiple voices, this parameter will not set the voice when the espeakup connector is used between speakup and espeak. What: /sys/accessibility/speakup/soft/vol KernelVersion: 2.6 Contact: speakup@linux-speakup.org Description: Gets or sets the volume of the speech synthesizer. Range is 0-9, with zero being the softest, and nine being the loudest. --qDbXVdCdHGoSgWSk--