Korean (CJK) characters show as boxes (□) on macOS Apple Silicon in ReadyAPI 4.x

Hi,

After upgrading from ReadyAPI 3.66.0 to the 4.x line on macOS (Apple Silicon), all Korean characters in the UI render as empty boxes (□, "tofu"). This affects test suite / test case / project names in the Navigator tree and the Test Cases list. Latin characters display fine. The same projects show Korean perfectly in 3.66.0, so the project data is intact — this is a UI font-rendering issue, not encoding or data corruption.

It is reproducible on every 4.x version I have tried: 4.0.1, and still present after updating to 4.2.0 today. Rolling back to 3.66.0 is currently the only way to restore correct display.

Environment

• ReadyAPI 4.0.1 (build 1) and 4.2.0 — both affected
• macOS on Apple Silicon (aarch64)
• Bundled JRE and JavaFX 21 (mac-aarch64) shipped inside the app bundle
• Same projects display correctly in ReadyAPI 3.66.0 on the same machine

Steps to reproduce

1. Open a project whose suite / case / project names contain Korean characters in 3.66.0 (displays correctly).
2. Open the same project in ReadyAPI 4.x (tested on 4.0.1 and 4.2.0) on macOS Apple Silicon.
3. All Korean text in the Navigator tree and Test Cases list renders as □. Latin text is fine.

What I have already investigated

• The 4.x UI is rendered with JavaFX 21 (javafx-*-21.0.9-mac-aarch64.jar are present in Contents/Resources/app/lib), so Swing/AWT fontconfig changes have no effect on the affected UI.
• The bundled JRE's fontconfig.properties.src (Contents/Resources/jre.bundle/Contents/Home/lib/) maps Korean fallback fonts to Windows-only fonts — korean=Gulim / Batang (gulim.TTC, batang.TTC), which do not exist on macOS. This looks like a Windows font configuration shipped in a macOS build.
• The following JVM options were tried (via vmoptions.txt and ~/.readyapi/userDefinedVmOptions.vmoptions) with no effect on the boxes:
  • -Dfile.encoding=UTF-8
  • -Dprism.fontdir=/System/Library/Fonts
  • -Dprism.embeddedfonts=true
  • -Dprism.order=sw (software rendering — boxes still present, so not a hardware-pipeline-only issue)
• Adding a custom macOS fontconfig.properties (mapping Korean to AppleSDGothicNeo) in the bundled JRE lib folder also had no effect (expected, since the UI is JavaFX, not Swing).

Impact
The tool is effectively unusable for Korean-language projects on macOS Apple Silicon, since suite/case/project names cannot be read. This has persisted across multiple 4.x releases (4.0.1 → 4.2.0).

Questions

1. Is this a known issue in the 4.x line on Apple Silicon?
2. Is there a supported workaround, or a planned fix?

Since the bundled JavaFX 21 appears to lack a CJK font fallback on macOS aarch64, this looks like it needs a fix in the build's font configuration rather than a user-side setting. I have attached screenshots showing the same project in 3.66.0 (correct) and 4.x (boxes).

Thanks!