Bug 2218729

Summary:	After upgrading to FC38, Xterm no longer displays Japanese correctly.
Product:	[Fedora] Fedora	Reporter:	Mark Fassler <spin.interrupt>
Component:	xterm	Assignee:	Tomas Korbar <tkorbar>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	38	CC:	dickey, tkorbar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-07 11:14:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***