On Wed, Jun 20, 2018 at 10:59:08PM -0400, Nicolas Pitre wrote:
> On Thu, 21 Jun 2018, Adam Borowski wrote:
>
> > On Tue, Jun 19, 2018 at 11:34:34AM -0400, Nicolas Pitre wrote:
> > > On Tue, 19 Jun 2018, Adam Borowski wrote:
> > > > Thus, it'd be nice to use the structure you add to implement full
On Fri, 22 Jun 2018 12:28:17 -0400 (EDT)
Nicolas Pitre wrote:
> On Fri, 22 Jun 2018, Alan Cox wrote:
>
> > > The other point is a quite pointless assumption that existing scrollback
> > > is
> > > "optimized". Even vgacon mostly uses software scrollback these days, as
> > > the
> > > amount o
On Fri, 22 Jun 2018, Alan Cox wrote:
> > The other point is a quite pointless assumption that existing scrollback is
> > "optimized". Even vgacon mostly uses software scrollback these days, as the
> > amount of VGA display memory is really small.
>
> All of our console driver code is horribly un
> The other point is a quite pointless assumption that existing scrollback is
> "optimized". Even vgacon mostly uses software scrollback these days, as the
> amount of VGA display memory is really small.
All of our console driver code is horribly unoptimized for most of
todays hardware. Long ago
Adam Borowski, le ven. 22 juin 2018 03:54:45 +0200, a ecrit:
> if the former, this is my way to show you how actual Latin letters
> look like, without a lengthy description of letter shapes. :) )
What will unfortunately not work: braille displays only show one line at
a time, so they can't show th
On Wed, Jun 20, 2018 at 10:21:37PM -0400, Dave Mielke wrote:
> [quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>
> >It's meant for displaying braille to _sighted_ people. And in real world,
> >the main [ab]use is a way to show images that won't get corrupted by
> >proportional fonts.
On Wed, 20 Jun 2018, Dave Mielke wrote:
> [quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>
> >It's meant for displaying braille to _sighted_ people. And in real world,
> >the main [ab]use is a way to show images that won't get corrupted by
> >proportional fonts. :-þ
>
> It's not a
On Thu, 21 Jun 2018, Adam Borowski wrote:
> On Tue, Jun 19, 2018 at 11:34:34AM -0400, Nicolas Pitre wrote:
> > On Tue, 19 Jun 2018, Adam Borowski wrote:
> > > Thus, it'd be nice to use the structure you add to implement full Unicode
> > > range for the vast majority of people. This includes even
[quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>It's meant for displaying braille to _sighted_ people. And in real world,
>the main [ab]use is a way to show images that won't get corrupted by
>proportional fonts. :-þ
It's not abuse at all. I often use U+28xx to show sighted people
On Tue, Jun 19, 2018 at 11:34:34AM -0400, Nicolas Pitre wrote:
> On Tue, 19 Jun 2018, Adam Borowski wrote:
> > Thus, it'd be nice to use the structure you add to implement full Unicode
> > range for the vast majority of people. This includes even U+2800..FF. :)
>
> Be my guest if you want to use
On Tue, 19 Jun 2018, Adam Borowski wrote:
> On Sun, Jun 17, 2018 at 03:07:02PM -0400, Nicolas Pitre wrote:
> > The vt code translates UTF-8 strings into glyph index values and stores
> > those glyph values directly in the screen buffer. Because there can only
> > be at most 512 glyphs, it is impos
[quoted lines by Adam Borowski on 2018/06/19 at 17:14 +0200]
>> Not at all. We braille users, especially when working with languages other
>> than
>> English, need more than 256 non-braille characters. Even for those who can
>> live
>> with just 256 non-braille characters, it's still a major pai
On Tue, Jun 19, 2018 at 09:52:13AM -0400, Dave Mielke wrote:
> [quoted lines by Adam Borowski on 2018/06/19 at 15:09 +0200]
>
> >You're thinking small. That 256 possible values for Braille are easily
> >encodable within the 512-glyph space (256 char + stolen fg brightness bit,
> >another CGA pecu
[quoted lines by Adam Borowski on 2018/06/19 at 15:09 +0200]
>You're thinking small. That 256 possible values for Braille are easily
>encodable within the 512-glyph space (256 char + stolen fg brightness bit,
>another CGA peculiarity).
Not at all. We braille users, especially when working with
On Sun, Jun 17, 2018 at 03:07:02PM -0400, Nicolas Pitre wrote:
> The vt code translates UTF-8 strings into glyph index values and stores
> those glyph values directly in the screen buffer. Because there can only
> be at most 512 glyphs, it is impossible to represent most unicode
> characters, in wh
15 matches
Mail list logo
