Description of problem: From customer: "Although "more" and "cat" can display UNICODE correctly, "vi" and "less" have the problem that UNICODE is not displayed correctly. It seems to be difficult to use bterm as substitution of kon." Version-Release number of selected component (if applicable): How reproducible: everytime Steps to Reproduce: 1. bterm 2. less unicode.txt 3. Actual results: cannot able to read the txt Expected results: should able to read the txt Additional info:
Look like it is because of less and vi in RHEL3 does not support UTF-8. Tagoh-san, can you still able to reproduce it on RHEL4 or RHEL3 with bterm and updated apps?
did you try that on ja_JP.eucJP? at least on RHEL4 (and on ja_JP.UTF-8 locale) vi and less works on bterm. vim-minimal-6.3.028-2 less-382-4 bogl-bterm-0.1.18-2
just talked about it with Fuchi-san. and I understand that the customer wants to see EUC-JP text on the console on EM64T box. unfortunately kon2 which we provided to see Japanese on the console, depends on x86 architecture. so it has been built for i386 only. so they couldn't see EUC-JP text on the console so that the customer was lacking of kon2 on their box. I see the point of view for this bug is to privide the way to see EUC-JP on the console on the architecture except x86.
bterm is utf8 *only*. There's no way around that (and kon is also definitely i386 specific since it depends on real mode)