On Thu, Mar 17, 2016 at 12:00:47AM -0600, Anthony J. Bentley wrote: > YASUOKA Masahiko writes: > > Hi, > > > > ok? > > > > Fix jless not to crash when it starts running. Diff from Akira Kato. > > This does fix the amd64 crash for me. > > I'm concerned about this port, though. It's an unmaintained ISO-2022 > patchset on top of less-332, which was released in *1997*. The patches > no longer exist except on our mirrors. Have there been any > vulnerabilities in less in the past 19 years? Do the patches introduce > any? > > It seems like it might be worthwhile for jless users to alias it to > "iconv -f iso-2022-jp -t utf-8 | less", and see if it acts as a > reasonable approximation. > > I'm very concerned about keeping such an old, unmaintained fork in > our tree, when the original software has since grown its own support > for Japanese. I have similar concerns about kterm (1996 xterm), > jvim (1996 vim), ja-groff (1995 groff), hanterm-xf (2003 xterm)...
I don't know. Japanese is slightly peculiar, and they sometimes have needs that haven't gotten to the 21st century... keeping a toolchain that works with JIS/SJIS encoding probably makes some sense. Analogy with western countries: we just switched to utf8 by default less than a release ago. before that, a lot of people, me included were still mostly working with iso-8859-*
