Re: [PATCH v2 07/30] qapi/block-core.json: Use literal block for ascii art

[Samuel Thibault]

Hello,

Philippe Mathieu-Daudé, le lun. 17 févr. 2020 01:44:35 +0100, a ecrit:
> On Sat, Feb 15, 2020 at 10:01 PM Aleksandar Markovic
> <address@hidden> wrote:
> > 9:56 PM Sub, 15.02.2020. Philippe Mathieu-Daudé <address@hidden> је 
> > написао/ла:
> > > On Fri, Feb 14, 2020 at 12:04 AM Aleksandar Markovic
> > > <address@hidden> wrote:
> > > >
> > > > 6:59 PM Čet, 13.02.2020. Peter Maydell <address@hidden> је написао/ла:
> > > > >
> > > > > The ascii-art graph
> > > >
> > > > Just out of couriousity, are unicode characters allowed in rst files?
> > >
> > > I remember 2 years ago a blind developer thanked the QEMU community to
> > > still restrict commits to 80 characters, because while 4K display are
> > > available, he and other visually impaired developers cloud still
> > > browse the QEMU codebase with their refreshable Braille display (which
> > > was 80 cels). I don't know how many visually impaired developers are
> > > following this project. A quick google returns " There is no concept
> > > of Unicode in Braille. In that sense Braille is similar to old 8-bit
> > > code pages which represented different symbols in different languages
> > > for the same symbol code."
> > > (https://superuser.com/questions/629443/represent-unicode-characters-in-braille).
> > >
> > > (I'm Cc'ing Samuel who cares about Braille displays.)

Nowadays' screen reader do provide some translations for some unicode
fancies. But the analogy with codepage remains true: since there are
only 256 braille pattern, there will be ambiguity between representation
of plain text and representation of unicode fancies. Using plain ascii
avoids this issue, i.e. blind developers will know that '|' and '-' are
commonly used for drawing, and their Braille representations are not
ambiguous. So that's indeed better to keep them ascii.

More generally, ascii art is however hard to catch with a Braille device
anyway...

Samuel