Re: less & composing characters - fix

[Nadim Shaikli <shaikli at yahoo dot com>]

--- Behdad Esfahbod <behdad at cs dot toronto dot edu> wrote:
>   * Most important one is that we don't know how a bidi-enabled
> terminal should act.  Should it make ligatures or not?  Should it
> only make LA ligature or some optional ones?  A solution is to
> make a double-width LA ligature.

Not sure what you mean by "don't know how terminals should act".
We should move away from exceptions as fast as we possibly can
and it seems rather logical to treat the LAA ligature in the same
manner that we treat harakat (ie. fatha, etc) - ie. they should not
take-up any visual room (we should be as close to the WYSIWYG idea
as possible).

>   * About Non-Spacing Marks like Fatha it makes more sense.  But
> again, the problem is that:  Terminals like xterm and probably
> mlterm, put the mark on top of the character, so no width
> allocated for the mark.  But what we're gonna do in Linux
> console?  There (as done by BiCon now), a non-spacing mark still
> occupies a single width.  So how's less gonna handle this case?

Sounds like we need to solve it in BiCon for it to function like
it will on xterm (and does on mlterm).

Salam.

 - Nadim


__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools