Bug 2188765 - Chinese text in Java GUI apps is displayed as squares in the default install of Fedora 38.
Summary: Chinese text in Java GUI apps is displayed as squares in the default install ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: java-17-openjdk
Version: 38
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: jiri vanek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-22 04:29 UTC by Daniel
Modified: 2024-05-21 14:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:41:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Demo of the problem in a fresh VM. (348.39 KB, image/jpeg)
2023-04-22 04:39 UTC, Daniel
no flags Details
Demo of the package swap fix. (263.06 KB, image/jpeg)
2023-04-22 04:43 UTC, Daniel
no flags Details

Description Daniel 2023-04-22 04:29:49 UTC
When you input Chinese text using IBUS "Chinese - Intelligent Pinyin" (traditional) into a Java GUI program, it is rendered as squares as if a font is missing. This worked in Fedora 37. Upgraded to 38 this evening and discovered the squares.

Reproducible: Always

Steps to Reproduce:
1. Boot Fedora 38's Cinnamon spin in a VM.
2. Install `java-17-openjdk`
3. Launch any Java program that allows text input. Any hello world JSwing demo will work. JDownloader's settings has some text inputs that also show this.
Actual Results:  
Both in a toy utility and JDownloader the Chinese shows up as squares while you can see the actual Chinese characters in libpinyin's selection.

Expected Results:  
The Chinese shows up in the Java and libpinyin.

The following dnf commands will make it render again and solve the problem.

dnf install google-noto-sans-cjk-fonts.noarch --allowerasing
dnf install google-noto-sans-cjk-ttc-fonts

Both packages must be installed. If only the fonts but not ttc package is installed, the Chinese is rendered in Java but is now squares in the libpinyin input. Libpinyin appears to need the ttc fonts.

It appears something is missing from the new google-noto-sans-cjk-vf-fonts.noarch package that supercedes the above.

Comment 1 Daniel 2023-04-22 04:39:56 UTC
Created attachment 1959019 [details]
Demo of the problem in a fresh VM.

Comment 2 Daniel 2023-04-22 04:43:24 UTC
Created attachment 1959020 [details]
Demo of the package swap fix.

Comment 3 Aoife Moloney 2024-05-07 16:09:25 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2024-05-21 14:41:34 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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