lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210601215843.ajebgifrgm2mth5t@begin>
Date:   Tue, 1 Jun 2021 23:58:44 +0200
From:   Samuel Thibault <samuel.thibault@...-lyon.org>
To:     Jani Nikula <jani.nikula@...ux.intel.com>
Cc:     Igor Torrente <igormtorrente@...il.com>, corbet@....net,
        gregkh@...uxfoundation.org, grandmaster@...klimov.de,
        rdunlap@...radead.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] docs: Convert the Speakup guide to rst

Jani Nikula, le mar. 01 juin 2021 18:51:49 +0300, a ecrit:
> On Tue, 01 Jun 2021, Igor Torrente <igormtorrente@...il.com> wrote:
> > There's a way to do that without these blank lines?
> >
> > For me, it doesn't look very good, but I think the tradeoff worth it 
> > improves readability to speakup users. If it is the case.
> 
> I was thinking:
> 
> acntsa
>   Accent SA
> 
> acntpc
>   Accent PC
> 
> apollo
>   Apollo

Having the two pieces on separate lines makes it a bit more tedious to
read on Braille displays, it's better to keep them single-line.

> >>> +
> >>> +.. note::
> >>> +
> >>> +   | Speakup does **NOT** support usb connections!
> >>> +   | Speakup also does **NOT** support the internal Tripletalk!
> >> 
> >> Why the pipes "|"?
> >
> > This is the way I found to separate these sentences into two different 
> > lines. I'm gladly accepting a better solution for this :)
> 
> Maybe just like this?
> 
> .. note::
> 
>    Speakup does **NOT** support usb connections!
> 
>    Speakup also does **NOT** support the internal Tripletalk!

That will be fine (though the first statement is actually outdated)

Samuel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ