Bug 179630 - tcsh(1): nls catalog file has wrong character code(ja_JP.eucJP)
Summary: tcsh(1): nls catalog file has wrong character code(ja_JP.eucJP)
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 8.4-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Dmitry Chagin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-17 08:40 UTC by YOSHIHARU ITO
Modified: 2021-03-16 06:33 UTC (History)
1 user (show)

See Also:

Attachments
tcsh-20130701.diff (974 bytes, patch)
2013-07-15 19:24 UTC, aono 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description YOSHIHARU ITO 2013-06-17 08:40:00 UTC 
/usr/share/nls/ja_JP.eucJP/tcsh.cat should be the EUC-JP, but it is in UTF-8.

Fix: 

1. move /usr/share/nls/ja_JP.eucJP/tcsh.cat to /usr/share/nls/ja_JP.UTF-8/tcsh.cat.
2. re-generate catalog file in EUC-JP, if possible.
How-To-Repeat: 1. set to ja_JP.eucJP the shell variable LANG.
2. character code setting of the terminal to EUC-JP.
3. generate an error as blow.

% q [return]

get garbled text.
Comment 1 aono 2013-07-15 19:24:01 UTC 
Since tcsh upgrade to 6.18.01 (r231990), it seems NLS catalog files are
written in UTF-8.
(ex. 
http://svnweb.freebsd.org/base/head/contrib/tcsh/nls/ja/charset?r1=155833&r2=231990)
But bin/tcsh/Makefile does not follow this change, so spotted behavior
occurs. Installing libiconv (by ports) would be a workaround, because
tcsh use it to convert charset of catalog.

Attached file is concept patch for 8/9/HEAD to install Japanese
(and Russian (cf. bin/179488)) catalog file to correct directory
(locale). Probably same change for other locale (some_LOCALE.charset ->
some_LOCALE.UTF-8) will be needed. Also corresponding change for port
tcsh-nls is needed.
Comment 2 Dmitry Chagin freebsd_committer freebsd_triage 2017-04-01 15:44:04 UTC 
take it
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:47:47 UTC 
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 4 Dmitry Chagin freebsd_committer freebsd_triage 2021-03-16 06:33:07 UTC 
Fixed by ume@ by r295204 (e4b59b10f8aebe45f87939a9703638f4130908c0)