Bug 76908 - initscripts causes tcsh BROKEN for CJK
initscripts causes tcsh BROKEN for CJK
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
8.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-29 04:09 EST by Nakai
Modified: 2014-03-16 22:32 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-29 04:09:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nakai 2002-10-29 04:09:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.0.1) Gecko/20020830

Description of problem:
There is bugs in /etc/profile.d/lang.csh, it sucks
tcsh behavior in CJK environment.

- Spell mistake - Not dspmpbyte, dspmbyte is correct.
  ( man tcsh )
- dspmbyte=euc works only for Japanese language.
  (But works for ko_KR.eucKR becase multibyte code point
   is as same as ja_JP.eucJP)
- Lack of UTF-8 recognition

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. See /etc/profile.d/lang.csh
2.
3.
	

Additional info:

--- initscripts-6.95/lang.csh.orig      2002-10-29 17:53:37.000000000 +0900
+++ initscripts-6.95/lang.csh   2002-10-29 17:56:53.000000000 +0900
@@ -85,10 +85,18 @@
 
 if ($?LANG) then
     switch ($LANG)
+       case ja*UTF-8:
+       case ko*UTF-8:
+       case zh*UTF-8:
+            set dspmbyte=utf8
+            breaksw
+       case zh_TW*:
+            set dspmbyte=big5
+            breaksw
        case ja*:
-       case zh*:
        case ko*:
-            set dspmpbyte=euc
+       case zh*:
+            set dspmbyte=euc
             breaksw
     endsw
 endif
Comment 1 Bill Nottingham 2002-11-12 00:02:11 EST
Fixed in CVS, will be in 6.96-1

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