tags 217519 fixed-upstream
thanks

On Sun, Oct 26, 2003 at 05:51:08PM +0900, [EMAIL PROTECTED] wrote:
> From: Colin Watson <[EMAIL PROTECTED]>
> > /usr/bin/pager on your system appears to point to less. less does not
> > understand LESSCHARSET=nippon (provided so that jless works), and fails.

(I meant LESSCHARSET=ja here.)

> > I recommend using a pager such as jless or lv.
> > 
> > May I close this bug, or is there still some other way man could behave?
> > Remember that it can't tell what /usr/bin/pager really is.
> 
> I don't have strong objection to closing Bug#217519.
> 
> I knew setting $PAGER to "more" makes man work. But I also noticed that
> running /usr/bin/pager -s with an ASCII file worked fine. So I
> suspected that man executed /usr/bin/pager -s in an inappropriate way.
> 
> (I always use English manual pages and I didn't think I have to use
> jless to read English manual pages.)
> 
> Does really /usr/bin/man have to set LESSCHARSET? Isn't it better to
> leave LESSCHARSET unchanged? Because it can't tell what /usr/bin/pager
> really is, as you said.

It turns out that there's a separate JLESSCHARSET environment variable
available, so we can set that without interfering with less. I've
belatedly done this for man-db 2.5.2.

Mon May  5 01:39:22 BST 2008  Colin Watson  <[EMAIL PROTECTED]>

        Fix jless support to avoid breaking less (Debian bug #217519).

        * src/encodings.c (less_charset_table): Add jless_charset members.
          Move EUC-JP less_charset to jless_charset, falling back to iso8859
          for less. Use the more explicit japanese-ujis rather than ja.
        * src/encodings.c (get_jless_charset): New function.
        * src/encodings.h (get_jless_charset): Add prototype.
        * src/man.c (make_roff_command): Set JLESSCHARSET to the return
          value of get_jless_charset if non-NULL.

Cheers,

-- 
Colin Watson                                       [EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to