Bug 157029 - Korean Font in UI is mismatched on English version of Windows & LibreOffice
Summary: Korean Font in UI is mismatched on English version of Windows & LibreOffice
Status: ASSIGNED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.5.5.2 release
Hardware: All Windows (All)
: medium minor
Assignee: DaeHyun Sung
URL:
Whiteboard: target:25.2.0
Keywords:
Depends on: CJK-Korean
Blocks: Desktop-Integration
  Show dependency treegraph
 
Reported: 2023-08-31 00:39 UTC by baesoft777
Modified: 2024-11-13 19:30 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Korean font is mismatched (20.57 KB, image/png)
2023-08-31 00:41 UTC, baesoft777
Details
Example of Malgun Gothic font on Windows11 (123.45 KB, image/png)
2023-09-30 14:54 UTC, DaeHyun Sung
Details
Example of Gulim font on Windows11 (85.29 KB, image/png)
2023-09-30 15:02 UTC, DaeHyun Sung
Details
After modified the VCL.xcu, I can show LibreOffice UI and tooltip with appropriate Korean font (50.27 KB, image/png)
2023-10-02 12:16 UTC, DaeHyun Sung
Details

Note You need to log in before you can comment on or make changes to this bug.
Description baesoft777 2023-08-31 00:39:39 UTC
Description:
Font is mismatched on English of Windows & LibreOffice. Default font set by Windows is "Malgun Gothic (맑은 고딕)", but UI Font of LibreOffice is something else.

Steps to Reproduce:
1. Install English Version of Libreoffice on English Version of Windows
2. Install several 3rd party Korean-focused Fonts
(Ex. Noto Sans KR, NanumGothic(나눔 고딕))
3. Enable Korean Input, save document to Korean

1. 영문 버전의 Windows에서 LibreOffice 영문판을 설치합니다.
2. 한글 폰트를 설치합니다. (예. Noto Sans KR, 나눔고딕)
3. 한국어 입력기를 활성화하고, 한글로 문서를 저장합니다.

Actual Results:
Font is mismatched. Default font set by Windows is "Malgun Gothic (맑은 고딕)", but UI Font of LibreOffice is something else.

UI 폰트가 다릅니다. Windows에서 기본으로 지정한 폰트는 맑은 고딕이지만, LibreOffice에서는 맑은 고딕이 아닌 다른 폰트를 사용합니다.

Expected Results:
Set default Korean font on UI to "Malgun Gothic(맑은 고딕)"

한글을 표시하는 UI 폰트를 맑은 고딕으로 지정해야 할 것 같습니다.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.5.2 (X86_64) / LibreOffice Community
Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e
CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 1 baesoft777 2023-08-31 00:41:25 UTC
Created attachment 189272 [details]
Korean font is mismatched
Comment 2 Julien Nabet 2023-08-31 06:42:02 UTC
DaeHyun: thought you might be interested in this one since it concerns Korean UI.
Comment 3 Stéphane Guillou (stragu) 2023-09-29 15:21:57 UTC
Can you please also include a screenshot of what the font looks like elsewhere on Windows, for comparison?
Thank you!
Comment 4 DaeHyun Sung 2023-09-30 10:46:43 UTC
In my opinion, LibreOffice on Windows can't read the current Windows Korean version's default font "맑은 고딕(English Name: Malgun Gothic)".
"맑은 고딕(English Name: Malgun Gothic)" font has been introduced and applied since Windows Vista.

(In reply to baesoft777 from comment #1)
> Created attachment 189272 [details]
> Korean font is mismatched

Because the former Windows Korean font is "Gulim". 
The screenshot's default font use "Gulim" font.

So, LibreOffice Korean users, need to set "Malgun Gothic" for Windows users.
(ps. Mac OS's Korean default font is "Apple SD Gothic Neo".
Comment 5 DaeHyun Sung 2023-09-30 10:54:04 UTC
In my opinion, 
https://git.libreoffice.org/core/+/refs/heads/master/officecfg/registry/data/org/openoffice/VCL.xcu#427

In my opinion, SANS_UNICODE's font prioritization should be changed.
Comment 6 DaeHyun Sung 2023-09-30 14:54:26 UTC
Created attachment 189908 [details]
Example of Malgun Gothic font on Windows11

Example of Malgun Gothic font on Windows11
Comment 7 DaeHyun Sung 2023-09-30 15:02:30 UTC
Created attachment 189909 [details]
Example of Gulim font on Windows11

Example of Gulim font on Windows11.
In my opinion, LibreOffice's Korean font rendering looks like 'bolded' gulim font.
Comment 8 Ming Hua 2023-09-30 15:45:34 UTC
(In reply to DaeHyun Sung from comment #5)
> In my opinion, 
> https://git.libreoffice.org/core/+/refs/heads/master/officecfg/registry/data/
> org/openoffice/VCL.xcu#427
> 
> In my opinion, SANS_UNICODE's font prioritization should be changed.
The font lists like SANS_UNICODE can be changed by the user, via expert configuration.

As you are the Korean expert here, I suggest you just tweak with the list and find the correct font name(s).

Maybe also try the CJK_DISPLAY and UI_SANS lists. And as the bug reporter was using an English locale, you may also want to change the font lists for "en" setting.
Comment 9 DaeHyun Sung 2023-10-02 12:16:25 UTC
Created attachment 189948 [details]
After modified the VCL.xcu, I can show LibreOffice UI and tooltip with appropriate Korean font

(In reply to DaeHyun Sung from comment #5)
> In my opinion, 
> https://git.libreoffice.org/core/+/refs/heads/master/officecfg/registry/data/
> org/openoffice/VCL.xcu#427
> 
> In my opinion, SANS_UNICODE's font prioritization should be changed.


I changed some Korean font list priority such as "SANS_UNICODE" on VCL.xcu

https://git.libreoffice.org/core/+/refs/heads/master/officecfg/registry/data/org/openoffice/VCL.xcu#427

After modified the VCL.xcu, I can show LibreOffice UI and tooltip with appropriate Korean font on Windows.
Comment 10 DaeHyun Sung 2023-10-03 07:53:03 UTC
I submitted the fixed source code https://gerrit.libreoffice.org/c/core/+/157494 .

I checked it on Windows, Mac M1, Linux.

Please, check & review it.
Comment 11 Commit Notification 2024-09-05 17:39:55 UTC
DaeHyun Sung committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/e830f2a041271f4af65dabb2d8c0968b7f3bac6e

tdf#157029 changed Korean Font priority for LibreOffice UI

It will be available in 25.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 12 Buovjaga 2024-11-13 19:30:44 UTC
DaeHyun: feel free to close as fixed.