Bug 2218729 - After upgrading to FC38, Xterm no longer displays Japanese correctly.
Summary: After upgrading to FC38, Xterm no longer displays Japanese correctly.
Keywords:
Status: CLOSED DUPLICATE of bug 2216908
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:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-30 03:10 UTC by Mark Fassler
Modified: 2023-07-07 11:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-07 11:14:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Mark Fassler 2023-06-30 03:10:09 UTC 
I have a fresh install of FC38, and also an upgraded install of FC38.  On both systems, Japanese no longer displays in xterm.  It works fine in XFce-Terminal.  It used to work fine in FC37 and before.

Reproducible: Always

Steps to Reproduce:
1.Copy and paste some UTF-8 Japanese characters into xterm.  For example:

日本語   ¯\_(ツ)_/¯

Actual Results:  
In xterm, the UTF-8 symbols are displayed as blocks.  

Expected Results:  
In XFce-Terminal, the characters are displayed correctly.  In FC37 xterm, the characters were displayed correctly.
Comment 1 Mark Fassler 2023-06-30 03:59:40 UTC 
Building from source, xterm version 381 fixes the problem.
Comment 2 Mark Fassler 2023-06-30 04:04:50 UTC 
oops.  Looks like xterm version 382 is necessary.
Comment 3 Thomas E. Dickey 2023-06-30 07:27:20 UTC 
https://invisible-island.net/xterm/xterm.log.html#xterm_382

amend xtermDrawString, fixing regression with --disable-wide-chars configuration from patch #380.

(however I'm told there's a remaining issue with bitmap fonts, which will be fixed in #384).
Comment 4 Tomas Korbar 2023-07-07 11:14:27 UTC 
Hi,
Thanks for reporting this. I will close this bug as a duplicate,
because we already have one for this issue.

*** This bug has been marked as a duplicate of bug 2216908 ***
Note You need to log in before you can comment on or make changes to this bug.