Bug 2216908 - xterm-380 breaks default rendering of Japanese widechars
Summary: xterm-380 breaks default rendering of Japanese widechars
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xterm
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomas Korbar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2218729 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-23 07:22 UTC by Jens Petersen
Modified: 2023-07-20 05:24 UTC (History)
5 users (show)

Fixed In Version: xterm-383-1.fc37 xterm-384-1.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-11 01:35:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2023-06-23 07:22:52 UTC
It would be good to rebase xterm in F38 to a newer version.
Rendering Japanese is currently broken by default in F38 xterm-380.

It seems fixed in xterm-382 in Rawhide.

Reproducible: Always

Steps to Reproduce:
1. xterm
2. LANG=ja_JP.utf8 date

Actual Results:  
Dashed boxes appear in place of widechars

Expected Results:  
Japanese characters to render by default like with xterm-379.

Comment 1 Thomas E. Dickey 2023-06-23 07:35:39 UTC
agreed (simple bug, simple fix).

There's a packaging glitch however - you may want 383

xterm-383 will be along in a few days, when documentation is done.

The main change in 383 is that it adds a new mode to accommodate
any users of the revised mode 45, for which see

   https://bugzilla.redhat.com/show_bug.cgi?id=2182357

Documenting and work on esctest also found a few minor bugs to fix.

Comment 2 Tomas Korbar 2023-07-07 11:14:27 UTC
*** Bug 2218729 has been marked as a duplicate of this bug. ***

Comment 3 Fedora Update System 2023-07-07 11:59:29 UTC
FEDORA-2023-a9f50af979 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a9f50af979

Comment 4 Fedora Update System 2023-07-07 12:09:49 UTC
FEDORA-2023-c4cd0c9e2d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c4cd0c9e2d

Comment 5 Fedora Update System 2023-07-08 01:25:57 UTC
FEDORA-2023-a9f50af979 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a9f50af979`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a9f50af979

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-07-08 02:05:05 UTC
FEDORA-2023-c4cd0c9e2d has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c4cd0c9e2d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c4cd0c9e2d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2023-07-11 01:35:13 UTC
FEDORA-2023-c4cd0c9e2d has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-07-12 02:11:57 UTC
FEDORA-2023-4378a55eec has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-4378a55eec`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4378a55eec

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2023-07-20 05:24:35 UTC
FEDORA-2023-4378a55eec has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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