Re: less & composing characters - fix

[Nadim Shaikli <shaikli at yahoo dot com>]

--- Mark Nudelman <markn at greenwoodsoftware dot com> wrote:
> My apologies -- a stupid bug was ruining all UTF-8 output.
> This one should work better:
>
>   http://www.greenwoodsoftware.com/less/less-385.tar.gz

This version (385) is solid.  I tried a number of things
and all worked without issue.

One minor annoyance.  When I search for LAA via '/'
(LAA is a combined character made up of LAM + AlEF), the
LAM disappears on me (as it should), but instead of seeing
the LAA glyph, I see the ALEF.  So I'm guessing it is an
encoding issue or similar.  In terms of encodings,

  ALEF - 0x0627 -> 0xfe8d or 0xfe8e
  LAM  - 0x0644 -> 0xfedd or 0xfede or 0xfedf or 0xfee0
  LAA  -           0xfefb or 0xfefc

Composing characters (fatha, damma, etc) work without issue
on searches.

BTW: I did see instances where mlterm should not show 2-3
     lines in a file esp. when doing a search and the only
     way to illuminate the highlighted text is to scroll-up
     say 10-12 lines and CTRL-L (redraw).  Not sure if this
     is an mlterm issue or less (same things used to happen
     on 381 for me - I am inclined to think that some control
     characters are not being passed correctly to mlterm
     ("more" doesn't have this problem in the least)).

Thanks & Regards,

 - Nadim



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