[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] Bug#822958: ANN: lynx2.8.9dev.9

From: Thomas Dickey
Subject: Re: [Lynx-dev] Bug#822958: ANN: lynx2.8.9dev.9
Date: Sat, 30 Apr 2016 20:42:25 -0400 (EDT)

----- Original Message -----
| From: "Vincent Lefevre" <address@hidden>
| To: address@hidden, address@hidden
| Sent: Saturday, April 30, 2016 8:33:37 PM
| Subject: Bug#822958: [Lynx-dev] ANN: lynx2.8.9dev.9
| Hi,
| On 2016-04-30 17:22:26 +0200, Axel Beckert wrote:
| > Thomas Dickey wrote:
| > > If someone sees it "working" in some version, that is accidental
| > > (i.e., a bug), since neither ncurses nor slang actually support
| > > bidi
| > > in the sense that they know what's on the screen between the
| > > (zero-width!) markers.
| > 
| > Ok, marking as "wontfix" then.
| OK, interesting information. If I understand correctly, all ncurses
| based applications should filter out these bidi marks.

ncurses doesn't actually know anything about the BIDI marks.

It only knows about characters that are printable (or not), and the widths of 
If the C runtime claims that a BIDI mark is printable, ncurses will (try to) 
print it.
If it says it's not printable, ncurses will either treat it as a control 
character (and "render" it),
or it will treat it as part of a combining character.

(I'll do some investigation and see what holes might exist).

Thomas E. Dickey <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]