Bug 164165 - Combining enclosing keycap is not displayed correctly
Summary: Combining enclosing keycap is not displayed correctly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, regression
Depends on:
Blocks: Font-Rendering
  Show dependency tree / graph
 
Reported: 2024-12-04 16:13 UTC by vfel
Modified: 2024-12-10 09:20 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
File to reproduce the issue (23.23 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2024-12-04 16:14 UTC, vfel 		Details
Actual Display of the text in Writer (3.17 KB, image/png)
2024-12-04 16:14 UTC, vfel 		Details
Expected Display of the text (ms-Word) (2.44 KB, image/png)
2024-12-04 16:15 UTC, vfel 		Details
screenshot (90.73 KB, image/png)
2024-12-05 05:42 UTC, BogdanB 		Details
Commit log of bibisected range (96.14 KB, text/plain)
2024-12-10 09:19 UTC, Buovjaga 		Details
List of hashes from bisect (13.73 KB, text/plain)
2024-12-10 09:20 UTC, Buovjaga 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vfel 2024-12-04 16:13:05 UTC 
Description:
The Combining enclosing keycap (Unicode: U+20E3) used in text ist not displayed correct. It's spacing is off so that it is overlapping with the text next to it. Also it is not displayed at all, if it is bold.
The problem seems to be related to the used font. I found the problem in Sgeoe UI, while Arial seems to work.
The sample file was created using MS-Word.

Steps to Reproduce:
1. Create a document in MS-Word
2. Insert a text using Combining enclosing keycap
3. Change the font to Segoe UI
4. Open the document in LibreOffice Writer

Actual Results:
Actual (LibreOffice Writer).png

Expected Results:
Expected (MS-Word).png


Reproducible: Always


User Profile Reset: Yes

Additional Info:
The file I used for testing is also attached.
Comment 1 vfel 2024-12-04 16:14:09 UTC 
Created attachment 197934 [details]
File to reproduce the issue
Comment 2 vfel 2024-12-04 16:14:48 UTC 
Created attachment 197935 [details]
Actual Display of the text in Writer
Comment 3 vfel 2024-12-04 16:15:17 UTC 
Created attachment 197936 [details]
Expected Display of the text (ms-Word)
Comment 4 Aryeh 2024-12-04 22:18:28 UTC 
I tested your attachment, but I was not able to reproduce the bug. LO is showing normal behavior.

Version: 24.8.3.2 (AARCH64) / LibreOffice Community
Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92
CPU threads: 8; OS: macOS 14.5; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 5 BogdanB 2024-12-05 05:42:38 UTC 
Created attachment 197943 [details]
screenshot
Comment 6 BogdanB 2024-12-05 05:43:25 UTC 
Confirm with
Version: 24.8.3.2 (X86_64) / LibreOffice Community
Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92
CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 7 Buovjaga 2024-12-10 09:19:43 UTC 
Created attachment 198035 [details]
Commit log of bibisected range

Bibisected with win32-4.3, but it threw up a range. The hashes don't seem to be in order, so I won't link to a Gitiles range query. Instead, I'm attaching the source commit log and a list of hashes as separate text files.

I used Windows because it comes with Segoe UI font. On Linux with a substituted font it looked bad even in the oldest of the 4.3 bibisect repo.
Comment 8 Buovjaga 2024-12-10 09:20:15 UTC 
Created attachment 198038 [details]
List of hashes from bisect