Red Hat Bugzilla – Bug 103493
less.sh/less.csh should not set JLESSCHARSET for UTF-8 locales
Last modified: 2017-02-23 14:19:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
Description of problem:
I use ko_KR.UTF-8 locale and found that all Korean characters were turned by
less to '&&&' after upgrading to RH 9.0. It turned out that
/etc/profile.d/less.sh set JLESSCHARSET to 'ko' for any ko* locale. I changed
the script not to set it if I'm running in UTF-8 locale and it works fine. A
similar fix is necessary for /etc/profile.d/less.csh
I don't know whether RH 9.0 supports UTF-8 locales for CJK. I had used my own
CJK locales for RH 8.0 before upgrading to RH 9.0 and I didn't bother to check
if RH 9.0 came with CJK UTF-8 locales. If it still uses legacy codeset t for
CJK, it's very much disappointing. Anyway, in that case, this bug would be invalid.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.set LC_ALL to ko_KR.UTF-8 or ja_JP.UTF-8
2.spawn a new shell or a new terminal
3.try to view any UTF-8 files (with non-ASCII characters)
Actual Results: All non-ascii characters are turned to &'s
Expected Results: Non-ascii characters should be displayed
see also bug 88868 comment #5
The current less.[c]sh files parse the LC_ALL and LANG variables differently
Does it check LC_CTYPE as well? It has to.
This works for me with the current less.
libreoffice-188.8.131.52-7.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3453b4764a
libreoffice-184.108.40.206-7.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3453b4764a
libreoffice-220.127.116.11-7.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.