Bug 134757 - bterm does not able to use vi and less in UTF-8
Summary: bterm does not able to use vi and less in UTF-8
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: bogl   
(Show other bugs)
Version: 3.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-06 04:53 UTC by Leon Ho
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-06 16:22:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Leon Ho 2004-10-06 04:53:02 UTC
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:

Steps to Reproduce:
1. bterm
2. less unicode.txt
Actual results:
cannot able to read the txt

Expected results:
should able to read the txt

Additional info:

Comment 1 Leon Ho 2004-10-06 04:56:20 UTC
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?

Comment 2 Akira TAGOH 2004-10-06 07:34:02 UTC
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.


Comment 3 Akira TAGOH 2004-10-06 08:26:13 UTC
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.

Comment 4 Jeremy Katz 2004-10-06 16:22:06 UTC
bterm is utf8 *only*.  There's no way around that (and kon is also
definitely i386 specific since it depends on real mode)

Note You need to log in before you can comment on or make changes to this bug.