linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@gregn.net>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Igor Matheus Andrade Torrente <igormtorrente@gmail.com>,
	speakup@linux-speakup.org, corbet@lwn.net,
	gregkh@linuxfoundation.org, grandmaster@al2klimov.de,
	rdunlap@infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: docs: Convert the Speakup guide to rst
Date: Mon, 31 May 2021 16:15:15 -0700	[thread overview]
Message-ID: <20210531231515.GB8130@gregn.net> (raw)
In-Reply-To: <20210531220754.h4ep2dj65wl6hejf@begin>

On Tue, Jun 01, 2021 at 12:07:54AM +0200, Samuel Thibault wrote:
> Mmm, I'm unsure how the result is readable with the speakup screen
> reader itself. I have attached the result, could people on the speakup
> mailing list check how well it goes? If it significantly degrades
> readability, we'll have to reject the move to rst formatting, since in
> the end it's people who use the speakup screen reader who need to be
> able to read this document.

It sounds OK to me with punctuation level set to 1, and using software
synthesis through espeakup. The formatting could be a problem if
someone is using a higher punctuation level, or a braille
display. Could a txtdocs option be implemented as a documentation
target for kernel builds, which would produce plain text files? That I
think would provide the best of both worlds where the guide could be
maintained as RST, but could be output in plain text like the format
the guide exists in now.

Another concern is that if the speakup guide is maintained in RST,
that could dissuade others from keeping it updated who don't already
know RST.

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-manager@EU.org

  parent reply	other threads:[~2021-05-31 23:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 21:57 [PATCH v2] docs: Convert the Speakup guide to rst Igor Matheus Andrade Torrente
2021-05-31 22:07 ` Samuel Thibault
2021-05-31 22:40   ` Chime Hart
2021-05-31 22:42   ` Didier Spaier
2021-05-31 22:44     ` Samuel Thibault
2021-05-31 22:54       ` Samuel Thibault
     [not found]     ` <648b7668-1aa8-dc1d-c92e-7dfc8d3270a7@slint.fr>
2021-05-31 23:03       ` Didier Spaier
2021-06-01  2:11     ` Chris Brannon
2021-05-31 23:15   ` Gregory Nowak [this message]
2021-05-31 23:19     ` Samuel Thibault
2021-05-31 23:29     ` Didier Spaier
2021-05-31 23:39       ` Samuel Thibault
2021-05-31 23:31   ` Alexander Epaneshnikov
2021-06-01  4:17   ` Tom Fowle
2021-06-01 15:39   ` Igor Torrente
2021-06-01 21:55     ` Samuel Thibault
2021-06-01 23:32       ` Igor Torrente
2021-06-02 12:27         ` Jani Nikula
2021-06-02 13:38           ` Igor Torrente
2021-06-01 11:28 ` [PATCH v2] " Jani Nikula
2021-06-01 15:11   ` Igor Torrente
2021-06-01 15:51     ` Jani Nikula
2021-06-01 21:58       ` Samuel Thibault
2021-06-01 21:57     ` Samuel Thibault
2021-06-01 23:43       ` Igor Torrente
2021-06-01 18:53 ` Jonathan Corbet
2021-06-01 22:06   ` Samuel Thibault
2021-06-01 22:18     ` Jonathan Corbet
2021-06-01 22:37       ` Samuel Thibault
2021-06-01 22:44         ` Samuel Thibault
2021-06-01 22:45           ` Samuel Thibault
2021-06-01 22:48             ` Samuel Thibault
2021-06-02  0:54               ` Kirk Reiser
2021-06-02  0:55                 ` Kirk Reiser
2021-06-01 22:47         ` Jonathan Corbet
2021-06-02  6:47           ` Samuel Thibault
2021-06-02  2:54         ` Chris Brannon
2021-06-02  6:46           ` Samuel Thibault
2021-06-04 13:21       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210531231515.GB8130@gregn.net \
    --to=greg@gregn.net \
    --cc=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=igormtorrente@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).