Text-mode apps (Was :Who are the "spacists"?)

Mikhail V mikhailwas at gmail.com
Sat Apr 1 17:40:33 EDT 2017


On 1 April 2017 at 22:57, Chris Angelico <rosuav at gmail.com> wrote:
> On Sun, Apr 2, 2017 at 6:07 AM, Mikhail V <mikhailwas at gmail.com> wrote:
>> On 1 April 2017 at 06:38, Rick Johnson <rantingrickjohnson at gmail.com> wrote:
>>> On Thursday, March 30, 2017 at 9:14:54 AM UTC-5, Steve D'Aprano wrote:
>>
>>>> - and making band names look ǨØØĻ and annoy old fuddy-
>>>> duddies.
>>>
>>> So now we've even included graffiti artists in our little
>>> "inclusivity project". My, my... we are so _not_ mean!
>>
>> Lol :)  First we'll wait for Unicode version with
>> table-drawing character for all possible corner styles
>> and line weights, and monospaced legible Arabic for
>> Chris' MUDs.
>
> Not sure what you mean by monospaced, given that Arabic is RTL anyway.
> I mean, when your code is capable of handling all the oddities of
> mixed LTR and RTL text, variable-width characters are almost trivially
> easy to handle. (And yes, I do indeed handle them just fine.)

Monospaced text = each glyph appears in a constant-width
box (the whole thread is about this). Nothing to do with writing
direction.
Both Windows and Linux default console renders monospaced
text only. Unless you use something else, which can render
both monospaced and proportional text, Arabic is
not adequatly presentable there. Eg alef's width is ca 0,2 sheen's width.
So one gets piles of poo instead of normal Arabic text in console.


More information about the Python-list mailing list